12 Replies Latest reply on Feb 24, 2007 8:40 AM by jjarkko

    juddi.war and publishing

    jjarkko Feb 6, 2007 5:55 PM

      Hello,
      I'm still having trouble understanding how to configure JBoss ESB to use juddi.war. Actually I'm failing to get juddi publish service to work properly. I'm using Eclipse Web Services Explorer to query / publish and it works OK againts http://uddi.xmethods.net/inquire so I'm assuming WSEplorer works ok.

      What ever I do all I get back is

      <?xml version='1.0' encoding='UTF-8'?>
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><authToken generic='2.0' operator='myOperator'><authInfo>authToken:B1AD0D50-B632-11DB-A386-8F03F23E54D1</authInfo></authToken></env:Body></env:Envelope>


      Query was: 
      <?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <uddiv2:get_authToken cred="password" generic="2.0" userID="jbossesb" xmlns:uddiv2="urn:uddi-org:api_v2"/>
 </soapenv:Body>
</soapenv:Envelope>


      And the same information in JBoss AS log: 
      00:37:58,328 INFO [STDOUT] 2007-02-07 00:37:58,328 [http-0.0.0.0-8080-2] INFO org.apache.juddi.datastore.jdbc.JDBCDataStore - Generated token 'authToken:B1AD0D50-B632-11DB-A386-8F03F23E54D1' for user: 'jbossesb/JBoss ESB User'


      Nothing else. It almost seems that the communication is interrupted or something wrong with the login? Does inquiry require login as it seems to work better?



      • 23514 Views
      • Tags:
        • 1. Re: juddi.war and publishing
          kurtstam
          kurtstam Feb 6, 2007 10:20 PM (in response to jjarkko)

          Hi Jarkko,

          I'm not sure what it is you're trying to do. You don't need the juddi.war for JBossESB to talk to juddi. By default we use an embedded protocol. However I think what you are doing is working just fine. You first send a username/passwd to get a autorization token. With that token in hand you can then do the real query.

          You may want to try http://uddibrowser.org to do some browsing.

          Hope this helps.

          --Kurt

            • Actions
          • 2. Re: juddi.war and publishing
            jjarkko Feb 7, 2007 1:51 AM (in response to jjarkko)

            Hello, And thanks for the answer.
            What I'm trying to do is I'm trying to use the ESB jUDDI to register additional WebServices in that directory. I wouldn't want to setup additional jUDDI for that.

              • Actions
            • 3. Re: juddi.war and publishing
              kurtstam
              kurtstam Feb 7, 2007 9:32 AM (in response to jjarkko)

              Hi Jarkko,

              Sure that sounds good to me, and that's the intended use. On the juddi mailing list someone posted a nice write on how to get juddi working on tomcat http://www.mail-archive.com/juddi-user@ws.apache.org/msg00576.html//www.mail-archive.com/juddi-user@ws.apache.org/msg00576.html
              Maybe that writeup can help you, since it is really juddi functionalilty you are trying to use. PLease let me know if that helps, we'll get you up an running one way on another!

              --Kurt

                • Actions
              • 4. Re: juddi.war and publishing
                jjarkko Feb 8, 2007 3:13 AM (in response to jjarkko)

                Thanks for the information. I'm still continuing the discussion in here instead Apache arenas. I assume that I'm supposed to use the juddi.war from install/jUDDI-registry. I tried to follow the instructions in docs/services/RegistryConfiguration.pdf Ch 2.4 SOAP. There are couple issues causing discomfort ;)
                First juddi.properties file is located in three different places


                default/conf/juddi.properties
                juddi.war/WEB-INF/juddi.properties
                juddi.war/WEB-INF/classes/juddi.properties

                When juddi.war is starting it says that it is reading configuration from WEB-INF/juddi.properties so maybe delete the one in classes directory? What about the one in conf directory? Who's using that one? So it's hard to determine which one to edit.

                Second: I had to explode juddi.war and edit juddi.war/WEB-INF/web.xml and comment out RegisterServicesWithJNDI servlet: 
                <!-- uncomment if you want to enable making calls in juddi with rmi -->
 <servlet>
 <servlet-name>RegisterServicesWithJNDI</servlet-name>
 <servlet-class>org.apache.juddi.registry.rmi.RegistrationService</servlet-class>
 <load-on-startup>1</load-on-startup>
