Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Thiago H de Paula Figueiredo
On Fri, 07 Dec 2012 20:05:45 -0200, Ken in Nashua wrote: The problem I have with these replies... Is no body wants to demonstrate with syntax using code Are you sure we're talking about the same user mailing list? Its guesswork sure I have used block component before but semantically how

Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Josh Canfield
* You are closing the t:beaneditor element. * ** On Fri, Dec 7, 2012 at 5:22 PM, Ken in Nashua wrote: > > Well here is the code... > > It yeilds same solution from Josh snippet. > > > > > >

RE: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Ken in Nashua
Well here is the code... It yeilds same solution from Josh snippet.   or   ${message:org.tynamo.i18n.

RE: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Ken in Nashua
Thanks josh... there is a bit of confusion on my part... block block parameter block component concepts and terms my fault... and if the code wasnt up to snuff I can fix that easy too. I will give that a shot

Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Josh Canfield
Hey Ken. Your question was poorly formatted. You didn't include the code that was failing except the snippet that was reported in the exception. Extracting that code is extra work that I have to do to figure out what you're doing wrong. If you aren't going to take the time to format good question

RE: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Ken in Nashua
The problem I have with these replies... Is no body wants to demonstrate with syntax using code Its guesswork sure I have used block component before but semantically how ? I wish things could be more generous.

Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Emmanuel DEMEY
I did not see it ! you have to put the parameter block inside the beaneditor component. 2012/12/7 Thiago H de Paula Figueiredo > On Fri, 07 Dec 2012 09:00:21 -0200, Ken in Nashua > wrote: > > classpath:org/tynamo/examples/**hibernatesecurity/pages/Edit.**tml: Block >> parameters are only allo

Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Thiago H de Paula Figueiredo
On Fri, 07 Dec 2012 09:00:21 -0200, Ken in Nashua wrote: classpath:org/tynamo/examples/hibernatesecurity/pages/Edit.tml: Block parameters are only allowed directly within component elements. The error message is very clear. :) -- Thiago H. de Paula Figueiredo -

RE: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Ken in Nashua
Thanks Manu... But it leads to another new error. ? org.apache.tapestry5.ioc.internal.OperationExceptionFailure parsing template classpath:org/tynamo/examples/hibernatesecurity/pages/Edit.tml: Block parameters are only allowed directly within component elements.locationclasspath:org/tynamo

Re: The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Emmanuel DEMEY
Have you tried this syntax ? Manu 2012/12/7 Ken in Nashua > editor field. > > Can anyone post the proper syntax? I have searched all messages and posts. > It is > -- Emmanuel DEMEY Ingénieur Etude et Développement ATOS Worldline +33 (0)6 47 47 42 02 demey.emman...@gmail.com http://em

The element has been deprecated in Tapestry 5.3 in favour of 'tapestry:parameter' namespace.

2012-12-07 Thread Ken in Nashua
Hi Folks, I am receiving the following error when attempting to model a different bean-editor field. Can anyone post the proper syntax? I have searched all messages and posts. It isn't clear to me how to specify proper syntax in order to override property fields. Thanks Ken 87.04% unrealiz

Re: tapestry:parameter namespace

2008-12-19 Thread Andy Pahne
ried using the xmlns:p="tapestry:parameter" namespace a couple times, but it doesn't seem to work. Also, the manual says t:parameter is deprecated, but then says that the new namespace was introduced in Tapestry 5.1 - which I don't think exists yet? Any ideas? From th

Re: tapestry:parameter namespace

2008-12-18 Thread Howard Lewis Ship
h an else block), > but it diesn't seem to work. But I did not have time to investigate further. > > Andy > > > > James Hillyerd schrieb: >> >> I've tried using the xmlns:p="tapestry:parameter" namespace a couple >> times, but it doesn'

Re: tapestry:parameter namespace

2008-12-18 Thread Andy Pahne
he xmlns:p="tapestry:parameter" namespace a couple times, but it doesn't seem to work. Also, the manual says t:parameter is deprecated, but then says that the new namespace was introduced in Tapestry 5.1 - which I don't think exists yet? Any ideas? From the manual: Parameter Names

tapestry:parameter namespace

2008-12-17 Thread James Hillyerd
I've tried using the xmlns:p="tapestry:parameter" namespace a couple times, but it doesn't seem to work. Also, the manual says t:parameter is deprecated, but then says that the new namespace was introduced in Tapestry 5.1 - which I don't think exists yet? Any ideas? >