On 08/26/2012 10:23 AM, Muhammad Gelbana wrote:
After reading Taha's
article<http://tawus.wordpress.com/2011/04/20/tapestry-magic-3-plugin-blocks/>,
I'm now trying to dissect my application to be able to distribute it to
different clients. So it will be distributed as one slim web application
with really nothing to offer. And to use one feature, a tapestry module
(.jar) file will just be dropped in the classpath and it should be
auto-loaded (using tapestry).
I find Taha's article highly innovative but I'm trying to find out if
anyone tackled the problem with a different approach that could be
"simpler" or capable of handling what Taha's solution probably didn't.
This might prove useful:
http://blog.tapestry5.de/index.php/2010/01/19/tapestry-ioc-modularization-of-web-applications-without-osgi/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