</servlet>

                otherwise there's some conflict and error message is displayed in console log (dunno if it serious or not (but disturbing anyways ;) 
                10:06:39,273 INFO [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi.war/
10:06:40,188 INFO [STDOUT] 2007-02-08 10:06:40,187 [main] INFO org.apache.juddi.registry.rmi.JNDIRegistration - Creating Initial Context using:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming
10:06:40,196 INFO [STDOUT] 2007-02-08 10:06:40,196 [main] INFO org.apache.juddi.registry.rmi.JNDIRegistration - Setting /InquiryService, org.apache.juddi.registry.rmi.InquiryService
10:06:40,211 ERROR [STDERR] javax.naming.NameAlreadyBoundException
10:06:40,211 ERROR [STDERR] at org.jnp.server.NamingServer.bind(NamingServer.java:144)
10:06:40,211 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:06:40,211 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:06:40,211 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,211 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,211 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
10:06:40,211 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.java:153)
10:06:40,212 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
10:06:40,212 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
10:06:40,212 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
10:06:40,212 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
10:06:40,212 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
10:06:40,212 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
10:06:40,212 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
10:06:40,212 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
10:06:40,212 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.bind(Unknown Source)
10:06:40,212 ERROR [STDERR] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:566)
10:06:40,212 ERROR [STDERR] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:531)
10:06:40,212 ERROR [STDERR] at javax.naming.InitialContext.bind(InitialContext.java:359)
10:06:40,212 ERROR [STDERR] at org.apache.juddi.registry.rmi.JNDIRegistration.register(JNDIRegistration.java:74)
10:06:40,212 ERROR [STDERR] at org.apache.juddi.registry.rmi.RegistrationService.init(RegistrationService.java:36)
10:06:40,212 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:211)
10:06:40,212 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
10:06:40,212 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932)
10:06:40,212 ERROR [STDERR] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3951)
10:06:40,212 ERROR [STDERR] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4225)
10:06:40,213 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
10:06:40,213 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
10:06:40,213 ERROR [STDERR] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
10:06:40,213 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:06:40,213 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:06:40,213 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,213 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,213 ERROR [STDERR] at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
10:06:40,213 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
10:06:40,213 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,213 ERROR [STDERR] at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
10:06:40,213 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:06:40,213 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:06:40,213 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,213 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,213 ERROR [STDERR] at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,214 ERROR [STDERR] at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
10:06:40,214 ERROR [STDERR] at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
10:06:40,214 ERROR [STDERR] at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
10:06:40,214 ERROR [STDERR] at org.jboss.web.WebModule.startModule(WebModule.java:83)
10:06:40,214 ERROR [STDERR] at org.jboss.web.WebModule.startService(WebModule.java:61)
10:06:40,214 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
10:06:40,214 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
10:06:40,214 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
10:06:40,214 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,214 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
10:06:40,214 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,632 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,632 ERROR [STDERR] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
10:06:40,632 ERROR [STDERR] at $Proxy0.start(Unknown Source)
10:06:40,632 ERROR [STDERR] at org.jboss.system.ServiceController.start(ServiceController.java:417)
10:06:40,632 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
10:06:40,632 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,632 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,632 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,632 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
10:06:40,633 ERROR [STDERR] at $Proxy42.start(Unknown Source)
10:06:40,633 ERROR [STDERR] at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
10:06:40,633 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:06:40,633 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:06:40,633 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,633 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
10:06:40,633 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
10:06:40,634 ERROR [STDERR] at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
10:06:40,634 ERROR [STDERR] at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
10:06:40,634 ERROR [STDERR] at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
10:06:40,634 ERROR [STDERR] at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
10:06:40,634 ERROR [STDERR] at $Proxy43.start(Unknown Source)
10:06:40,634 ERROR [STDERR] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
10:06:40,634 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
10:06:40,634 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
10:06:40,634 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
10:06:40,634 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,634 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,634 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,676 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
10:06:40,677 ERROR [STDERR] at $Proxy8.deploy(Unknown Source)
10:06:40,677 ERROR [STDERR] at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
10:06:40,677 ERROR [STDERR] at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
10:06:40,677 ERROR [STDERR] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
10:06:40,677 ERROR [STDERR] at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
10:06:40,677 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
10:06:40,677 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
10:06:40,677 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
10:06:40,677 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,677 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,677 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,678 ERROR [STDERR] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
10:06:40,678 ERROR [STDERR] at $Proxy0.start(Unknown Source)
10:06:40,678 ERROR [STDERR] at org.jboss.system.ServiceController.start(ServiceController.java:417)
10:06:40,678 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
10:06:40,678 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,678 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,678 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,679 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
10:06:40,679 ERROR [STDERR] at $Proxy4.start(Unknown Source)
10:06:40,679 ERROR [STDERR] at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
10:06:40,679 ERROR [STDERR] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
10:06:40,679 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
10:06:40,679 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
10:06:40,726 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
10:06:40,726 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:06:40,726 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
10:06:40,726 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
10:06:40,726 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
10:06:40,726 ERROR [STDERR] at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
10:06:40,726 ERROR [STDERR] at $Proxy5.deploy(Unknown Source)
10:06:40,727 ERROR [STDERR] at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
10:06:40,727 ERROR [STDERR] at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
10:06:40,727 ERROR [STDERR] at org.jboss.Main.boot(Main.java:200)
10:06:40,727 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:490)
10:06:40,727 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
10:06:40,732 INFO [STDOUT] 2007-02-08 10:06:40,732 [main] INFO org.apache.juddi.registry.RegistryServlet - Loading jUDDI configuration.
10:06:40,736 INFO [STDOUT] 2007-02-08 10:06:40,736 [main] INFO org.apache.juddi.registry.RegistryServlet - Resources loaded from: /WEB-INF/juddi.properties
10:06:40,736 INFO [STDOUT] 2007-02-08 10:06:40,736 [main] INFO org.apache.juddi.registry.RegistryServlet - Initializing jUDDI components.



                Is juddi-users.xml used when using the juddi.war from JBoss ESB distribution? Somehow it bypasses information in there and goes to somewhere else ( jbossesb/password seem to work). juddi.auth states that DefaultAuthenticator should be used, but it looks pretty weird (unknown where) http://www.docjar.com/html/api/org/apache/juddi/auth/DefaultAuthenticator.java.html


                  • Actions
                • 5. Re: juddi.war and publishing
                  kurtstam
                  kurtstam Feb 8, 2007 10:10 AM (in response to jjarkko)

                  1. juddi.properties in multiple places

                  This one in default/conf is used when running in embedded mode. The ones in the war are supposed to be used by the war. Only one of them is actually used, so yes deleting the one in the classes directory is the right thing to do. I think I will remove that one al together.

                  2. We now already register the the juddi publish and query services in the sar. So if you deploy the war to the same server you should comment out the 'load-on-startup' RegistrationService in the web.xml, as it is bound already.

                  3. I think by default it only looks for an exising publisher username. I don't think juddi-users.xml is used by default.

                  Did you try the brower? Is that working for you now?

                  --K

                    • Actions
                  • 6. Re: juddi.war and publishing
                    kurtstam
                    kurtstam Feb 8, 2007 10:15 AM (in response to jjarkko)

                    BTW some people also use the eclipse webservice explorer. I have not tried that yet, but that should work too.

                      • Actions
                    • 7. Re: juddi.war and publishing
                      jjarkko Feb 18, 2007 5:43 PM (in response to jjarkko)

                      I'm using Eclipse Web Services Explorer per instructions from http://help.eclipse.org/help32/topic/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html.

                      Just doesn't work ;) From watching the traffic between Eclipse and juddi.war it seems that there is no more traffic after the login/authentication request/response SOAP call.
                      E.g. only one request to get the authentication token (which is successful).

                      I've also found this
                      http://www.nabble.com/Creating-and-publishing-Web-Services-to-jUDDI-tf2128286.html,
                      which is basically the same information.

                        • Actions
                      • 8. Re: juddi.war and publishing
                        jjarkko Feb 18, 2007 5:46 PM (in response to jjarkko)

                        And I've been using the juddi.war/jar from JBoss ESB 4.0GA.. Which includes a modified version of juddi 0.94rc4, right?

                        I also tried with the Eclipse WTP (Web Tools Platform) http://www.eclipse.org/webtools/main.php to see if it's a problem with Eclipse, but even the devel latest version (2.0M4) behaved the same.

                          • Actions
                        • 9. Re: juddi.war and publishing
                          kurtstam
                          kurtstam Feb 19, 2007 1:00 PM (in response to jjarkko)

                          Yes the juddi.war contains the code on the trunk of the juddi SVN. I previously successfully tested the uddibrowser. I retry and post the steps.

                            • Actions
                          • 10. Re: juddi.war and publishing
                            kurtstam
                            kurtstam Feb 21, 2007 12:17 PM (in response to jjarkko)

                            Hi Jarkko,

                            I just tried it again and it looks that eventough I fixed jUDDI so it runs in embedded mode when deployed to JBoss, this does in fact not fix (most of the) SOAP requests. It's one of those situations where the JBoss SOAP stack tries to do the 'right' thing, which bites us now and it makes things fail. For the time being the workaround is to deploy the juddi.war to tomcat and have it point to the same juddi database.

                            --Kurt

                              • Actions
                            • 11. Re: juddi.war and publishing
                              kurtstam
                              kurtstam Feb 21, 2007 2:41 PM (in response to jjarkko)

                              I opened an issue in jUDDI's jira: https://issues.apache.org/jira/browse/JUDDI-99

                              --Kurt

                                • Actions
                              • 12. Re: juddi.war and publishing
                                jjarkko Feb 24, 2007 8:40 AM (in response to jjarkko)

                                I finally managed to create a working juddi environment from juddi.war from JBoss ESB product/install/jUDDI-registry/. The problem is not with Eclipse Web Services Explorer or (as it seems) with the juddi.war but with JBossWS/SOAP doing the 'right thing' ;)

                                To make juddi.war work I used jaxrpc.jar and saaj.jar from BIRT runtime environment ( which I guess are pretty standard ) instead of the ones found in JBoss AS 4.0.5GA installation ( client/jboss-saaj.jar, client/jboss-jaxrpc.jar).

                                I guess I could deploy the juddi.war containing the standard(?) saaj.jar and jaxrpc.jar (to override the JBoss SOAP stack) in a JBoss AS installation also, I'll check that and if JBoss ESB can us this juddi installation through it's "internal(RMI?)" transport.

                                Looking for: javax.xml.soap.SOAPMessage
+Found in: /home/jarkko/uddi/apache-tomcat-5.5.20/webapps/juddi/WEB-INF/lib/saaj.jar
Looking for: javax.xml.rpc.Service
+Found in: /home/jarkko/uddi/apache-tomcat-5.5.20/webapps/juddi/WEB-INF/lib/jaxrpc.jar
Looking for: com.ibm.wsdl.factory.WSDLFactoryImpl


                                  • Actions