GoDaddy Hosting, Tomcat 5.0.27

[rafaelubaldo]

I've some Struts demo application I will be porting over to SEAM this weekend, and mixing in some IceFaces and GWT samples for the blog.

The target demo environment is a shared Linux Deluxe web hosting account offered by GoDaddy as an offer for review. GoDaddy supposedly offers Tomcat 5.0.27 (JVM 1.5). Furthermore, when deploying WAR files, they won't be exploded (as in my changes taking affect) until the next day, and will run in a very conservative environment. GoDaddy's Java built-in support offering appears by no means serious, but may work for these casual demonstrations.

Questions for Discussion:

[1] Can SEAM be deployed to Tomcat 5.0.27?

[2] I doubt the JBOSS Micro-kernel or JBOSS Embedded EJB3 will work in Tomcat 5.0.X (confirm?). In lieu of JBE, SEAM applications can be built POJO/Hibernate. What are some limitations and experiences of those out there who have gone POJO-only?

Thanks in advanced,

Rafael



 

[luxspes]

Rafael Ubaldo wrote on Mar 19, 2009 04:46:


I've some Struts demo application I will be porting over to SEAM this weekend, and mixing in some IceFaces and GWT samples for the blog.

The target demo environment is a shared Linux Deluxe web hosting account offered by GoDaddy as an offer for review. GoDaddy supposedly offers Tomcat 5.0.27 (JVM 1.5). Furthermore, when deploying WAR files, they won't be exploded (as in my changes taking affect) until the next day, and will run in a very conservative environment. GoDaddy's Java built-in support offering appears by no means serious, but may work for these casual demonstrations.

Questions for Discussion:

1. Can SEAM be deployed to Tomcat 5.0.27?

In you seam directory at the the subdirectory \examples\jpa that example has support for generating a .war compatible
with 5.5.x, I recommend you to try and see if that .war runs in Tomcat 5.0.27

1. I doubt the JBOSS Micro-kernel or JBOSS Embedded EJB3 will work in Tomcat 5.0.X (confirm?). In lieu of JBE, SEAM applications can be built POJO/Hibernate. What are some limitations and experiences of those out there who have gone POJO-only?

limitations for POJO-only?, Think that again ;-), it is more like limitations for EJB-only

Thanks in advanced,

Rafael