1) Not quite: Seam makes simpler architectures *possible*, and essentially lets you layer your application however *you* like. You can certainly follow whatever architectural patterns you prefer, and in particular you can certainly have your entity beans have no Seam dependency. Up to you to weigh the costs and benefits.
2) Should be. I've certainly used multiple ejb jars. Have not specifically tried multiple wars, if you do that you will need to be careful about classloader issues, the wars will need their own classloading scope, I suppose. 3) The design patterns are your own design patterns, that's the whole point: to give you flexibility. My example apps mostly concentrate on simplicity at the cost of all else. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939606#3939606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939606 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
