Eclipse Community Forums: Equinox » Class Loading Architecture

Home » Eclipse Projects » Equinox » Class Loading Architecture

Class Loading Architecture [message #55001]

Fri, 16 December 2005 08:35

Eclipse User

Originally posted by: chs.tipas.at

OSGi_R4.core.pdf -> 3.4 Class Loading Architecture defines the "class
space".

It further points out:
"A class space must be consistent, such that it never contains two classes
with the same fully qualified name (to prevent Class Cast Exceptions). "

I have tested this with a simple example Plugin A, B and C.
B and C exports the same class in the same package. A creates a dependency
to B and C.
It perfectly runs at least with my eclipse 3.1.0 installation.
It also fits the deep first search, if B requires C the class from C is
loaded.

Is this a defined behaviour for equinox or is there any strict mode that
avoids this feature ?

Re: Class Loading Architecture [message #57638 is a reply to message #55001]

Mon, 23 January 2006 23:10

Eclipse User

Originally posted by: jeff_nospam_mcaffer.ca.ibm.com

This is expected behaviour. Is it causing you a problem?

Jeff

"Chris Schaefer" <chs@tipas.at> wrote in message
news:dnufru$ls9$1@news.eclipse.org...
> OSGi_R4.core.pdf -> 3.4 Class Loading Architecture defines the "class
> space".
>
> It further points out:
> "A class space must be consistent, such that it never contains two classes
> with the same fully qualified name (to prevent Class Cast Exceptions). "
>
> I have tested this with a simple example Plugin A, B and C.
> B and C exports the same class in the same package. A creates a dependency
> to B and C.
> It perfectly runs at least with my eclipse 3.1.0 installation.
> It also fits the deep first search, if B requires C the class from C is
> loaded.
>
> Is this a defined behaviour for equinox or is there any strict mode that
> avoids this feature ?
>
>
>
>
>

Re: Class Loading Architecture [message #57937 is a reply to message #57638]

Tue, 24 January 2006 05:05

Eclipse User

Originally posted by: chs.tipas.at

it does not cause a problem if it is known.
But it does not reflect the osgi standard in reflect to the "consistency of
the class space" ?

"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
news:dr49ap$r1m$1@utils.eclipse.org...
> This is expected behaviour. Is it causing you a problem?
>
> Jeff
>
> "Chris Schaefer" <chs@tipas.at> wrote in message
> news:dnufru$ls9$1@news.eclipse.org...
>> OSGi_R4.core.pdf -> 3.4 Class Loading Architecture defines the "class
>> space".
>>
>> It further points out:
>> "A class space must be consistent, such that it never contains two
>> classes
>> with the same fully qualified name (to prevent Class Cast Exceptions). "
>>
>> I have tested this with a simple example Plugin A, B and C.
>> B and C exports the same class in the same package. A creates a
>> dependency
>> to B and C.
>> It perfectly runs at least with my eclipse 3.1.0 installation.
>> It also fits the deep first search, if B requires C the class from C is
>> loaded.
>>
>> Is this a defined behaviour for equinox or is there any strict mode that
>> avoids this feature ?
>>
>>
>>
>>
>>
>
>

Re: Class Loading Architecture [message #58189 is a reply to message #57937]

Thu, 26 January 2006 09:00

Eclipse User

Originally posted by: jeff_nospam_mcaffer.ca.ibm.com

Might be best to enter a bug report in the Eclipse/Equinox bugzilla with
some example code. I'm not quite seeing the problem.

Jeff

"Chris Schaefer" <chs@tipas.at> wrote in message
news:dr4u5f$10t$1@utils.eclipse.org...
>
> it does not cause a problem if it is known.
> But it does not reflect the osgi standard in reflect to the "consistency
of
> the class space" ?
>
>
>
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> schrieb im Newsbeitrag
> news:dr49ap$r1m$1@utils.eclipse.org...
> > This is expected behaviour. Is it causing you a problem?
> >
> > Jeff
> >
> > "Chris Schaefer" <chs@tipas.at> wrote in message
> > news:dnufru$ls9$1@news.eclipse.org...
> >> OSGi_R4.core.pdf -> 3.4 Class Loading Architecture defines the "class
> >> space".
> >>
> >> It further points out:
> >> "A class space must be consistent, such that it never contains two
> >> classes
> >> with the same fully qualified name (to prevent Class Cast Exceptions).
"
> >>
> >> I have tested this with a simple example Plugin A, B and C.
> >> B and C exports the same class in the same package. A creates a
> >> dependency
> >> to B and C.
> >> It perfectly runs at least with my eclipse 3.1.0 installation.
> >> It also fits the deep first search, if B requires C the class from C is
> >> loaded.
> >>
> >> Is this a defined behaviour for equinox or is there any strict mode
that
> >> avoids this feature ?
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>

Previous Topic:	How to resolve the PATH containing the OSGi's DLL
Next Topic:	Bundle-RequiredExecutionEnvironment: supported in 3.1/3.2?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 23:08:19 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter