JBossDeveloper

What will the evolution of Seam look like once the first implementation of Web Beans is released? A life of its own with a migration path? Some sort of compatibility layer? I assume the Web Bean implementation will have a separate code base although Seam has many features in common?

Well I actually found this later on (google seems to do a better job at searching this forums than the forum search itself)

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054171

Is this still the case?

Roughly, yes.

Seam is obviously more than Web Beans (Web Beans is more like the core contextual/bijection engine of Seam) and Web Beans is quite different from Seam in its current state.

You can expect exciting times ahead for Seam :)

Aah, so it will be sort of JPA:s relation to Hibernate Core/Annotations/EntityManager? Use the standard tags for most things and then the boosted once for features that didn't make it into the specs...

This sounds really promising, however I have some concerns, that probably come from the not thorough enough understanding I have at the moment.

It seems to me that with webbeans business logic and wiev related logic get mixed up in the session/backing beans. That also makes developing a remote/rmi client more difficult. The idea of sctrict separation between layers that the EE 5 specification has seems to be lost this way.

I really would appreciate if you could address these issues in an installment!

Thanks:
PSz

Well, if it follows the ideaology of Seam (as I have understood it does), there is nothing stopping you from writing service locators returning abstract facade-factories etc...

Seam has developed very well in the past months, especially regarding depen dency reduction and wider application server support.

Nevertheless the gap between the WebBean specification hasn't narrowed since the release of the early specification draft in october. This is quite critical because for example it's pretty clear that bijection is dead as the @Out annotation is no part of the specification and discussions have shown that it will not get into the standard. But since these features are still there they will be used. To me it's clear that there will be future migration paths away from Seam specific annotations towards the standard like it happended with the JPA standard to hibernate. But especially when concepts like outjection will vanish it will make migration quite hard.

So my question is: When will Seam to start to adopt the upcoming standard and when will this standard be available.

Best regards,
Christian

I haven't heard anything specific regarding outjection, what is your source as it being dead (and the motivation for it)?

Haven't you read the early draft yet? You will not find it there.

Seam is a superset of WebBeans. Not every concept in Seam will be a part of the spec, especially not the first draft of it.

Seam 3 will be the WebBeans-compatible release.

Hi Norman,

great news!

I'm really glad to hear about the plans to adopt this upcoming standard in a future release.

When do you think we can expect a final realase of the specification and a first flavour of the RI?

When you're talking about Seam as a superset of WebBeans what does this mean regarding the current bijection mechanism? Will it be supported in future or not?

This is really important to me because it will make the migration of Seam 2.x applications really hard when current concepts are not supported in future. So we need to no about these movements soon - the early we now the less painfull the migration will be.

Can you please give us an advice how to use Seam today in order to make the migration easy?

Regards,
Christian

btw. my bad that this forum got reposted instead of being demoted to non-sticky while we were cleaning up the forums for the seamframework.org release.