axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark D. Hansen" <m.hanse...@verizon.net>
Subject RE: [jira] Commented: (AXIS-1788) Interoperability issue with JBoss 4.0.1
Date Fri, 28 Jan 2005 04:09:16 GMT
when/why did JBoss fork their own version of Axis?

> -----Original Message-----
> From: Davanum Srinivas (JIRA) [mailto:axis-dev@ws.apache.org]
> Sent: Thursday, January 27, 2005 12:29 PM
> To: axis-dev@ws.apache.org
> Subject: [jira] Commented: (AXIS-1788) Interoperability issue 
> with JBoss
> 4.0.1
> 
> 
>      [ 
> http://issues.apache.org/jira/browse/AXIS-1788?page=comments#a
> ction_58171 ]
>      
> Davanum Srinivas commented on AXIS-1788:
> ----------------------------------------
> 
> See JBoss's CVS:
> http://cvs.sourceforge.net/viewcvs.py/jboss/jaxrpc/src/main/or
> g/apache/axis/utils/Mapping.java?r1=1.1&r2=1.2
> 
> They created the problem in their forked version of Axis...So 
> you need to ask them to fix it.
> 
> -- dims
> 
> > Interoperability issue with JBoss 4.0.1
> > ---------------------------------------
> >
> >          Key: AXIS-1788
> >          URL: http://issues.apache.org/jira/browse/AXIS-1788
> >      Project: Axis
> >         Type: Bug
> >     Versions: 1.2RC2
> >     Reporter: Joel Rosi-Schwartz
> >  Attachments: publisher.wsdl, stacktrace.txt
> >
> > 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 
> protion 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.
> 
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the 
> administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira
> 
> 

Mime
View raw message