tapestry+jboss live class reloading problem

2014-05-15 Thread leandroaispuru
Hi, all I am facing the following problem with Tapestry live class reloading and jboss application server. Up to last month i was using maven+jetty+tapestry with eclipse IDE to develop and debug my web applications. I have two tapestry projects , the first one is the Webapp with custom styles and

Invalidating a session

2014-05-15 Thread Sanket Sharma
Hi, I'm trying to implement a logout page in my application that uses session state object. Going through documentation and mailing lists I found the only way to invalidate a session is calling the invalidate method not the session object. Since some of the responses on mailing lists date way back

JSDay in Verona Italy

2014-05-15 Thread Massimo Lusetti
Hi all, I'll be in Verona - Italy ad JavaScript Conf Italy next 14 and 15 may. Drop me a note for a beer and a chat! -- Massimo Lusetti

Assets t5.4

2014-05-15 Thread George Christman
Hi everyone, I'm getting the following error, (AssetSourceImpl.java:188) - Packaging of classpath assets has changed in release 5.4; Assets should no longer be on the main classpath, but should be moved to 'META-INF/assets/' or a sub-folder. Future releases of Tapestry may no longer support assets

Re: formatting attributes

2014-05-15 Thread Lance Java
I'm not sure how you have assumed that tapestry knows how understand a "format:" binding prefix. Certainly none of the tapestry documentation mentions it? The simple solution is to provide a getter for the formatted date String. If you really want a "format:" binding prefix, you can create a cust

Re: Invalidating a session

2014-05-15 Thread Thiago H de Paula Figueiredo
On Wed, 14 May 2014 11:02:24 -0300, Michael Gentry wrote: Generally, yes, but sometimes you need access to methods not available in Request. He asked specifically about session invalidation, which can and should be done in Tapestry's Session, so my answer is accurate. ;) In addition, in

Re: QName::=(NCName':')?NCName error when tml is parsed

2014-05-15 Thread mailingl...@j-b-s.de
It looks like the library mapping name is causing this effect: in case the name begins with a digit as first character like "1st" component rendering fails. Using "first" instead fixes the problem and everything works as expected. To me it looks like bug, but if it is expected behaviour I would

Re: formatting attributes

2014-05-15 Thread Jens Breitenstein
What about a component like this: public class DateFormatter { @Inject private Messages _messages; @Parameter(required = true, defaultPrefix = "prop") private Date _date; @Parameter(required = false, defaultPrefix = "literal") private String _format; boolean beginRender(final

Re: formatting attributes

2014-05-15 Thread Thiago H de Paula Figueiredo
content="${format:date=-MM-DD hh:mm:ss 'UTC' Z,someDate} On Wed, 14 May 2014 09:09:25 -0300, Chris Poulsen wrote: You probably do not want the ${ } as that converts its contents into a string. The original poster didn't describe what he meant by "not work". Guys, please avoid sayin