Eclipse Community Forums: Equinox » org.eclipse.equinox.registry refactoring observation

Home » Eclipse Projects » Equinox » org.eclipse.equinox.registry refactoring observation

org.eclipse.equinox.registry refactoring observation [message #55190]

Wed, 21 December 2005 17:06

Eclipse User

I am examining the plug-in org.eclipse.equinox.registry and I see some
references that suggest that the refactoring might not be incomplete. Here
are my observations:

package: org.eclipse.core.internal.registry.osgi

seems to have content that is targeted to the registry's use in an
eclipse/osgi runtime. Class RegistryStrategyOSI for example (and its
dependency on Eclipse jobs)

This package has references from the following classes in other packages:
org.eclipse.core.equinox.registry.RegistryUtils
org.eclipse.equinox.registry.tracker.ExtensionTracker

My target for the registry is on a J2EE server (no OSGI) where I planned
to only include jars for the plugin org.eclipse.equinox registry and its
dependents:
org.eclipse.equinox.common
org.eclipse.equinox.supplement

Thanks,
Jim D'Anjou

Re: org.eclipse.equinox.registry refactoring observation [message #55218 is a reply to message #55190]

Wed, 21 December 2005 18:20

Eclipse User

I might add that even with the observations noted in the orignal entry, I
was able to deploy the registry project jars in a J2EE server and run my
JunitEE tests against the registry successfully. So I am not inadvertently
entering the mentioned classes that would probably fail in this
environment due to OSGI references. Nonetheless, it would be preferable to
not have them present in this environment.

Jim D'Anjou

Previous Topic:	Recommendations for provider id when using the equinox extension registry
Next Topic:	Intercept class loading

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 23:50:23 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter