Errors/Warning compiling a WSDL file - but the generated Java sources are ok #243
Comments
|
Please try to add the WSDL option as the error message indicates see this example: https://github.com/highsource/maven-jaxb2-plugin/tree/master/tests/wsdl |
|
Thanks for your response. This has already been confgured in the first line of the section. Switching over to the way to configure does unfortunately not change anything. As in the other cases, the sources are correctly generated. I have found older issue having the same warning noted: #96 (comment) Maybe an additional parameter "-wsdl" must be set when invoking xjc for WSDL-files? As everything works, the issue is not that important but it is a little bit annoying. |
|
I have the exact same issue, and my configuration is identical to that of @weberhofer. |
|
I have a similar error after upgrading from 0.14.0 to 0.15.1 Error message: pom.xml <plugin>
<groupId>org.jvnet.jaxb2.maven2</groupId>
<artifactId>maven-jaxb2-plugin</artifactId>
<version>0.15.1</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
<configuration>
<schemaLanguage>WSDL</schemaLanguage>
<generatePackage>com.example.generated</generatePackage>
<schemaDirectory>src/main/resources/cas</schemaDirectory>
<schemaIncludes>
<include>*.wsdl</include>
</schemaIncludes>
</configuration>
</plugin> |
|
I'll take a look at it this weekend. Seems odd since the root of the stack trace is the xjc layer. |
|
Hi, any update here? |
|
I'm facing the same issue when upgrading to version |
|
I'm facing the same issue when upgrading to version 0.15.1 with java 17 and spring boot 2.7.2 |
|
Any news with it? My configuration is similar to others on JDK 17 |
|
I've noticed the same exception but all the sources were generated on JDK 17. |
|
I am also experiencing this exception on JDK 17. But It looks like it has no effect. |
|
I am also experiencing this exception with JDK 17 and Spring boot 2.7: |
|
+1 |
|
I got the same issue, I've decided to use the 0.14.0 instead..... |
|
+1 with JDK17 and 0.15.2 <plugin>
<groupId>org.jvnet.jaxb2.maven2</groupId>
<artifactId>maven-jaxb2-plugin</artifactId>
<version>0.15.2</version>
<configuration>
<verbose>true</verbose>
<forceRegenerate>${maven-jaxb2-plugin.forceRegenerate}</forceRegenerate>
<removeOldOutput>false</removeOldOutput>
</configuration>
<executions>
<execution>
<id>generate-wsdl</id>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<schemaLanguage>WSDL</schemaLanguage>
<schemaDirectory>${project.basedir}/src/main/resources/wsdl</schemaDirectory>
<schemaIncludes>
<include>*.wsdl</include>
</schemaIncludes>
<generateDirectory>${project.build.directory}/generated-sources/</generateDirectory>
<locale>en</locale>
</configuration>
</execution>
<execution>
<id>generate-camt-xsd</id>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<schemaDirectory>${project.basedir}/src/main/resources/camt</schemaDirectory>
<schemaIncludes>
<include>*.xsd</include>
</schemaIncludes>
<generateDirectory>${project.build.directory}/generated-sources/</generateDirectory>
<locale>en</locale>
</configuration>
</execution>
</executions>
</plugin>Error: I downgraded to 0.14.0 and specified the jaxb dependency to make it work: <plugin>
<groupId>org.jvnet.jaxb2.maven2</groupId>
<artifactId>maven-jaxb2-plugin</artifactId>
<version>0.14.0</version>
<configuration>
...
</configuration>
<executions>
...
</executions>
<dependencies>
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>2.3.5</version>
</dependency>
</dependencies>
</plugin> |
|
Any update on this? I am facing same issue with Java 19 Jaxb 3.0 |
-XtoString
Do you find any solution for this issue? |
Any Solution do you find? I am also facing same issue |
|
Hi everyone. There's nothing (in my opinion) we can do to get rid of this message (it's just a warning for 'experimental' features that still exists in v4 of xjc, with more generation warning about rng / rnc files) and classes should be just generated fine. |
|
@weberhofer / @yanivnahoum / @dhpalan / @lepus / @DeepanshuRastogi1 / @funnybobde / @Grogdunn / @gadton / @Ikrao / @jbrechbuehl / @ielkhalloufi : do you confirm that classes are well generated ? |
|
@laurentschoelens I can confirm, classes are well generated. |
|
@laurentschoelens I can also confirm that the classes are generated correctly. |
|
Thanks @lepus and @DeepanshuRastogi1 |
|
@laurentschoelens I confirm that classes are well generated. |
|
Found this issue in jaxb-ri impl that was treated in main : eclipse-ee4j/jaxb-ri#1701 |
|
Just wanted to +1 this - even though the classes are still generated successfully, having such an error message in our build logs is extremely alarming and is going to raise flags and have to be explained any time a new person joins our team and sees it for the first time. To the point that we're strongly considering reverting to 0.14.0 just to avoid this message. I'll add a comment on the jaxb-ri issue as well, but if there's any way you can modify the library versions you're using under the hood in this plugin to eliminate this bogus message, it would be appreciated. :) |
|
You can still override the dependency of jaxb-ri in the plugin used by adding the dependencies section but the result won't be guaranteed since untested and some bugs had been fixed with upgraded version of jaxb-ri |
|
@aprevost : Lukas is currenlty backporting some fixes into jaxb 2.3.X branch |
|
Thanks for the update @laurentschoelens. As an FYI, we have in fact reverted to 0.14.0 to eliminate the logs, so we are waiting on this fix before we upgrade back to the latest again. :) |
|
@aprevost : if you want to go to the 2.0.9 version jaxb-tools without waiting for 2.0.10 (which will get the fix from jaxb-ri by upgrading to 2.3.9) you can do the following :
We are currently working on 4.0.1 version (it should be out by the end of the year) and then go back to 2.0.10 with backports. |
|
Hi, I have the same issue with this package maven-jaxb2-plugin:0.15.3 when I migrated to java 17. What was solution? |
|
Hi @lenaalex This is only a warning (with stacktrace but still a warning) and can be safely ignored by the way. Please also look at migration guide to get the latest 2.x version |
|
@laurentschoelens I dont quite understand what do u mean? Do I have to upgrade here see photo? Which version of spring boot do I have to use with jaxb-tools and jdk17? |
|
Are you targeting JAXB 2.3 ? Which version of SpringBoot do you want to use ? Depending of your answer, I'll help you the right way |
|
I would like to use spring boot 3.x.x. with java 17 or 21. When I used maven-jaxb2-plugin.version 0.13.3, classes generated not quite correct and after increased to 0.15.3, I am getting this error. I am really need help from person who knows this package well :-) |
|
Ok so for SB3, you'll need to go to jaxb-maven-plugin 4.x which already contains the fix. This would be the plugin configuration : <plugin>
<groupId>org.jvnet.jaxb</groupId>
<artifactId>jaxb-maven-plugin</artifactId>
<version>4.0.3</version> <!-- latest current available version for JakartaEE10 -->
<executions>
<execution>
<id>generate</id>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
<configuration>
<extension>true</extension>
<args>
<arg>-wsdl</arg>
<arg>-Xfluent-api</arg> <!-- see https://github.com/highsource/jaxb-tools/wiki/JAXB2-Fluent-API-Plugin -->
</args>
<plugins>
<plugin>
<groupId>org.jvnet.jaxb</groupId>
<artifactId>jaxb-plugins</artifactId>
<version>4.0.3</version> <!-- same as maven-plugin version -->
</plugin>
</plugins>
<schemaDirectory>${project.basedir}/src/main/resources/wsdl</schemaDirectory>
<schemaIncludes>
<include>*.wsdl</include>
</schemaIncludes>
</configuration>
</plugin>
|
|
The plugin is compatible with JDK17 and JDK21 by the way 😉 |
|
Thanks a lot :-) It works now! |
|
@weberhofer / @yanivnahoum / @dhpalan / @lepus / @DeepanshuRastogi1 / @funnybobde / @Grogdunn / @gadton / @Ikrao / @jbrechbuehl / @ielkhalloufi / @aprevost : sorry for the spam 😄 This was fixed in Will also be fixed in v2.0.10 |
|
Will be closed in next v2.x release. Fixed by #437 |
First: Thanks for all the new contributions to the project!
I have tried to update a project which creates java sources from a WSDL. Unfortunately I see the following exception on invoking the compiler:
The exception asks something like "Do you try to compile WSDL? Support for WSDL is for test purposes. You can activate it with the option -wsdl.
With version 0.14.0 everything was working without that message. However, the tool creates the Java-Codes as expected!
The relevant section in my pom.xml is:
The text was updated successfully, but these errors were encountered: