You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Lars-Fredrik Smedberg <it...@gmail.com> on 2015/02/10 12:28:19 UTC
Quersion on @AccessTimeout....
Hi!
Just curious, on
http://tomee.apache.org/examples-trunk/access-timeout/README.html I read
that @AccessTimeout also works for Stateless EJBs but in the JavaDoc for
AccessTimeout and EJB (318) I only see stasteful and singleton EJBs....
Out of curiosity... is this "out of spec" and something implemented in
TomEE only?
Regards
LF
--
Med vänlig hälsning / Best regards
Lars-Fredrik Smedberg
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
address(es) and may contain confidential or privileged information. If
you are not the intended recipient, please notify Lars-Fredrik Smedberg
immediately at itsmeden@gmail.com, and destroy all copies of this
message and any attachments.
Re: Quersion on @AccessTimeout....
Posted by Lars-Fredrik Smedberg <it...@gmail.com>.
Hi
Guess so, the TomEE example was refering to the case where there were no
available stateless EJBs in the pool... and the application could in that
case choose to wait or not...
Regards
LF
On Tue, Feb 10, 2015 at 12:41 PM, Brent Douglas <br...@gmail.com>
wrote:
> Hi Lars,
>
> That sounds like a TomEE thing. In the EJB 3.1 spec section 4.3.14 says
> this:
>
> There is no need for any restrictions against concurrent client access to
> > stateless session beans because
> > the container routes each request to a different instance of the
> stateless
> > session bean class.
>
>
> Brent
>
> On Tue, Feb 10, 2015 at 12:28 PM, Lars-Fredrik Smedberg <
> itsmeden@gmail.com>
> wrote:
>
> > Hi!
> >
> > Just curious, on
> > http://tomee.apache.org/examples-trunk/access-timeout/README.html I read
> > that @AccessTimeout also works for Stateless EJBs but in the JavaDoc for
> > AccessTimeout and EJB (318) I only see stasteful and singleton EJBs....
> >
> > Out of curiosity... is this "out of spec" and something implemented in
> > TomEE only?
> >
> > Regards
> > LF
> >
> > --
> > Med vänlig hälsning / Best regards
> >
> > Lars-Fredrik Smedberg
> >
> > STATEMENT OF CONFIDENTIALITY:
> > The information contained in this electronic message and any
> > attachments to this message are intended for the exclusive use of the
> > address(es) and may contain confidential or privileged information. If
> > you are not the intended recipient, please notify Lars-Fredrik Smedberg
> > immediately at itsmeden@gmail.com, and destroy all copies of this
> > message and any attachments.
> >
>
--
Med vänlig hälsning / Best regards
Lars-Fredrik Smedberg
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
address(es) and may contain confidential or privileged information. If
you are not the intended recipient, please notify Lars-Fredrik Smedberg
immediately at itsmeden@gmail.com, and destroy all copies of this
message and any attachments.
Re: Quersion on @AccessTimeout....
Posted by Brent Douglas <br...@gmail.com>.
Hi Lars,
That sounds like a TomEE thing. In the EJB 3.1 spec section 4.3.14 says
this:
There is no need for any restrictions against concurrent client access to
> stateless session beans because
> the container routes each request to a different instance of the stateless
> session bean class.
Brent
On Tue, Feb 10, 2015 at 12:28 PM, Lars-Fredrik Smedberg <it...@gmail.com>
wrote:
> Hi!
>
> Just curious, on
> http://tomee.apache.org/examples-trunk/access-timeout/README.html I read
> that @AccessTimeout also works for Stateless EJBs but in the JavaDoc for
> AccessTimeout and EJB (318) I only see stasteful and singleton EJBs....
>
> Out of curiosity... is this "out of spec" and something implemented in
> TomEE only?
>
> Regards
> LF
>
> --
> Med vänlig hälsning / Best regards
>
> Lars-Fredrik Smedberg
>
> STATEMENT OF CONFIDENTIALITY:
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> address(es) and may contain confidential or privileged information. If
> you are not the intended recipient, please notify Lars-Fredrik Smedberg
> immediately at itsmeden@gmail.com, and destroy all copies of this
> message and any attachments.
>