Re: page activation + components

2008-05-05 Thread Josh Canfield
27;ve been saying is missing here is, what are you > > > > trying > > > > > > to do? I don't mean technically, I mean what is the end result for > > the > > > > > > user? Understanding this is critical, but even if I don't your > >

Re: page activation + components

2008-05-02 Thread János Jarecsni
; service and move on? > > > > > > > > > > János Jarecsni wrote: > > > > > > Hi, > > > > > > > > > > > > I looked everywhere for usage of request scope variables, but > found > > > > > nothi

Re: page activation + components

2008-05-02 Thread Josh Canfield
set some attribute > > for > > > > the > > > > > request only (not the session!) and then component B could render > > itself > > > > > according to the attribute set by component A? > > > > > > > > > > I

Re: page activation + components

2008-05-02 Thread Josh Canfield
e: > > > > > > Hi, > > > > > > > > > > > > I looked everywhere for usage of request scope variables, but > > found > > > > > nothing > > > > > > (maybe I'm impatient a bit :)... > > > > > > Is it really

Re: page activation + components

2008-05-02 Thread János Jarecsni
gt; > > > > > thx > > > > Janos > > > > > > > > 2008/4/30 Filip S. Adamsen <[EMAIL PROTECTED]>: > > > > > > > > > > > >> Nope, you're exactly right. > > > >> > > > >> -Filip >

Re: page activation + components

2008-05-02 Thread nicholas Krul
having an action link eventhandler where it would set some > attribute > > for > > > > the > > > > > request only (not the session!) and then component B could render > > itself > > > > > according to the attribute set by component A? >

Re: page activation + components

2008-05-02 Thread János Jarecsni
gt; > > > > I think it should be a piece of cake :) > > > > > > > > thx > > > > Janos > > > > > > > > 2008/4/30 Filip S. Adamsen <[EMAIL PROTECTED]>: > > > > > > > >

Re: page activation + components

2008-05-01 Thread Chris Lewis
Josh, Yeah that looks like it would do it, working much like what proposed with pagelinks. Given a choice I would use the pagelink based way because architecturally it works the same (news page collects the id via context), but using pagelinks reduces the round-trips and the need to deal with even

Re: page activation + components

2008-04-30 Thread Josh Canfield
Here's an app that does what I believe is trying to be done: // Page public class News { @Property private Integer _newsId; public void onActivate(Integer newsId) { _newsId = newsId; } public Integer onPassivate() { r

Re: page activation + components

2008-04-30 Thread Chris Lewis
I do hope we've missed a simpler way, but I don't think it's surfaced yet. Regarding parameters, how would that address the issue? NewsQuote displays a collection of items as links that represent selectable items (expressed as links). The action must be taken based on the user's selection, so a com

Re: page activation + components

2008-04-30 Thread Josh Canfield
n link eventhandler where it would set some attribute for > >>>> > >>> the > >>> > >>>> request only (not the session!) and then component B could render itself > >>>> according to the attribute set by component A? > >>>> >

Re: page activation + components

2008-04-30 Thread Chris Lewis
this the last of it 4) In our embedding page class, News, we have an event handler to be notified of the selection by handling the "viewitem" event: void onViewitem(long id) { this.currentItem = newsSource.getItemById(id); logger.info("got " + this.currentItem.getTitle

Re: page activation + components

2008-04-30 Thread Chris Lewis
ent A? >>>> >>>> I think it should be a piece of cake :) >>>> >>>> thx >>>> Janos >>>> >>>> 2008/4/30 Filip S. Adamsen <[EMAIL PROTECTED]>: >>>> >>>> >>>>

RE: page activation + components

2008-04-30 Thread Joel Wiegman
f I'm off base... I only skimmed the thread. -Original Message- From: Chris Lewis [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 30, 2008 4:27 PM To: Tapestry users Subject: Re: page activation + components I see how this whole push on/pull off environment will solve the iss

Re: page activation + components

2008-04-30 Thread Chris Lewis
it should be a piece of cake :) >>>> >>>> thx >>>> Janos >>>> >>>> 2008/4/30 Filip S. Adamsen <[EMAIL PROTECTED]>: >>>> >>>> >>>> >>>>> Nope, you're exactly right. >>&g

Re: page activation + components

2008-04-30 Thread Chris Lewis
uld be a piece of cake :) >>>> >>>> thx >>>> Janos >>>> >>>> 2008/4/30 Filip S. Adamsen <[EMAIL PROTECTED]>: >>>> >>>> >>>> >>>>> Nope, you're exactly right.

Re: page activation + components

