I've spent some time looking at the j2eeca 1.5 spec again and can't
fine any mention of which thread context classloader a Work submission
is supposed to operate under. Therefore I think if you want your
adapter to be portable you should not make any assumptions about it and
we have no need to set the thread context classloader ourselves. So,
while I'm open to discussion, so far I'm -1 on this.
thanks
david jencks
On Oct 2, 2004, at 9:00 PM, Aaron Mulder wrote:
So it looks like when a "Work" is executed, the thread context
class loader is not useful. I have to set it to
getClass().getClassLoader() in order to access content in the
connector's
JARs. Is it OK if I put in a bug to set the TCCL to the RA CL while a
Work from that RA is executed, and set it back to the otherone
thereafter?
Thanks,
Aaron
