12:36 p.m.
Add support for unmarshal(Source)
---------------------------------
Key: JBXB-100
URL: http://jira.jboss.com/jira/browse/JBXB-100
Project: JBoss XML Binding (JBossXB)
Issue Type: Feature Request
Affects Versions: JBossXB-1.0.0.CR9
Reporter: Thomas Diesler
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 a.m.
New subject: [JBoss JIRA] Updated: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky updated JBXB-100:
-----------------------------------
Assignee: Alexey Loubyansky
AFAICS, just Source won't be more efficient. Since it gives access only to the
systemId of the source. Or am I missing something?
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
4:59 a.m.
New subject: [JBoss JIRA] Closed: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky closed JBXB-100.
----------------------------------
Resolution: Rejected
Please, re-open if I am missing something. I don't see how this can be an improvement.
BTW, recently another unmarshal(...) method was added which takes
org.xml.sax.InputSource.
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
6:21 a.m.
New subject: [JBoss JIRA] Reopened: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
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
6:38 a.m.
New subject: [JBoss JIRA] Commented: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Alexey Loubyansky commented on JBXB-100:
----------------------------------------
So what are you asking for? To add unmarshal(javax.xml.transform.Source)? Then its
implementation will be
unmarshal(Source s)
{
return unmarshal(s.getSystemId());
}
Or unmarshal(DOMSource ds) and navigate through the Nodes producing SAX-like events?
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
8:21 a.m.
New subject: [JBoss JIRA] Updated: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Richard Opalka updated JBXB-100:
--------------------------------
JBoss Forum Reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269992
See associated forum reference for more info
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
10:27 a.m.
New subject: [JBoss JIRA] Commented: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Richard Opalka commented on JBXB-100:
-------------------------------------
How about:
unmarshal(Source source)
{
if (source instanceof DOMSource)
{
Node node = ((DOMSource)source).getNode();
... // process node
}
else throw new UnsupportedOperationException();
}
Or you prefer to use DOMSource class directly in your method signatures?
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
12:55 p.m.
New subject: [JBoss JIRA] Resolved: (JBXB-100) Add support for unmarshal(Source)
[
https://jira.jboss.org/jira/browse/JBXB-100?page=com.atlassian.jira.plugi...
]
Richard Opalka resolved JBXB-100.
---------------------------------
Resolution: Rejected
This feature request is not valid anymore.
I fixed JBossWS deserialization process.
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
5491
days inactive
6484
days old
7 comments
4 participants
participants (4)
-
Alexey Loubyansky (JIRA) -
Martin Vecera (JIRA)
-
Richard Opalka (JIRA)
-
Thomas Diesler (JIRA)