Come on. Don't be shortsighted. I managed to add a service layer and bind it in the AppModule. I was thinking to have declarative transaction each time the web layer invoke the method in this service layer.
Whatever works for you. Every project has its own nuances. For me, transactions are not a concern of the Web teir. In my ideal development world, concerns are separated strictly. I feel as though if I do not separate my concerns then I'm cutting a corner. But, this is only my opinion and its based on a perspective of development that I have. When I hear about transactional demarcation in the web tier I immediately think, "what if I want to swap my service implementation with a WS call?" The TX has to be thought of completely differently in this respect. Without WS-TX the usual route is to go with course-grained methods that apply a TX around the backend logic, or something of that sort. In any case, the web tier has no say in the TX. I'm not saying everyone should think this way. It is the way I have come to think because my exposure to certain architectures. Consider one such that core services are exposed via SOAP and orchestrated via ESB. I have no direct interaction with the "code", per se. This influences me because now when I build anything I think in highly decoupled terms - my Tap app should not know anything about the services it uses, not even whether there is a transactional state to manage. Honestly, this makes the development of a site more difficult - it's harder to build this way. But the gains I receive in the overall architecture, scalability, as well as the development lifecycle impact, are suitably large to make it worthwhile. With regards to implementing this in Tapestry, I can't say it's "bad" in all cases. I can say that there are more [easily] scalable solutions that have more clearly defined architectural borders. This is the reason I wouldn't use this feature. I know that having this clear separation allows me to modify my service layer without having to alter my web layer in any way. I can move development ahead on many fronts between many teams with minimal impact between the teams. This isn't everyone's goal. All that aside, this is a moot point. Tapestry core will remain focused as Howard says. I get to have my cake, as do you, and we can both eat it. On 6/28/07, Joshua Jackson <[EMAIL PROTECTED]> wrote:
On 6/28/07, Todd Orr <[EMAIL PROTECTED]> wrote: > Transactions declared in the Web tier? Oy vey. What's next, Tapestry-SOAP??? Come on. Don't be shortsighted. I managed to add a service layer and bind it in the AppModule. I was thinking to have declarative transaction each time the web layer invoke the method in this service layer. -- Let's create a highly maintainable and efficient code YM!: thejavafreak Blog: http://www.nagasakti.or.id/roller/joshua/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
