On 9/27/11 3:21 PM, Teemu Kanstrén wrote:
2011/9/27 Richard S. Hall<[email protected]>
The real reason people run into so many issues when trying OSGi is because
they are either knowingly or unknowingly trying to use legacy code that
makes tons of assumptions about global type visibility. It has very little
to do with multiple versions being present at the same time.
Is it not the need to run legacy code in your container a large factor that
leads to requiring classloader sandboxing? So does the solution address a
problem that is likely to cause problems for the solution? :) But yes, I
agree with you that this is the main source of issues in OSGI and if someone
would solve that, there would be few reasons ever not to use OSGI..
OSGi is not a solution for addressing such shortcomings in legacy Java
code. Almost without fail, legacy code needs to be ported to OSGi to
work properly. In some cases, the porting is easier than others.
Anything else is akin to compiling C code with g++ and expecting it to
somehow become more object oriented.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
