I have created one service war using latest Tuscany 0.99, and deploy it on
Tomcat, It was perfectly creating wsdl on the fly.
Now when i have installed same war file into WebSphere following error comes
at time of startup of WebSphere.all the lib jars are same in both the cases.
SystemOut.log
That looks like WebSphere has an old back level version of the wsdl4j jar
thats being picked up instead of the 1.6.2 one used by Tuscany. It could be
the same problem as documented here for Apache Muse:
http://ws.apache.org/muse/docs/2.2.0/manual/troubleshooting/wsdl4j-version-on-websphere.html
hi,
we have created a component implementation for a small RESTful composition
language which does not support references to other components, now we want
to add support for that. The component implementation is similar to BPEL,
but without all the WSDL and partnerlink stuff. Just support for
I'm not sure what this one is and I don't have WebShpere installed to try it
on. It looks like it could be a jre xalan problem, could you try downloading
a xalan jar and adding it to your lib folder:
http://repo1.maven.org/maven2/xalan/xalan/2.7.0/xalan-2.7.0.jar
...ant
On 9/11/07, Nishant
I will be out of the office starting 12.09.2007 and will not return until
04.10.2007.
Ich bin bis 04.10.2007 in Urlaub. In dringenden Fällen bin ich erreichbar
unter +49 (0)170 9659336.
-
To unsubscribe, e-mail: [EMAIL
Florian Rosenberg wrote:
hi,
we have created a component implementation for a small RESTful composition
language which does not support references to other components, now we want
to add support for that. The component implementation is similar to BPEL,
but without all the WSDL and partnerlink
Hello every one,
uri attribute of binding.ws/ is much convenient to attach a WS in.
But it works only within a few circumstances, such as another java generated WS
provided by Tuscany, JAXWS.
But much more WS is complecated, such as JBoss or even a Tuscany WS when the
wsdl becomes delicate.
