Thanks Aki.

Here is my rpc.xml


<body>
  <app_name>appname</app_name>
  
  <return_type>XML</return_type>
  <me02_mbr_acct>345678888</me02_mbr_acct>
  <me02_password>password</me02_password>
  <trace>N</trace>
</body>

I believe that JAX-WS standard supports the use of the Dispatch to consume a
JAX-RPC client.

I am not understanding as to why the IllegalStateException Current event not
START_ELEMENT or END_ELEMENT is coming because per the spec it comes if a
call is made to a .next when hasNext returns false that would mean that my
file is not parsed correctly or am I missing anything else  in the xml?

I followed this resource 

http://www.ibm.com/developerworks/library/ws-tip-jaxwsrpc4/


Any insights into this would be of great help.

@Glenn:I know that JAX-RPC is no more recommended but as I already stated we
do not have any control on the hosting vendor and we need to consume their
service as-is.




-----
Saludos
Kartheek
--
View this message in context: 
http://cxf.547215.n5.nabble.com/Using-JAX-WS-support-for-JAX-RPC-service-Dispatch-API-tp5710673p5710677.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to