I just stumbled upon this.. I was assuming that it is perfectly fine to: - define a shared pool in package - make a class which using given pool in same package
but when MC loads it , it looks like it doesn't care about loading order and if it loads the class which using pool first, it says that pool not exists and asks me to create it. if you create it, then when it loads the pool , it barks that given class already in system... i know that solution is to have 2 packages, 1 with pool, and another with classes which using them, but somehow i was assumed that it should work fine in single package.. So, here 2 questions: - does anybody knows if this worked ever? - do we need that? -- Best regards, Igor Stasenko.
