[jboss-jira] [JBoss JIRA] Reopened: (JBXB-100) Add support for unmarshal(Source)

Tue Dec 8 07:21:29 EST 2009

     [ https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Vecera reopened JBXB-100:
--------------------------------

Hello Alexey, I think that your point of view is from the XB perspective. The issue is in its usage by other projects like JBossWS (see the linked issue). Currently, there is a performance issue in JBWS because it must convert a Source object to a String representation. This manipulation costs like 18% of the overall JBossAS server processing time, when I executed WS performance test.

We should not expect any gain on the XB side, but we could get a big one on the WS side. See org.jboss.ws.core.binding.DeserializerSupport.sourceToString() method for more details. Usage of DOMWriter causes a real trouble here...

> Add support for unmarshal(Source)
> ---------------------------------
>
>                 Key: JBXB-100
>                 URL: https://jira.jboss.org/jira/browse/JBXB-100
>             Project: JBoss XML Binding (JBossXB)
>          Issue Type: Feature Request
>    Affects Versions: JBossXB-1.0.0.CR9
>            Reporter: Thomas Diesler
>            Assignee: Alexey Loubyansky
>
> JBossWS fragments the incomming SOAP message into Source elements. Currently its using DOMSource.
> The interface to JBossXB is inefficient since the DOMSource needs to be serialized into a String and then into an InputStream. 
> It would be much better if JBossXB could unmarshall the Source directly.
> Later we could transparently switch from DOMSource to some more efficient implementation.

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