So far as I know, all the existing WS tooling requires that the
project be a Dynamic Web Project. The upside of this is that we know what runtimes are
associated with that project (i.e. JBoss AS 7, SOA-P 5.2, EAP, etc) and thus know which
command-line tools to run to do the code generation for a top-down or bottom-up WS
implementation.
ah yes - I forgot that part of it.
But that could be solved by having the wizard just take the default choice from the
project and if nothing specified let the user choose which runtime to run against.
IMO, though you may only need Axis2 for SwitchYard, if this is going
to become the defacto standard for java2wsdl or wsdl2java code generation, we have to keep
other runtimes in mind. If we go with Axis2 by itself, my concern is that we aren't
supporting JBossWS, which we need for our runtime products.
Yes, i'm not sure what kind of differences there will be though. if axis2 is just used
for codegeneration does that output work for/with (old) JBossWS and JBossWS-CXF ?
max
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Rob Cernich" <rcernich(a)redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Sent: Monday, March 5, 2012 4:56:57 PM
Subject: [jbosstools-dev] Wizards for Java2WSDL and WSDL2Java
Hey all,
One of the things missing from our toolset that would really improve productivity when
developing SwitchYard applications is a mechansim for generating WSDL from Java, and, to a
lesser degree, Java from WSDL. Currently, SY relies on wsconsume and wsprovide for this
functionality.
> From a tooling perspective, it seems that all the translators require a dyanmic web
project to invoke them. Is this a correct assessment? Have I missed something?
So far, the best tool I've found (that meets the needs of SY) is the Axis2 code gen
plugin. The functionality is a bit sparse, but it works rather well, requiring minimal
cleanup. I think if the interface were improved, it might easily produce results that
don't require any cleanup.
In addition to the translators, SY would need transformers created (or stubbed out) so
the runtime could manage conversion between the types (e.g. Java2XML). This makes me lean
toward a custom SY solution, but I think it would be nice if the core could be shared.
Any ideas, opinions, comments, concerns...
Thanks in advance,
Rob
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev