Eclipse Community Forums: Equinox » Specify packages ... without explicitly identifying their orginating plug-in?

Help

Home

Home » Eclipse Projects » Equinox » Specify packages ... without explicitly identifying their orginating plug-in?

Show: Today's Messages :: Show Polls :: Message Navigator

Specify packages ... without explicitly identifying their orginating plug-in? [message #81378]

Thu, 18 January 2007 01:22

John J. Barton

Messages: 311
Registered: July 2009

Senior Member

Ok, so I'm keen to use more "imported packages", zero plugin class path,
and minimum required plugins.

But right off I get stuck: what .java or .class files are being used
when I add to the list of "Imported Packages"? We don't identify their
orginating plugin, so they don't come from a plugin (right?). They
aren't on our bundle class path. ..I'm drawing a blank here ;-)

Plus I have 50 compile errors like

Access restriction: The type HttpServlet is not accessible due to
restriction on required library javax.servlet

all of which disappear when I put javax.serlvet plugin as required plugin.

Just when I thought I understood this stuff,
John.

Report message to a moderator

Re: Specify packages ... without explicitly identifying their orginating [message #81434 is a reply to message #81378]

Thu, 18 January 2007 10:35

Eclipse User

Originally posted by: alex_blewitt.yahoo.com

You can get rid of the errors by changing the level of error reported in those scenarios in the PDE preferences :-)

The access restriction would seem to be that the plugins that are available don't explicitly Export-Package the javax.servlet, or if they do, they're saying Export-Package: javax.servlet;internal=true or some such (which probably wouldn't make sense, so I suspect the former). Of course, you also have to have javax.servlet in the target platform; and if you've made changes to the target platfrom, you have to refresh it (Erm. Somewhere in preferences. Not sure where.)

That's a guess, anyway.

Alex.

Report message to a moderator

Re: Specify packages ... without explicitly identifying their orginating plug-in? [message #81449 is a reply to message #81378]

Thu, 18 January 2007 11:47

Stefan Langer

Messages: 236
Registered: July 2009

Senior Member

JOHN J. BARTON wrote:
> Ok, so I'm keen to use more "imported packages", zero plugin class path,
> and minimum required plugins.
>
> But right off I get stuck: what .java or .class files are being used
> when I add to the list of "Imported Packages"? We don't identify their
> orginating plugin, so they don't come from a plugin (right?). They
> aren't on our bundle class path. ..I'm drawing a blank here ;-)
>
> Plus I have 50 compile errors like
>
> Access restriction: The type HttpServlet is not accessible due to
> restriction on required library javax.servlet

I think your problem is that the packages are retrieved from a bundle
that only exposes these packages to a subset of bundles and yours isn't
part in that.
>
> all of which disappear when I put javax.serlvet plugin as required plugin.
Now you are specifiing where the package is imported from and it is more
than likley that the package is also visible to your bundle.

> Just when I thought I understood this stuff,
> John.

Report message to a moderator

Previous Topic:	quesiton for testing sample.http.registry with equinox in servlet container
Next Topic:	Strange problem when plugin is in jar format (works OK in directory format)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Sep 18 23:46:51 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter