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
Hi!
On Sat, 25 Jul 2015 09:16:30 -0300, Ilya Obshadko
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
Tapestr
On Sat, Jul 25, 2015 at 3:55 PM, Dmitry Gusev
wrote:
You may be mixing "business logic" with tapestry's page/component classes.
>
No, that's not the case actually.
> You shouldn't put any business logic to the presentation layer
> (which is TMLs and page/component java classes).
>
Even if bus
Thanks Chung,
That seems very close to the solution I was looking for.
On Sat, Jul 25, 2015 at 3:54 PM, Chung Khanh Duy <
chungkhanhduy1...@gmail.com> wrote:
> Hi,
>
> I suggest Tapestry+RestEasy+AngularJS. AngularJS is powerful MVC font-end
> framework. Moreover you should research to try integ
Hi,
You may be mixing "business logic" with tapestry's page/component classes.
You shouldn't put any business logic to the presentation layer
(which is TMLs and page/component java classes).
All logic should be extracted to tapestry services, or even EJB as in the
JumpStart examples:
http://jump
Hi,
I suggest Tapestry+RestEasy+AngularJS. AngularJS is powerful MVC font-end
framework. Moreover you should research to try integrate bower grunt in
your project. Bower is used to pull necessary third party js go with
angular and grunt is used for building css based on sass.
So the final project
