Comments on Tapestry Central: Live Service Reloading in Tapestry 5.2

Woot! This would make writing code more fun, more ...

2010-03-29T08:32:14.073-07:00

Woot! This would make writing code more fun, more productive.

P.S. Where's the Tapestry5 book?

It's available as a snapshot artifact from the...

2010-03-16T08:24:54.258-07:00

It's available as a snapshot artifact from the Tapestry Maven snapshot repository. http://tapestry.formos.com/maven-snapshot-repository/

Thanks for another good change in T5. Can somebody...

2010-03-16T06:27:50.512-07:00

Thanks for another good change in T5. Can somebody pl put the link as I could not find the link which will download this latest change?

@Bouil Not much Tapestry can do there, I'm not...

2010-03-15T12:50:26.644-07:00

@Bouil Not much Tapestry can do there, I'm not sure how different servlet containers will react to a JAR file changing out from underneath them. In any case, you can always develop services in an agile manner as part of an application, then (once the behavior is nailed down), refractor out to a library module.

That could speed up simple developments, but for e...

2010-03-15T12:38:09.551-07:00

That could speed up simple developments, but for example, on my current project, the services are inside another project, which is imported as a dependency with Maven.

congratulations, this will speed up even more deve...

2010-03-13T10:18:40.435-08:00

congratulations, this will speed up even more development time :)

@Igor, Check the code :-) Each individual servic...

2010-03-13T10:08:10.994-08:00

@Igor,

Check the code :-)

Each individual service gets its own class loader, so it's not like components. This works because the implementation will just see the proxies for other services.

Tom, the idea is to reload the service implementa...

2010-03-13T01:23:13.639-08:00

Tom,

the idea is to reload the service implementations at development time. You change your class, save it, switch to the browser, reload the page and see the results immediately. No server shutdown is needed.

We don't want to update any services at runtime, so OSGi is not an option for Tapestry.

This feature is more comparable with JRebel. With Tapestry you have a light version of JRebel built it. This reduces the turnaround costs and gives Tapestry a further advantage over competing web frameworks.

This sounds fantastic Howard, does only the change...

2010-03-12T23:21:44.469-08:00

This sounds fantastic Howard, does only the changed implementation class/es get reloaded? or all of them?

The later sounds as if it could be less scalable? my concern is that we have a few thousand service implementations, so reloading all of these could do more harm than good for us if this was the case.

You could do this with OSGi -- but then you'd ...

2010-03-12T13:06:57.745-08:00

You could do this with OSGi -- but then you'd have two problems :-)