You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2007/10/24 22:59:50 UTC
[jira] Resolved: (WSCOMMONS-268) SOAPFault* internalSerialize
method problems
[ https://issues.apache.org/jira/browse/WSCOMMONS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved WSCOMMONS-268.
--------------------------------------
Resolution: Fixed
Committed revision 588018
> SOAPFault* internalSerialize method problems
> --------------------------------------------
>
> Key: WSCOMMONS-268
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-268
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> Problem:
> The syntax for SOAP Fault is radically different for SOAP 1.1 and SOAP 1.2.
> The Axiom tree stores a model that represents SOAP 1.2.
> When necessary the implementation methods override internalSerialize to serialize the xml using the correct protocol syntax.
> The problem is the internalSerialize methods use a lot of "cut and paste" code from OMElementImpl. An IBM developer, Gordon Kuo, has encountered several
> cases where the code is incorrect.
> Solution:
> I did some slight method refactoring.
> If specialized code is necessary, the specialized serializeInternal code is placed within SOAP11Fault* classes.
> If specialized code is not necessary (but ContentHandler registration is needed), the code does the registeration and upcalls to super.internalSerialize.
> The new logic is smaller, easier to follow and will scale better.
--
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org