|
Re: same package in two different bundles: a problem? [message #331528 is a reply to message #331517] |
Thu, 11 September 2008 12:56 |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Paul Th. Keyser wrote:
> WinXP & R3.3
>
> We have two different bundles (plug-ins) that happen both to declare a
> package, say "com.mun.ist.foo", but contain no conflicting classes
> (i.e., if there is a class named Bar in that package it appears in only
> one of the bundles). The code all compiles and runs fine.
>
> I think this is not a problem, as (e.g.) Eclipse does the same:
>
> But someone is now trying to claim that the mere presence of the same
> package in two bundles will cause the class-loader to fail. (He offers
> no actual evidence.)
First thing I'd say is, "show me the money!" In other words, produce a
demonstration or documentation that says it fails. Without that, there
is no discussion.
Secondly, you have already pointed out that Eclipse "core" plugins do
this all over he place without any problems. That is pretty strong
evidence to the contrary.
Finally, remind this someone that plugins use a special custom
classloader, so his understanding of the standard classloader may not
apply here. OSGi is specialized when it comes to class loading.
Hope this helps,
Eric
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04009 seconds