You need to be careful with the http session. It can be used on
multiple threads unlike an ejb stateful session bean.
Regards,
Adrian
On Mon, 2004-01-19 at 16:50, Bill Burke wrote:
> I'd like for somebody to look into being able to define transaction
> demarcation like we can for EJB at the serv
ll
Marc Fleury wrote:
Isn't that already part of the AOP framework or
are you talking about a
servlet filter?
narcf
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On
Behalf Of Bill Burke
Sent: Monday, January 19, 2004 11:51 AM
To: Jboss-Dev
Subject: [JBoss-dev] URL
Jboss-Dev
Subject: [JBoss-dev] URL based transaction
demarcation and
long running transations
I'd like for somebody to look into being able to
define
transaction demarcation like we can for EJB at the
servlet/jsp/war level. So, based on a URL pattern
you can
specify trans-attributes.
TED]
>
>>[mailto:[EMAIL PROTECTED]
> On
> >>Behalf Of Bill Burke
> >>Sent: Monday, January 19, 2004 11:51 AM
> >>To: Jboss-Dev
> >>Subject: [JBoss-dev] URL based transaction
> demarcation and
> >>long running transations
> >>
> &g
JBoss-dev] URL based transaction demarcation and
long running transations
I'd like for somebody to look into being able to define
transaction demarcation like we can for EJB at the
servlet/jsp/war level. So, based on a URL pattern you can
specify trans-attributes. Along with this would b
ect: [JBoss-dev] URL based transaction demarcation and
> long running transations
>
> I'd like for somebody to look into being able to define
> transaction demarcation like we can for EJB at the
> servlet/jsp/war level. So, based on a URL pattern you can
> specify tra
I'd like for somebody to look into being able to define transaction
demarcation like we can for EJB at the servlet/jsp/war level. So, based
on a URL pattern you can specify trans-attributes. Along with this
would be stuffing the transaction into the HTTP session so that you can
have long tran
