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
>From your earlier question... The logging framework is your choice. Hence
the config is dependent on the logging framework chosen.
On 2 Oct 2014 07:49, "Chris Mylonas" wrote:
> Hi All,
>
> How do you turn the logging level down. I would have thought there'd be a
> symbol or configuration menti
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/
package rs.domaci.components;
import org.apache.tapestry5.PersistenceConstants;
import org.apache.tapestry5.annotations.Persist;
import org.apache.tapestry5.hibernate.annotations.CommitAfter;
import
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
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 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
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
Hi Kalle,
I have tapestry-security 0.6.0 working successfully in GAE with tapestry5.4
beta 22.
My problem was due to an oversight in my code which was quasi-impossible to
isolate from just looking at GAE logs.
Finally broke down and got the app running locally in a debugger today and
fixed my prob
Thanks for pointing that out Lance - my part-time java foo is a bit rusty
from 10 years ago, so the thinking pipeline is not so streamlined.
Sample logback.xml file - changed to info root level - in
src/main/resources
http://logback.qos.ch/manual/configuration.html
did the trick
On Thu,
