2 Replies Latest reply on Mar 25, 2008 4:43 PM by Samuel Doyle

    Seam and Spring

    Samuel Doyle Apprentice

      I have just started working with an application that is Spring based. I don't much about Spring but will be ramping up. I have noticed several posts regarding Spring integration with an EE Application Server and was curious why I would want to do this. I asked this since there appears to be much overlap possibly from JEE taking many of the useful concepts of Spring in its creation.


      Looking on these forums I see people integrating Spring with Seam. So as I had asked previously, why would I integrate Spring with an EE Application Server? I will now ask why would I want to integrate Spring with Seam especially if I am using Seam within a EE environment?


      The last project I was working on was based on Seam running within GlassFish. I'm curious what additional benefits adding Spring into the mix would give me that the Seam/EE App. Server combo would not?

        • 1. Re: Seam and Spring
          youngm Novice

          One possible reason might be the ability to integrate Seam into an existing Spring application.  Existing spring apps may wish to take advantage of Conversation Scoped Persistence Contexts.


          Spring provides some integrations that Seam does not such as Spring Batch.


          Spring provides a more powerful TransactionManager (nested transactions)


          Some people may just prefer the embedability and flexibility of JMS, various remoting schemes, etc. in Spring to that provided by JEE.


          Why choose between Spring, Seam and JEE when you can use all of them together just fine? :)  If you don't see a reason to use Spring then don't use it.  If you like some things in Spring more than Seam then that should not stop you from using Seam.


          Just a few thoughts.


          Mike

          • 2. Re: Seam and Spring
            Samuel Doyle Apprentice

            Thanks, I am ramping up on Spring but naturally I was curious about any form of coexistence that may exist between it and some of the other technologies I have experience with. It's interesting that three work together fine but I would really like to avoid throwing another framework into the mix and introducing a framework hell sort of speak. We here are not making use of Spring 2.5 yet so are stuck in the XML configuration mess I hated with J2EE and so loved when I didn't have to have in JEE.