You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2010/10/11 15:07:33 UTC
[jira] Created: (CXF-3056) Aegis handles MTOM fallback
assymetrically
Aegis handles MTOM fallback assymetrically
------------------------------------------
Key: CXF-3056
URL: https://issues.apache.org/jira/browse/CXF-3056
Project: CXF
Issue Type: Bug
Components: Aegis Databinding
Reporter: Benson Margulies
Fix For: 2.3
I'm not sure if this will prove out as a defect, but I'm writing it up. In the DataHandler type class in Aegis the wrapBytes method does not package the bytes as a ByteArrayInputStream in a data source. The result is that 'unoptimized' data handlers are completely different inside from optimized ones, and code has to condition on it, and it's a pain. It would be better, if not very compatible, to always set up a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-3056) Aegis handles MTOM fallback
assymetrically
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies reassigned CXF-3056:
-------------------------------------
Assignee: Benson Margulies
> Aegis handles MTOM fallback assymetrically
> ------------------------------------------
>
> Key: CXF-3056
> URL: https://issues.apache.org/jira/browse/CXF-3056
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Reporter: Benson Margulies
> Assignee: Benson Margulies
> Fix For: 2.3.1, 2.4
>
>
> I'm not sure if this will prove out as a defect, but I'm writing it up. In the DataHandler type class in Aegis the wrapBytes method does not package the bytes as a ByteArrayInputStream in a data source. The result is that 'unoptimized' data handlers are completely different inside from optimized ones, and code has to condition on it, and it's a pain. It would be better, if not very compatible, to always set up a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-3056) Aegis handles MTOM fallback
assymetrically
Posted by "Alessio Soldano (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated CXF-3056:
---------------------------------
Fix Version/s: 2.4
> Aegis handles MTOM fallback assymetrically
> ------------------------------------------
>
> Key: CXF-3056
> URL: https://issues.apache.org/jira/browse/CXF-3056
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Reporter: Benson Margulies
> Fix For: 2.3.1, 2.4
>
>
> I'm not sure if this will prove out as a defect, but I'm writing it up. In the DataHandler type class in Aegis the wrapBytes method does not package the bytes as a ByteArrayInputStream in a data source. The result is that 'unoptimized' data handlers are completely different inside from optimized ones, and code has to condition on it, and it's a pain. It would be better, if not very compatible, to always set up a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3056) Aegis handles MTOM fallback
assymetrically
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies resolved CXF-3056.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.3.1)
> Aegis handles MTOM fallback assymetrically
> ------------------------------------------
>
> Key: CXF-3056
> URL: https://issues.apache.org/jira/browse/CXF-3056
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Reporter: Benson Margulies
> Assignee: Benson Margulies
> Fix For: 2.4
>
>
> I'm not sure if this will prove out as a defect, but I'm writing it up. In the DataHandler type class in Aegis the wrapBytes method does not package the bytes as a ByteArrayInputStream in a data source. The result is that 'unoptimized' data handlers are completely different inside from optimized ones, and code has to condition on it, and it's a pain. It would be better, if not very compatible, to always set up a stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.