Re: [axis2] Problem with Websphere 6 and Axis2 security module

[Ruchith Fernando]

Hi,

RE: Problem #2:

>
> Caused by: java.lang.RuntimeException: Unable to create 
> nullNodejava.lang.NullPointerException
>         at 
> org.apache.xml.security.c14n.implementations.CanonicalizerBase.<clinit>(Unknown
>  Source)

The Axis2 security module contains the wss4j-SNAPSHOT.jar and the
xml-security.jar since its required by WSS4J. When WSS4J initializes
the xml-security library it will load the
org.apache.xml.security.c14n.implementations.CanonicalizerBase class.
At that point the following static block will be called.

  static {
    try {
        nullNode=DocumentBuilderFactory.newInstance().
            
newDocumentBuilder().newDocument().createAttributeNS(Constants.NamespaceSpecNS,XMLNS);
        nullNode.setValue("");
    } catch (Exception e) {
        throw new RuntimeException("Unable to create nullNode"/*,*/+e);
    }
  }

nullNode is an org.w3c.dom.Attr attribute.

Therefore as you can see it was not possible to create the nullNode.
Please check whether you can do the above within WebSphere.

The security module shipped with Axis2 0.94 will change the default
DOM impl of the VM to be DOOM (AXIOM complient DOM impl)... but this
works without a problem in Tomcat, Jetty and Axis2-SimpleHTTPServer.
I'm not sure whether changing the VM's DOM impl to DOOM caused any
problems inside WebSphere.
Right now the DOOM impl is changed to be able to set the DOM impl in a
ThreadLocal manner where the changed DOM impl will only be visible on
the thread that changed it not the whole VM. Therefore you can try the
SVN head as well.

Thanks,
Ruchith