What I try to do is use Ant to run Jetty (or Resin :-) ) locally, operating directly on my workspace directories. JBoss can run in the background and all the EJB access will be via RMI.
Ideally, you could create a little batch file that would start the two processes for the HTML guy. It'll be interesting to see what the HTML contingent makes of the 2.4 changes. There'll be more "gunk" in the HTML, but it'll still be HTML and attributes. Or you can continue to develop exactly as you do today, or you can mix and match as appropriate. -- [EMAIL PROTECTED] http://tapestry.sf.net > Hi - > > This was a timely question. Our UI designer was getting very frustrated > trying to tweak the HTML associated with Tapestry components because of the > long turn around times. Based on the suggestions on the list, we developed > a process where he could change the HTML and see results in a few seconds. > > Here is the process for people using JBoss/Resin or JBoss/Jetty with > Tapestry. > > 1. Change the JBoss startup script to pass > '-Dnet.sf.tapestry.disable-caching=true'. When you disable caching, you can > change the HTML/page or jwc files after deployment. Pages are rendered a > little more slowly but not too bad. > > 2. Change war file so that all HTML, jwc, page files are packaged under the > war's WEB-INF/classes directory. When deployed, these Tapestry files can be > modified without rebuilding, redeploying or restarting JBoss. > > 3. Go ahead and change the deployed Tapestry files. After the change, > refresh the browser page to force Tapestry to re-load your definitions and > HTML. Here are directions for finding the deployed Tapestry files > for Resin and Jetty. > > - If you are using Resin, the deployed Tapestry files are > located under the jboss/server/default/tmp directory assuming > you are using the 'default' server configuration. > > - If you are using Jetty, the location is located in your Documents > directory. Watch the deployment and JBoss/Jetty tells you > where the deployed files are located. Here a sample of the output. > > 10:38:50,231 INFO [jbossweb] Registered > jboss.web:Jetty=0,JBossWebApplicationContext=4,context=/asset > 10:38:50,451 INFO [jbossweb] Extract jar:file:/D:/jboss-3.0.5RC1/ > server/default/tmp/deploy/server/default/deploy/ > admin.ear/27.admin.ear-contents/asset.war!/ to > c:\DOCUME~2\Owner\LOCALS~1\Temp\Jetty_0_0_0_0_8080__asset\webapp > > 4. Make sure to copy any deployed Tapestry files back to your source > directories before redeploying/restarting JBoss. > > Hope that helps... > Dorothy > > -----Original Message----- > From: Neil Clayton > To: Simon Robins; [EMAIL PROTECTED] > Sent: 1/3/03 1:12 AM > Subject: Re: [Tapestry-developer] Reducing the time of the development > cycle. > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I could see the use as an Ant task. Typically, my current build > environment > uses Ant and JBoss. Although hot redeployment works in JBoss, it is very > slow > when used in development mode with Tapestry (problem with the way it's > unified classloader does things) - so this task would speed things up > for me > in the case where I make a simple mistake. > > It would be good! > > On Thursday 02 Jan 2003 8:30 pm, Simon Robins wrote: > > Happy New Year All! > > > > Now that I feel comfortable with Tapestry, one of the areas of > > improvement for me would be to reduce the development cycle - code, > > compile, deploy, test, code... > > > > One of the problem areas is also one of the most powerful - namely the > > dynamic nature of Tapestry. For example, forgetting to add an accessor > > which is referenced in a .page or .jwc document isn't spotted until > the > > test cycle, also forgetting to add a component to the same documents > > isn't spotted until the .html page is referenced. Also an invalid xml > > document is also a problem area. Obviously a validating XML editor > > would solve this one - but I tend to hand write xml documents as I > > haven't come across an XML editor that integrates well with my > > development environment. > > > > To this end I'm thinking of writing an Ant task altough initially it > > will probably just be an application. Firstly it would check the > > validity of the relevant XML document, then it would do it's best to > > check that the relevant accessors were available in the matching .java > > file. It would also check that any jwcid attributes within the HTML > > file had matching components. Lastly it could check that any > > string-binding's had matching entries in the properties file including > > the <span key=""/> HTML tag. Plus anything else that comes to mind. > > > > I'm interested to hear any suggestions - would anyone else find it > > useful, have I missed anything, etc. > > > > Cheers, > > > > Simon > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Tapestry-developer mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > > - -- > Regards, > Neil Clayton > > (PS: If you see strange text you don't understand underneath my email, > don't > worry - it's just my PGP signature) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE+FVQILXcfQF3yrNoRAnt0AKC0fsNJsAGAmdZ2Vk8lk+4qS2bAuACgsWic > cQLfDQjQlO/WBHSWh9ics7I= > =QKgv > -----END PGP SIGNATURE----- > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
