You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Davanum Srinivas <da...@gmail.com> on 2005/01/24 22:17:24 UTC
Re: Problem using Axis RC2 against JBoss 4.0.1
Joel,
1) Try latest CVS version/nightly build of axis.
2) Log a bug in JIRA
thanks,
dims
On Mon, 24 Jan 2005 18:38:15 +0000, Joel Rosi-Schwartz
<Jo...@etish.org> 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
>
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Problem using Axis RC2 against JBoss 4.0.1
Posted by Joel Rosi-Schwartz <Jo...@Etish.org>.
Thanks Dims. I just tried last nights cvs and I get the same results. I will
log a Jira issuse as you recommend.
Cheers,
Joel
On Monday 24 January 2005 21:17, Davanum Srinivas wrote:
> Joel,
>
> 1) Try latest CVS version/nightly build of axis.
> 2) Log a bug in JIRA
>
> thanks,
> dims
>
> On Mon, 24 Jan 2005 18:38:15 +0000, Joel Rosi-Schwartz
>
> <Jo...@etish.org> 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