Eric Williams wrote,
> [snip: thread and IO restrictions]
> But I am guessing that whatever EJB server you are using, you
> can bend the rules to a degree. There is usually a way to get
> around the restrictions, as long as you can live with the
> "less than portable" nature of your code.
Is that really necessary?
Hmm ... I haven't been paying that much attention, because
EJB isn't really my department, but, on the face of it, it
looks like the restrictions are pretty easy to work around,
so long as it's possible for a bean to communicate with an
entity which isn't hosted in the container (tho' it might be
hosted by the same JVM). To use a threaded entity from a bean
you could use a passive object which communicates with it via
a queue; to use an IO entity you use a non-IO object that can
forward to it out of the container.
Am I missing something?
Cheers,
Miles
--
Miles Sabin Cromwell Media
Internet Systems Architect 5/6 Glenthorne Mews
+44 (0)20 8817 4030 London, W6 0LJ, England
[EMAIL PROTECTED] http://www.cromwellmedia.com/
===========================================================================
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".
