'What will probably be the biggest changes (losses) switching from Seam 2 to plain JavaEE 6?

Question pretty much says it all, though explicitly I'm looking for the things I will probably miss about Seam 2 in a Java EE 6 environment ("losses").

For my latest (small) project JavaEE 6 or more specifically JSF 2 was a fix requirement, so using Seam 2 wasn't an option (and won't be). Even though some people said to get Seam 2 working with JSF 2, I never made it. So far I've only used Seam 2 and I fear switching to a plain JavaEE environment poses more of a problem than I'm currently aware.

The project has the following basic/core requirements:

  • Role and permission-based security concept (~50 users)
  • JPA 2 transactional persistence
  • ...

The rest will be rather GUI-based, search forms, client validation etc. which will be handled be RichFaces 4 and JavaEE 6 bean validation. There are no web services, no restful URLs, no messaging, no emailing.

I can see that using Seam security would defintitely be a loss, but I'm not sure about what Seam persistence, the entity/query framework, JBoss EL, and others would be, especially the overall programming model (navigation, EL, beans). Note that we will be able to add Seam 3 modules when it makes sense, so you might include Seam 3 in the discussion in the "gains" section.

So, can anybody clear this up a little? (it doesn't have to be a complete wrap-up, whatever springs to your mind, go ahead)

PS: I wasn't able to connect to the Seam forums so I felt I needed to ask here.

seamjava-ee-6cdiseam2seam3


Solution 1:[1]

I experienced the same. Java EE is not enough in several cases and it wasn't intended to be. So there are CDI extensions. I learned some days ago that others experienced the same:

Java EE all you need

If its too easy to be true

If you are a Seam2 user, go with Seam3 (I think they plan to provide similar stuff again - just conversations are very poor) and help them to get it stable, add features you miss,... or switch to other extensions. There are a lot e.g. we prefer MyFaces CODI, because it's very stable and fast and their notion of conversations is better. There is also a very open community and they also help a lot, listen to ideas,...

The question is not "What" it is "When will it be available in an extension". I guess as soon as someone asks for a feature.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 n00begon

Related Questions