Deprecated warnings while using XMLBeans

Question

Greetings,
Using XMLBeans Builder in WorkShop 9.2 raises hundreds of deprecated warnings. It seems that the XMLBeans Builder generated code doesn't compile against ... XMLBeans itself ? It that possible ? Any workaround ?
Many thanks in advance,
Nicolas

Answer 1

Hi Nicolas,
To highlight your issue:
"""...how could I compile, without any warnings, including deprecation
warnings, XMLBeans Builder generated code. After all, as it's name
clearly suggests, an XMLBeans Builder generates code to be compiled
against XMLBeans. It seems very strange that a product which generates
XMLBeans compliant code cannot compile this code without deprecation
warnings."""
I spent some time working with XMLBeans and unfortunately, what you want
(code without deprecation warnings) is actually something to make a
request of from the Apache XmlBeans folks. The code the XMLBeans Builder
generates is not any different from that which the Apache XmlBeans
project would generate when a schema is compiled via the 'scomp' tool.
Here's how you can see the cause of this outside of the Xmlbeans builder
tool or the Workshop IDE
1) go to http://xmlbeans.apache.org and download a binary distribution
2) unzip the binary distribution to a dir on your filesystem
3) copy your xsds to <unzip-dir>\xmlbeans-2.2.20\bin
4) cd to <unzip-dir>\xmlbeans-2.2.20\bin
5) run the following:
scomp -src srcOutputDir *.xsd
This will generate the src files from the xsd (similar to how the
XMLBeans Builder tool would) on your filesystem.
From there, browse to a .java file and view in your favorite text editor.
You'll see that the java code produced from the XMLBeans tool itself
produces code with @deprecated javadoc
e.g,
/** @deprecated {@link XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream
Now to see this in the Workshop IDE, create a new J2EE Utility Project.
Make sure the XmlBeans->XmlBeans library facet is enabled.
Drag the contents of srcOutputDir (from above) to the src directory of
the J2EE Utility Project in the IDE window.
Upon successful rebuild of the srcs in the IDE, you'll be able to see
similar warnings from pure Apache XmlBeans related code.
If you really CANNOT have these deprecation warnings, your best bet may
be to email the Apache XmlBeans mailing list. At the very least they can
probably best explain why the deprecation is still left in the code.
The website for xmlbeans is:
http://xmlbeans.apache.org
and some helpful mailing lists can be found and queried from
http://xmlbeans.apache.org/community/index.html
Hope this helps,
-Jacobd
nicolas duminil wrote:
rfrost,
Many thanks for having taken the time to reply but ... you didn't get me. My point was not to disable compiler's deprecation warnings. I believe that it's very important to be aware that APIs you're using in your code is deprecated. This is certainly the reason which motivated the compiler's creators to provide an option able to signal deprecated calls in the code. Disabling this warnings doesn't provide any benefits, it is just hiding problems and the goal of a compiler is not to hide problems, but to hi
ghlight them. No, my point was simply to ask how could I compile, without any warnings, including deprecation warnings, XMLBeans Builder generated code. After all, as it's name clearly suggests, an XMLBeans Builder generates code to be compiled against XMLBeans. It seems very strange that a product which generates XMLBeans compliant code cannot compile this code without deprecation warnings. That's a big issue because a deprecation warning says to you: "Hey, you're using something you're not supposed to u
se any more". So, many thanks to you for having let me know how to disable compilation warnings, but this was not at all the point. The real point was how to use the XMLBeans Builder in order to generate XMLBeans code free of deprecation warnings. I understand you don't have the answer but, in this case, please don't feel obligated to reply.
Kind regards,
nicolas