In theory, an app should work on any app server, but from time to time
I've found out about incompatibilities the hard way. For instance,
Tomcat doesn't look to favorably on unclosed scriptlet tags... We
found out the hard way that Tomcat doesn't compile a page when your
page ends w/o the scriptlet tag being closed -
Doesn't work on tomcat (end of a page):
<% out.print("hello") ;
It works fine in resin though :)
Another thing I've found is that the size of an output buffer can have
an affect as well. For instance, if you are going to redirect based on
logic that executes further down the page (past the point where output
starts transmitting), you'll get an IllegalStateException. This is
right of course, but the redirect may work on some app servers if
there is a large output buffer. These were two issues I faced when
moving a large set of applications from resin to Tomcat. Both are,
IMO, bad programming, but w/o proper code review, the code was in
production. I can't vouch for the subtle differences between tomcat
and jetty, but I'm sure they exist.
-Wes
On Thu, Mar 19, 2009 at 10:53 AM, <stanl...@gmail.com> wrote:
> Right on my bro! I'll hop the source when I get back to that machine.
> However, if the code deployed to TC 6.x works fine and the *same* code
> deployed to Jetty 6.x does not, this seems whack. The application runs on
> Jetty (sort of) but things are whack. If I had been taking advantage of
> anything outside of the "spec" I might expect portability problems -- but I
> avoid that like the plague.
>
> Peace,
> Scott
>
--
Wes Wannemacher
Author - Struts 2 In Practice
Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
http://www.manning.com/wannemacher
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
