I think you should arm yourself with lot of patience. We are doing here a development which involves Tapestry as interface and various JBoss services and EJB3 I think most problems we have had where related to: - various configuration, packaging and classloader conflicts. Such problems can easy make you loose have a day for nothing. For example something as simple as logging and it's not easy enough http://www.len.ro/work/articles/jboss/webapp-logging/ - integrating the monitoring application with the jboss service dependency mechanism and jmx in such a way it whould work both with the webapp in jboss and in a remote tomcat.
The simplest part was working with EJB3. Len www.len.ro On Tue, 2007-01-23 at 18:02 +0100, Cyrille37 wrote: > Hello, > I have spent some time to learn Tapestry, and it will be my WebFront > framework. In this time I've learned a little about J2EE too. > > Now I've to create the architecture of my project. It must be a > multi-tier architecture, with Apache & Tomcat, a J2EE AS (JBoss or > Glassfish), and finally Mysql5 for the Data part. > Tapestry will be the WebFront framework, so it will run on Tomcat, with > probably the help of Spring2 framework for some stuff. > > I would like to have your opinion, comment, help and links about how to > make Tapestry works with applications hosted on the J2EE AS ... For da > moment I'm really floating in the unknown. > > Thanks a lot > Cyrille. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
