Hi guys,

 

We’re picking up the UDDI again, and I’m having some difficulties authenticating.

 

I’m using jUDDI v0.9 rc 3 on Jonas. I had some JNDI issues at first, but managed to configure it correctly now. jUDDI happiness page shows everything should be ok.

I inserted 2 publishers (juddi and admin). When I try to get and authorization token with uddi4j, things start to fail.

 

Doesn’t matter whether I use ‘admin’ or ‘juddi’ to authenticate (both in publishers), I always get a serverexception.

 

Here are the errors:

*********** Running BusinessServiceExample ***********

 

Get authtoken

TransportFactory: Using transport name:org.uddi4j.transport.ApacheAxisTransport

 

Request message:

<ns1:get_authToken generic="2.0" xmlns="urn:uddi-org:api_v2" userID="admin" cred="password" xmlns:ns1="urn:uddi-org:api_v2"/>

 

Response message:

<soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:Server</faultcode><faultstring>Server Error</faultstring><detail><ns2:stackTrace xmlns:ns2="http://xml.apache.org/axis/">Server Error

            at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:470)

            at org.apache.axis.server.AxisServer.invoke(AxisServer.java:285)

            …

 

</ns2:stackTrace><ns3:hostname xmlns:ns3="http://xml.apache.org/axis/">ws03-bpel</ns3:hostname></detail></soapenv:Fault>

Server Error

            at org.uddi4j.UDDIElement.<init>(UDDIElement.java:38)

            at org.uddi4j.response.AuthToken.<init>(AuthToken.java:84)

            at org.uddi4j.client.UDDIProxy.get_authToken(UDDIProxy.java:1459)

            at uddi4j.samples.BusinessServiceExample.run(BusinessServiceExample.java:78)

            …

 

Am I forgetting something, or what could be a configuration error?

 

Kind regards,

 

Dylan Honorez

_______________________________________________

 

                  kZEN | 4C

Researcher & Developer | Integration Consultant

_______________________________________________

 

Reply via email to