Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

org.apache.juddi.v3.client.transport.TransportException: Cannot locate uddi.properties

 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
trying to call the following code to obtain a security token from juddi.
Every time I call it I get the following error message:
org.apache.juddi.v3.client.transport.TransportException: Cannot locate configuration source uddi.properties

I have looked on the web for an example of this file, and could not find one.
I have found out that it is used by the client to enable it to communicate with the register using JAX-WS.
I als found out that you can set the transport type used to talk to the register.

I currently have the following jar files within my class path:-
commons-configuration-1.5.jar
log4j-1.2.13.jar
commons-logging-1.1.jar
uddi-client-3.0.0.rc1.jar
uddi-ws-3.0.0.jar
commons-lang-2.3.jar
commons-collections-3.2.1.jar



Has anybody got or seen an example of the contents of a uddi.properties file

Mat
 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
can anybody explain what the content of a uddi.properties file should look like, or an example would be good.
If nobody can answer this or it's too easy, can you point me to a site that could help solve this problem.

Mat
 
Mat Anthony
Ranch Hand
Posts: 261
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
for anybody that is interested, I gave up on my initial approach . Instead I'm using the axis binary stack to generate
the client java files that are used to call Juddi. I can access the services available on Juddi via the 'View Service Listing' link.
I then click on one of the service addresses (i.e. UDDI Security) so that I capture the wsdl url. Next I created a
CodeGenerator class and added in the captured url (i.e. http://localhost:8080/juddiv3/services/security?wsdl)


Before I was able to run the above code I needed to put the Axis jar files within the classpath so that
import org.apache.axis2.wsdl.WSDL2Code
could be seen.

The CodeGenerator will generate axis stubs and handler classes that allow you to call the juddi api's via JAX-WS.

The code below shows how a client can make a call to the juddi get_authToken api.
Note that you will have to put the stub generated classes in the classpath of this build for it to work.


This approach seems a lot easier than my initial attempts and is driven by the wsdl from the juddi.
Hence the client can be built another language.

Hope this helps anybody who had the problem I had.

Mat



 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic