On Thu, Mar 19, 2009 at 11:12 AM, Wes Wannemacher w...@wantii.com wrote:
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,
Similarly, I found incompatibility in JSP parsers in the past. My
issue was moving
Yeah, as it turns out, this was the culprit. Jetty 6.x had issues with the
conditionality where TC 6.x did not.
s:if test=%{#blog.content != 'NoPost' }
ul
li
a
s:action var=blog name=blog-menu1/
s:property
concerning JSP page compiles containing S2 tags. Is
there an issue concerning the two JSP compilers?
Peace,
Scott
--
View this message in context:
http://www.nabble.com/Jetty-6.x-vs-Tomcat-6.x-tp22591346p22591346.html
Sent from the Struts - User mailing list archive at Nabble.com
application is sort of
running when deployed in that environment, however, there seems to be a
strange phenomenon concerning JSP page compiles containing S2 tags. Is
there an issue concerning the two JSP compilers?
Peace,
Scott
--
View this message in context:
http://www.nabble.com/Jetty-6.x-vs
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
application is sort of
running when deployed in that environment, however, there seems to be a
strange phenomenon concerning JSP page compiles containing S2 tags. Is
there an issue concerning the two JSP compilers?
Peace,
Scott
--
View this message in context:
http://www.nabble.com/Jetty-6.x-vs-Tomcat-6.x
6 matches
Mail list logo