Alix, the UDDI Browser requires UDDI4j to access a UDDI registry - it's
the only option. I use it regularly to test/validate code changes to the
jUDDI registry.
So, the UDDI Browser does not use jUDDI but may connect to a jUDDI
registry or any UDDI registry.
Steve
-----Original Message-----
From: Alix Pouladdej [mailto:alixpyh@yahoo.com]
Sent: Thursday, February 24, 2005 12:13 PM
To: juddi-user@ws.apache.org
Subject: RE: "inquiry" and "publish" deployment for juddi
Steve,
I guess my problem is that I have a juddi set up for my UDDI and
I was trying to access it with the UDDI browser using the following SOAP
transports:
TransportClassName=org.uddi4j.transport.ApacheSOAPTransport
or
TransportClassName=org.uddi4j.transport.ApacheAXISTransport
(after I had included the axis.jar in the browser classpath).
Not surprizingly
I get a number of java.lang.NullPointerException.
Initially I had mistakingly used the following transport class
TransportClassName=org.juddi.transport.ApacheAXISTransport.
This does NOT exist!!! as juddi.jar does not have such a class.
Does anyone know of a UDDI browser that I could use with juddi.
I downloaded the browser from uddibrowser.org which seems to be
specific to uddi4j, I think.
So basically, my problem is that I have successfully installed
juddi and can access its DataSource with a servlet, but what I need to
be able to do is
to inquire and publish with a client and a uddi-browser. Any
suggestions that you may have is appreciated.
Thanks,
Alix
"Viens, Stephen" <Stephen.Viens@LibertyMutual.com> wrote:
Alix,
You've got a UDDIBrowser classpath problem. UDDIBrowser
is looking for
the class "org/apache/axis/AxisFault" but the axis.jar
file is not in
your classpath so it's unable to locate it.
Here's what's in your classpath:
lib\activation.jar;
lib\BCEL.jar;
lib\bsf.jar;
lib\imap.jar;
lib\java_cup.jar;
lib\JLex.jar;
lib\mailapi.jar;
lib\pop3.jar;
lib\regexp.jar;
lib\runtime.jar;
lib\servlet-2_3-fcs-classfiles.zip;
lib\smtp.jar;
lib\soap.jar;
lib\uddi4j.jar;
lib\xalan.jar;
lib\xalanservlet.jar;
lib\xercesImpl.jar;
lib\xmisoap.jar;
lib\xml-apis.jar;
lib\xmlParserAPIs.jar;
lib\xsltc.jar;
lib\jsse.jar;
lib\ub.jar;
C:\me\dev\uddi4j\samples
Also, which SOAP transport have you specified in the
confing/soap-transport.prop file? It looks as though you
have
org.uddi4j.transport.ApacheSOAPTransport specified which
would require
that Axis be in the classpath.
Steve
-----Original Message-----
From: Alix Pouladdej [mailto:alixpyh@yahoo.com]
Sent: Thursday, February 24, 2005 10:17 AM
To: juddi-user@ws.apache.org; steve@viens.net
Subject: RE: "inquiry" and "publish" deployment for
juddi
Thanks Steve. My problem is that I am trying to set up
registry
parameters
for juddi to be able to access it through an external
client (I will
adopt one
from uddi4j). But the problem I am having now is that
eventhough I have
set up juddi properly and can access its database
through happyjudy.jsp
and a database servlet, I can't access it through a
uddi-browser
(uddibrowser.org). I am trying to use the browser to set
the inquiry and
publish parameters for the juddi.
I get the following errors:
D:\uddi_browser>java -Xmx30m -cp
"lib\activation.jar;lib\BCEL.jar;lib\bsf.jar;li
b\imap.jar;lib\java_cup.jar;lib\JLex.jar;lib\mailapi.jar;lib\pop3.jar;li
b\regexp
.jar;lib\runtime.jar;lib\servlet-2_3-fcs-classfiles.zip;lib\smtp.jar;lib
\soap.ja
r;lib\uddi4j.jar;lib\xalan.jar;lib\xalanservlet.jar;lib\xercesImpl.jar;l
ib\xmiso
ap.jar;lib\xml-apis.jar;lib\xmlParserAPIs.jar;lib\xsltc.jar;lib\jsse.jar
;lib\ub.
jar;C:\me\dev\uddi4j\samples"
org.uddibrowser.UDDIBrowser
Exception in thread "Thread-3"
java.lang.NoClassDefFoundError:
org/apache/axis/A
xisFault
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.uddi4j.transport.TransportFactory.getTransport(Unknown
Source)
at org.uddi4j.client.UDDIProxy.send(Unknown Source)
at org.uddi4j.client.UDDIProxy.find_business(Unknown
Source)
at
org.uddibrowser.uddi.UDDIWrapper.findBusiness(UDDIWrapper.java:477)
at
org.uddibrowser.RegistryActionController.processRead(RegistryActionCo
ntroller.java:500)
at
org.uddibrowser.RegistryActionController.asyncWork(RegistryActionCont
roller.java:471)
at
org.uddibrowser.RegistryActionController.access$000(RegistryActionCon
troller.java:76)
at
org.uddibrowser.RegistryActionController$1.construct(RegistryActionCo
ntroller.java:354)
at
org.uddibrowser.ui.SwingWorker$2.run(SwingWorker.java:137)
at java.lang.Thread.run(Thread.java:595)
Steve Viens wrote:
Alix,
The "juddi.proxy.xxxx" properties are used by the jUDDI
proxy (an
alternative to UDDI4j) and are not used or referenced by
the jUDDI
server.
Unfortunately setting them will not help you solve the
UDDI4j
configuration problem you're experiencing.
Steve
-----Original Message-----
From: Alix Pouladdej [mailto:alixpyh@yahoo.com]
Sent: Wednesday, February 23, 2005 3:14 PM
To: juddi-user@ws.apache.org
Subject: "inquiry" and "publish" deployment for juddi
To follow up with my earlier problem of :
java.net.MalformedURLException
at java.net.URL.(URL.java:601)
at java.net.URL.(URL.java:464)
at java.net.URL.(URL.java:413)
at org.uddi4j.client.UDDIProxy.setInquiryURL(Unknown
Source)
at FindBusinessExample.run(FindBusinessExample.java:63)
at FindBusinessExample.main(FindBusinessExample.java:46)
having given the following:
# jUDDI Proxy Properties (used by RegistryProxy)
juddi.proxy.adminURL = http://localhost:8080/juddi/admin
juddi.proxy.inquiryURL =
http://localhost:8080/juddi/inquiry
juddi.proxy.publishURL =
http://localhost:8080/juddi/publish
juddi.proxy.transportClass =
org.apache.juddi.proxy.AxisTransport
juddi.proxy.securityProvider =
com.sun.net.ssl.internal.ssl.Provider
juddi.proxy.protocolHandler =
com.sun.net.ssl.internal.www.protocol
from juddi.properties file.
Does one need to explicitly activate "inquiry" and
"publish"
functionality for juddi after a juddi server
installation?
Thanks,
ALEX
Post your free ad now! Yahoo! Canada Personals
Post your free ad now! Yahoo! Canada Personals
________________________________
Post your free ad now! Yahoo! Canada Personals
<http://ca.personals.yahoo.com/>
|