I go with Thiago. We use different maven modules for our business logic and persistence classes so both maven modules are standalone using their own tests. There is no relation to Tapestry at all for these modules.
We use Tapestry services and Tapestry IOC to tie it together in our webapps We even use these budinesslogic in non Tapestry war's e.g to support cron based jobs in parallel or reuse the backend services in different Tapestry Apps. I do not see any reason to use a remote connection, beside you have different life cycles for these modules and deployment is out of your control Jens Von meinem iPhone gesendet > Am 27.07.2015 um 14:56 schrieb Thiago H de Paula Figueiredo > <thiag...@gmail.com>: > > Hi! > >> On Sat, 25 Jul 2015 09:16:30 -0300, Ilya Obshadko <ilya.obsha...@gmail.com> >> wrote: >> >> >> However, there is one particular issue: when the whole thing is built on >> Tapestry, any person involved should understand the framework, and it's not >> possible to isolate frontend tasks from backend ones (because all the >> Tapestry "endpoints" are in fact event handlers and all AJAX requests are >> handled through usual event processing chain). > > I'm not sure I can agree with you. Business logic is supposed to be written > inside Tapestry-IoC services, so people working on them only need to know > T-IoC basics, which are very simple, so you can easily create tasks that > don't need any knowledge at all on Tapestry-core (the web framework). > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
