If your problem is to use jaxb on JDK 1.4, you should take a look at using jaxb2 + retrotranslator. There is some special flags to set when generating the jaxb2 pojos so that all the needed informations are kept under JDK 1.4, but I should work.
On 4/5/07, Reshat Sabiq <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Reshat Sabiq > Sent: Wednesday, April 04, 2007 2:26 PM > To: [email protected] > Subject: [xfire-dev] Adding JAXB 1 support to WsGen > > Folks, I think it's a pity, well actually a disaster, that WsGen > doesn't support JAXB 1, while JAXB 1 binding is supported on the way > from java to schema. > > I am able to spend several hours on this, and would like to give it a > shot to add JAXB 1 support to WsGen. I'd appreciate any tips on this. > I am guessing it involves calling xjc and should not be rocket science > per se. > > P.S. Alternatively, any feedback on how to bind an enum emulation > class in java to XML Schema enum w/o using Java 5 would be > appreciated. Based on what I know, I don't believe that's possible > using JAXB 1 from java to schema, given that there is no xjc-related > step involved. Could somebody give me some feedback on this. Does WsGen always generate annotated code? For instance, if the code is updated to use JAXB 1 JaxbTypeRegistry, would that enable the rest of it to generate JAXB 1 stubs, or is the rest hard-wired for annotations, something else from Java 5? Thanks. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
