use of "id" as parameter name

[Rich Johns <rj...@vignette.com>]

apache soap 2.0

Does anyone remember if there was a problem at some point where
the use of "id" as a parameter name caused some kind of problem?
I'm getting an exception in the xerces parser. I show the exception below
as well as the payload that causes it. The line it blows on is in RPCRouterServlet:

   Document callDoc = xpl.read("- SOAP HTTP RPC Call Envelope -",
          new CharArrayReader (payload));

and the payload that causes the error is:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:findObjectById xmlns:ns1="com_glicko_cms_client_ejb_XZOOps"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<ejbkey xsi:type="xsd:string">
&lt;com.glicko.cms.client.common.EJBKey&gt;&lt;className&gt;com.glicko.cms.server.ejb.XZOOps&lt;/className&gt;&lt;id&gt;378915:e48aff075b:-8000&lt;/id&gt;&lt;/com.glicko.cms.client.common.EJBKey&gt;</ejbkey>

<type xsi:type="xsd:string">
&lt;com.glicko.cms.client.common.XZOObjectType&gt;&lt;value&gt;13&lt;/value&gt;&lt;/com.glicko.cms.client.common.XZOObjectType&gt;</type>

<id xsi:type="xsd:string">
&lt;com.glicko.cms.client.common.ObjectId&gt;&lt;id&gt;0a13013c00602bbc000000e45c42b40c8017&lt;/id&gt;&lt;/com.glicko.cms.client.common.ObjectId&gt;</id>

</ns1:findObjectById>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

herre's the exception:

java.lang.NullPointerException
 at org.apache.xerces.validators.common.XMLValidator.init(XMLValidator.java:1512)
 at org.apache.xerces.validators.common.XMLValidator.<init>(XMLValidator.java:403)
 at org.apache.xerces.framework.XMLParser.<init>(XMLParser.java:203)
 at org.apache.xerces.parsers.DOMParser.<init>(DOMParser.java:214)
 at org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:79)
 at org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:187)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:208)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1127)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Everything looks ok and I'm able to successfully pass stuff like this. This problem seems
intermittent,
but I'm not sure yet. Any insight would be very much appreciated.

thanks.