Re: Recommended way to instantiate EventContext

2016-11-29 Thread Adam X
Thanks Chris. I got it all working. On Mon, Nov 28, 2016 at 7:32 PM, Chris Poulsen wrote: > Normally you would return an Object[] from passivate and tapestry will > coerce it into the correct result. > > -- > Chris > > On Mon, Nov 28, 2016 at 6:41 PM, Adam X wrote: > >> Okay, I tried @Persist(FL

Re: Recommended way to instantiate EventContext

2016-11-28 Thread Chris Poulsen
Normally you would return an Object[] from passivate and tapestry will coerce it into the correct result. -- Chris On Mon, Nov 28, 2016 at 6:41 PM, Adam X wrote: > Okay, I tried @Persist(FLASH) EventContext ec storing it in activation > and simply returning in passivation and it works. > > Thi

Re: Recommended way to instantiate EventContext

2016-11-28 Thread Adam X
Okay, I tried @Persist(FLASH) EventContext ec storing it in activation and simply returning in passivation and it works. This came up as I was trying to solve a different problem which is still haunting me. Essentially, I did a modal feature just like in the jumpstart and it all works very nice:

Re: Recommended way to instantiate EventContext

2016-11-28 Thread Adam X
I'm trying to passivate large number (and dynamic) contexts. The signature of my activation looks like this: @OnEvent(value=EventConstants.ACTIVATE) void parseContext(EventContext ec) { and there is a lot going on in there as far as parsing the context. So I'm trying to do this to passiva

Re: Recommended way to instantiate EventContext

2016-11-28 Thread Peter Hvass
Hey again! Are you trying to pass a value to the context parameter of an eventlink by any chance? You can just use any old properties in Java classes - either the Tapestry way with an @Property attached to a field or a public getter of any old type. If it's anything beyond standard Java types (i.