2 Replies Latest reply on Jul 16, 2009 5:40 AM by kconner

    Problems with Scout/jUDDI

      I have a problem using the scout.jar file.

      I registered an external web service (using "http" as access point type and the WSDL-URL as access point url) to juddi using the UDDI Browser. After that I started the ESB and got a class cast exception when trying to find the external service. I figured out that there's a problem in the current scout.jar which was solved in the current version of scout (scout-1.0.jar).
      I replaced the jar-file and started the ESB again and the there was no error.
      For testing purposes I then deployed the HelloWorld example and got an error that the Service could not be found in the registry.


      org.jboss.soa.esb.services.registry.RegistryException: No such EPR found for service with name = SimpleListener and EPR=JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_helloesb_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]
      at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.unRegisterEPR(JAXRRegistryImpl.java:214)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)



      When I look in the registry database I can see the service is being "deployed" in the database properly. The only difference is that the portReference in the table BINDING_TEMPLATE has a prefix containing the namespace:

      <wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      Does the current implementation of scout behave differently from the old one in finding internal and external services?

      Thanks in advance,


      Marcus

        • 1. Re: Problems with Scout/jUDDI
          kconner

          Moving to user forum

          • 2. Re: Problems with Scout/jUDDI
            kconner

            The EPR usage is is not related to scout, rather it is the way in which we bind services into the registry. The only purpose of the entries in those sections of the registry is to publicise ESB (internal) services to other ESB aware clients.

            We have never supported lookup of external services through the registry, even though the http gateway does register one.