10 Replies Latest reply on Dec 28, 2007 4:55 PM by Mark Little

    JBoss ESB 4.2.1 server libs

    Vinicius Carvalho Apprentice

      Just a dummy question here. I'm using jboss-esb-4.2.1 server since the installation of the esb on a jboss as 4.2.1 with jboss-messaging 1.4.0SP1 caused a lot of version problems (I'm still thankful for the support here that helped me to solve it).
      But, the server version, seems to be missing a few libs (that I configure on my IDE):
      a few that I missed:

      jboss-ejb3.jar from ejb3.depoyer (which is not there)
      jnp-client from the client libs

      What happened to them? I'm using those libs from another jboss installation, but I'm affraid I get another version problem nightmare.

      Best regards

        • 1. Re: JBoss ESB 4.2.1 server libs
          Vinicius Carvalho Apprentice

          Well, the jbossesb-server does not deploys ejb3...
          Really running out of options here...

          • 2. Re: JBoss ESB 4.2.1 server libs
            Vinicius Carvalho Apprentice

            Sorry all for the message spam.
            But it's really frustrating trying to get jboss esb to work. I've risk a lot on our project just to get it working, and yet, everytime I think I solve an issue, another rise. It's such a nightmare :(

            JBossESB standalone, when deployed on a jboss 4.2.0, it deploys my ejb, my jsr 181 ws, but, the messaging is not working :( I get all that versioning problems with jboss-remoting and jboss-messaging (I've tried jboss-messaging from 1.4.0 to 1.4.0SP3 none work)

            Getting the server version (the 115mb one ;) ) It simply does not deploy any ejb3. It's missing a lot of libs, and although in this version I can send messages through jms clients, it does not deploy my webservices.

            Is there a reasonable (not asking for simple) way to get ESB to work with EJB3 + JSR181 WS + Messaging?

            All samples are using war files to deploy their WS.

            Best regards

            • 3. Re: JBoss ESB 4.2.1 server libs
              Claudio R Novice

              Hi Vinicius,

              You can install:

              1 - JbossAs 4.2.1.GA
              2 - JbossMessaging 1.4.0.GA
              3 - JbossWs 2.0.0.GA
              4 - JbossEsb 4.2.1.GA (not server version)

              I am using this versions here with success.
              Thanks

              • 4. Re: JBoss ESB 4.2.1 server libs
                Vinicius Carvalho Apprentice

                Thanks claudio, I'm trying this right now, hope everything works, cuz so far, one config works messaging but not ws, other ws but not messaging.
                Really would be glad to create a wiki page with detailed instructions for others...

                • 5. Re: JBoss ESB 4.2.1 server libs
                  Mark Little Master

                   

                  "viniciuscarvalho" wrote:
                  Just a dummy question here. I'm using jboss-esb-4.2.1 server since the installation of the esb on a jboss as 4.2.1 with jboss-messaging 1.4.0SP1 caused a lot of version problems (I'm still thankful for the support here that helped me to solve it).
                  But, the server version, seems to be missing a few libs (that I configure on my IDE):
                  a few that I missed:

                  jboss-ejb3.jar from ejb3.depoyer (which is not there)
                  jnp-client from the client libs

                  What happened to them? I'm using those libs from another jboss installation, but I'm affraid I get another version problem nightmare.


                  The server is not meant to install EJB3. If you need them then you should go with the JBossAS installation.

                  • 6. Re: JBoss ESB 4.2.1 server libs
                    Mark Little Master

                     

                    "viniciuscarvalho" wrote:

                    Is there a reasonable (not asking for simple) way to get ESB to work with EJB3 + JSR181 WS + Messaging?


                    The ESB Server is not meant to be a replacement for JBossAS. If you want more than is shipped with the ESB Server, then you should go with JBossAS. Currently we support AS 4.2.1. Support for the next release of AS that includes the latest versions of JBM, JBossWS etc. will be available in January. Using the CP branch of ESB should help you now though.

                    • 7. Re: JBoss ESB 4.2.1 server libs
                      Vinicius Carvalho Apprentice

                      Mark, the problem I believe lies in the readme.txt, there are a quite few places also that points that one should use jboss 4.2.0 not 4.2.1. After packing this:

                      JBoss 4.2.1
                      JbossWS 2.0.0
                      Jboss messaging 1.4.0SP3

                      I finally got it working, the bus is getting messages from both jms and soap listeners. I still have a few questions regarding the body content and the payload of the messages. I'm trying to figure it out, docs are not help much sorry :(. I can imagine how much work you guys are putting on it. I hope docs improve a bit :) It is still bit confusing on how the Body.DEFAULT_LOCATION is fulfilled. I'm setting values on it, and on later actions, It does not return the values I've set :(

                      Best regards

                      • 8. Re: JBoss ESB 4.2.1 server libs
                        Mark Little Master

                        Are you using the ESB trunk? Did you download the ESB 4.2.1 binary? Or are you using some other branch?

                        • 9. Re: JBoss ESB 4.2.1 server libs
                          Vinicius Carvalho Apprentice

                          I'm using the 4.2.1 binary now :)

                          • 10. Re: JBoss ESB 4.2.1 server libs
                            Mark Little Master

                            The binary is not necessarily using all of the latest releases of other projects because they weren't available when it was produced. The SOA Platform is the main stable product which will use all of the stable (and supported) releases of the other projects.