Thanks, I've figured it out now, hadn't read the doc on 'selected'
attribute :(
Nick Westgate wrote:
Isn't this just a field of your page base class?
In T4 you can inherit, which should be great.
In T3 I had to add the property to each .page file.
Cheers,
Nick.
Paul Stanton wrote:
thanks,
Isn't this just a field of your page base class?
In T4 you can inherit, which should be great.
In T3 I had to add the property to each .page file.
Cheers,
Nick.
Paul Stanton wrote:
thanks, listener="ognl:page.listeners.formSubmit" works.
anyone know how to read the 'tag' attribute once in th
thanks, listener="ognl:page.listeners.formSubmit" works.
anyone know how to read the 'tag' attribute once in the form submit
listener?
Nick Westgate wrote:
I have no T4 project to test with, but in T3 I used OGNL expressions:
getPage().listeners.submitForm
getPage().submitTarget
Cheers,
Nick
I have no T4 project to test with, but in T3 I used OGNL expressions:
getPage().listeners.submitForm
getPage().submitTarget
Cheers,
Nick.
Paul Stanton wrote:
Nick (or anyone), two questions:
1. If I define the form in the border component, why doesn't
listener="listener:page.formSubmit" work
Nick (or anyone), two questions:
1. If I define the form in the border component, why doesn't
listener="listener:page.formSubmit" work? It seems I have to define a
listener in the border component that delegates to the page method?
2. How do I read the value of the 'tag' attribute of a LinkSu
thanks nick.
Nick Westgate wrote:
Paul Stanton wrote:
Hmm.. I guess what I don't get is how you can submit a form from a
DirectLink component.
I'm guessing you can't, unless you emulate what LinkSubmit does:
http://tapestry.apache.org/tapestry4.1/components/form/linksubmit.html
In my Tapest
Paul,
I apologize for recommending a 'dirty' way of solving your problem!
You could just create a new component based on the AbstractSubmit class or
the Submit component. That way you could utilize the form submission from
AbstractSubmit. In addition, the html in your tab could display this new
Paul Stanton wrote:
Hmm.. I guess what I don't get is how you can submit a form from a
DirectLink component.
I'm guessing you can't, unless you emulate what LinkSubmit does:
http://tapestry.apache.org/tapestry4.1/components/form/linksubmit.html
In my Tapestry 3 apps I actually used form submi
On 5/14/07, Phillip Rhodes <[EMAIL PROTECTED]> wrote:
>> >>
>> >> You can you use IListener as a parameter. On each page, you can
bind
>> >> your
>> >> component to the specific page listener that you want invoked.
>> >>
>> >
t;> your
>> >> component to the specific page listener that you want invoked.
>> >>
>> >> This works good, as I am using this approach myself.
>> >>
>> >>
>> >> - Original Message -
>> >> From: "Pa
pproach myself.
>>
>>
>> - Original Message -
>> From: "Paul Stanton" <[EMAIL PROTECTED]>
>> To: "Tapestry users"
>> Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
>> Subject: expert needed
>>
>
good, as I am using this approach myself.
>>
>>
>> - Original Message -
>> From: "Paul Stanton" <[EMAIL PROTECTED]>
>> To: "Tapestry users"
>> Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
>> Subject: e
I am using this approach myself.
- Original Message -
From: "Paul Stanton" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
Subject: expert needed
Tapestry 4.1
I've got a set of anchors () which are commo
myself.
- Original Message -
From: "Paul Stanton" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
Subject: expert needed
Tapestry 4.1
I've got a set of anchors () which are common for a grou
on" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
Subject: expert needed
Tapestry 4.1
I've got a set of anchors () which are common for a group of pages
and are contained within a component, however on each
Tapestry users"
Sent: Monday, May 14, 2007 8:56:54 PM (GMT-0500) America/New_York
Subject: expert needed
Tapestry 4.1
I've got a set of anchors () which are common for a group of pages
and are contained within a component, however on each page they need to
do different things. Essentially
Tapestry 4.1
I've got a set of anchors () which are common for a group of pages
and are contained within a component, however on each page they need to
do different things. Essentially they will either submit a form on the
page with or without client side validation or perform a simple page li
17 matches
Mail list logo