axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal Jayasinghe <dee...@opensource.lk>
Subject Re: [jira] Commented: (AXIS2-2922) Please fix codegen issues relating to Rampart-29 and Rampart-53
Date Mon, 16 Jul 2007 06:10:31 GMT
Hi Sharma,

We will definitely fix the issue before our next RC which we are
targeting on this week.

Thanks
Deepal
>     [ https://issues.apache.org/jira/browse/AXIS2-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512863
] 
>
> Sharma, Vishal  commented on AXIS2-2922:
> ----------------------------------------
>
> Hi Deepal,
>
> When do you think we would be able to get the solution to the Rampart
> issue.
>
> Thanks and Regards,
> Vishal
>
>
>   
>> Please fix codegen issues relating to Rampart-29  and Rampart-53
>> ----------------------------------------------------------------
>>
>>                 Key: AXIS2-2922
>>                 URL: https://issues.apache.org/jira/browse/AXIS2-2922
>>             Project: Axis 2.0 (Axis2)
>>          Issue Type: Bug
>>          Components: codegen
>>    Affects Versions: 1.3
>>         Environment: All
>>            Reporter: Dimuthu Leelarathne
>>            Assignee: Amila Chinthaka Suriarachchi
>>            Priority: Blocker
>>
>> When code generated code is converted to doom, build() method of the SOAPEnvelope
is called. This would create the SOAPEnvelope that is wrong. 
>> In Rampart29 case
>> ===============
>> Please remove the <base64Binary> element out from the message. This element
is added by "public javax.xml.stream.XMLStreamReader getPullParser(javax.xml.namespace.QName
qName){" in the generated code
>> <data xmlns:axis2ns1="http://www.w3.org/2005/05/xmlmime"
>> axis2ns1:contentType="application/pdf">
>> <base64Binary xmlns="http://www.w3.org/2001/XMLSchema">
>> Y29udGVtcG9yYXJ5C ........29tbXVuaXRpZXMgbGl2aW5nIG91dHNpZGUgdGhlIGxhbmQgb2YgSbXVuaXRpZXMuCg==
>> </base64Binary>
>> </data>
>> In Rampart53 case 
>> =============== 
>> SOAPEnvelope's build() method does not add the type parameter for type hierarchies.
For example  xsi:type="s1:van" is missing in the evelope.
>> What the SOAP envelope should be:
>> <?xml version='1.0' encoding='UTF-8'?>
>>    <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
>>       <soapenv:Body>
>>          <ns2:getVehicleResponse xmlns:ns2="http://messages.sample/xsd">
>>             <ns2:vehicle xmlns:s1="http://sample/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="s1:van">
>>                <s1:vehicleID>1</s1:vehicleID>
>>                <s1:weight>0</s1:weight>
>>                <s1:passengers>0</s1:passengers>
>>                <s1:maxload>0</s1:maxload>
>>             </ns2:vehicle>
>>          </ns2:getVehicleResponse>
>>       </soapenv:Body>
>>    </soapenv:Envelope> 
>> What we get now:
>> <?xml version='1.0' encoding='UTF-8'?>
>>    <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
>>       <soapenv:Body>
>>          <ns2:getVehicleResponse xmlns:ns2="http://messages.sample/xsd">
>>             <vehicle xmlns="http://messages.sample/xsd">
>>                <vehicleID xmlns="http://sample/xsd">1</vehicleID>
>>                <weight xmlns="http://sample/xsd">0</weight>
>>                <passengers xmlns="http://sample/xsd">0</passengers>
>>                <maxload xmlns="http://sample/xsd">0</maxload>
>>             </vehicle>
>>          </ns2:getVehicleResponse>
>>       </soapenv:Body>
>>    </soapenv:Envelope>0 
>>     
>
>   

-- 
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"



---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message