Hi,
It seems that the StAX parser from WebLogic is not happy with empty
namespace in the NamespaceContext.getPrefix() call made by the JAXB
marshaller.
java.lang.IllegalArgumentException: The uri may not be theempty string.
at
weblogic.xml.stax.util.NamespaceContextImpl.getPrefix(NamespaceContextImpl.java:76)
at
com.sun.xml.bind.v2.runtime.StAXPostInitAction.run(StAXPostInitAction.java:95)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.prewrite(MarshallerImpl.java:365)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:327)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:175)
at
org.apache.tuscany.sca.databinding.jaxb.axiom.JAXBDataSource$1.run(JAXBDataSource.java:81)
By the javadoc [1], the call should be OK. I also debugged the test case
with woodstox and it's happy with the empty namespace.
[1]
http://java.sun.com/j2se/1.5.0/docs/api/javax/xml/namespace/NamespaceContext.html#getPrefix(java.lang.String)
Thanks,
Raymond
--------------------------------------------------
From: "Dave Sowerby" <[EMAIL PROTECTED]>
Sent: Tuesday, August 05, 2008 6:05 AM
To: <[email protected]>
Subject: Re: Problems using weblogic hosted binding.ws services
Hey,
So I'm seeing this behaviour in the samples too....
sample-calculator-ws-webapp:
I moved to composite into META-INF as previously discussed
(http://davesowerby.blogspot.com/2008/02/using-tuscany-with-weblogic.html)
Deployed to my weblogic 9.2 domain
Request http://localhost:7001/sample-calculator-ws-webapp/calc.jsp I
get a HTTP 500
The server side stack is attached, once again it contains:
java.lang.IllegalArgumentException: The uri may not be theempty string.
Does anyone have any ideas? If I find more time I'll see if I can
investigate further than I have, though I haven't been able to make
much progress....
Cheers,
Dave.
--
Dave Sowerby MEng MBCS
On Tue, Aug 5, 2008 at 10:10 AM, Dave Sowerby <[EMAIL PROTECTED]>
wrote:
Hey Simon,
This is a webapp I've taken directly from websphere 6.1 and deployed
it to weblogic so I'd have expected it to work.
The last time I tried Tuscany on weblogic was back on 1.2, so I'll
give some of the example webapps a go in their default state and see
if I can the same exceptions there.
Cheers,
Dave.
--
Dave Sowerby MEng MBCS
On Tue, Aug 5, 2008 at 10:06 AM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Mon, Aug 4, 2008 at 5:14 PM, Dave Sowerby <[EMAIL PROTECTED]>
wrote:
Hi All,
I'm currently trying to use a Tuscany binding.ws webapp service on
weblogic 9.2 - the service itself starts fine and I can access the
appropriate ?wsdl endpoint.
However, when I attempt to use this service through a Tuscany client I
get an Exception with a root cause of:
Caused by: org.apache.axis2.AxisFault:
java.lang.IllegalArgumentException: The uri may not be theempty
string.
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker$1.run(Axis2BindingInvoker.java:128)
Is this something anyone has seen?
I've attached a service and client example which reproduces this fault
along with the full Exception.
Any help would be greatly appreciated.
Cheers,
Dave.
--
Dave Sowerby MEng MBCS
Hi Dave
Unfortunately I don't have a WebLogic server I can test on. Looking at
the
test case and the stack trace it looks like it didn't even get past
sayHello(). Is that right? Does the app runs ok in other containers?
Regards
Simon
