Newbie questions about JBoss Seam

[aquila_deus]

1.Does EJB3 make any difference for Seam-based web applications? I checked the source but found it's just buggy and requires more code...

2.How can I switch the scope of some varables at runtime? For example, I have an application-scope string "SiteText", which is basically read-only - only admins are allowed to change it, but they don't modify the variable directly. Instead, the modification process is:

(1).Copy the SiteText into session, named "SiteText"
 (2).Since now, all variables refering to "SiteText" point to the one in session.
 (3).Edit the SiteText in session.
 (4).Save the SiteText back to DB.
 (5).Reload application-scoped SiteText from DB.

3.Is there any Seam-based web-site now?

[gavin.king]

1. Yes, there are currently a number of bugs in JBoss EJB3, and we are working hard to get them ironed out before the final release.

And yes, EJB3 offers all kinds of wonderful advantages over JavaBeans, including:

* txn demarcation
* efficient state management (passivation and replication with settable policies)
* security
* injection of resources like JMS, JDBC, JavaMail, etc
* support for WS invocation
* (in JBoss) much faster and more robust hot (re)deploy

Of course, you could implement -some- of those using Seam interceptors, but why bother when EJB3 has already got it all there for you.

2. You have expressed an *implementation* of a requirement. But you have not told us what the actual requirement was.

3. Seam has been in beta1 for only a short time, so most certainly there are no production applications yet. However, we have severalJBoss customers using it in development.

[aquila_deus]

1. Yes, there are currently a number of bugs in JBoss EJB3, and we are working hard to get them ironed out before the final release.

And yes, EJB3 offers all kinds of wonderful advantages over JavaBeans, including:

* txn demarcation
* efficient state management (passivation and replication with settable policies)
* security
* injection of resources like JMS, JDBC, JavaMail, etc
* support for WS invocation
* (in JBoss) much faster and more robust hot (re)deploy

Of course, you could implement -some- of those using Seam interceptors, but why bother when EJB3 has already got it all there for you.

Thanks!

2. You have expressed an *implementation* of a requirement. But you have not told us what the actual requirement was.

Hmmm... I'm thinking of a property with one getter and many setters, like:

String getText()
void setTextForSession(String text)
void setTextForContext(String text)

There are actually two fields of "text", one is in session and the other is in servlet context. And the getter always returns the one with higher priority (session) unless it's null. But i'm not sure how the setters should be used.

3. Seam has been in beta1 for only a short time, so most certainly there are no production applications yet. However, we have severalJBoss customers using it in development.