----- Original Message ---- From: Steve Loughran <[EMAIL PROTECTED]> To: Ant Users List <user@ant.apache.org> Sent: Wednesday, February 21, 2007 12:51:17 PM Subject: Re: How to compile jsp files with ANT
>> And, also if I were to run HttpUnit on a production environment, it would >> have to be done during off-peak hours when not many visitors are on the site. >if you are live upgrading the site you will need a way to take a >specific node in the cluster offline, no? Or do you really do a full hot >deploy on your running system? I wasn't incharge of deploying the app to production, but I think it was a deploy without restarting Tomcat (not very sure). But the web application I'm refering to was very old (legacy code which used JSP Model 1 architecture ) - and we were simply maintaining it until there was a consideration to build a newer system. I'm not on the old project anymore, but I did learn about Jasper on that project, now from this thread discussion I've learned about HttpUnit / Apache Cacuts being a better alternative for the pre-compile process. From this discussion I agree that It's better to keep the code and the build process as platform/ web container independent as possible, which saves a lot of time if the project were to have different web containers accorss environments or if they were to upgrade the web container version. I am building a test/ study project on my personal time, which currently uses Jasper, but I will try out HttpUnit and eventually Apache Cactus on it and see how it works out. >The way I've done upgrades is > -configure the router to not route to the system you are updating > -update that system by stopping the app server, installing the new > WAR/EAR and restarting > -test it is happy > -switch to it *only* > -upgrade the other other one I don't think we had a redundant system in place (not sure). But, it's definitely a good practice for better user experience. >As long as you dont have a shared session state across machines, using >serialized java objects, this mostly works. doing a cold server restart >stops you getting burned by the local session state haiving legacy >serializations of the old classes. I'm not very sure if they re-started the web server. They probably did re-start it to get rid of the sessions and serialization of old classes. >And yes, you can automate all of this. commercial Routers have an SSH >console, so if you can automate SSH command you can manipulate the >router during deployment. I guess if you used consumer-grade >linksys/netgear boxes you could just deploy a UPNP component with your >webapp and have it automatically point the router at it. Another nice thing to know - thanks for sharing this, I will keep it in mind for future projects. >ok, you need to fast forward to chapter 12, and ignore the bit where it >tells you how to use <jspc>. that bit has been cut from the sequel for >that very reason. Ok, I see HTTPUnit and Apache Cactus covered after Chap 12, I will take a look at those chapters. From looking at the chapters in "Java Development with Ant" , you have covered Ant with respect to other parts of Java such as EJBs, SOAP, Log4J, I should make more time to go over the book. I've been reading so many things like XSLT, JSTL etc just trying to stay up to date with the latest and greatest, and there's still so much I don't know :-( - like JSF etc. But I guess, I should start reading on an as-needed basis rather than reading things sequentially, after gaining a basic understanding of concepts. Thanks for your help. -Rashmi ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
