Not out of the box. See http://grepcode.com/file/repo1.maven.org/maven2/org.tynamo/tapestry-conversations/0.1.2/org/tynamo/conversations/services/ConversationManagerImpl.java I would prefer using it as a query param in some cases. You could do it yourself by manually activating the conversation etc.
Cheers, Dragan Sahpaski On Thu, Nov 7, 2013 at 3:01 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > Quick question: does the package support mapping the conversation id to a > query parameter? > > > On Thu, 07 Nov 2013 11:30:59 -0200, Dragan Sahpaski < > dragan.sahpa...@gmail.com> wrote: > > On Thu, Nov 7, 2013 at 2:07 PM, Dmitriy Vsekhvalnov >> <dvsekhval...@gmail.com>wrote: >> >> Hey Dragan, >>> >>> conversations seems to be ok, except one issue i ran into, my context >>> looks >>> like this: /page/parent-id/child-id or /page/parent-id, e.g. >>> >>> /page/100/23 - edit object >>> /page/100 - new object >>> >>> if i add conversion id how can i distinguish second one? >>> /page/100/123213213 vs. /page/100/23 ? >>> >>> >> See org.tynamo.conversations.services.ConversationManager. You can check >> if the second parameter is a valid conversation id. Best to keep the >> conversation id as the last parameter and check for it's validity. BTW if >> you've already decided to use conversations consider if persisting the >> parent-id and child-id context parameters is a viable option. With the >> conversation id in the page context your pages are bookmarkable, so now >> the >> balance between keeping objects in memory or in the context is a >> complexity >> balancing issue. More complex code or bigger memory hit. Up to you to >> decide. >> >> >> >> >> >>> >>> >>> >>> On Wed, Nov 6, 2013 at 3:23 PM, Dragan Sahpaski >>> <dragan.sahpa...@gmail.com>wrote: >>> >>> > Hi Dmitriy, >>> > What you've described is having a conversational scope. >>> > Look at the tapestry-conversations module >>> > http://tynamo.org/tapestry-conversations+guide. I think the guide is >>> > pretty >>> > clear and you will have an easy time integrating it. >>> > We use the module in multiple projects and it works very well. >>> > >>> > Cheers, >>> > Dragan Sahpaski >>> > >>> > >>> > On Wed, Nov 6, 2013 at 12:11 PM, Dmitriy Vsekhvalnov < >>> > dvsekhval...@gmail.com >>> > > wrote: >>> > >>> > > Hi all, >>> > > >>> > > looking for a way to have session storage per context, e.g. 2 pages: >>> > > >>> > > /profile/details/1 >>> > > /profile/details/2 >>> > > >>> > > if work with both in different tabs session storage data obviously >>> > > clashing. >>> > > >>> > > Any ideas how to make per-context session? >>> > > >>> > > Thanks. >>> > > >>> > >>> >>> > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
