On Tuesday 02 March 2004 07:12, Cameron Fieber wrote:Geez - I kind of noticed you were responding to emails all day!
> I'm in the process of porting an application to Merlin (version 3.2.5 in
> this case), and I'm trying to figure out the classloader relationship
> for nested block xmls.
Right now it is 8 o'clock in the morning and the brain is about to shut down,
BUT...
Your assumption is basically right.
You should not need to re-declare the implementation classes, only the APIs.
And if that container is re-used at a higher level, only the APIs that the
container exposes as services are needed in the enclosing higher container,
and so on.
Why it doesn't work your way... I don't know right now.
If the app is not too big, zip it up and I'll take a look at it tomorrow...uhhh I mean later today, after I slept for a long while.
I have an example that shows what I was talking about at: http://remsats1.hpr.for.gov.bc.ca/composition-test.tar.gz
It includes an updated version of cornerstone-threads-impl-1.0.jar that fixes the block.xml that is embedded in it to include excalibur-pool.
Anyway, I think the problem may be partly due to the fact that there isn't a separation of API and Impl for excalibur-thread, but the ThreadPool interface is part of the API of cornerstone-threads so that excalibur-thread has to be imported in the top level classloader.
Thanks again,
-Cameron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
