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
Hmm.. I guess what I don't get is how you can submit a form from a
DirectLink component. Are you saying to move my form handling to within
my border component and include it/exclude it based on current page? If
my tabs all call a listener method via a DirectLink the request will be
made without
Cool. I would just handle all of it within a listener method. You could use
a direct link for your tabs and handle forms based upon which tab you're
currently using. If the content within the tab is defined within your page
anyway, you could just tack the listener method on the page and access it
Basically I have a tab structure with 5 tabs, each is an individual
page. The tabs are contained within my border component, the content
with the tab is defined in the page template.
Now 2 of the pages have no form, and 3 of the pages have a form. The
behaviour of the tabs should be that click
Could you tell me more about the what the pages are and what the links would
do on each of the pages? That may help with finding a solution to your
problem!
-Ben
On 5/22/07, Paul Stanton <[EMAIL PROTECTED]> wrote:
Actually, I think something is missing .. how do I tell the links that I
want t
Actually, I think something is missing .. how do I tell the links that I
want to submit a form if a form is present? ie, I can implement the
listener for each page, but in a couple of cases, this would mean the
listener would be called without the required form data on the request.
I'll see wh
Ok thanks guys, will try this approach now.
Ben Acker wrote:
I am using a similar approach to Phillip, but using the same method
name for
each page. We have the method implemented in a base page that is
extended by
the pages implementing the component. Anytime we need the method to do
somethin
I am using a similar approach to Phillip, but using the same method name for
each page. We have the method implemented in a base page that is extended by
the pages implementing the component. Anytime we need the method to do
something different, we just overwrite it in that page.
On 5/14/07, Ph
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.
This works good, as I am using this approach myself.
- Original Message -
From: "Paul Stanton" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Mond
16 matches
Mail list logo
