1 2 Previous Next 18 Replies Latest reply on Mar 29, 2005 8:21 AM by Vaughn T. Combs

    jUDDI part of JBoss 4.0?

    Nikolaos Oikonomidis Newbie

      Hi all,

      I'm a bit confused about the support of jUDDI. Is it integrated in the current version (4.0.1) or not?

      Thanks in advance,
      Nikos

        • 1. Re: jUDDI part of JBoss 4.0?
          Anil Saldanha Master

          No. We are in the process of bringing it back!!!

          • 2. Re: jUDDI part of JBoss 4.0?
            Vaughn T. Combs Newbie

            Can you tell me in which version of JBoss was jUDDI included before it was taken out?

            Many Thanks,
            Vaughn

            • 3. Re: jUDDI part of JBoss 4.0?
              Anil Saldanha Master

              I think it was starting with JBoss 3.2.5, juddi was removed. It is not included in JBoss 4.0. It currently is available in JBoss 5.0 (in cvs HEAD).

              Do you have immediate need to use jUDDI with Jboss 4.0? If yes, I can post a wiki page with instructions to integrate juddi into v4.0. Its pretty simple to do. But I need to test it out.

              Before that, I need answers to the following questions:
              a) Why do you need jUDDI?
              b) How do you plan to access jUDDI (that is integrated with JBoss)? (Via UDDI4J or Apache Scout?)
              c) Are you looking for jUDDI in Jboss for research/prototype kind of projects or you are seriously looking to use in internal projects?

              I need answers to the above questions because then I can decide whether spending some time to write instructions on integrating jUDDI in V4.0 is worthwhile.

              Keep the faith.

              • 4. Re: jUDDI part of JBoss 4.0?
                Vaughn T. Combs Newbie

                Wonderful!

                First, thanks for the speedy and very helpful reply.

                a.) We are working internally on a research project in the area of information management and have developed a number of web services that we currently have deployed within 4.0.1. We would like to experiment with using UDDI as a discovery mechanism in order to dynamically interract with our platform components.

                b.) Initally we would probably use UDDI4J but ultimately would move to Scout as we would like to abstract away the underlying discovery technologies (UDDI, ebXML, etc.).

                c.) Currently I would put this in the research/prototype category but we have had great success with JBoss and have distributed our current implementation to approximately 50 collaborating researchers. Counting previous releases we are probably over the 400 mark. In all cases we have used previous versions of JBoss.

                Yes. I would very much like to get Juddi up and running once again.

                If you would like more information I would be glad to discuss the project with you.

                Many Thanks,
                Vaughn

                • 5. Re: jUDDI part of JBoss 4.0?
                  Anil Saldanha Master

                  Hi Vaughn,
                  thanks for the lucid description. Because of your comment wrt your wonderful experiences with Jboss, I will get you the instructions to integrate juddi in v4.0 in 2-3 days.

                  I will not do anything magical, just take the juddi-service.sar from the 5.0 workspace and deploy it in v4.0. But you will get the instructions. :-)

                  It will be a few months before jUDDI will be officially part of v4.0

                  Cheers,
                  Anil

                  • 6. Re: jUDDI part of JBoss 4.0?
                    Vaughn T. Combs Newbie

                    Many thanks!

                    I look forward to using jUDDI as soon as you can make it available.

                    BTW, if you are interested in the project that we working on please feel free to browse the publicly available web site. We are in the process of updating the site a bit (i.e. we are at version 1.2.0 now) but it will certainly give you plenty of information.

                    http://www.rl.af.mil/programs/jbi/


                    Take Care and, again, thank you for your efforts,
                    Vaughn

                    • 7. Re: jUDDI part of JBoss 4.0?
                      Anil Saldanha Master

                      http://www.jboss.org/wiki/Wiki.jsp?page=JAXR

                      I have given the instructions to integrate juddi into JBoss v4.0.1

                      These just discuss integrating jUDDI into JBoss. I am assuming that you will use UDDI4J or (optionally) Scout to access jUDDI.

                      If you need more info on using Scout with jUDDI, ask on this thread.

                      Both jUDDI and Scout are licensed by Apache Software Foundation.
                      http://ws.apache.org/LICENSE.txt

                      • 8. Re: jUDDI part of JBoss 4.0?
                        Vaughn T. Combs Newbie

                        Up and running without so much as a burp!

                        You RULE!

                        • 9. Re: jUDDI part of JBoss 4.0?
                          Anil Saldanha Master

                          I am glad that it worked out for you.

                          Is it possible for you to contribute back a case story on how you used JBoss/jUDDI in your project, when you are ready?

                          Remember both jUDDI and Scout will have updates and the wiki page will be the ultimate reference as to what is happening in the Jaxr integration space in JBoss.

                          • 10. Re: jUDDI part of JBoss 4.0?
                            Mackenna Dsouza Newbie

                            Hi Anil

                            I am a newbie to Juddi and this may be more a Juddi question rather than a Jboss question, but I thought it may be relevant to this thread.

                            I followed the instructions on the integration of Juddi with JBoss and am able to connect to the registry using the uddi browser.

                            A search for all businesses returns a valid soap message with no businesses in the registry (I anticipate that I am using the inquiry servlet ).

                            Subsequently when I try to add a business (publish), I get the following error from the JbossJuddiAxisProcessor

                            "The user ID and password pair passed in a get_authToken message is not known to the Operator Site or is not valid"

                            I am using PostGreSQL - the publisher table has only one row - with the dbowner entry.

                            My question is would addition of a new entry in the publisher solve the problem ( add row using SQL ), or are there more tasks that I need to do to get started.

                            I am working on exploring Juddi + JBoss as a private registry of services within a hub.

                            Thanks
                            Mackenna Dsouza

                            • 11. Re: jUDDI part of JBoss 4.0?
                              Anil Saldanha Master

                              Hi Mackenna,
                              the database creation scripts are in juddi-service.sar/META-INF You can have a look at what tables are created and what data is inserted.

                              INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,EMAIL_ADDRESS,ENABLED,ADMIN) VALUES ('jboss','JBoss User','jboss@xxx','true','true');


                              So 'jboss' is an authorized userid for juddi in my installation.

                              Similarly, u can add userids to the publisher table.

                              Currently, juddi does not have default authentication. You can create one
                              http://wiki.apache.org/ws/Create_20a_20custom_20jUDDI_20Authenticator

                              • 12. Re: jUDDI part of JBoss 4.0?
                                Mackenna Dsouza Newbie

                                Hi Anil

                                I got JUddi up and running, thanks for the tip. I used my dbowner account that was created in the publisher table. Will add another system account subsequently

                                Anyways, I have been toying around with Scout as the JAXR implementation of choice. I am getting some errors in the creation of an organization.

                                My client app is a simple Java application that is connecting to the IBM test registry ( and also the local JUddi registry ).

                                From the error, I am anticipating the problem to be in the UDDI message generated where in the businessentity tag does not have the businessKey attribute which is causing a parse error.

                                I tried adding a "Key" and it went through ( brute force ), but the key should be generated by the UDDI registry and gave me an error when it started to lookup the organization/businessentity in the registry with the given key for an update ( as per my understanding )

                                Any pointers ?

                                The stack trace :

                                AxisFault
                                faultCode: Client
                                faultSubcode:
                                faultString: Client Error
                                faultActor:
                                faultNode:
                                faultDetail:
                                {urn:uddi-org:api_v2}dispositionReport: E_fatalError (10500) Serious technical error has occurred while processing the request. cvc-complex-type.4: Attribute 'businessKey' must appear on element 'businessEntity'.

                                Client Error
                                at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:260)
                                at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:169)
                                at org.apache.axis.encoding.DeserializationContextImpl.endElement(DeserializationContextImpl.java:1015)
                                at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
                                at org.apache.crimson.parser.Parser2.content(Unknown Source)
                                at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
                                at org.apache.crimson.parser.Parser2.content(Unknown Source)
                                at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
                                at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
                                at org.apache.crimson.parser.Parser2.parse(Unknown Source)
                                at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
                                at javax.xml.parsers.SAXParser.parse(Unknown Source)
                                at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)
                                at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
                                at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
                                at org.apache.axis.client.Call.invokeEngine(Call.java:2583)
                                at org.apache.axis.client.Call.invoke(Call.java:2553)
                                at org.apache.axis.client.Call.invoke(Call.java:1672)
                                at org.apache.juddi.proxy.AxisTransport.send(AxisTransport.java:73)
                                at org.apache.juddi.proxy.RegistryProxy.execute(RegistryProxy.java:443)
                                at org.apache.juddi.AbstractRegistry.saveBusiness(AbstractRegistry.java:582)
                                at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.executeOperation(BusinessLifeCycleManagerImpl.java:459)
                                at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.saveOrganizations(BusinessLifeCycleManagerImpl.java:321)
                                at udditest.ConnectToRegistry.main(ConnectToRegistry.java:98)

                                • 13. Re: jUDDI part of JBoss 4.0?
                                  Anil Saldanha Master

                                  You are using Crimson parser that comes with JDK. You should be using Xerces parser. Provide a system property "java.endorsed.dirs" that points to a location where the xerces jars are. One place you can obtain the xerces jars are in jboss-xxx/lib/endorsed dir.

                                  • 14. Re: jUDDI part of JBoss 4.0?
                                    Mackenna Dsouza Newbie

                                    Hi Anil

                                    I have used UDDI4J successfully to register organizations in the directory. Will get back to the Scout implementation once I am done with the UDDI4J client implementation.

                                    Thank you for the tips.

                                    Mackenna

                                    1 2 Previous Next