[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Understanding extension points

the easiest way to get started is probably to check out the relevant projects direct from the equinox incubator by adding the repository location (:pserver:anonymous@xxxxxxxxxxxxxxx/cvsroot/eclipse) into the PDE ("checkout as project" when right-click on the relevant folder in the CVS repository view). Then, you should be able to run your project directly from within the workbench to get something up and running.

On Jun 2, 2006, at 6:19 PM, Melih Onvural wrote:


Thanks for the answer. I think that the issue is I'm having a tough time understanding how to tell the specific project
where to find the specific dependencies. These dependencies seem to be the root of the problem, and they're
manifesting by not allowing the extension points to be recognized. What I was able to do was build the jar files for
bridge.http and bridge.launcher and add them as dependencies to my test project. Now, I'm stuck because I've built
the http.registry project, but it doesn't have a Registry class as well as some others that the dependencies I was
given are looking for. Do you think that switching from http.* to bridge.* will resolve this? I'll try it out now, and let
you know. Again, thanks for your help,

Melih Onvural

On 6/2/06, Peter Neubauer <pnb@xxxxxxxxxxx> wrote:
I'm not sure which Extension Point you are trying to see, but we use the ones in org.eclipse.equinox.servlet.ext (httpcontext, resource, servlet), and AFAIK this requires only the standard equinox.registry, sitting in the default Eclipse installation. So I think you should not use the http.registry, or is that a misconception?
Instead, I think what you want is to check out
and then, maybe Simons embedded Jetty implementation behind that, at https://bugs.eclipse.org/bugs/show_bug.cgi?id=132555

Does this help?



Från: Melih Onvural [mailto:melih.onvural@xxxxxxxxx ]
Skickat: fr 2006-06-02 03:01
Till: equinox-dev@xxxxxxxxxxx
Ämne: [equinox-dev] Understanding extension points


I'm trying to get a basic OSGi bundle to execute, and I'm stuck at the point
where my test bundle keeps complaining about the org.eclipse.equinox.http.registry.*
extension points. I brought the org.eclipse.equinox.http.registry project down onto
my computer, but it too is complaining about not knowing where those extension
points are to be found. Has anyone run into this issue? Where should I start looking
to work this out? Thanks,

Melih Onvural

equinox-dev mailing list

equinox-dev mailing list