2 Replies Latest reply on Oct 26, 2007 6:45 AM by pmuir

    EJB vs POJO (I don't need transactions)

    joeyxxx

      Hello All,
      If I'm writing a simple application that just communicates with a WS and I have no need for transactions nor remote clients yet, which is the way to go?
      What I care about the most is speed in a clustered environment I don't have a need for distribution yet neither.
      Thanks

        • 1. Re: EJB vs POJO (I don't need transactions)
          modoc

          I think you've answered your question.... Go with POJOs.

          • 2. Re: EJB vs POJO (I don't need transactions)
            pmuir

            Your post is a bit unclear, but by this

            What I care about the most is speed in a clustered environment I don't have a need for distribution yet neither.


            I assume you mean your primary concern is performance of your application when running on a cluster. In this case you should certainly use EJB3 as it's more performant than POJOs on a cluster (Seam POJOs work fine, but we haven't put time into optimizing this as EJB3 has).