Hi!
Ashwin Dinakar wrote:
> >Further, there is nothing that prevents Enterprise Beans to be producers
> >of JMS messages, or at least you should not consider the EJB threading
> >restrictions to be the cause, again as has been discussed extensively
> >during the past weeks. See my post on EJB and its relation to the
> >security API for example
> Ok. This is something I didnt realize. I thought both producer and consumers were
>both 'clients' of the JMS SP.
Correct. But there are less practical problems with being a producer
than a consumer.
> >(http://archives.java.sun.com/cgi-bin/wa?A2=ind9911&L=ejb-interest&P=R45924).
> >
> >Is there anything about this matter that you feel to be unclear, and if
> >so, what?
> >
> >/Rickard
> That posting relates to the security issues with I/O and sockets...
> with threads...if you invoke threads within EJB does one still get security
>exceptions ? Or in other words how does the Container prevent the bean developer from
>using threads ??
In order to create Threads you need a special RuntimePermission which an
EJB does not have. However it may call other classes that has these
permissions.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
