Try Tynamo Resteasy! I think you'll like it. We use it to support a extjs
front end we have (served in its raw form (html and js) as part of a
Tapestry web application. We jave tapestry pages working right alongside
the raw html/js page. Even better is that our rest resources use the same
servic
On Thu, 02 Oct 2014 11:38:39 -0300, wrote:
I expect to use something like Jersey to support a REST API (both
internal and external) instead of Tapestry pages to handle requests.
Ok! Just giving an suggestion. :) Have you seen
http://tynamo.org/tapestry-resteasy+guide?
Perhaps I worded my
I expect to use something like Jersey to support a REST API (both internal and
external) instead of Tapestry pages to handle requests.
Perhaps I worded my question incorrectly. I’m really wondering if IOC will
always be tied to Tapestry core in terms of releases, or will it be spun off
in
On Thu, 02 Oct 2014 01:14:27 -0300, raygarsta...@gmail.com
wrote:
Just curious - are there any plans to carve out the IOC portion of
Tapestry and release that as a separate project? Since I’m moving
towards client-side frameworks (such as angular and ember) for future
projects, I don’t
Tapestry IOC is a separate module and can be used standalone.
On 2 Oct 2014 06:38, "raygarsta...@gmail.com" wrote:
> Just curious - are there any plans to carve out the IOC portion of
> Tapestry and release that as a separate project? Since I’m moving towards
> client-side frameworks (such as a
Just curious - are there any plans to carve out the IOC portion of Tapestry and
release that as a separate project? Since I’m moving towards client-side
frameworks (such as angular and ember) for future projects, I don’t have much
need for TML, page, and component-related logic. But, I’m quite
