You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2010/08/03 21:06:16 UTC
[jira] Created: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
-----------------------------------------------------------------------------------------------------------
Key: AXIS2-4791
URL: https://issues.apache.org/jira/browse/AXIS2-4791
Project: Axis2
Issue Type: Improvement
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Background:
The JAX-WS engine uses JAXB data objects.
The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
Problem:
If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
However the SOAP node receiving the message will fail.
Solution:
Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4791.
-----------------------------------
Resolution: Fixed
This issue has been resolved
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894996#action_12894996 ]
Andreas Veithen commented on AXIS2-4791:
----------------------------------------
Rich, please take into account that introducing a change that relies on new code in Axiom at this stage will probably delay the 1.6 release.
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894996#action_12894996 ]
Andreas Veithen commented on AXIS2-4791:
----------------------------------------
Rich, please take into account that introducing a change that relies on new code in Axiom at this stage will probably delay the 1.6 release.
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894996#action_12894996 ]
Andreas Veithen commented on AXIS2-4791:
----------------------------------------
Rich, please take into account that introducing a change that relies on new code in Axiom at this stage will probably delay the 1.6 release.
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894996#action_12894996 ]
Andreas Veithen commented on AXIS2-4791:
----------------------------------------
Rich, please take into account that introducing a change that relies on new code in Axiom at this stage will probably delay the 1.6 release.
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4791.
-----------------------------------
Resolution: Fixed
This issue has been resolved
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4791.
-----------------------------------
Resolution: Fixed
This issue has been resolved
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4791.
-----------------------------------
Resolution: Fixed
This issue has been resolved
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-4791.
-----------------------------------
Resolution: Fixed
This issue has been resolved
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4791) JAX-WS: Support an option to allow
invalid xml characters to be removed from an outbound JAXB serialization
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894996#action_12894996 ]
Andreas Veithen commented on AXIS2-4791:
----------------------------------------
Rich, please take into account that introducing a change that relies on new code in Axiom at this stage will probably delay the 1.6 release.
> JAX-WS: Support an option to allow invalid xml characters to be removed from an outbound JAXB serialization
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4791
> URL: https://issues.apache.org/jira/browse/AXIS2-4791
> Project: Axis2
> Issue Type: Improvement
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Background:
> The JAX-WS engine uses JAXB data objects.
> The JAXB data objects are marshaled to xml using a JAXB provided Marshaler.
> The Marshaler writes information to an XMLStreamWriter (which will be the axiom provided MTOMXMLStreamWriter).
> Problem:
> If a customer populates the JAXB bean with non-xml characters (0x15), the JAXB Marshaler will write the illegal characters without errors.
> However the SOAP node receiving the message will fail.
> Solution:
> Provide a JAX-WS property that a customer can set (using the @WebServiceContext) to recognize and remove illegal characters.
> This solution will have an axiom and axis2 contribution.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org