You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Krishna R Seelam (JIRA)" <ax...@ws.apache.org> on 2007/05/31 07:11:16 UTC
[jira] Commented: (AXIS-2613) faultString:
org.xml.sax.SAXException: Invalid element in com.icl.content.contentReq
-providers error accurs frequently
[ https://issues.apache.org/jira/browse/AXIS-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500286 ]
Krishna R Seelam commented on AXIS-2613:
----------------------------------------
Chethan
We got the same problem at client end when the wsdl defination is changed ( i.e. added new attributes) at server side.
We fixed the problem by synch the client end java bean get/set methods with the new wsdl attributes.
but the question is;
If the wsdl changes at server end; Does the client need to change?
-K
> faultString: org.xml.sax.SAXException: Invalid element in com.icl.content.contentReq -providers error accurs frequently
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS-2613
> URL: https://issues.apache.org/jira/browse/AXIS-2613
> Project: Axis
> Issue Type: Bug
> Environment: jdk :1.4_2
> Reporter: chethan
>
> ======================================================
> faultCode: {http://xml.apache.org/axis/}Server.userException
> faultString: org.xml.sax.SAXException: Invalid element in com.icl.content.contentReq-providers
> faultActor: null
> faultDetail:
> stackTrace: org.xml.sax.SAXException: Invalid element in com.icl.content.contentReq-providers
> at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:252)
> at org.apache.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:893)
> at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:200)
> at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:684)
> at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:207)
> at org.apache.axis.message.RPCElement.getParams(RPCElement.java:265)
> at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:190)
> at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:276)
> at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
> at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:437)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:316)
> at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:701)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:165)
> at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:103)
> at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:82)
> at com.caucho.server.http.Invocation.service(Invocation.java:288)
> at com.caucho.server.http.RunnerRequest.handleRequest(RunnerRequest.java:340)
> at com.caucho.server.http.RunnerRequest.handleConnection(RunnerRequest.java:270)
> at com.caucho.server.TcpConnection.run(TcpConnection.java:140)
> at java.lang.Thread.run(Thread.java:534)
> ===================================================
> some times the above error accurs infrequently in our client-side application. wht should be reason for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org