Re: XSS vulnerability in calendar component

Hi With François and Nourredine, we have just checked the Tapestry 5.2.4 datefield.js. A part of our patch was not included into the new javascript file. We still have an vulnerability in the sendServerRequest method. We can inject some JavaScript code for example, using the Paros software. B

Noticed another stackoverflow question on Tapestry 5, go vote

See http://stackoverflow.com/questions/3831807/java-server-faces-2-0-or-tapestry-5-2. I love the marketing effort from the play framework guys, they are very serious about their play :) The given Tapestry answers given seem very reasonable. Kalle -

Re: [T5.2] Pass additional info/context on Ajax Select

Hi Mark, Nothing special in my code. I was just following sample of AjaxFormLoop on Tapestry Jumpstart ( http://jumpstart.doublenegative.com.au/jumpstart/examples/tables/ajaxformloop1) and combined it with your suggestion on thread: "Update Zone inside AjaxFormLoop". Here is the snippet from my so

Re: Annotation for Field Description

On Tue, 08 Feb 2011 21:55:01 -0200, Mark wrote: The mixin approach sounds reasonable, but I'm not sure how to approach changing what gets rendered in each row of the bean editor. I'm not sure how to go about changing the functionality of an existing components. This mixin wouldn't change the

Re: How to program "Self-service password reset" in tapestry?

Hi Mark, Thanks a lot! This is quick and in great detail. This is going to save me tons of work. Thanks again. I really appreciate it. I will update how this goes later. On Tue, Feb 8, 2011 at 5:48 PM, Mark wrote: > Here is a possible approach. > > Create a page called PasswordReset or when some

Re: Annotation for Field Description

The mixin approach sounds reasonable, but I'm not sure how to approach changing what gets rendered in each row of the bean editor. I'm not sure how to go about changing the functionality of an existing components. The mixins that I'm familiar with usually add some code to the page or to the compo

Re: How to program "Self-service password reset" in tapestry?

Here is a possible approach. Create a page called PasswordReset or when someone visits this page with the secret code on the url, this page can figure out who they are based on the code and reset their password by either letting them change it or by emailing them a new one. Once this is done you

How to program "Self-service password reset" in tapestry?

I know this is pretty standard but I've never done this before. Can anyone share some experience of how this can be done in tapestry? Basically I want to sent a link to the user so when clicked he will be brought to a page and able to type in the new password. Thanks a lot. BTW, I'm using 5.1.0.

Re: Annotation for Field Description

Please file a JIRA asking for an additional parameter (, for example) in BeanEditor/BeanEditForm that is put inside the field edition block. Or some other message key convention, such as xxx-description, to do the same without any markup customization. Meanwhile, you could try writing a mix

Re: Annotation for Field Description

On Tue, Feb 8, 2011 at 12:53 PM, LLTYK wrote: > > A more descriptive label would be easy, just add the keys to the properties > file. More than that will probably delve into custom decorator or property > block territory. I need the label to stay the same. I'm familiar with the property block, bu

Re: Annotation for Field Description

A more descriptive label would be easy, just add the keys to the properties file. More than that will probably delve into custom decorator or property block territory. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Annotation-for-Field-Description-tp6004837p6005098.html

Re: How to fix the id attribute of a select component

Hi Mark - the element only occurs in one block, so this shouldn't be an issue I think. R. On Tue, 2011-02-08 at 11:48 -0600, Mark wrote: > On Tue, Feb 8, 2011 at 9:36 AM, Richard Hill wrote: > > > > Sure. But in my case I have only the one element, it's static in .tml > > and not rendered in a

Re: How to fix the id attribute of a select component

On Tue, Feb 8, 2011 at 9:36 AM, Richard Hill wrote: > > Sure. But in my case I have only the one element, it's static in .tml > and not rendered in a loop. > > I think maybe what's causing it is that the element (t:select) is > contained within the zone it updates. If I understand your setup, you

Annotation for Field Description

I am working on a project where the datamodel is being changed frequently. The bean edit form is a huge timesaver because it changes automatically and I don't have to go in an edit every form. However, I'm finding that I need a bit more explanatory information for my test users. I know I can ove

Filter exclusion

Hi, I have an event filter that implement "ComponentEventRequestFilter". My project is devided on two packages A & B. I need to exclude B from the filter, so the filter is not applicable for all pages in this package. Can you tell how to do ? Thanks in advance.

Re: How to fix the id attribute of a select component

Yeah this is a bit heavy for a simple select (for me anyway). My workaround is to use the name attribute. Cheers On Tue, 2011-02-08 at 08:22 -0800, LLTYK wrote: > The current "solution" is to use a mixin instead of onchange. Mixins will get > the newly generated id passed in to their initializ

Re: How to fix the id attribute of a select component

The current "solution" is to use a mixin instead of onchange. Mixins will get the newly generated id passed in to their initialize(), where you would then attach an onchange listener with prototype observe. -- View this message in context: http://tapestry-users.832.n2.nabble.com/How-to-fix-the-i

Re: How to fix the id attribute of a select component

Well apparently there is this clientid attribute you can add to the component in .tml which I understand from Igor is supposed to allow you to do just this. However it didn't work for me :( On Tue, 2011-02-08 at 10:52 -0500, Benny Law wrote: > Yes, but in this case, I don't see any potential f

Re: How to fix the id attribute of a select component

Yes, but in this case, I don't see any potential for conflicts. After the zone update, you will still have one select element, but with a new id. This seems to have tripped up people who are new to Tapestry. My question is, does it not make sense to perhaps add a parameter to the zone component so

Re: How to fix the id attribute of a select component

Sure. But in my case I have only the one element, it's static in .tml and not rendered in a loop. I think maybe what's causing it is that the element (t:select) is contained within the zone it updates. On Tue, 2011-02-08 at 12:56 -0200, Thiago H. de Paula Figueiredo wrote: > On Tue, 08 Feb 2

IOC Advice Chaining

I'm trying to figure out how to chain advice together, and I'm having trouble finding a good example. Basically what I want to do is insert my advice after some existing advice from the Tynamo tapestry-security module. I'm hoping this will allow me to run my own logic whenever the existing advice

Re: How to fix the id attribute of a select component

On Tue, 08 Feb 2011 12:50:57 -0200, Benny Law wrote: I understand that Tapestry is doing this to avoid potential conflicts, but can somebody provide a real example of when this is necessary? Anytime you could have the same id used twice in a page, something that is forbidden by HTML and

Re: How to fix the id attribute of a select component

I understand that Tapestry is doing this to avoid potential conflicts, but can somebody provide a real example of when this is necessary? This behavior seems to be causing confusion and inconvenience to people, myself included. Even when the danger of the conflict is real, there are still cases whe

Re: How to fix the id attribute of a select component

Hi Mark, Yes that is correct, it is being clobbered by tapestry (5.2) - specifically tapestry is appending a character sequence like "myIdName_672hjfty6". I have also tried Igor's suggestion of "clientId" and various permutations, but no luck I'm afraid. R. On Mon, 2011-02-07 at 11:40 -0600,

Re: [T5.2] Pass additional info/context on Ajax Select

On Tue, Feb 8, 2011 at 2:46 AM, Yohan Yudanara wrote: > In AddRow/RemoveRow, I save zone ids in AjaxFormLoop into session. > So, when the onValueChanged of Select component occured, I can retrieve this > value from session. Interesting. Could you share an example of how you are doing this? Mar

Re: Tynamo Security and Tapestry case insensitive paths

Thanks for the quick fix. When I saw the "run as" and "remember me" support in Shiro I knew I had to take a closer look and I think I'm out of the security business now. This is the first package I've seen that easily solves the simple problem like the one above, yet is robust enough for sites whe

Re: T5.3 and chenillekit

On Fri, Feb 4, 2011 at 7:08 PM, Sergio Esteves wrote: > Using chenillekit 1.3.0 with tapestry 5.3 I get the following error: Chenillekit 1.3.2 which is compatible with T5 5.2.4 is on the way out... I've been very very busy playing with neo4j and with severe back illness. Cheers -- Massimo http

Re: [T5.2] Pass additional info/context on Ajax Select

Thanks for your suggestion and link reference. But I'm using standard T5.2 Select component. However, I've solve my problems. In AddRow/RemoveRow, I save zone ids in AjaxFormLoop into session. So, when the onValueChanged of Select component occured, I can retrieve this value from session. Thanks

Re: [T5.2] Update Zone inside AjaxFormLoop

Yes, It does.. Thank you very much.. Now, I can control id of zone elements inside AjaxFormLoop. On Tue, Feb 8, 2011 at 12:31 AM, Mark wrote: > You can set the client side id to something like: > > id=${rowZoneId} > > public String getRowZoneId() { > return "rowZone-" rowId; > } > > That way i