jUDDI Console

[tobysaville]

Hello,

I am using JBoss ESB 4.2.1GA Server bundle. I am trying to execute a get_registryInfo query from the jUDDI console, however i get the following stack trace on the server:

10:43:18,300 INFO [STDOUT] 2007-11-15 10:43:18,285 [http-127.0.0.1-8080-2] ERROR org.apache.juddi.registry.AbstractService - org.jboss.ws.core.soap.TextImpl
java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl
 at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:103)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
 at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
 at java.lang.Thread.run(Thread.java:595)
10:43:18,300 INFO [STDOUT] 2007-11-15 10:43:18,300 [http-127.0.0.1-8080-2] ERROR org.apache.juddi.registry.AbstractService - A serious error has occured while assembling the SOAP Fault.
javax.xml.soap.SOAPException: Fault code 'Server' must be namespace qualified
 at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:191)
 at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:175)
 at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:317)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
 at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
 at java.lang.Thread.run(Thread.java:595)

any suggestions?

cheers,
Toby

[kurtstam]

Hi Toby,

The jUDDI console was never really indented to be used as a user console, more like a developer test console. I would suggest you take a look at the uddibrowser.

I have added some text and screen shots in the latest Registry doc. See
http://anonsvn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_2_1_GA_CP/product/docs/services/Registry.pdf

Hope that helps.

--Kurt

[kurtstam]

I forgot to mention to look for the chapter called UDDI Browser. Somehow the pdf has not updated yet, but the open document version is.

http://anonsvn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_2_1_GA_CP/product/docs/services/

[domkun]

Hi,

I had the same problem.
But during the deployment I saw following output:

12:01:00,765 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../tmp/deploy/tmp29448juddi-exp.war/
12:01:01,218 INFO [RegistryServlet] Loading jUDDI configuration.
12:01:01,218 INFO [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties

To solve the problem I modified the juddi.war from svn/trunk.

I replaced the juddi.properties file in the WEB-INF directory of juddi.war with the contents of ${jboss.esb.server.4.2.1GA.home}\server\default\deploy\jbossesb.sar\esb.juddi.xml

Then redeployed it. After that I was able to browse through the registry with the uddibrowser.

Greetings,
Dominik

[kurtstam]

Actually you can remove both the juddi.jar and the juddi.properties file from the war altogether, since we're deploying it to the jbossesb.sar and both are already there. (I also just changed this in the SVN yesterday).

--Kurt

[domkun]

Thanks for the hint, Kurt! Works like a charm :)

[tobysaville]

thanks Kurt, ill take a look at those docs - ive installed uddibrowser already, but had trouble connecting, hopefully there is info in the ODFs to help me.

any ideas why the JMXOPERATION table wasnt created automatically? The other three are created, even when i dont have management.esb deployed.

- Tobes

[tobysaville]

and thanks for the solution re the juddi jar & properties files.

also, thanks domkun for your help :)

- tobes

[tobysaville]

and forget my question about the JMXOPERATION table. ive got so many posts going here, i lose track of what im submitting...