We're running an enterprise-wide application for data collection and
a public access website about this data for a US Federal organization.
Main glitches: quirks of various J2EE server; variables are *not*
retained if you have to restart the server (unlike the WitangoServer,
which does save user sessions); J2EE needs to be restarted for
changes to take effect.
If your code will run on the 5.5 WitangoServer, then it's close to
being ready to compile. We develop, test on WitangoServer before ever
moving to compilation. The syntax checker helps, but you will have
occasional instances where the compiler fails anyway (due to bad
coding). You have to really go crazy on quoting if you want reliable
apps. E.g., <@ifequal this that> is not good. To make array filters
work, you pretty much have to do this <@assign name="request$this"
value="<@filter array='request$thatarray' expr='#2 = "whatever" '>">
or it's very likely to fail. You cannot go wrong, quoting everything
(properly nested, of course).
If you use lots of include files you can change these on the fly
without having to restart the J2EE server. (Advantage!)
If you use lots of include files you increase your chances of putting
in code that will cause errors on the J2EE server, and these of
course are not checked by either the syntax checker or compiler
(Disadvantage!)
It's a learning process, getting from older code to J2EE-successful
code, but we have found that (with debugged code) it is a remarkably
robust, well-performing solution. Initially it was a bit painful, but
now we do it so routinely, it's hard to recall lots of our "learning
curve" issues.
Haven't experimented with v6 yet.
On May 14, 2007, at 2:32 PM, Shane Pearlman wrote:
Hi folks,
We have been poking at the compile to J2EE option under projects in
the 5.5 studio.
Has anyone deployed a solution using this? What was your
experience? Tips, thoughts, bugs, quirks & issues we should know
about?
Has this changed much with 6.0 beta?
Shane Pearlman
831.345.7033
S&P, Inc.
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
