WSDL2JAVA code generation

[Virtual Light <vi...@hotmail.com>]

I have noticed that with Axis2 1.3 that the code generated by the WSDL2JAVA eclipse plugin does not by default generate methods that throw RemoteException (ADB binding) as was the case with Axis 1.4.  Is this by design or is this a bug?  I had seen a similar post asking about this but there was no resolution.    

Bill

Latest XML parser performance comparison

[jimmy Zhang <cr...@comcast.net>]

Here is a latest XML parsing performance comparison comparing Xerces DOM, Xerces SAX, Piccolo, Pull, VTD-XML and VTD-XML in C...

http://www.ximpleware.com/2.3/benchmark_2.3_parsing_only.html

RE: WSDL2JAVA code generation

["Pantvaidya, Vishwajit" <vp...@selectica.com>]

Bill,

I presume you are comparing Axsi1 1.4 with Axis2 1.3.

I had also run into this earlier and here is what I understand - Axis1 followed the JAX-RPC (WSDL2Java) standard which required that methods throw RemoteException. Axis2 does not follow the Sun JAX-RPC spec. Secondly, it is better for webservices to throw user-defined custom exceptions defined in the WSDL rather than Java specific exceptions so that WSDL2Java on the client side and the server side knows the exception and can properly deserialize it into the corresponding object.

So it seems to me that this is by design and not a bug.


- Vish.

________________________________
From: Virtual Light [mailto:virtuallight@hotmail.com]
Sent: Tuesday, March 04, 2008 10:58 AM
To: axis-user@ws.apache.org
Subject: WSDL2JAVA code generation

I have noticed that with Axis2 1.3 that the code generated by the WSDL2JAVA eclipse plugin does not by default generate methods that throw RemoteException (ADB binding) as was the case with Axis 1.4.  Is this by design or is this a bug?  I had seen a similar post asking about this but there was no resolution.

Bill