This jsut makes me sick that my company is sooo in love with Tomcat. It would
be much easier to get started with Seam projects here if it was not for that
Tomcat fiasco. I mean it is 2007 and I have yet to see an application server
that takes a multiple amount of time to load compared to Tomcat.
I guess WebBeans will come into play to clear this up for the EJB.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077252#4077252
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077252
"asookazian" wrote : well what if you deploy to JBoss AS?
JBoss AS is an EJB3 container so of course that works well.
You can deploy Seam managed JavaBeans to an EJB3 container. You can then use
MDBs, SFSB/SLSB etc. as needed. A number of examples do this.
View the original post :
http://www.
"stephen.friedrich" wrote : * In general JBoss does not recommend this solution
because it is not tested as much as Seam in a full EE container.
well what if you deploy to JBoss AS?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076997#4076997
Reply to the p
Here's my understanding of this issue, somebody correct me if I'm wrong:
* JSF, Seam-annotated POJOs plus JPA- or plain hibernate entities is certainly
possible without EJB support. Of course Seam POJOs support conversations.
* The seam reference manual is sparse to say the least, see section "25
and is it possible to use POJO's in the business layer with the conversational
context (as you can with SFSB's)?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076963#4076963
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
