You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by James Carman <ja...@carmanconsulting.com> on 2006/05/02 14:39:31 UTC
[tapernate] Session-Per-Conversation...
All,
I've removed support (well, it wasn't really supporting it anyway) for
session-per-conversation in Tapernate. I would like to make it much more
robust, allowing for "named" conversations. I need to figure out a nice,
clean way to declare what conversation an action is supposed to take part
in. Of course, we could declare an API like this:
conversationUtils.joinConversation( "updateMessage" );
conversationUtils.endConversation( "updateMessage" );
And, if you don't join a conversation, you just take part in the general
conversation (which is only request-scoped). But, this would clutter up the
code with these join/end conversation requests. I'd like to use annotations
for this, but haven't come up with a nice way of doing so. I might be able
to use an EnhancementWorker to do it.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [tapernate] Session-Per-Conversation...
Posted by Konstantin Iignatyev <kg...@yahoo.com>.
Spring Hibernate Template is the truly horrible piece of code that
should be removed from Spring codebase.
Please read the blog
http://houseofhaug.net/blog/archives/2005/08/12/hibernate-hates-spring/
and check technical arguments, have to filter out emotions though.
Spring Has much nicer and even easier solutions to the Hibernate
integration which do proper transaction propagation etc.
http://www.onjava.com/pub/a/onjava/2005/05/18/swingxactions.html?page=1
http://sandbox.sourcelabs.com/kosta/hibernate-bhw/java/com/sourcelabs/hibernate/bhw/haop/doc/haop.html
Mark wrote:
>
>> And, if you don't join a conversation, you just take part in the general
>> conversation (which is only request-scoped). But, this would clutter
>> up the
>> code with these join/end conversation requests. I'd like to use
>> annotations
>> for this, but haven't come up with a nice way of doing so. I might
>> be able
>> to use an EnhancementWorker to do it.
>>
>
> Since you use some Spring stuff anyway, how about some Spring-Template
> style solution to this?
> It would really be great if you could figure out a way to keep
> Tapernate 1.4 compatible (if it's not too late already)...
>
> MARK
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Thanks,
Konstantin Ignatyev
http://www.kgionline.com
PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2.700 tons of CFCs to the stratosphere, and increase their population by 263.000
Bowers, C.A. The Culture of Denial:
Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools.
New York: State University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: [tapernate] Session-Per-Conversation...
Posted by James Carman <ja...@carmanconsulting.com>.
Oh, that would be an option. Right now, you do the transaction demarcation
in your hivemodule.xml file.
-----Original Message-----
From: Mark [mailto:lists@mark-arnold.net]
Sent: Thursday, May 04, 2006 1:56 AM
To: Tapestry users
Subject: Re: [tapernate] Session-Per-Conversation...
I mainly wrote that because you were thinking about annotations for the
transaction demarcation...
James Carman wrote:
> I'll have to look at it, but I don't know that I use any 1.5-specific
> features. I think I only have one place where I use a "typed" collection
> (in the persistence strategy), but that's not a must. I'll see what I can
> do.
>
>
>
>
> It would really be great if you could figure out a way to keep
> Tapernate
> 1.4 compatible (if it's not too late already)...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [tapernate] Session-Per-Conversation...
Posted by Mark <li...@mark-arnold.net>.
I mainly wrote that because you were thinking about annotations for the
transaction demarcation...
James Carman wrote:
> I'll have to look at it, but I don't know that I use any 1.5-specific
> features. I think I only have one place where I use a "typed" collection
> (in the persistence strategy), but that's not a must. I'll see what I can
> do.
>
>
>
>
> It would really be great if you could figure out a way to keep
> Tapernate
> 1.4 compatible (if it's not too late already)...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: [tapernate] Session-Per-Conversation...
Posted by James Carman <ja...@carmanconsulting.com>.
I'll have to look at it, but I don't know that I use any 1.5-specific
features. I think I only have one place where I use a "typed" collection
(in the persistence strategy), but that's not a must. I'll see what I can
do.
-----Original Message-----
From: Mark [mailto:lists@mark-arnold.net]
Sent: Wednesday, May 03, 2006 1:51 AM
To: Tapestry users
Subject: Re: [tapernate] Session-Per-Conversation...
> And, if you don't join a conversation, you just take part in the general
> conversation (which is only request-scoped). But, this would clutter up
the
> code with these join/end conversation requests. I'd like to use
annotations
> for this, but haven't come up with a nice way of doing so. I might be
able
> to use an EnhancementWorker to do it.
>
Since you use some Spring stuff anyway, how about some Spring-Template
style solution to this?
It would really be great if you could figure out a way to keep Tapernate
1.4 compatible (if it's not too late already)...
MARK
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [tapernate] Session-Per-Conversation...
Posted by Mark <li...@mark-arnold.net>.
> And, if you don't join a conversation, you just take part in the general
> conversation (which is only request-scoped). But, this would clutter up the
> code with these join/end conversation requests. I'd like to use annotations
> for this, but haven't come up with a nice way of doing so. I might be able
> to use an EnhancementWorker to do it.
>
Since you use some Spring stuff anyway, how about some Spring-Template
style solution to this?
It would really be great if you could figure out a way to keep Tapernate
1.4 compatible (if it's not too late already)...
MARK
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: [tapernate] Session-Per-Conversation...
Posted by James Carman <ja...@carmanconsulting.com>.
Henri,
It doesn't quite have a homepage just yet. It's going to be hosted along
with the other Tapestry goodies at Howards site
(http://howardlewisship.com/tapestry-javaforge/). I just haven't had time
to move it just yet (or come up with a cool logo). For now, it's just a
demo application that I have on my own SVN server. I'll try to set it up
soon, I promise.
James
-----Original Message-----
From: Henri Dupre [mailto:henri.dupre@gmail.com]
Sent: Tuesday, May 02, 2006 10:00 AM
To: Tapestry users
Subject: Re: [tapernate] Session-Per-Conversation...
What is the homepage of the tapernate project?
It sounds really great.
On 5/2/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> All,
>
> I've removed support (well, it wasn't really supporting it anyway) for
> session-per-conversation in Tapernate. I would like to make it much more
> robust, allowing for "named" conversations. I need to figure out a nice,
> clean way to declare what conversation an action is supposed to take part
> in. Of course, we could declare an API like this:
>
> conversationUtils.joinConversation( "updateMessage" );
> conversationUtils.endConversation( "updateMessage" );
>
> And, if you don't join a conversation, you just take part in the general
> conversation (which is only request-scoped). But, this would clutter up
> the
> code with these join/end conversation requests. I'd like to use
> annotations
> for this, but haven't come up with a nice way of doing so. I might be
> able
> to use an EnhancementWorker to do it.
>
> James
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Thanks,
Henri.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: [tapernate] Session-Per-Conversation...
Posted by Henri Dupre <he...@gmail.com>.
What is the homepage of the tapernate project?
It sounds really great.
On 5/2/06, James Carman <ja...@carmanconsulting.com> wrote:
>
> All,
>
> I've removed support (well, it wasn't really supporting it anyway) for
> session-per-conversation in Tapernate. I would like to make it much more
> robust, allowing for "named" conversations. I need to figure out a nice,
> clean way to declare what conversation an action is supposed to take part
> in. Of course, we could declare an API like this:
>
> conversationUtils.joinConversation( "updateMessage" );
> conversationUtils.endConversation( "updateMessage" );
>
> And, if you don't join a conversation, you just take part in the general
> conversation (which is only request-scoped). But, this would clutter up
> the
> code with these join/end conversation requests. I'd like to use
> annotations
> for this, but haven't come up with a nice way of doing so. I might be
> able
> to use an EnhancementWorker to do it.
>
> James
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Thanks,
Henri.