I recommend that you try the filter approach. You could solve your transaction boundary problem for all your Hibernate users doing webapps at once. Someone could be doing something as primitive as a servlet+jsp w/ scriptlets and you would still have them covered. I'm not sure, but Sitemesh+WW integration might make things tricky if you don't extend your transaction boundary around Sitemesh.
-Maurice
On Friday, November 8, 2002, at 06:06 AM, Gavin King wrote:
I havn't tried anything at all. I am mainly asking for a recommended "best"Hav you tried using a servlet filter for this?/Rickard
approach that I can add to our doco. If thats the best approach, I will
write that :)
Thanks Rickard.
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
