Anne,
In case it was a general problem I have reattached the WSDL file here.
I am not certain if your reply reflects an "official" response from the Axis
team or if you are simply a user being helpful. If this is a team response
then I am somewhat at a loss of where to go from here. One of the promises of
Web Services is interoperability between various vendors between the clients
and server.
As far as I can tell there are still three distinct possibilities as to the
cause of my problem:
1. I am doing something wrong;
2. It is a JBoss issue;
3. It is an Axis issue.
So far I have 1) a response from the the JBoss team that asserts that it is
probably an Axis issue and pretty much I get the impression that they
consider it a closed issue; and 2) your response that indicates that this is
a JBoss issue. So far no one has indicated this is likely to me my problem,
but I have not yet ruled that out.
To paraphrase a John Denver lyric, "This is no place at all." Where do I go
from here? Yes, I do understand that both are OS projects and no one owes me
or anyone else support. Still, if this type of interoperability issue is not
at the heart of both the Axis and JBoss projects, then to paraphrase another
song, "What is it all about?"
Please understand there is no irritability on my part; this is not intended as
a rave. Simply my attempt to shake the trees and get an issue that I feel
deserves attention noticed.
Btw, as an aside, is using Axis as the client and JBoss as the server such an
odd combination? I wonder why I do not find other users complaining about
this problem. I guess this is one of the reasons I have not yet ruled out
that this may be my problem.
/joel
On Wednesday 26 January 2005 23:32, Anne Thomas Manes wrote:
> For some reason I can't open the attached WSDL file, but there's
> nothing wrong with specifying xmlns="" in an unqualified element. In
> fact, assuming that the <in0> is an unqualified element, it's
> required.
>
> So I don't think this is a bug in Axis. If JBoss is rejecting the
> xmlns="" attribute, then it's a bug in JBoss.
>
> - Anne
>
>
> On Mon, 24 Jan 2005 18:38:15 +0000, Joel Rosi-Schwartz
>
> <[EMAIL PROTECTED]> wrote:
> > Apologies for reposting this, but this is really show stopper for me and
> > I could truly use some advice on this. Even a response to the extent that
> > this must certainly be something that I have screwed up would be
> > appreciated, as right now I simply have no idea if this is my problem, an
> > axis issue or a JBoss issue.
> >
> > Thanks kindly for your thoughts,
> > Joel
> >
> > Hi,
> >
> > I have a set of web services that I have been developing using Apache
> > Axis 1.2 RC2 on the Java client and JBoss 4 on the server. They have been
> > functioning fine under JBoss 4.0.0, but I am having trouble migrating
> > them to Jboss 4.0.1. When I make a call to any of the web services I get
> > a
> > "java.lang.IllegalArgumentException: Namespace URI cannot be null". I
> > have attached a debug level output of the pertinent portion of the log
> > below.
> >
> > I posted a request for assistance on the JBoss forum. They acknowledge
> > that JBoss is mishandling the Nullpointer exception, but they think the
> > root cause is an Axis issue on the client.
> >
> > There is one line from the log that looks like it may indicate the cause,
> > but I have insufficient experience with Web Services to be sure.
> >
> > [org.apache.axis.transport.http.AxisServlet]
> > <soapenv:Envelope
> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > <soapenv:Body>
> > <publish xmlns="http://webservices.est.useme.etish.com";>
> > <in0 xmlns="">joel</in0>
> > <in1 xmlns="">secret</in1>
> > <in2 xmlns="">1</in2>
> > <in3 xmlns="">6</in3>
> > <in4 xmlns="">2</in4>
> > </publish>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> > It appears that all of the arguments being passed in have an xmlns=""
> > attribute. Is this the culprit and if so how do I correct it?
> >
> > I have attached the relevant wsdl and the stacktrace. Please let me know
> > if there is any other information that I can provide to help diagnose
> > this.
> >
> > Thanks,
> > Joel
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://webservices.est.useme.etish.com";
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:impl="http://webservices.est.useme.etish.com";
xmlns:intf="http://webservices.est.useme.etish.com";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
<!--WSDL created by Apache Axis version: 1.2RC2
Built on Nov 16, 2004 (12:19:44 EST)-->
<wsdl:message name="publishResponse">
<wsdl:part name="publishReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="publishRequest">
<wsdl:part name="in0" type="xsd:string"/>
<wsdl:part name="in1" type="xsd:string"/>
<wsdl:part name="in2" type="xsd:string"/>
<wsdl:part name="in3" type="xsd:string"/>
<wsdl:part name="in4" type="xsd:short"/>
</wsdl:message>
<wsdl:portType name="PublisherWSEndPoint">
<wsdl:operation name="publish" parameterOrder="in0 in1 in2 in3 in4">
<wsdl:input message="impl:publishRequest" name="publishRequest"/>
<wsdl:output message="impl:publishResponse" name="publishResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PublisherWSSoapBinding" type="impl:PublisherWSEndPoint">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="publish">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="publishRequest">
<wsdlsoap:body namespace="http://webservices.est.useme.etish.com"; use="literal"/>
</wsdl:input>
<wsdl:output name="publishResponse">
<wsdlsoap:body namespace="http://webservices.est.useme.etish.com"; use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PublisherWSEndPointService">
<wsdl:port binding="impl:PublisherWSSoapBinding" name="PublisherWS">
<wsdlsoap:address location="http://dummy-location"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
