Re: Configuring pages to be invisible

2013-04-02 Thread Borut Bolčina
Alejandro, I have just tried this approach with factory chains, but the solution still eludes me. I've tried every variation of creating the right chain for ruling out the index page and all other subfolders - besides one folder. This configuration is the closest of what I think should do the

Re: Configuring pages to be invisible

2013-04-02 Thread Alejandro Scandroli
Hi Borut For rulling out everything but one public folder this configuration should work. configuration.add(factory.createChain(/assets/**).add(factory.anon()).build()); configuration.add(factory.createChain(/public/**).add(factory.anon()).build());

Re: Configuring pages to be invisible

2013-04-02 Thread Borut Bolčina
Hi Alejandro, the above example works ok! I moron had forgotten to remove contributeSecurityConfiguration in DevelopmentModule which was overriding configuration in AppModule. Those three lines are all I need. I have a form in the allowed page and it works as expected. What did you mean by

RegistryShutdownHub replacement?

2013-04-02 Thread Michael Prescott
Now that RegistryShutdownHub has been deprecated in 5.3, is there a preferred way for services to be notified that the application is shutting down? Gratefully, Michael

Re: RegistryShutdownHub replacement?

2013-04-02 Thread Ivan Khalopik
As I know RegistryShutdownHub is not deprecated. RegistryShutdownListener is deprecated and can be replaced with a Runnable. http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ioc/services/RegistryShutdownHub.html#addRegistryShutdownListener(java.lang.Runnable) On Tue, Apr 2, 2013

Re: RegistryShutdownHub replacement?

2013-04-02 Thread Michael Prescott
Ah yes, of course you're absolutely correct. Thanks very much, Ivan. On 2 April 2013 09:17, Ivan Khalopik ikhalo...@gmail.com wrote: As I know RegistryShutdownHub is not deprecated. RegistryShutdownListener is deprecated and can be replaced with a Runnable.

Ajax Parameter Handling

2013-04-02 Thread Tony Nelson
Given a simple contrived example like this: $('#button1').click(function (event) { $.get(specs.button1_url, { a: 'b', c: 'd'}) .done(function(data) { $(#responseDiv).text(data.response); }) })

Re: Ajax Parameter Handling

2013-04-02 Thread Thiago H de Paula Figueiredo
On Tue, 02 Apr 2013 11:03:04 -0300, Tony Nelson tnel...@starpoint.com wrote: JSONObject onButton1Press(SimplePojo pojo) { logger.info(pojo.toString()); return new JSONObject(response, ok3); } For this kind of parameter in an event handler method, Tapestry expects it

Re: Ajax Parameter Handling

2013-04-02 Thread Tony Nelson
I thought maybe I could contribute a ValueEncoder but that only sees individual parameters, not the whole request. Even this might work: JSONObject onButton1Press(JSONObject jsonObject) { SimplePojo pojo = SimplePojo.build(jsonObject); logger.info(pojo.toString());

Re: Ajax Parameter Handling

2013-04-02 Thread Paul Stanton
FYI https://issues.apache.org/jira/browse/TAP5-2021 On 3/04/2013 1:32 AM, Tony Nelson wrote: I thought maybe I could contribute a ValueEncoder but that only sees individual parameters, not the whole request. Even this might work: JSONObject onButton1Press(JSONObject jsonObject) {