2008-04-30 Thread Josh Canfield
gt; This is not what I understood 'perthread' scope to be. I thought that > > it > > >> > > >>> meant that each thread using a service gets its own instance of the > > service > > >>> to use, even though that instance may not be the same

Re: page activation + components

2008-04-30 Thread Filip S. Adamsen
ilto:[EMAIL PROTECTED] Sent: 29 April 2008 17:34 To: Tapestry users Subject: Re: page activation + components Hello, You can define the scope of each service...you can set that particular service to be tied to only one session. See http://tapestry.apache.org/tapestry5/tapestry-ioc/service.html , a

Re: page activation + components

2008-04-30 Thread Chris Lewis
n component B could render >>>>> >> itself >> >>>>> according to the attribute set by component A? >>>>> >>>>> I think it should be a piece of cake :) >>>>> >>>>> thx >>>>> Janos

Re: page activation + components

2008-04-30 Thread János Jarecsni
t be the same as any > > > > previous > > > > instance it used. In other words, nothing to do with user sessions, > > > > it's > > > > just for services that are not thread safe and cannot be singletons. > > > > > > > > Have I got the wrong en

Re: page activation + components

2008-04-30 Thread János Jarecsni
gt; >>>> Nope, you're exactly right. > >>>> > >>>> -Filip > >>>> > >>>> Blower, Andy skrev: > >>>> > >>>> This is not what I understood 'perthread' scope to be. I thought > that

Re: page activation + components

2008-04-30 Thread Chris Lewis
gt;> >> it >> >>>>> meant that each thread using a service gets its own instance of the >>>>> >> service >> >>>>> to use, even though that instance may not be the same as any previous >>>>

Re: page activation + components

2008-04-30 Thread János Jarecsni
instance it used. In other words, nothing to do with user sessions, > > > > it's > > > > just for services that are not thread safe and cannot be singletons. > > > > > > > > Have I got the wrong end of the stick here? > > > > > > >

Re: page activation + components

2008-04-30 Thread János Jarecsni
x27; scope to be. I thought that > it > >> > >>> meant that each thread using a service gets its own instance of the > service > >>> to use, even though that instance may not be the same as any previous > >>> instance it used. In

Re: page activation + components

2008-04-30 Thread Chris Lewis
gt;> just for services that are not thread safe and cannot be singletons. >>> >>> Have I got the wrong end of the stick here? >>> >>> -Original Message- >>> >>>> From: Andy Huhn [mailto:[EMAIL PROTECTED] >>>> Sent:

Re: page activation + components

2008-04-30 Thread Filip S. Adamsen
other words, nothing to do with user sessions, it's just for services that are not thread safe and cannot be singletons. Have I got the wrong end of the stick here? -Original Message- From: Andy Huhn [mailto:[EMAIL PROTECTED] Sent: 29 April 2008 17:34 To: Tapestry users Subject: Re: page

Re: page activation + components

2008-04-30 Thread János Jarecsni
to do with user sessions, it's > > just for services that are not thread safe and cannot be singletons. > > > > Have I got the wrong end of the stick here? > > > > -Original Message- > > > From: Andy Huhn [mailto:[EMAIL PROTECTED] > > > Sent

Re: page activation + components

2008-04-30 Thread Filip S. Adamsen
This is not what @Retain is for. If you use it, the value won't be cleared out at the end of the request. http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/annotations/Retain.html -Filip Michael Gerzabek skrev: 6) @Retain could do the job. Your String will be available until the

Re: page activation + components

2008-04-30 Thread Filip S. Adamsen
ry users Subject: Re: page activation + components Hello, You can define the scope of each service...you can set that particular service to be tied to only one session. See http://tapestry.apache.org/tapestry5/tapestry-ioc/service.html, and search for "perthread". Thanks, Andy On T

Re: page activation + components

2008-04-30 Thread János Jarecsni
nstance it used. In other words, nothing to do with user sessions, it's > > just for services that are not thread safe and cannot be singletons. > > > > Have I got the wrong end of the stick here? > > > > > -Original Message- > > > From: Andy Huhn

Re: page activation + components

2008-04-30 Thread János Jarecsni
MAIL PROTECTED] > > Sent: 29 April 2008 17:34 > > To: Tapestry users > > Subject: Re: page activation + components > > > > > > Hello, > > > > You can define the scope of each service...you can set that particular > > service to be tied to only on

RE: page activation + components

2008-04-30 Thread Blower, Andy
ions, it's just for services that are not thread safe and cannot be singletons. Have I got the wrong end of the stick here? > -Original Message- > From: Andy Huhn [mailto:[EMAIL PROTECTED] > Sent: 29 April 2008 17:34 > To: Tapestry users > Subject: Re: page activation + c

