FYI one bonus of using @PageActivationContext is that you automatically
have onPassivate() generated for you. If you declare onActivate() you'll
need to do this yourself
On 20 Sep 2016 5:56 p.m., "Thiago H de Paula Figueiredo"
wrote:
> On Tue, 20 Sep 2016 13:24:08 -0300, Nathan Quirynen <
> nat.
On Tue, 20 Sep 2016 13:46:27 -0300, Adam X wrote:
How do I create links? Can I do this:
yo
bam
I'd go with a separate method:
yo
Object[] getPageContext() {
// whatever logic you want or need.
}
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
On Tue, 20 Sep 2016 13:24:08 -0300, Nathan Quirynen
wrote:
|You can do something like the following: void onActivate(EventContext
eventContext) { |
||if(eventContext.getCount() == 1) { ... }
if(eventContext.getCount() == 2) { ... }
if(eventContext.getCount() == 3) { ... } ...
Sorry... I spoke to soon. You want index=1 to be a string sometimes and a
long others? If you want to use @PageActivationContext you'll need to
declare as a string and parse to long yourself
On 20 Sep 2016 5:51 p.m., "Lance Java" wrote:
> You don't need explicit nulls, it'll work with or without
You don't need explicit nulls, it'll work with or without them.
On 20 Sep 2016 5:46 p.m., "Adam X" wrote:
> Wow, you guys rock and support is great. I like
> onActivate(EventContext eventContext). I like even better
> @PageActivationContext annotation (I'm doing a new project on 5.4.1 so
> I can
Wow, you guys rock and support is great. I like
onActivate(EventContext eventContext). I like even better
@PageActivationContext annotation (I'm doing a new project on 5.4.1 so
I can use it).
So in my earlier example, if I define this:
@PageActivationContext(index=0) private String foo;
@PageActi
Correction: This feature was added in 5.4 (not 5.3)
On 20 Sep 2016 5:29 p.m., "Lance Java" wrote:
> @PageActivationContext supports multiple values thanks to the new index
> property added in 5.3. Missing values will simply be null
>
> Eg:
> @PageActivationContext(index=0) private String value0;
@PageActivationContext supports multiple values thanks to the new index
property added in 5.3. Missing values will simply be null
Eg:
@PageActivationContext(index=0) private String value0;
@PageActivationContext(index=1) private String value1;
@PageActivationContext(index=2) private String value2;
|You can do something like the following: void onActivate(EventContext
eventContext) { |
||if(eventContext.getCount() == 1) { ... } if(eventContext.getCount() == 2)
{ ... } if(eventContext.getCount() == 3) { ... } ... |
} |
On 20/09/16 18:04, Adam X wrote:
I would like to have mul
Try this:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/navigation/variableparameters1
Geoff
> On 21 Sep 2016, at 12:04 AM, Adam X wrote:
>
> I would like to have multiple (overloaded) onActivate methods in my
> page but seems like Tapestry is always picking a method with
I would like to have multiple (overloaded) onActivate methods in my
page but seems like Tapestry is always picking a method with fewest
arguments.
How can I achieve something like this?
TargetPage {
void onActivate(String foo, String bar) {
}
void onActivate(String foo, Long id1, Long id2) {
}
e subclass signature being:
>
> Object activate(EventContext)
>
> I know I've used similar patterns in 5.3, but haven't tried in 5.4 yet.
>
> mrg
>
>
> On Wed, Apr 22, 2015 at 6:56 AM, Chris Poulsen
> wrote:
>
> > Hi,
> >
> > W
AM, Chris Poulsen
wrote:
> Hi,
>
> We have an abstract parent class with an activation handler declared like
> this:
>
> @OnEvent( EventConstants.ACTIVATE )
> void activate( EventContext ec ) (Called)
>
> And an extending class with an activation handler declared like this:
Possibly a sign you should be using composition instead of inheritance ;)
Hi,
We have an abstract parent class with an activation handler declared like
this:
@OnEvent( EventConstants.ACTIVATE )
void activate( EventContext ec ) (Called)
And an extending class with an activation handler declared like this:
@OnEvent( EventConstants.ACTIVATE )
Object activate
tivate
>>
>
> Unless these ids are sensitive by itself (SSN number, for example), I
> don't think that's actually needed, specially if they're database-generated
> values. Encoded/encripted activation context or not, you still need to
> check, in every reques
parameters before storing in the
url and to decode before onActivate
Unless these ids are sensitive by itself (SSN number, for example), I
don't think that's actually needed, specially if they're
database-generated values. Encoded/encripted activation context or not,
you stil
Hi all,
I really like the concept to store values in the url instead of
storing in the session. But in most cases these are IDs of the
entities that can be manipulated by users in the url.
Is it a good idea to try to encode parameters before storing in the
url and to decode before onActivate and i
<
> geoff.callender.jumpst...@gmail.com> wrote:
>
>> It's worth noting that if your grid is in a component then activation
>> context might not be suitable. A solution is on the way:
>>
>>https://issues.apache.org/jira/browse/TAP5-2297
f your grid is in a component then activation
> context might not be suitable. A solution is on the way:
>
> https://issues.apache.org/jira/browse/TAP5-2297
>
> Cheers,
>
> Geoff
>
> On 27 Aug 2014, at 11:08 am, Chris Mylonas wrote:
>
> > Hi Tapestry Noobs of t
It's worth noting that if your grid is in a component then activation context
might not be suitable. A solution is on the way:
https://issues.apache.org/jira/browse/TAP5-2297
Cheers,
Geoff
On 27 Aug 2014, at 11:08 am, Chris Mylonas wrote:
> Hi Tapestry Noobs of th
Hi Tapestry Noobs of the future!
...that come across this problem,use onPassivate to keep your app working
nicely.
I had the pleasure of using my software in a field trial (nothing exciting,
equipment tracking in a data centre) and made a few adjustments to quicken
my task though the night althou
Thanks Dimitri
: )
I didnt think I physically had to make the match happen in code.
I thought the formal parameter spec was optional.
I will give that a shot.
So it seems signature counts.
Thanks a bunch !!!
eters are 2 and 2. Not sure how you get 2 from
the "team" instance, I believe this is the work of encoders.
And you will always have these two numbers the same here.
Why don't you just remove one from activation context?
So what we have at the end is:
@OnEvent(EventConstants.PASSIV
tHANKS gEOFF...
bUT it tell sme I have a serious problem onmy hands
the output is not matching the input
I dont know what to do
I have seen this months ago tryign to create CRUD pages.
Maybe it has to do with the routing features of tynamo? I dont know...
Here is the routing feature
@At("/{2
ied the context specified below but clazz during activation always comes
> in as null.
>
> is this a tapestry bug ?
>
> @OnEvent(EventConstants.ACTIVATE)
>Object onActivate(Class clazz) {
>if (clazz == null)
>return Utils.new404(messages);
>
Thanks Thiago...
The usage of THIS... is because I am operating exclusively out of
RosterQuery.JAVA and RosterQuery.tml
This module renders ...
=
| criteria form GO |
=
| table|
=
I select my criteria and hit GO. The
On Mon, 20 May 2013 15:04:35 -0300, Ken in Nashua
wrote:
I tried the context specified below but clazz during activation always
comes in as null.
is this a tapestry bug ?
No. If you wan to get the class as the first page activation context
value, it should be the first value in the
This seems to help me stay on the same page...
/*
@OnEvent(EventConstants.ACTIVATE)
Object onActivate(Class clazz) {
if (clazz == null)
return Utils.new404(messages);
this.beanType = clazz;
return null;
}
*/
@OnEvent(EventConstants.PASSIVATE)
I tried the context specified below but clazz during activation always comes in
as null.
is this a tapestry bug ?
@OnEvent(EventConstants.ACTIVATE)
Object onActivate(Class clazz) {
if (clazz == null)
return Utils.new404(messages);
this.beanType = clazz
Hi Tapestry Pro's...
Good morning..
I was wondering about my page.
Here is the link to my page... its basically a prototype I will retrofit in
later.
http://localhost:8080/pphl/rosterquery
My page renders and everything is good. I select my criteria and hit GO
(submit).
My tabel list gets p
I'm guessing that you render the "recalculate" zone by submitting another
form... correct?
If so, you could include the values from the first calculate as in the second form.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context
calculated values from the
initial calculation. Now I don't see another way than to @Persist these
values to use them, or is there a better/other way?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717966
(). Assuming you have a
ValueEncoder configured, you can do the following:
@PageActivationContext
private Policy policy;
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717941.html
Sent from the Tapestry
;
}
[1]
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ValueEncoder.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717939.html
Sent from the Tapestry - User mailing list archive at
Hi,
Have you checked out: http://tapestry.apache.org/page-navigation.html
To see if "onPassivate" or providing an explicit activation context can help you
--
Chris
On Mon, Nov 12, 2012 at 4:20 PM, nquirynen wrote:
> Hi
>
> I have a page with an activation context:
>
Hi
I have a page with an activation context:
void onActivate(int policyId) {
policy = policyRepository.get(policyId);
}
Now I have a component on this page which does AJAX requests. At this point
the policy variable set in the activation context is null.
Now I can 'solve' thi
te(EventContext) method.
3. If you still want multiple onActivate methods, return true to avoid
processing other onActivate methods.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/activation-context-method-tp5716091p5716093.html
Sent from the Tapestry - User mailing
Hi,
I am facing a weird problem related to the activation method of page.
I have three pages named as, Page1, Page2 & Page3.
In Page1, I have two activation methods.
@OnEvent(value = EventConstants.ACTIVATE)
public void activateFromDetails(String contractNumber, String page
then you could push them on the Environmental stack and not
> >> pass any parameters - just have the component query the stack.
> >>
> >>
> > Wouldn't that work just for one component? As soon as one component pops
> the
> > object(s) from the Enviro
tack.
>>
>>
> Wouldn't that work just for one component? As soon as one component pops the
> object(s) from the Environment stack, others won't have it (them) anymore?
>
> Thanks,
> borut
>
>
> Steve.
>> --
>> Steve Eynon
>>
>>
>&g
s) from the Environment stack, others won't have it (them) anymore?
Thanks,
borut
Steve.
> --
> Steve Eynon
>
>
> On 24 August 2011 18:07, Borut Bolčina wrote:
> > Hi,
> >
> > if a component needs to have its parent's activation context (say two
> >
parameters - just have the component query the stack.
Steve.
--
Steve Eynon
On 24 August 2011 18:07, Borut Bolčina wrote:
> Hi,
>
> if a component needs to have its parent's activation context (say two
> strings), is the preffered way to pass it as parameters or is there a "le
Hi,
if a component needs to have its parent's activation context (say two
strings), is the preffered way to pass it as parameters or is there a "less
code way"?
The solution must not use a session.
Cheers,
Borut
On Thu, 24 Feb 2011 04:58:26 -0300, Vjeran Marcinko
wrote:
Hello all,
Hi!
I just wanted to hear if current state of page configuration and
activation is the desired one?
What do you mean by page configuration?
(this is the reason for one of my architectural problems, but I don&#
Hello all,
I just wanted to hear if current state of page configuration and activation
is the desired one? (this is the reason for one of my architectural
problems, but I don't want to go into details here since it will boil down
to - why don't I use RequestFilters insted of page
I had an onPassivate. I realized something in my javascript was stripping the
query parameters from the link from createEventLink.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Re-T5-2-Activation-context-for-ajax-requests-tp5921878p5922180.html
Sent from the Tapestry
reff: T5.2 - Activation context for ajax requests
Gesendet: Fr, 14. Jan 2011
Von: LLTYK
>
> So I am using Inge's ZoneUpdater. Previously in 5.1, the createEventLink in
> it results in a "?t:ac=1/2" being tacked onto the end of the event link.
> Afterwards, when the event is trigg
iables that are then used by the event handler (which is buried in some
component).
Now in 5.2, this "t:ac" query parameter isn't being put on. Tapestry then
thinks that there is no page activation context (it goes for onActivate()
with no params), and then the event handler proceeds to
se the configuration in a contribution on a per-app basis. Sounds
fun right? :)
On Fri, Sep 17, 2010 at 5:44 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Fri, 17 Sep 2010 12:58:52 -0300, Jack Nuzbit
> wrote:
>
> Hi,
>>
>
> Hi!
>
> Is
On Fri, 17 Sep 2010 12:58:52 -0300, Jack Nuzbit
wrote:
Hi,
Hi!
Is there a way to create Pages and initialise their activation context
at a service level?
I'm curious about what you're trying to accomplish here. :)
Is there a way I can set an activation/event context in this
Hi,
Is there a way to create Pages and initialise their activation context at a
service level?
ComponentSource can give me Component instances but casting it to my page
instance results in a ClassCastException due to the different classloaders.
Is there a way I can set an activation/event
Actually, splitting hairs, I would call field persistence the heavier
option ... you just don't see all the machinery it takes to make it
work.
On Wed, May 19, 2010 at 1:20 PM, Thiago H. de Paula Figueiredo
wrote:
> On Wed, 19 May 2010 17:04:25 -0300, Pete Poulos
> wrote:
>
>> I considered this,
On Wed, 19 May 2010 18:25:19 -0300, Pete Poulos
wrote:
So, if the only thing I'm using the session for is to store this user
feedback message am I going to suffer a huge scalability hit as
indicated in the SSO docs?
"Scalable web applications do not create the side session needlessly.
If yo
On Wed, 19 May 2010 18:09:43 -0300, Pete Poulos
wrote:
* I would need to create a class to wrap the message since I don't
like the idea of using the String type for an SSO since SSO are
injected based on type and not name.
Absolutely right.
* SSOs are not cleared automatically after a Fla
So, if the only thing I'm using the session for is to store this user
feedback message am I going to suffer a huge scalability hit as
indicated in the SSO docs?
"Scalable web applications do not create the side session needlessly.
If you can avoid creating the session, on first access to your we
> I considered this, but the documentation for SessionState makes it
> sound like it is a very heavy handed solution, Whereas, the
> documentation for Flash Persistence makes it sound like the right fit.
Both @Persist (flash, and session) and @SessionState (via
ApplicationStateManager) use the Htt
> Instead of using @Persist, why not creating a class to hold the message and
> use it as @SessionState? Just remember to clear the field with the message
> after it is requested.
This is the strategy that I use. I have a UserMessageHolder object
stored as @SessionState and have a component that r
>> I considered this, but the documentation for SessionState makes it
>> sound like it is a very heavy handed solution,
>
> Why? Just curious. :)
>From an implementation perspective...
* I would need to create a class to wrap the message since I don't
like the idea of using the String type for an
On Wed, 19 May 2010 17:04:25 -0300, Pete Poulos
wrote:
I considered this, but the documentation for SessionState makes it
sound like it is a very heavy handed solution,
Why? Just curious. :)
Whereas, the
documentation for Flash Persistence makes it sound like the right fit.
It surely fi
Hi Thiago,
Thanks for your quick reply.
> Instead of using @Persist, why not creating a class to hold the message and
> use it as @SessionState? Just remember to clear the field with the message
> after it is requested.
I considered this, but the documentation for SessionState makes it
sound li
On Wed, 19 May 2010 16:56:24 -0300, Pete Poulos
wrote:
Btw, it's not at all intuitive that this would work. I guess what's
happening is that when you acquire a page instance and set (persisted)
values on it, then those are the values that will be used the next
time the page is accessed?
Wh
So... I just tried the following and it worked, so I guess I answered
my own question. Sorry for troubling you folks.
private Object deleteItem( long id, String page, String context ) {
itemDao.delete( id );
Component comp = componentSource.getPage( page );
if( comp instanceof F
On Wed, 19 May 2010 16:49:45 -0300, Pete Poulos
wrote:
Hi,
Hi!
Instead of using @Persist, why not creating a class to hold the message
and use it as @SessionState? Just remember to clear the field with the
message after it is requested.
--
Thiago H. de Paula Figueiredo
Independent Ja
e top that says " has been deleted". The vast
majority of the users state is stored in the page's activation
context, but I don't want to store the feedback message there as it
ends up complicating the context processing across all of the
applications pages.
There is already a @pageActivationContext that does this. It only works for
simple properties though
http://tapestry.apache.org/tapestry5/tapestry-hibernate/userguide.html
On Mon, Mar 29, 2010 at 10:50 PM, Michael Prescott <
michael.r.presc...@gmail.com> wrote:
> Hey, it would be really nice if I
Hey, it would be really nice if I could skip all the writing of onActivate()
and onPassivate() methods, just using an annotation like this:
@Persist("activationContext")
public String someUsefulIdentifier;
Or, perhaps (and more useful for my case, when I want a domain entity
handy):
@ActivationC
Hey... I did a little follow-up on this and decided to create an "event-safe
loop" that can restore the state of the loop variable using the page
activation context. It's not quite perfect, but it's good enough for my
needs right now. For my application, the resulting code e
it would be great if there would be a way for the Loop
component to automatically encode loop state into something like the page
activation context and then automatically restore that point-in-time state
when processing the eventlink request. It would work like a blend of the
page activation conte
it could be the lack of a feature, not a bug. Or just lack of T5
>>> experience. :)
>>
>>
>> I have to laugh at the miscommunication happening here. Otherwise I'd get
>> frustrated. I was not trying to say it was a bug in Tapestry. It's a "bug
>>
;> experience. :)
>
>
> I have to laugh at the miscommunication happening here. Otherwise I'd get
> frustrated. I was not trying to say it was a bug in Tapestry. It's a "bug
> in my code" in the fact that I'm trying to use a nonexistent feature. And
>
I'm NOT suggesting that T5 should replay loops like T4. Tapestry has moved
beyond that and I have too. I am fully aware that Tapestry has introduced a
number of other features (page activation context, action context, and
formState) to take the place of replaying loops. I just haven&#
for the event.
And don't forget that the EventLink context is independent from the page
activation context. ComponentEventRequestParameters has two contexts: the
page one (getPageActivationContext) and the event one ().
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry
I agree... It sounded like a normal use case to me and I was fully expecting
it to "just work." But it didn't. I'm not trying to complicate things...
I'm looking for an uncomplicated solution... but I have not found one yet.
All of the code necessary to run this example can be found in my origin
hen tapestry processes
the click from the eventlink, so I need to find a way to make it not null
while tapestry processes that eventlink click... and specifically make it
equal the a value for a specific iteration through the loop... the iteration
that was occurring at the time the eventlink was being ren
I've been trawling the archive again on ways to manipulate the page
activation context and break up the parameters.
The specific scenario I'm working on is that of 'hijacking' part of the
activation context by a transformation worker or similar.
For example, I'd li
I also think that you're over-complicating this. To me this sounds like a
very normal use case, looping over items and creating a form for each one.
It should "just work". And it shouldn't be too many lines of complicated
code either, so the code listed here confuses me a bit.
Someone should post
On Sun, 14 Feb 2010 17:33:43 -0200, Nathan Kopp
wrote:
Even with your suggested change, this would still generate a null pointer
exception (NPE) in the same place, since the problem lies with
"fooLoopVar" being null when the eventlink is click is processed by
Tapestry.
You simply can't
ur event onEdit etc.
>@Persist @Property private Boolean isEditing;
>
>
>public void onSaveEditDonkey() {
>foo.getDonkey().saveToDB();
>}
> }
>
>
> Description:
>
> Its that simple.
>
> Peter
>
>
> - Original Message -
>
ooLoopVar), as T5 doesn't have a rewind phase.
Basically, I need something that works like the page activation context,
but generalized to work with any component at any level of the component
tree.
Inject ComponentEventLinkEncoder and use its
decodePageRenderRequest(Request request) me
irut, Bucharest,
Istanbul
Subject: Activation context for a component?
Hey everyone! I'm new here and I apologize for not lurking long before
posting. I have searched the archives extensively for this issue and have
come up empty, so I'm just going to jump in.
I'm working in Tapestry
ical, so there's no
way to tell which Donkey should be edited.
I tried using the "context" parameter of the eventlink component, but since
events start at the deepest level and bubble up, I got the null pointer
exception before I could use the context for anything useful at the outer
(p
-
From: Kristian Marinkovic [mailto:kristian.marinko...@porsche.co.at]
Sent: 18 January 2010 13:12
To: Tapestry users
Subject: Antwort: Passing Activation parameters to a page
hi,
you can't do it this way. if you return a string Tapestry will interpret it as
a logical page name and retu
Excellent.. Thanks Thiago. Ill give that a go.
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 18 January 2010 15:03
To: Tapestry users
Subject: Re: Passing Activation parameters to a page
On Mon, 18 Jan 2010 12:18:10 -0200, wrote:
> I hav
On Mon, 18 Jan 2010 12:18:10 -0200, wrote:
I have a large collection of lots of different Objects of varying
classes (all stemming from the one superclass) and have a view/edit page
for each of them. Instead of a big switch I simply wanted to redirect
to page "viewthe"+selectedType and th
@gmail.com]
Sent: 18 January 2010 13:07
To: Tapestry users
Subject: Re: Passing Activation parameters to a page
On Mon, 18 Jan 2010 11:00:12 -0200, wrote:
> Hi folks,
Hi!
> But I have a situation where I need to use the String method for page
> navigation but still need to pass a pa
d and return it in your
action method
g,
kris
18.01.2010 14:00
Bitte antworten an
"Tapestry users"
An
Kopie
Thema
Passing Activation parameters to a page
Hi folks,
Quick question - I am trying to pass parameters using the activation
context.
I normally use:
InjectPag
On Mon, 18 Jan 2010 11:00:12 -0200, wrote:
Hi folks,
Hi!
But I have a situation where I need to use the String method for page
navigation but still need to pass a parameter.
You can't return a String and still pass the activation context. Why do
you need to return a String at
Hi folks,
Quick question - I am trying to pass parameters using the activation context.
I normally use:
InjectPage
PageX thePage
...
...
onSomeEvent() {
thePage.setSomeParameter("SS");
Return thePage;
}
But I have a situation where I need to use the String method for page
navigation
Em Sat, 28 Nov 2009 12:04:19 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
Ok. Thanks for your quick answers. The problem was an URL rewriting rule
which messed up a few things. Sorry for the fuss.
No problem. :) URL rewriting is very interesting, but needs to be
implemented in a very car
. Clicking on submit will raise an error,
because param1 is null.
Have you tested it with an URL with an activation context value? I use
forms in pages that use the activation context to edit objects all the
time and never had this problem.
I am sorry, but what do you mean by independent? Is the
Em Sat, 28 Nov 2009 11:56:44 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
Here is a simple test. Clicking on submit will raise an error, because
param1 is null.
Have you tested it with an URL with an activation context value? I use
forms in pages that use the activation context to edit
Hi.
Here is a simple test. Clicking on submit will raise an error, because
param1 is null.
I am sorry, but what do you mean by independent? Is the activation
context supplied with form submits or not?
Br,
Timo.
public class FormSubmit {
private String param1;
void onActivate
Em Sat, 28 Nov 2009 09:27:27 -0200, Timo Westkämper
escreveu:
Hi.
Hi!
This is a Tapestry beginner's question :
When doing form submissions is the page's activation context submitted
and taken into account in the onActivate call or are activationContexts
only for na
Hi.
This is a Tapestry beginner's question :
When doing form submissions is the page's activation context submitted
and taken into account in the onActivate call or are activationContexts
only for navigational requests?
The documentation of Form doesn't mention on
Hi Angelo,
> I attempted to do some page/component testings with PageTester, finally
gave
> up, lately tried again with Testify, and gave up as well, following the
> tutorials, it works, but when trying to apply the test to an existing
> project, can not make it work, probably we need some more t
Hi Mats,
> I use Testify to smoke test our pages, and currently I have
> problems with a non-empty onActivate() function:
>
> public Object onActivate(Long id) {
> // ...
> }
>
> What do I need to mock to get this onActivate() function to
> be called?
To get the onActivate calle
nsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Testify-and-activation-context-problems-tp26057369p26075146.h
Hi!
I use Testify to smoke test our pages, and currently I have
problems with a non-empty onActivate() function:
public Object onActivate(Long id) {
// ...
}
What do I need to mock to get this onActivate() function to
be called?
Mats
About the above : with the caveat that propertyA and propertyB in MyPage
need to either be persistent or somehow handled w/ the
onActivate/onPassivate (see the jumpstart examples on that).
Cheers,
Alex K
On Thu, Oct 8, 2009 at 8:19 AM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
1 - 100 of 242 matches
Mail list logo
