The blog post is fantastic but It lacks the point that Taha tackled which is contributing blocks to the main application. My goal here isn't to contribute blocks (which seems to be the best option so far because it solves the problem of having links displayed as sub links to another top link. Igor tried to solve this using annotations which is really nice. I still have to compare between using annotations and blocks to categories my page links. Although for some reason, I feel contributing blocks will be easier, may be I'm wrong.
May be I can work around contributing blocks by having components act as the contributed tml part and annotate the component with a reasonable annotation to indicate that it's template has to be displayed ? Then Igor's loop would have a "delegate" component instead of the hyperlink one ? On Sun, Aug 26, 2012 at 9:21 PM, Richard Frovarp <rfrov...@apache.org>wrote: > 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/<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/<http://blog.tapestry5.de/index.php/2010/01/19/tapestry-ioc-modularization-of-web-applications-without-osgi/> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