Re: page activation + components

2008-04-30 Thread János Jarecsni
laborate more on your > problem > will probably be able to give a more concise advice :) > > g, > kris > > > > > "János Jarecsni" <[EMAIL PROTECTED]> > 30.04.2008 08:50 > Bitte antworten an > "Tapestry users" > > > An &g

Re: page activation + components

2008-04-30 Thread János Jarecsni
s <[EMAIL PROTECTED]>: > > >> > >>> > > >> > >>> > > >> > >>> > > >> > >>>> 5) @InjectPage the page and call the getter > > >> > >>>> > > >> > >>&g

Re: page activation + components

2008-04-30 Thread Kristian Marinkovic
able to give a more concise advice :) g, kris "János Jarecsni" <[EMAIL PROTECTED]> 30.04.2008 08:50 Bitte antworten an "Tapestry users" An "Tapestry users" Kopie Thema Re: page activation + components Hi, thx for the info! Another idea... is ther

Re: page activation + components

2008-04-29 Thread János Jarecsni
;>> hi janos, > >> > >>>>> > >> > >>>>> there are several possibilities: > >> > >>>>> > >> > >>>>> 1) declare a component parameter and pass in the variable > >> > >>>>> > >> > >>>

Re: page activation + components

2008-04-29 Thread Andy Huhn
ossibilities: >> > >>>>> >> > >>>>> 1) declare a component parameter and pass in the variable >> > >>>>> >> > >>>>> 2) put it in a ASO and inject the ASO in all your components >> > (using >> > >>>>>

Re: page activation + components

2008-04-29 Thread János Jarecsni
t;> 3) put it into the Environment and read it whereever you need it > > in > > >>>>> > > >> your > > >> > > >>>>> nested components. > > >>>>> be careful when you put your object in your environment. if you > > put it &

Re: page activation + components

2008-04-29 Thread János Jarecsni
> 3) put it into the Environment and read it whereever you need it in > >>>>> > >> your > >> > >>>>> nested components. > >>>>> be careful when you put your object in your environment. if you put > it > >>>

Re: page activation + components

2008-04-29 Thread Chris Lewis
;>>>> request it will not be able in the render request (because of the page >>>>> redirect). >>>>> >>>>> page: >>>>> >>>>> @Inject Environment env; >>>>> >>>>> @Persi

Re: page activation + components

2008-04-29 Thread János Jarecsni
.class,w);} > >>> > >>> components: > >>> > >>> @Environmental Whateverclass var; > >>> > >>> 4) define a service that can take this variable (and saves it > >>> > >> appropriatly > >> > >

Re: page activation + components

2008-04-29 Thread Chris Lewis
;> onActivate(w) { this.w= w } >>> >>> setupRender() { env.push(whateverclass.class,w);} >>> >>> components: >>> >>> @Environmental Whateverclass var; >>> >>> 4) define a service that can take this variable (and saves i

Re: page activation + components

2008-04-29 Thread Michael Gerzabek
try users" An "Tapestry users" Kopie Thema page activation + components Hi there, I have an activatable page, in its onActivate(String param) method I save the param to a normal instance variable of the page class (no persistence!). How can any component embedded wit

Re: page activation + components

2008-04-29 Thread János Jarecsni
lost on a redirect:)) and inject your service in the components where > > needed > > to retrieve the value. > > > > maybe there are some more possibilities :) > > > > g, > > kris > > > > > > > > > > "János Jarecsni" <[EM

Re: page activation + components

2008-04-29 Thread Michael Gerzabek
6) @Retain could do the job. Your String will be available until the end of the request. János Jarecsni schrieb: Hi there, I have an activatable page, in its onActivate(String param) method I save the param to a normal instance variable of the page class (no persistence!). How can any compone

Re: page activation + components

2008-04-29 Thread Chris Lewis
gt; maybe there are some more possibilities :) > > g, > kris > > > > > "János Jarecsni" <[EMAIL PROTECTED]> > 29.04.2008 08:15 > Bitte antworten an > "Tapestry users" > > > An > "Tapestry users" > Kopie > >

Re: page activation + components

2008-04-29 Thread Kristian Marinkovic
components where needed to retrieve the value. maybe there are some more possibilities :) g, kris "János Jarecsni" <[EMAIL PROTECTED]> 29.04.2008 08:15 Bitte antworten an "Tapestry users" An "Tapestry users" Kopie Thema page activation + components

page activation + components

2008-04-28 Thread János Jarecsni
Hi there, I have an activatable page, in its onActivate(String param) method I save the param to a normal instance variable of the page class (no persistence!). How can any component embedded within this page access this variable? the page class: //... private String param; public void onActiva