axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1484) SAAJ/DOM importNode problem
Date Sun, 01 Aug 2004 14:51:11 GMT
The following comment has been added to this issue:

     Author: Ias
    Created: Sun, 1 Aug 2004 7:51 AM
I don't see any explicit dependency on Xerces on the patches.
Is it a Crimson's problem not to support the logics used in Kyoung-Koo's improvement?
If all the code in the patches are firmly based on JAXP APIs, I think the improvement is worth
being applied to Axis because Crimson is sort of obsolete and we can override it by Xerces
in case of J2SE 1.4. (Fortunately, Sun's J2SE 5 provides com.sun-prefixed Xerces as a default
JAXP implementation.)

Any other thoughts?
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1484
    Summary: SAAJ/DOM importNode problem
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Axis
             current (nightly)

   Reporter: Jongjin Choi

    Created: Sun, 1 Aug 2004 1:41 AM
    Updated: Sun, 1 Aug 2004 7:51 AM
Environment: Windows 2000/XP, Xerces 2.6.X, Crimson (in J2SDK 1.4.X)

The current Apache AXIS SAAJ 1.2 implementation lacks of its feature in SAAJ/DOM importNode()
When importing node from SAAJ to DOM, it results in error. The reverse is unimplemented. 

The first case, importing node from SAAJ to DOM, the cause is that the getOwnerDocument()
returns 'null' for SOAPHeaderElement or SOAPBodyElement. 

I and my colleague 'Kyung-Koo Yoon' in Tmax Soft made a patch and test case. KyungKoo implemented
unimplmented method in SOAPDocumentImpl.

There are some open issue for this:
- The patch only applies to Xerces. 
  When you use crimson in J2SDK 1.4.X, the problem remains same.
- The implementation of importing node from DOM to SAAJ 
  has also some unimplemented features.

We'd like Axis committers review this code and enhance it.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message