axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Commented: (AXIS-1498) AXIS2: pluggable XML transformations (JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
Date Wed, 11 Aug 2004 04:44:20 GMT
The following comment has been added to this issue:

     Author: Aleksander Slominski
    Created: Tue, 10 Aug 2004 9:43 PM
       Body:
maybe i did not make it clear enough: i think that, based on my experience and what i see
in all WS/SOAP/XML projects, there in no ONE  "BEST" API - not only that but there will be
never such "optimal" XML API.

instead we have many APIs such as SAX, DOM,  XmlPull or StAX, SAAJ, and related XML/java binding
APIs such as JAXB, JaxMe, Castor, XmlBeans, JIBX, whatnot ...

so instead of trying to design framework for _one_ API (ApacheSOAP -> DOM, AXIS -> SAX-kind-event-stream-with-DOM/SAAJ)
i would suggest to try to define underlying XML infoset representation that can be easily
*viewed* and *manipulated* through any of those APIs (XmlBeans and XSUL/XB1/XPP3 can be given
as exampels and even AXIS internal Message* design to show that converting XML infoset to
different representations is nto good and streaming needs to be think about and can not be
jsut delegated to a "simple" choice of streaming vs trees ...)

the real challenge i think is to build XML infoset tree model that can be _streamable_ - even
though it sounds difficult it was already done in XPP2 XmlPullNode (and i think it is possible
to tweak XOM NodeFactory) to allow control over buildign of XML tree and streaming to allow
processing of huge XML data without need to do lot of extra work 

ultimately goal would be to allow dealing with XML stream _and_ tree transformations (XSL(T),
WS-Security, WS-RM, ...) over one internal XML representation of SOAP message that is streamed
in and out of SOAP engine

in other words: i think that in XML APIs land plurality rules, and event though we would like
to live and work with whatever-preferred APIs we like we have to let live other APIs :)

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1498?page=comments#action_37158

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1498

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1498
    Summary: AXIS2: pluggable XML transformations (JavaBeans2XML, XSD with JaxMe/JAXB, Castor,
XmlBeans, RelaxNG, ...)
       Type: Wish

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             Basic Architecture

   Assignee: 
   Reporter: Aleksander Slominski

    Created: Fri, 6 Aug 2004 10:36 AM
    Updated: Tue, 10 Aug 2004 9:43 PM
Environment: ALL

Description:
allow to plug different XML<->Java object model transformations (and maybe also allow
them to be pipelined!)

that would make XML processing much more flexible and would allow users to choose how their
XML messages should be processed



---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message