Now. I see you just left. You need to ping me on irc - i.e. call my id -
otherwise I won't know somebody is asking for me.
Kalle
On Wed, Apr 29, 2009 at 2:54 PM, Jorge Saridis <jsari...@gmail.com> wrote:
> Kalle, I'm using Tapestry 5.0.18, I'm checking if conversationId is null
> and I'm persisting to session conversationId
> When do I find you on #trails?
> Thanks
> Jorge
>
> On Wed, 2009-04-29 at 12:49 -0700, Kalle Korhonen wrote:
>
> > On Wed, Apr 29, 2009 at 12:06 PM, Jorge Saridis <jsari...@gmail.com>
> wrote:
> >
> > > Kalle, i couldn't make it work
> > > I used exactly the examples on the page. My application uses tapestry
> > > spring security, equanda and chenillekit. In case it matters.
> >
> >
> > I'm using chenillekit, but not equanda and instead of spring security,
> > jsecurity/ki integration with Tapestry. I'm using 0.0.3 of
> > Trails-conversations in a production app without issues. The two things
> that
> > could make a difference is Spring security and possibly the version of T5
> -
> > I have not tested against T5.1 yet.
> >
> > The boolean expression in this line:
> > > if (!conversationManager.isActiveConversation(conversationId)) {
> > > once conversation is created, always returns false, so conversation
> > > remains the same even when I navigate to another page.
> > > Another thing is that conversation persisted fields never "remember"
> > > their values if I create the conversation with useCookie = false
> > > What am I doing wrong?
> >
> >
> > Well, sounds like the conversation is not being activated properly -
> > obviously the values should be remembered if the conversation is active.
> > There are multiple different ways to set it up. There's a working example
> of
> > conversations in Trails trunk at
> >
> http://svn.codehaus.org/trails/trunk/trails/examples/trails-examples-conversations/
> .
> > But first things first - have you verified that conversationId is not
> null?
> > I.e. you are persisting conversationId to session? Might be easier to
> find
> > the problem if you join #trails on irc.codehaus.org.
> >
> > Kalle
> >
> >
> >
> > >
> > > On Sun, 2009-04-05 at 19:51 -0700, Kalle Korhonen wrote:
> > >
> > > > Codehaus release repo is automatically synched to repo1.maven.org,
> but
> > > it
> > > > takes a day or so after a release. Available now at
> > > >
> > >
> http://repo1.maven.org/maven2/org/trailsframework/tapestry-conversations/0.0.2/
> > > > .
> > > >
> > > > Kalle
> > > >
> > > >
> > > > On Sun, Apr 5, 2009 at 2:09 AM, Scott Russell <scottam...@gmail.com>
> > > wrote:
> > > >
> > > > > Could you supply a download link for 0.0.2? I can't find one on
> your
> > > site,
> > > > > and maven still shows only 0.0.1 available. I'll take a look and
> see if
> > > it
> > > > > fixes the problem I was having.
> > > > >
> > > > > cheers,
> > > > > Scott
> > > > >
> > > > >
> > > > > On Sun, 5 Apr 2009 14:34:30 Kalle Korhonen wrote:
> > > > > > On Sat, Apr 4, 2009 at 5:29 PM, Scott Russell <
> scottam...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > I tried your conversation module (v0.0.1) and it works quite
> well,
> > > > > except
> > > > > > > that I found a bug whereby the Conversation, upon being
> initially
> > > > > created,
> > > > > > > wasn't being activated properly. However, I patched it and
> found it
> > > to
> > > > > work
> > > > > > > quite well. Do you have a bug tracking site somewhere that I
> could
> > > file
> > > > > the
> > > > > > > bug and the fix?
> > > > > >
> > > > > >
> > > > > > I believe you are referring to
> > > > > > http://jira.codehaus.org/browse/TRAILS-170which is fixed in
> 0.0.2.
> > > The
> > > > > > link to JIRA component is at
> > > > > > http://jira.codehaus.org/browse/TRAILS/component/13674. The
> module
> > > is
> > > > > > developed as part of Trails. For 0.0.2 I renamed the artifactId
> from
> > > > > > trails-conversations to tapestry-conversations to indicate it can
> be
> > > used
> > > > > > independently from the rest of Trails modules. 0.0.2 also has the
> > > > > optional
> > > > > > ConversationModerator component to track idle conversations and
> to
> > > notify
> > > > > > user. Obviously the library is still in its infancy which is why
> > > haven't
> > > > > > made much noise about it but I've been using it in my own
> projects
> > > and
> > > > > found
> > > > > > it to work very well.
> > > > > >
> > > > > > Kalle
> > > > > >
> > > > > >
> > > > > > On Sun, 5 Apr 2009 08:38:59 Kalle Korhonen wrote:
> > > > > > > Use either "flash" persistence strategy (
> > > > > > > http://tapestry.apache.org/tapestry5/guide/persist.html) or
> create
> > > a
> > > > > > > "conversation" (
> > > > > > >
> http://docs.codehaus.org/display/TRAILS/Conversations+in+Trails,
> > > just
> > > > > > > released 0.0.2).
> > > > > > >
> > > > > > > Kalle
> > > > > > >
> > > > > > > On Sat, Apr 4, 2009 at 12:25 PM, Jorge Saridis <
> jsari...@gmail.com
> > > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > In Tapestry 4.1, I used a persistence strategy named
> > > "session-page"
> > > > > > > > obtained from
> > > http://wiki.apache.org/tapestry/SessionPagePersistence
> > > > > ,
> > > > > > > > that allows discard session values when user exits the page.
> > > > > > > > How can I do this in Tapestry 5?
> > > > > > > > Thanks in advance
> > > > > > > > Jorge
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > > > > > > For additional commands, e-mail:
> users-h...@tapestry.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > > > > For additional commands, e-mail: users-h...@tapestry.apache.org
> > > > >
> > > > >
> > >
>
