Nope. JSR181 also works on client side. Yes, WsGen work only on java 5 ( because of annotations and because jaxb2 works only java 5 ). But you have some options to workaround this : - use retrotranslator to convert generated java 5 client code to java 1.4 code - use xmlbeans as databinding , remove java 5 annotation from generated client and add service xml file to configure factory.
On 4/13/07, Josh <[EMAIL PROTECTED]> wrote:
Gareth, Forgive my ignorance here, which annotations get generated on the client side? I always thought that the JSR 181 annotations only resided on the server side. Am I incorrect? Josh On 4/13/07, Gareth Webbley <[EMAIL PROTECTED]> wrote: > > > I think this is because when you use the generator to generate the client code, the generated code contains annotations which means that in order to compile a client you need Java 5 and the code will not compile with Java 1.4. > > Gareth > > > ________________________________ From: Josh [mailto:[EMAIL PROTECTED] > Sent: 13 April 2007 14:48 > To: [email protected] > Subject: [xfire-user] Re: Does wsgen really have a java 5 limitation > > > > > I am still not sure I understand this. If xFire supports the use of commons-attributes for jsr 181 style services, does this limitation still exist in the generator? Is there any real java 5 limitation? > > -Joshua > > > On 4/12/07, Josh <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > Reading through the documentation, I read the following line: > > > > "The generator Java 5.0 only at this point since it takes advantage of the JSR 181 annotations" > > > > Does this mean that you cannot use the generator if you are using java 1.4 or simply that you cannot use java 5 annotations if you are using java 1.4? > > > > Regards, > > > > Joshua > >
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
