I think that kind of complication becomes more trouble than just
implementing onActivate(), onPassivate().
On Wed, Jul 9, 2008 at 3:24 PM, Josh Canfield <[EMAIL PROTECTED]> wrote:
> Is there opposition to adding an index to the annotation so you don't have
> to use source order?
>
> @PageActiviati
Is there opposition to adding an index to the annotation so you don't have
to use source order?
@PageActiviationContext(index=2)
private Bar b
@PageActiviationContext(index=1)
private Foo a
Josh
On Wed, Jul 9, 2008 at 2:36 PM, Igor Drobiazko <[EMAIL PROTECTED]>
wrote:
> I see a problem with mul
I see a problem with multiple @PageActivationContext annotations inside a
page class.
Consider following example:
public class Start{
@PageActivationContext
private Foo b;
@PageActivationContext
private Bar a;
}
When Eclipse "Sort Member Save Action" feature is enabled, the order of
I thought that its main contribution to be able to use it for multiple
values,
and not yet I understand why this functionality has not been implemented.
So, I agree for jira.
Ted Steen wrote:
At the moment you should think of the @PageActivationContext as a
convenience annotation for you to us
IMHO, this is not the easyest approach
I prefer to inject the next page, set it's attributes and then pass it
as the method's return... this way you can set as many parameters as
you like
On Wed, Jul 9, 2008 at 2:29 PM, Francisco Manzano
<[EMAIL PROTECTED]> wrote:
> why don't ?
>
> Ted Steen wrot
At the moment you should think of the @PageActivationContext as a
convenience annotation for you to use when you only want to place a
single value in the context. Personally I think it would make more
sense if you where able to use it for multiple values.
Maybe worth adding a JIRA for that?
For ex
why don't ?
Ted Steen wrote:
I dont think you can use that with multiple values as the context :/
2008/7/9 Francisco Manzano <[EMAIL PROTECTED]>:
Or, you can use the new @PageActivationContext annotation for a greater
simplicity
Zanius
Ted Steen wrote:
Just add more parameters to t
>
> Or, you can use the new @PageActivationContext annotation for a greater
> simplicity
>
http://tapestry.formos.com/nightly/tapestry5/apidocs/src-html/org/apache/tapestry5/internal/transform/PageActivationContextWorker.html#line.37
037if (fields.size() > 1)
038throw
I dont think you can use that with multiple values as the context :/
2008/7/9 Francisco Manzano <[EMAIL PROTECTED]>:
> Or, you can use the new @PageActivationContext annotation for a greater
> simplicity
>
> Zanius
>
> Ted Steen wrote:
>>
>> Just add more parameters to the activate/passivate-meth
Or, you can use the new @PageActivationContext annotation for a greater
simplicity
Zanius
Ted Steen wrote:
Just add more parameters to the activate/passivate-methods.
Or you can use (Object[] parameters).
Or you can use (EventContext context)
The way to go for you would be to just add more p
Just add more parameters to the activate/passivate-methods.
Or you can use (Object[] parameters).
Or you can use (EventContext context)
The way to go for you would be to just add more parameters to the
activate/passivate-methods.
2008/7/9 t <[EMAIL PROTECTED]>:
> void onActivate(String message)
>
void onActivate(String message)
{
System.out.println("Another page is activated! The
message is: " + message);
this.passedMessage = message;
}
String onPassivate()
{
System.out.println("Another page is passivated...");
return passedMessage;
}
This is the
12 matches
Mail list logo
