2 Replies Latest reply on Oct 17, 2012 1:40 PM by Tom Cunningham

    JBoss ESB Developer Stack

    Eliseo Ocampos Newbie

      Hi all,

       

      I will intend to start a more general discussion here about how to start using JBoss ESB. First of all, you could refer to my previous post [0] where I briefly post some issues trying to use JBoss ESB on Juno and/or JDBS 5.0.

       

      As I the title says, my goal is to stablish a developer stack to work with JBoss ESB. The stack components should be the most-up-to-date version that work with each other without conflicts. AFAIK, the basic componets should be: Application Server, IDE, JBoss ESB and of course the JDK. Since we are using Java, the operative system shouldn't be important but for the sake of completeness we'll use an up to date installation of a VirtualBox VM with Ubuntu 12.10 (64bit).

       

      Well, here comes the questions:

       

      0) Wich version of JDK its more suitable/stable/well supported? Options are Sun's JDK and OpenJDK. Should I opt for Java 7 already? (The impact of this question is crucial since the entire stack relies on this, It could affect from the application server to the less important plugin in your IDE, but you know what I mean)

       

      1) Wich Application Server should I use? Can I use other than JBoss AS? My research didn't include wich other application servers support JBoss ESB, but what I know is that works for sure on JBoss AS (except 7). If JBoss AS is the only option, wich version should I use?

       

      2) Wich IDE should I opt for? I think the options here are JBDS and Eclipse EE bundle. But here I need to be careful to select the proper plugins to make things work. At this point, things starts to complicate becaouse of the components (and its dependencies) you are trying to integrate.

       

      3) Of course, we'll use JBoss ESB last stable version, unless you think it would be better to use a nigthly build or similar.

       

       

      Well, I think that's it. I will love to read how did you managed all this sort of things, it doesn't matter if you are an experienced developer or a rookie like me

       

      This is very important since where I work now we are starting a big project that will involve SOA as a major architectural design and development approach, hence the importance to have an ESB properly up and running (for development and production). JBoss ESB is one option, if at the end I can't get a developer stack (or results that its very difficult to set up/work with it) I should evaluate other options (SwitchYard? Mule? other?).

       

      So, do you have any thoughs/recomendations? What's your development stack looks like?

       

       

      [0] https://community.jboss.org/thread/205476?tstart=0

        • 1. Re: JBoss ESB Developer Stack
          Eliseo Ocampos Newbie

          Is there anyone who would like to share some thoughts?

          • 2. Re: JBoss ESB Developer Stack
            Tom Cunningham Master

            0) I personally use JDK 1.6 - if you are looking for what has been tested the most, I think you should go with 1.6.

             

            1) Your choices here are JBoss AS 4.2.3.GA, JBoss AS 5.1.0.GA, and JBoss AS 6.1.0.Final.        My strong suggestion here would be to use JBoss 5.1.0.GA.     There are areas on JBoss AS 6.1.0.Final where there are issues with ESB and some of the complementary projects to ESB (jbpm) don't offer AS 6 support which would cause you problems if you needed integration there.

             

            JBoss 5.1.0.GA has been well tested and used.    

             

            If enterprise support is one of your requirements, you may want to investigate using SOA-P 5.3, which is the Red Hat product (http://www.redhat.com/products/jbossenterprisemiddleware/soa/) that integrates JBoss ESB with the enterprise version of the AS and other projects like jbpm and drools.

             

            2) Personal preference.

             

            3) JBoss ESB 4.11 is the most recent release.

             

            And you should definitely take a look at SwitchYard to get a sense of what's there.