axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-255) A cloning mechanism for SOAPEnvelopes and OMElements
Date Wed, 30 Nov 2005 15:44:30 GMT
     [ http://issues.apache.org/jira/browse/AXIS2-255?page=all ]
     
Eran Chinthaka resolved AXIS2-255:
----------------------------------

    Fix Version: 0.93
     Resolution: Fixed
      Assign To: Eran Chinthaka

fixed with cloneOM() method. I didn't override the clone method as it return an "Object".


> A cloning mechanism for SOAPEnvelopes and OMElements
> ----------------------------------------------------
>
>          Key: AXIS2-255
>          URL: http://issues.apache.org/jira/browse/AXIS2-255
>      Project: Apache Axis 2.0 (Axis2)
>         Type: New Feature
>   Components: om
>     Reporter: Chamikara Jayalath
>     Assignee: Eran Chinthaka
>      Fix For: 0.93

>
> We got a requirement for cloning SOAPEnvelopes in the Sandesha2 implementation. It seems
that this has not been implemented yet.
> The scenarios is this. In WSRM we have to at times re-send messages. Currently we make
a copy of a message context and send it every time. But since the SOAP envelope cannot be
cloned we have to share it between resends. Unfortunately this causes the handlers after RM
to add their headers again and again. For example re-sent messages have multiple From,To ReplyTo
headers.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message