You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2006/10/17 16:59:36 UTC
[jira] Updated: (WSCOMMONS-71) OMSourcedElementImpl (was
OMObjectWrapperElement Feature Request)
[ http://issues.apache.org/jira/browse/WSCOMMONS-71?page=all ]
Rich Scheuerle updated WSCOMMONS-71:
------------------------------------
Summary: OMSourcedElementImpl (was OMObjectWrapperElement Feature Request) (was: OMObjectWrapperElement Feature Request)
Priority: Major (was: Minor)
Status:
I have made progress by using OMSourcedElementImpl/OMDataSource instead of creating a new abstraction.
I have found two problems when adding an OMSourcedElementImpl object to an existing tree.
a) An NPE if the OMSourcedElement has an unqualified namespace.
b) A problem exposed in OMNavigator when the element is an OMSourcedElementImpl.
The solution for (a) is simple and straightfoward.
The solution for (b) is more involved. I am developing a test that demonstrates the problem.
Also I noticed that the existing OMSourcedElementImplTest uses an OMDataSource that is not consumed when it is read (the data is stored as a String). I was going to change this to a ByteArrayInputStream so that we can demonstrate support for data sources that are destructed when touched. Ultimately we may want to ammend the OMDataSource interface (or add an extended interface) to communicate whether the underlying datasource is rewindable.
I will provide another update after I make more progress.
Thanks,
scheu
> OMSourcedElementImpl (was OMObjectWrapperElement Feature Request)
> -----------------------------------------------------------------
>
> Key: WSCOMMONS-71
> URL: http://issues.apache.org/jira/browse/WSCOMMONS-71
> Project: WS-Commons
> Issue Type: New Feature
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assigned To: Rich Scheuerle
>
> Notes on the forum indicate that work is being done on the OMObjectWrapperElement feature for Axiom.
> This feature could be used to increase performance in the JAX-WS layer. For example, the JAX-WS layer could put a JAXB object into an OMObjectWrapperElement; thus deferring serialization until the transport layer.
> This issue is opened as an official request for this feature.
> If the work on this feature has stalled, please supply information so that the community can help it proceed. I would like to know the current state of the work and its proposed delivery . If additional development support is necessary, the community and the Axis2 JAX-WS developers would like to participate.
> Thanks,
> scheu
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org