I am using JBoss with Jetty and I just copy my .war over and it redeploys
automatically.
generate-branding-library:
generate-tapestry-holder:
pingfederate-war:
[jar] Building jar:
/home/mstang/projects/ping/devel/HuronPeak/build/pf-war/lib/pingbranded.jar
[war] Building war:
/home/mstang/projects/ping/devel/HuronPeak/build/stage/pingfederate.war
db-setup:
[delete] Deleting directory
/home/mstang/projects/ping/devel/pingfederate/server/default/data/hypersonic
[java] update count 0
indexuptodate:
index:
deploy-saml2:
pingfederate-war-deploy:
[copy] Copying 1 file to
/home/mstang/projects/ping/devel/pingfederate/server/default/deploy
BUILD SUCCESSFUL
Total time: 6 seconds
-----Original Message-----
From: Celia Mou [mailto:[EMAIL PROTECTED]
Sent: Thu 8/3/2006 8:02 AM
To: Tapestry users
Cc: Tapestry users; Tapestry development
Subject: Re: This would be a handy tool
Hi,
I also think it's a problem having to wait for server reloads or
complete restarts. Even though Tapestry provides the reset function for
template changes, it somehow doesn't work in my combination of Apache
and Tomcat with Tomcat connector. And also since I don't want to have
the tomcat manager running on live, I always have to shutdown and start
the server again for every change, even the simplest changes such as an
image source reference in the HTML.
I'd like to hear opinions and ideas/tips on this issue.
Thanks, everyone!
celia
Sam Gendler wrote:
> I don't know about you folks, but the permgen space thing causes me to
> reload my app server all the time (the time lost waiting for
> startup/shutdown is matched by the time gained by being able to enable
> caching, i think), and spring/hivemind initialization takes a fair
> while these days.
>
> One of the things I've noticed about Tapestry is that I spend an
> enormous amount of my time tracking down silly little template syntax
> errors which cause runtime exceptions, and this is made worse by the
> turnaround time of the compile/deploy/test cycle. I don't know if it
> is possible, but it sure would be handy to have a utility which would
> parse a template, generate a java source file with a single method
> that calls every method that will be called by the template. I could
> compile against it and actually let the compiler do its job, instead
> of having to wait for the runtime system to discover a missing method
> (or rather, a typo in an ognl string).
>
> Just a thought. Unfortunately, it seems like the kind of thing that
> wouldn't be terribly high on the developer priorities, but it sure
> would ease my life.
>
> --sam
>
> ---------------------------------------------------------------------
> 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]
