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 > > >
