T4: Alternatives to Servlet Sessions?
Dear Tapestry Mailing List, How are you today? I am wonder if there's a straightforward way of getting tapestry to use an alternative session approach to Servlet Sessions, ie file system or database. One option would be to completely bypass Tapestry's session mechanisms but this would probably be unnecessarily hackish if there's a neater way of doing it. Regards, Andrew __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T4] Modifying RadioGroup
Hi Dario, That only works if there's only one RadioGroup, the problem is that the first RadioGroup needs to refer only to the first column of Radios in the table, whilst the second needs to refer only to the second column. Since Radios have to be inside RadioGroups and RadioGroups can't be nested I can't see any way to do this without rewriting how these things work (which I attempted but hit the problem outlined in my first message). Regards, Andrew Darío Vasconcelos wrote: Hi Andrew, if you start the RadioGroup in an "invisible" spot, it will render correctly, as in or at least that's the case with lightly formatted tables... Regards, Dario __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[T4] Modifying RadioGroup
I'm trying to use radio options in the following way: pseudo-html: This doesn't work with Tapestry's RadioGroup component because there's no way of wrapping a RadioGroup around the related radio fields without wrapping the other. I tried the obvious approach of overriding Radio to allow me to specify the RadioGroup to use as a parameter rather than requiring it to be nested. To do this I changed the first line of Radio's renderComponent to get a supplied RadioGroup rather than the one from the cycle. This is the only change I made, but I get this error: "Property 'rewinding' of [RadioGroup Instance] may only be accessed while the component is rendering." Does anyone have any idea how I can solve this problem? I had expected it to be something quite easy to do and it's already taken far longer than I'd hoped. Regards, Andrew Ingram __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Form names in T4.1
Hi Brian, I'm not sure if this is the reasoning behind the change, but when using a strict doctype the form tag isn't allowed a name attribute and id is used instead. In tapestry 3 I had to rewrite the form component to use id rather than name. Rewriting the form component to use name instead would be the obvious answer, but you probably need to consider whether you should actually be using name at all. Regards, Andrew Brian Long wrote: Hi all, this is just a quick question, in previous versions of tapestry a Form was assigned a name using the convention jwcid="[EMAIL PROTECTED]", however in T4.1this no longer sets the name but assigns an id="someName". Question is, how do I assign a name to my Form component in 4.1, as informal parameters are allowed but name is reserved? Regards, Brian. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tapestry 3 and Valid XHTML Forms (generated Script tag)
Thanks Jonathan, I'm down to just one tapestry-generated validation error now. I'm still getting the language attribute on script tags (example below), i've looked through the tapestry source and the scripting stuff seems a bit complicated, even if I tell the component to not use client side scripting it still generates a small amount of script (used for focusing the text input). I'm interested in knowing two things: 1) Where in tapestry is the script tag written and how can I overwrite it to not use the language attribute? 2) Can I make a validfield generate no javascript whatsoever? Example output:
Tapestry 3 and Valid XHTML Forms
Hi, I'm trying to get Tapestry 3 to produce proper form markup but I've hit a few problems: 1) Tapestry doesn't seem to let me insert markup between the form tag and hidden fields, this means that the hidden fields cannot be put in a block level element so I can't get them to validate as xhtml 2) When using ImageSubmit the returned input has a border attribute which is invalid, I'm not sure how to remove this. 3) Another problem is that the generated javascript for validation has a language attribute which is again invalid. Any ideas? Regards, Andrew Ingram __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
