axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "balaji iyer (JIRA)" <>
Subject [jira] Issue Comment Edited: (AXIS2-2814) XSI:TYPE not being generated for SOAP JMS client requests
Date Mon, 18 Jun 2007 16:58:26 GMT


balaji iyer edited comment on AXIS2-2814 at 6/18/07 9:56 AM:

Pls find the attachment containing test code, soap request format(Axis-Http-SOAP-Request.txt
and  Axis-JMS-SOAP-Request.txt), wsdl and schemas over which axis wsdl2java is being used.

Axis-Http-SOAP-Request(SOAP BODY) seems to be fine.  The information does not contain qualified
namespace information. The local names follow the parent namespace. The XSI types are correctly
defined in the SOAP Request.

For Axis-JMS-SOAP-Request, this is not the case

> XSI:TYPE not being generated for SOAP JMS client requests
> ---------------------------------------------------------
>                 Key: AXIS2-2814
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Win XP, AXIS2 (1.2)
>            Reporter: balaji iyer
>         Attachments:
> I'm trying to run the SOAP JMS webservice which is hosted in businessworks. 
> I am using the AXIS2 wsdl2java to generate the client side stubs and databinding classes.
There are no issues for HTTP binding.
> However for JMS binding the generated code seems to be having the following issue. It
seems that AXIS2 is generating different soap request (payload)  for JMS and HTTP.  
> The issues is that the "xsi type" is not being generated for JMS requests. 
> Because of this problem, I'm unable to run AXIS2 SOAP/JMS and correspondingly parse them
consistently in businessworks. 

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:
For additional commands, e-mail:

View raw message