tag:blogger.com,1999:blog-4110180.post2017526621744694947..comments2023-06-20T05:31:24.545-07:00Comments on Tapestry Central: Tapestry AOP: MethodAdviceAnonymoushttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4110180.post-61004165412739225542008-04-24T22:38:00.000-07:002008-04-24T22:38:00.000-07:00Hi!this is great stuff! I have very conservative t...Hi!<BR/><BR/>this is great stuff! I have very conservative three tier system running. (Data access layer, business logic layer and ui.) All tiers are divided to interfaces and implementation and are arranged as individual projects. Currently Spring ties all this together, but as it is the only thing it does currently (transaction management also) i was thinking wether I should use T5 ioc for this. Is there an example of a "Heavy weight" project that uses hibernate and previously mentioned project structure? Tapestry-hibernate is not the answer as we don't want tapestry (web portion) to have any clue how data access layer persists the entities, or what technology is used. Session per request is currently used.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4110180.post-67758236139381281612008-04-24T13:25:00.000-07:002008-04-24T13:25:00.000-07:00The IoC framework is completely standalone; you ca...The IoC framework is completely standalone; you can absolutely use it outside of Tapestry; you can use it for non-web applications. If I was building an ESB of some flavor, I would almost certainly start cranking out logic using tapestry-ioc; perhaps builders that make Queues and Topics looks like services, etc.<BR/><BR/>On the Tapestry side, I'm hoping to put together a similar system whereby component methods can be advised, similar to how it works for services. This would be used by ComponentClassTransformWorker instances. There would be a ComponentMethodAdvise and ComponentInvocation interfaces, the same as the above, except that the component's ComponentResources object would be made available to the advise.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-22227875889669074372008-04-24T13:16:00.000-07:002008-04-24T13:16:00.000-07:00I agree with Massimo. I'm using chainbuilders to ...I agree with Massimo. I'm using chainbuilders to handle the ordering a rendering logic of tabs on our main pages. I'm using a masterdispatcher to handle our logins (and may use it for our OpenID implementation). I'm using object rendering strategies for some displays.<BR/><BR/>These are central parts of our app.<BR/><BR/>Formos could build a great business opportunity around training on the IOC and the meta-programming required.<BR/><BR/>Port to smalltalk for dynamicism :)Bill Hollowayhttps://www.blogger.com/profile/01824149803522705231noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-42818920568293747372008-04-22T02:25:00.000-07:002008-04-22T02:25:00.000-07:00so you call this stuff a "side issue" ... that's n...so you call this stuff a "side issue" ... that's not exactly what i have in mind.<BR/><BR/>The IoC is going to serve a lot of development in my environment, i'm eager to see if/when it comes to a somewhat standalone project...Massimohttps://www.blogger.com/profile/09841812729931064489noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-24208266068292882652008-04-21T12:15:00.000-07:002008-04-21T12:15:00.000-07:00I'm afraid its "inspired by" rather than "utilizin...I'm afraid its "inspired by" rather than "utilizing". Partly to avoid Yet Another Dependency, partly because I only needed one small piece, partly because I wanted the specific MethodAdvice and Invocation interfaces to be just exactly what T5 IoC needs. But I think you could "wrap" the Tapestry MethodAdvice and make something that looks a lot more like a AOP Alliance interface.Anonymoushttps://www.blogger.com/profile/04486596490758986709noreply@blogger.comtag:blogger.com,1999:blog-4110180.post-8540892796537865642008-04-21T11:20:00.000-07:002008-04-21T11:20:00.000-07:00Great staff Howard! It was indeed one of the pain ...Great staff Howard! It was indeed one of the pain points of T5 IOC compared with Hivemind. AOP Alliance support is very good decision IMHO.Renat Zubairovhttps://www.blogger.com/profile/12846719969746695973noreply@blogger.com