Xalan library conflict

WebNMS Framework

javageek

in WebNMS Framework • 10 years ago

Dear all,

I call a soap web service in BE side. when an exception is thrown by calling a web service, i got this exception:

java.lang.NullPointerException
at org.apache.xalan.transformer.TransformerIdentityImpl.setDocumentLocator(TransformerIdentityImpl.java:823)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.DomLoader$State.<init>(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.DomLoader.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ProxyLoader.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleStartElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(Unknown Source)
at com.sun.xml.internal.ws.message.stream.StreamMessage.readPayloadAsJAXB(Unknown Source)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.create(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at $Proxy34.authenticate(Unknown Source)
at my.BasicTester.main(BasicTester.java:26)

all thing works properly what when an exception thrown in soap server, i do not get proper exception and NPE occurs.

i searched a lot but i just found that it maybe xalan bug. xalan current release is 2.7 but i think WebNMS uses 1.1.

what is the solution?

why WebNMS uses xalan? why not java packages? i read since java 1.4 there is no need to use xalan separately and java support it's fuctionality embedded.

i searched but do not found source code for xalan 1.1.

regards,

javageek

Replies(5)

venkatram.. Employee

Hi

Please note that in WebNMS 5.0, we had removed the Xalan dependency for server & client by replacing xalan & crimson APIs with Java APIs.
But note that for the other IDEs (like ClientBuilder / Chassis wizard), we recommend customers to use Endorsed directory mechanism.
Hence please use Endorsed directory mechanism to resolve the issue

Please get back to us for any further clarification in this regard.

Thanks & regards
Venkatramanan

venkatram.. Employee

Re: Xalan library conflict

10 years ago

javageek

Re: Re: Xalan library conflict

10 years ago

Hi,

i did not use ClientBuilder / Chassis wizard. I applied customized authentication mechanism by calling a soap web service in verifyCredentials method. when an exception occurs in web service, i got the mentioned NPE exption.

i followed the 'Endorsed directory mechanism.' linked but nothing is changed.

you said

we had removed the Xalan dependency for server & client by replacing xalan & crimson APIs with Java APIs.

but why nms server still need it for start up?

regards,

javageek

venkatram.. Employee

Re: Xalan library conflict

10 years ago

Hi

Please note that by server & client, we meant starting the server for in-house / Radius / LDAP authentication only.

(We provide out-of-the-box support for in-house & Radius authentication and some of our customer had deployed LDAP authentication by themselves without any Xalan issues)

Please note that we had not tested SOAP authentication.

Get back to us for any further clarification in this regard.

Thanks & regards
Venkatramanan

javageek

Re: Re: Xalan library conflict

10 years ago

the problem is a soap call not authentication. this soap call could occurs anywhere and webnms will throw NPE (with interference of Xalan) in such places. you mean we should not use soap call in any place?isn't it a bug?

how can i handle this conflict? i did not get the answers of my previous post?

thanks again

Top Reply

Response title

Attachments

New to this Portal?