One difference between CXF J2W and Axis2 J2W appears to be that CXF follows
the JAXWS spec with respect
to the fault--exception mapping whereas Axis2 invents a new convention.
Correct me if I'm wrong but I don't think the Tuscany runtime supports the
Axis2 pattern, right?
This would imply some
Hi, simon
Axis2's JAVA2WSDL can handle the JAX-WS annnotations by default.
Since it's org.apache.axis2.description.java2wsdl.DefaultSchemaGeneratorcontains
following lines:
JAnnotation annotation = jclass.getAnnotation(
AnnotationConstants.WEB_SERVICE);
if (annotation != null) {
On 05/03/2008, Scott Kurz [EMAIL PROTECTED] wrote:
I didn't follow all of the discussion about removing SDO from the Tuscany
charter... but if SDO is no
longer a special part of the Tuscany project then what would happen to the
W2J/J2W tools built around
SDO support?
The WSDL/WSDL tools
On Tue, Mar 4, 2008 at 9:03 AM, Alex [EMAIL PROTECTED] wrote:
Hi All,
In tuscany-sca (1.1 above) , there are two modules related with java2wsdl:
1.) modules\interface-wsdl-java2wsdl
2.) tools\java2wsdl
The java2wsdl interface(1) provides a runtime interface to handle java
object to wsdl
One important difference if I understand correctly is the tool handles SDOs
whereas the runtime
interface-wsdl-java2wsdl module only handles POJO types.
I think the runtime code basically relies on Axis2's Java-XSD mapping,
which I don't think would
fully honor JAXB annotations in the Java as it
Hi Simon
Thanks for your reply, I would like to help to improve it.
I think maybe we can merge the tools\java2wsdl code, and let them both
follow the axis's approache.
On Wed, Mar 5, 2008 at 8:26 PM, Simon Laws [EMAIL PROTECTED]
wrote:
On Tue, Mar 4, 2008 at 9:03 AM, Alex [EMAIL PROTECTED]
Hi Scott,
the Axis2 Java2WSDL can add -sg option with the value
org.apache.axis2.jaxbri.JaxbSchemaGenerator.
then it can deal with the JXAB annotations.
since interface-wsdl-java2wsdl relies on Axis'2 java2wsdl directly, It's
easy to do JXAB.
But for tools\java2wsdl, it NOT easy since it use
See inline.
Simon
Scott Kurz wrote:
One important difference if I understand correctly is the tool handles SDOs
whereas the runtime
interface-wsdl-java2wsdl module only handles POJO types.
I think the runtime code basically relies on Axis2's Java-XSD mapping,
which I don't think would
fully
On Wed, Mar 5, 2008 at 2:30 PM, Alex [EMAIL PROTECTED] wrote:
Hi Scott,
the Axis2 Java2WSDL can add -sg option with the value
org.apache.axis2.jaxbri.JaxbSchemaGenerator.
then it can deal with the JXAB annotations.
since interface-wsdl-java2wsdl relies on Axis'2 java2wsdl directly, It's
See inline.
Simon
Simon Laws wrote:
On Wed, Mar 5, 2008 at 2:30 PM, Alex [EMAIL PROTECTED] wrote:
Hi Scott,
the Axis2 Java2WSDL can add -sg option with the value
org.apache.axis2.jaxbri.JaxbSchemaGenerator.
then it can deal with the JXAB annotations.
since interface-wsdl-java2wsdl relies
It's really the runtime code that Tuscany primarily needs to make choices on
and make as good as possible. Users will be able to use any W2J/J2W tool
which
generate Tuscany-supported databindings, and the JAX-WS annotations should
be honored i.e. in a bigger sense the runtime codegen
and
Please see my comments inline.
Thanks,
Raymond
[[snip]]
The question then is, what do we want these tools to do? Some thoughts
from
my point of view. This is just my view and others may disagree...
- The runtime J2WSDL should be able to generate WSDL for Java interfaces
for
the Java
Hi All,
In tuscany-sca (1.1 above) , there are two modules related with java2wsdl:
1.) modules\interface-wsdl-java2wsdl
2.) tools\java2wsdl
The java2wsdl interface(1) provides a runtime interface to handle java
object to wsdl object
the java2wsdl tool (2) provides a command-line tool for
13 matches
Mail list logo
