You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Simon Nash <na...@apache.org> on 2008/05/27 02:10:00 UTC
New Java2WSDL runtime generator is now active in the build
I've committted r660340 which adds supports for static SDOs to the
new Java2WSDL runtime generator and fixes a few problems. For
static SDOs generated from XSDs, the contribution is searched
for the original XSD definitions, and these are included in the
generated WSDL.
These changes are enough to get a full build to run, so I've turned on
the new generator code by default. More testing is still needed, and
it's possible that this new code could cause problems. If you see
anything unexpected in a Java2WSDL scenario (including the distributed
SCA binding, which uses Java2WSDL under the covers), please open a
JIRA and I'll look at it right away.
One interesting side-effect of these changes is that the tutorial
now builds cleanly for me. Previously it was failing.
Simon
Re: New Java2WSDL runtime generator is now active in the build
Posted by Raymond Feng <en...@gmail.com>.
Hi,
I did some refactoring to move the JAXBTypeHelper to databinding-jaxb module
and removed the JAXB dependency from databinding module. Meanwhile, I
changed the getXMLTypeHelperClass() to getXMLTypeHelper() to avoid extra
cache. I'll check in the change when the build is done.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Nash" <na...@apache.org>
Sent: Monday, May 26, 2008 5:10 PM
To: "tuscany-dev" <tu...@ws.apache.org>; "tuscany-user"
<tu...@ws.apache.org>
Subject: New Java2WSDL runtime generator is now active in the build
> I've committted r660340 which adds supports for static SDOs to the
> new Java2WSDL runtime generator and fixes a few problems. For
> static SDOs generated from XSDs, the contribution is searched
> for the original XSD definitions, and these are included in the
> generated WSDL.
>
> These changes are enough to get a full build to run, so I've turned on
> the new generator code by default. More testing is still needed, and
> it's possible that this new code could cause problems. If you see
> anything unexpected in a Java2WSDL scenario (including the distributed
> SCA binding, which uses Java2WSDL under the covers), please open a
> JIRA and I'll look at it right away.
>
> One interesting side-effect of these changes is that the tutorial
> now builds cleanly for me. Previously it was failing.
>
> Simon