The compiled code needs a set of Java libraries to implement the functionality provided by the Witango server. Yes, you must purchase a license to use those libraries. -- Bill
---------- Original Message ----------- From: "Shane Pearlman" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tue, 15 May 2007 15:48:11 -0700 Subject: RE: Witango-Talk: Compiling for J2EE > So looking into this deeper, I noticed on the Witango site that > there is the following: > > Witango for J2EE v5.5 Standard Edition AU$ 6499 US$ > 4875 EURO 4030 > > Witango for J2EE v5.5 Application Edition AU$ 3998 US$ 2999 > EURO 2479 > > I wonder if I made a stupid assumption. I was under the impression > that if I compiled from the Witango studio into J2EE compiled code > that tomcat could just run it. Does it actually need the Witango > pluggin and is that what costs 3-5k? Is there anything else I am > missing? > > What I was hoping to do is use this in conjunction with flex. The advantage > of flex for a front end is that it is completely browser and platform > independent. Using java to provide back end database services truly appealed > to me - especially if we could capitalize on the rapid development > time that Witango provides us. Most systems are java enabled and > that would allow us a certain freedom from the Witango server for > our self hosted clients. > > Shane Pearlman > > 831.345.7033 > > S <http://www.shaneandpeter.com> &P, Inc. > > _____ > > From: Dale Graham [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 15, 2007 11:01 AM > To: [email protected] > Subject: Re: Witango-Talk: Compiling for J2EE > > Yes, we use TCFs a lot and also custom tags. Works perfectly. (Once > the code is "Java clean", of course!) > > On May 15, 2007, at 1:04 PM, Shane Pearlman wrote: > > Nice. This is great. > > Are you using TCF objects at all? How are they working out? > > -S > > Shane Pearlman > > 831.345.7033 > > <http://www.shaneandpeter.com> S&P, Inc. > > _____ > > From: Dale Graham [mailto:[EMAIL PROTECTED] > Sent: Monday, May 14, 2007 6:28 PM > To: <mailto:[email protected]> [email protected] > Subject: Re: Witango-Talk: Compiling for J2EE > > We've used JBoss (SLOW compared to Tomcat - too much overhead that > we just did not need), are now using Tomcat (works just fine), and > are experimenting with Resin (FAST!) > > JDBC to Oracle. > > On May 14, 2007, at 9:09 PM, Shane Pearlman wrote: > > Thanks Dale, > > Which J2EE server are you using? JBoss, Geronimo, TomCat (doesn't > appear to be a full j2ee server - can it be used) . ? > > Are you using ODBC or JDBC for database connectivity? > > -S > > Shane Pearlman > > 831.345.7033 > > <http://www.shaneandpeter.com> S&P, Inc. > > _____ > > From: Dale Graham [ <mailto:[EMAIL PROTECTED]> > mailto:[EMAIL PROTECTED] > Sent: Monday, May 14, 2007 5:41 PM > To: <mailto:[email protected]> [email protected] > Subject: Re: Witango-Talk: Compiling for J2EE > > 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 > > <http://www.shaneandpeter.com> S&P, Inc. > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to > <http://www.witango.com/developer/maillist.taf> > http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to > <http://www.witango.com/developer/maillist.taf> > http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to > <http://www.witango.com/developer/maillist.taf> > http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ------- End of Original Message ------- ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
