Hey
Kenneth D. Litwak wrote:
> IN a stateful session bean, you need to save the state of the bean when it
> is passivated in case the server crashes while the bean is passivated. Great.
> Yet, the spec says yo shouldn't do I/O.
>
> A BMP Entity bean needs to save its state when passivated. Since there's
> not a requirement as such that t the bean use a db, it could end up doing I/O
> of some kind. In fact, I've read that BMP is good for sending or getting data
> from a legacy app. I see no way to do any of this wihtout violating the
> restriction on I/O. How do I save my session bean's state to persistent
> storeage without doing I/O, unless I want to use a database, which then means
> creating an Entity beanperhaps for the sole purpose of avoiding opening a
> strream or socket. SO I don't see how to put the restrictions and passivation
> of a stateful sessin bean or the restrictions and the work of a BMP together.
> Can someone enlighten me o on this? Thanks.
This relates directly to the recent discussion re: restriction on
threads i/o, so check archives or your EJB-INTEREST mail folder. The
conclusion is that as long as you package the classes that require no
restrictions and use doPrivileged at appropriate times, you're off the
hook. See the Java2 security model for more info, java.sun.com/security.
/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".
