Speaking of 4.1, I remember seeing a website in the last week or so that said it should not be used for production yet. I am guessing that the page (possibly on apache.org) is out of date.
Back to Tap 5, are there certain parts or a percentage of interfaces that we can count on not changing in Tap 5.0 final? I've heard lots of great stuff about it from the list. As an aside, I am just now learning about Spring integration with 4.0.1, so I guess I'm still pretty newb-ish. :-) Daniel On 3/16/07, Robert Zeigler <[EMAIL PROTECTED]> wrote:
On Mar 16, 2007, at 3/161:40 PM , Celia Mou wrote: > Greeting, everyone! > > I know Tapestry 5 only has preview releases at the moment. > > I'm excited to see the auto-reloading feature, which is the main > reason why I'm considering it for the current project. Without > this, though I've done 2 projects with Tapestry 3, I would still > tend to drop it because it's just unreasonable having to restart > the server for a simple HTML change (in production environment, > with Apache as web server). > > Has anyone played enough with Tapestry 5 and have an idea about these: > > 1. How fast can the app be up at server restart? > On my local machine (a core2duo 2.16 ghz mac with 2 gigs of ram), running jetty, a jetty restart takes under 1 second to be up and running the app again. > 2. Is it smooth working with Tomcat? > Yes. I'm running a set of pages off of tomcat (behind apache, connected via modjk), with no trouble. The only issue I ran into (http://issues.apache.org/jira/browse/ TAPESTRY-1343) has been resolved. > 3. Basically, is there any major issue that would prevent one from > using it for production? > What exists in tap5 is extremely solid. The following may or may not be issues for you: 1) tap5 templates have to be valid xml. So, if you don't declare a doctype, you can't use html entities. 2) The SAX parser chokes on the html doctypes, so you have to use an xhtml doctype Daniel Gredler recently contributed a patch (yet to be applied) that makes the tapestry template parser an entity resolver, so one could theoretically do a local mapping of the html doctypes to the xhtml doctypes; this would let you declare your doctypes as html, but still keep the sax parser happy. (see http://issues.apache.org/jira/TAPESTRY-1263) 3) Doctypes that are put into templates are not transmitted to the client, so your html documents that get sent to the client never have doctypes I've submitted a patch for this; my patch includes the material in Daniel's patch for TAPESTRY-1263. See http://issues.apache.org/jira/TAPESTRY-1264 4) framework completeness: the framework still lacks "native" support for some things that you may or may not need, such as an Upload component. 5) the page testing facility has some bugs related to context assets and ASO's. Otherwise, the page/component testing ability is awesome, and a real boon. My personal thoughts: if you need upload support and serious ajax support, consider something else (eg: tap4.1). But if you don't need those, tap5 is great as it stands now. Robert > My project is due to finish within a month or two, so I actually > need to make a decision rather quickly, say within a few days. If I > can't use Tapestry 5, I might consider JSF. > > Any suggestion or ideas will be extremely helpful! Thanks a lot! > > Celia > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
