Frank W. Zammetti wrote:
Is it still the case, given the JDK 1.5 concurrency stuff, that you are
still not technically allowed to spawn threads in a J2EE container (per
spec guidelines)? Did the latest J2EE spec loosen that restriction maybe?
Hi Frank,
I don't know of any loosening of that restriction.
As far as I understand, the compliant approach would be to use a Message
Driven Bean that's spawned from a pool managed by the container.
That would provide some nice decoupling between the OP's action and the
service/bean that performs the POST. However, I find the cost [1] of
that approach is difficult to justify for most applications.
cheers,
Jeromy
[1] cost in terms of learning the technology, the heavier weight
container, the JNDI lookup, the additional configuration, the additional
components affecting reliability, the increased deployment time etc etc etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
