UnsupportedOperationException("TODO") when unimplemented methods of 
org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderImpl class are called.
-------------------------------------------------------------------------------------------------------------------------------------------

         Key: AXIS2-428
         URL: http://issues.apache.org/jira/browse/AXIS2-428
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug
  Components: om  
    Versions: 0.94    
 Environment: Windows XP Pro, JBoss 3.2.3
    Reporter: Juanda Zeng


Since development of the classes in the org.apache.axis2.om.impl.dom.jaxp 
package is still in progress, quite a few methods in the DocumentBuilderImpl 
class are still not implemented yet.
These methods throw UnsupportedOperationException("TODO") when called.
Currently, WSDoAllReceiver and WSDoAllSender make system-wide change by setting 
the "javax.xml.parsers.DocumentBuilderFactory" property to 
org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.
This causes client modules to fail should there be a call to one of the 
unimplemented methods.
It is best to avoid using its DocumentBuilder until it is ready for testing.

SUGGESTED TEMPORARY WORKAROUND:
----------------------------------------------------------------
Use the DocumentBuilder from JDK (Crimson). Modify the newDocumentBuilder() 
method of the org.apache.axis2.om.impl.dom.jaxp.DocumentBuilderFactoryImpl 
class as follows:

  public DocumentBuilder newDocumentBuilder()
          throws ParserConfigurationException {
      /**
       * Juanda Zeng - 20060203
       * Since development is still in progress and a few methods are still not 
implemented yet,
       * it is best to avoid using its DocumentBuilder until it is ready for 
testing.
       * We will use the one from JDK (Crimson).
       */
      // return new DocumentBuilderImpl();
      return new 
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl().newDocumentBuilder();
  }



-- 
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

Reply via email to