axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Pannier" <>
Subject Bug 15288
Date Thu, 12 Dec 2002 15:31:41 GMT
I have entered a new bug report for a problem I encountered with AXIS
1.1Beta.  I'm not sure how the
whole Bugzilla bug-reporting process works, but I'll go ahead and
re-describe the problem here.

I'm doing UDDI registry access/publish operations using UDDI4J.  I am
using AXIS as the SOAP
transport.  Since I'm doing publish operations (using https), my UDDI
client program uses JSSE as
the security provider (*).  When I upgraded from AXIS 1.0
(which was working fine)
to AXIS 1.1Beta, I got the following NullPointerException:

TransportFactory: Using transport

Request message:
<get_authToken cred="myCred" generic="2.0" userID="myUserid" xmlns

Response message:
<ns1:Fault xmlns:ns1="">
    <ns1:stackTrace xmlns:ns1="

     at org.apache.axis.SimpleChain.doVisiting(
     at org.apache.axis.SimpleChain.invoke(
     at org.apache.axis.client.AxisClient.invoke(
     at org.apache.axis.client.Call.invokeEngine(
     at org.apache.axis.client.Call.invoke(
     at org.apache.axis.client.Call.invoke(
     at org.uddi4j.transport.ApacheAxisTransport.send(Unknown Source)
     at org.uddi4j.transport.TransportBase.send(Unknown Source)
     at org.uddi4j.client.UDDIProxy.send(Unknown Source)
     at org.uddi4j.client.UDDIProxy.get_authToken(Unknown Source)

In looking at the AXIS source code, I see there has been changes made to
the package.
When I did some minimal debugging to see what was going on in
SocketFactoryFactory.getFactory(), I found
that it's returning NULL (which causes the exception in
HTTPSender.getSocket) because
AxisProperties.newInstance(SecureSocketFactory.class...) returns NULL.  It
looks like the "discovery"
mechanism in the o.a.a.AxisProperties class is failing to discover the
secure socket factory.

I didn't take it any further than that, as I'm not an expert in
JSSE/SSL/security, plus I'm not sure what the intent of
the changes to the socket/discovery code is.  So I don't know if this is
really a bug, or if there is a way for me to
change some configuration parameter in AXIS to correct this.

At any rate, my description in Bugzilla states that I would attach a test
case in an email to the axis-dev list.  The
attached JAR contains a test case showing the above problem.

(See attached file: Bug-15288-TestCase.jar)

Steve Pannier
Jacada, Inc.
(763) 201-0002 Ext. 219

View raw message