Re: JAX-WS in Axis2
This article on REST invocation might be helpful: http://wso2.org/library/175 For JAX-WS, I believe the main difference here is that you use Sun's tools to do the code generation, not Axis2's; if you use JAX-WS, then by default you are also using JAXB to do the XML binding. More documentation on this is here: https://jax-ws.dev.java.net/. - Original Message - From: "Andrew Clegg" <[EMAIL PROTECTED]> To: Sent: Monday, July 07, 2008 7:07 AM Subject: Re: JAX-WS in Axis2 2008/7/7 Virtual Light <[EMAIL PROTECTED]>: JAX-WS with JAXB bindings is your best bet for compatibility across different SOAP engines. Forget about the wsdl2JAVA that is in Axis2 1.4 and use wsimport(contract first)/wsgen(code first). Both of these are now part of JDK 1.6. Okay... Thanks. From my brief look at wsimport it does seem to produce slightly more readable code than wsdl2java/ADB, and as long as it doesn't choke on any of the data structures in my XSDs I should be fine. (Is there any documentation on that anywhere?) It still seems like there's a bit of an explanatory gulf in the Axis2 manual between the parts that refer to Axis2's own code generation tools and data bindings, and the parts that use the JAX-WS approach... One question. Can a JAX-WS-style service deployed in Axis2 still be accessible via REST the way a conventional Axis2-style service can? Thanks, Andrew. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAX-WS in Axis2
2008/7/7 Virtual Light <[EMAIL PROTECTED]>: > Docs for wsimport > http://www.sws.bfh.ch/~fischli/kurse/ead/jws/jaxws-2.0-doc/wsimport.html wsimport seems to produce quite nice code, but I have a question. wsdl2java also produces metadata like services.xml for your services based on the WSDL, but wsimport doesn't seem to do this. Is there another tool in the jax-ws toolchain that does this? I'm not sure I like the idea of independently maintaining a service definition for each service and operation in the WSDL! Thanks, Andrew. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAX-WS in Axis2
Docs for wsimport http://www.sws.bfh.ch/~fischli/kurse/ead/jws/jaxws-2.0-doc/wsimport.html I believe that REST access is still available since that is something that the engine handles, though I have not tried it. Regards, Bill > Date: Mon, 7 Jul 2008 15:07:44 +0100 > From: [EMAIL PROTECTED] > To: axis-user@ws.apache.org > Subject: Re: JAX-WS in Axis2 > > 2008/7/7 Virtual Light <[EMAIL PROTECTED]>: > > JAX-WS with JAXB bindings is your best bet for compatibility across > > different SOAP engines. Forget about the wsdl2JAVA that is in Axis2 1.4 and > > use wsimport(contract first)/wsgen(code first). Both of these are now part > > of JDK 1.6. > > Okay... Thanks. From my brief look at wsimport it does seem to produce > slightly more readable code than wsdl2java/ADB, and as long as it > doesn't choke on any of the data structures in my XSDs I should be > fine. (Is there any documentation on that anywhere?) > > It still seems like there's a bit of an explanatory gulf in the Axis2 > manual between the parts that refer to Axis2's own code generation > tools and data bindings, and the parts that use the JAX-WS approach... > > One question. Can a JAX-WS-style service deployed in Axis2 still be > accessible via REST the way a conventional Axis2-style service can? > > Thanks, > > Andrew. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: JAX-WS in Axis2
2008/7/7 Virtual Light <[EMAIL PROTECTED]>: > JAX-WS with JAXB bindings is your best bet for compatibility across > different SOAP engines. Forget about the wsdl2JAVA that is in Axis2 1.4 and > use wsimport(contract first)/wsgen(code first). Both of these are now part > of JDK 1.6. Okay... Thanks. From my brief look at wsimport it does seem to produce slightly more readable code than wsdl2java/ADB, and as long as it doesn't choke on any of the data structures in my XSDs I should be fine. (Is there any documentation on that anywhere?) It still seems like there's a bit of an explanatory gulf in the Axis2 manual between the parts that refer to Axis2's own code generation tools and data bindings, and the parts that use the JAX-WS approach... One question. Can a JAX-WS-style service deployed in Axis2 still be accessible via REST the way a conventional Axis2-style service can? Thanks, Andrew. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JAX-WS in Axis2
JAX-WS with JAXB bindings is your best bet for compatibility across different SOAP engines. Forget about the wsdl2JAVA that is in Axis2 1.4 and use wsimport(contract first)/wsgen(code first). Both of these are now part of JDK 1.6. > Date: Mon, 7 Jul 2008 09:48:32 +0100 > From: [EMAIL PROTECTED] > To: axis-user@ws.apache.org > Subject: JAX-WS in Axis2 > > Morning all, > > I'm a little confused about the role of JAX-WS in Axis2. Maybe someone > can enlighten me a little. My previous WS experiences were in C# and > I've only been investigating the Java options for a month or so. > > Specifically, there seems to be a lot of overlap between the features > described in this page: > > http://ws.apache.org/axis2/1_4/jaxws-guide.html > > and those described in this one: > > http://ws.apache.org/axis2/1_4/quickstartguide.html > > For example: The first talks about XML Source, SAAJ and JAXB > databinding, the second about ADB, XMLBeans and JiBX. > > The first talks about using wsimport to create server classes from a > WSDL, the second talks about using wsdl2java for the same purpose. > > What's going on here? To a new user this redundancy is rather > unsettling, especially given that neither of the documents really > refers to the other one. I had been using Axis2 1.3, and all the > JAX-WS stuff is new in 1.4 right? I'd been under the impression that > JAX-WS was a rival technology to Axis2, but it seems I was wrong. This > isn't helped by the fact that a lot of articles on Java WS topics are > out of date or just plain wrong, which I suppose can't be helped with > a fast moving field containing lots of inter-related strands. > > My usage scenario looks like this: > > - Top-down (WSDL-first) design > > - WS-I compliance required > > - Complex data structures in the schema > > - Interopability with non-Java clients required > > Should I be going down the JAX-WS route or the 'native' Axis2 route? > [Or another framework completely? ;-) ] > > And with which of the many databinding options? > > Many thanks, > > Andrew. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
