You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2008/03/19 18:34:24 UTC
[jira] Updated: (AXIS2-3637) JAXBCustomBuilder should avoid
encrypted data
[ https://issues.apache.org/jira/browse/AXIS2-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle updated AXIS2-3637:
----------------------------------
Fix Version/s: 1.4
> JAXBCustomBuilder should avoid encrypted data
> ---------------------------------------------
>
> Key: AXIS2-3637
> URL: https://issues.apache.org/jira/browse/AXIS2-3637
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Fix For: 1.4
>
>
> Background:
> During JAXWS processing, a JAXB CustomBuilder is registered on the StAXOMBuilder.
> The CustomBuilder automatically unmarshalls the SOAPBody payload as an OMSoucedElement backed by a JAXB object.
> Problem:
> If the body is encrypted, JAXB unmarshalling fails.
> Solution:
> Quick Fix to recognize EncryptedData and use the normal StAXOMBuilder algorithm.
> Kudos to Huiran Wang for finding this problem.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org