>
>Bleagh. So my group's work for the past half year or so--on developing reusable
>plain-Java services that we hoped could be used by any application, EJB-based
>ones included--cannot now be called from our beans, because it creates and
>works with threads. Oh sigh. Our centralized logging service, for example,
>now violates EJB policy on two fronts: it uses the java.io package *and*
>creates threads. Silly us, thinking that we could use those features which the
>JDKSE gives us for free!
Sigh.. I would went through the same frustration back in December. I wanted to use
threads within EJB and also do file I/O. I was advised here on this list to wait for
EJB 2.0 which would resolve the issues with EJB and JMS at least.
I am back with RMI now.
The only thing to add to this note is to design your classes well so that when EJB
2.0 is ready you wont have to rewrite a lot of code.
Look up the archives under the string "EJB/JMS Integration" from December. Lot of
people have contributed to this.
Regards,
Ashwin.
>> For parallel processing, we don't have many options. AFAIK, the best
>> option is to use JMS's message session pooling to process messages in
>> parallel.
>
>I don't understand. Surely invoking JMS in any fashion results in a new thread
>being created. Is this thread creation "legal" because it is the container
>vendor who has implemented it?
>
>> This assumes the container actually implements JMS of course.
>> Again, maybe someday we'll have some standard facilities for creating
>> and managing container-compatible threads, but not yet.
>
>The more I work with this specification, the more I dislike it.
>
>Thanks for your informative and thoughtful reply.
>
>Cheers,
>Laird
>
> ==========================================================================
>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".
>
===========================================================================
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".
