java - Should I use EJB3 or Spring for my business layer? -


my team developing new service oriented product web front-end. in discussions technologies use have settled on running jboss application server, , flex frontend (with possible desktop deployment using adobe air), , web services interface client , server.

we've reached impasse when comes server technology use our business logic. big argument between ejb3 , spring, our biggest concerns being scalability , performance, , maintainability of code base.

here questions:

  1. what arguments or against ejb3 vs spring?
    • what pitfalls can expect each?
    • where can find benchmark information?

there won't difference between ejb3 , spring based on performance. chose spring following reasons (not mentioned in question):

  • spring drives architecture in direction more readily supports unit testing. example, inject mock dao object unit test business layer, or utilize spring's mockhttprequest object unit test servlet. maintain separate spring config unit tests allows isolate tests specific layers.
  • an overriding driver compatibility. if need support more 1 app server (or want option move jboss glassfish, etc.), carrying container (spring) you, rather relying on compatibility between different implementations of ejb3 specification.
  • spring allows technology choices persistence, object remoting, etc. example, using flex front end, , using hessian protocol communications between flex , spring.

Comments

Popular posts from this blog

c++ - How do I get a multi line tooltip in MFC -

asp.net - In javascript how to find the height and width -

c# - DataTable to EnumerableRowCollection -