tapestry 4 seems faster on some things, the same on others for me.
it does scale better as suddenly you can move a lot of persistant
state onto the client, optimize away unecessary creation of
application state objects, ognl calls are fewer and faster, etc.
for development turnaround, tapestry can only do much, and indeed, tap
4 is slower than tap 3 in this regard. maven2 (if youre in a position
to use it) affords us the jetty plugin which makes reloads the app as
youre working. its ridiculously productive. fwiw, the following xml
snippet gingerly applied to your pom does wonders..
peace,
Josh
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty6-plugin</artifactId>
<version>6.0.0beta17</version> <configuration>
<scanTargets>
<scanTarget>src/webapp</scanTarget>
</scanTargets>
<systemProperties>
<systemProperty>
<name>org.apache.tapestry.disable-caching</name>
<value>true</value>
</systemProperty>
</systemProperties>
<scanIntervalSeconds>10</scanIntervalSeconds>
</configuration>
</plugin>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
