Ulrich Mayring wrote:
Laszlo Hornyak wrote:
I think including the jar files in the .sar is a good thing, using the system calss loader, the global resources are still available.
You wrote, that it may be a problem that if you run an phoenix installation with about 100 phoenix applications, it takes a lot of memory, which is right, but what if all of the applications need different versions of the jar files?
If I need a different version I can already include it in the SAR. But I don't have to. Right now I have the choice.
It is just a little administration question, I think.
In my mind it's a feature taken away. I used to have two options, both with their pros and cons, now I only have one.
After running into problems on the James platform due to incopatible jar files esiting in the James dist and the Phonenix dist I think this is a good move. It forced projects that are dependent on Phoenix to include (and be responsible for) the appropriate version of a jar file they are using. In the Merlin environment is possible to added extension jar files that are sharable across applications - however I don't know if this is possible in Phoenix. If a sharable respository exists then this would solve the problem.
Cheers, Steve.
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
