You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Rick Litton <Ri...@ktd-kyocera.com> on 2006/12/08 19:57:44 UTC
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Rick Litton wrote:
> I hope the graph is displayed correctly by your mail client. Anyhow, I
> was getting quite a few BundleExceptions "Unable to resolve due to
> constraint violation"). So I removed all the optional bundles and
> proceeded to test each one. Immediately, the BundleException came up
> after I had just added/started the org.osgi.core bundle. I certainly
> would welcome any suggestion to resolve this problem.
One other thing to point out, in case it wasn't obvious, the "Unable to
resolve due to
constraint violation" is not an exception, but a DEBUG log message. So,
it is possible that things are resolving, even if you see this message.
-> richard
RE: Felix and Eclipse PDE roadblock
Posted by Rick Litton <Ri...@ktd-kyocera.com>.
Richard,
I just forwarded the email again to you (at heavy@ungoverned.org) with
the attachments. Please let me know after you have received it. Thanks
again.
Rick Litton
-----Original Message-----
From: Richard S. Hall [mailto:heavy@ungoverned.org]
Sent: Friday, December 08, 2006 11:28 AM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick Litton wrote:
> Richard,
>
> Actually I did send it via your personal email (mail full? Or got into
> your junk email? ;) I will send it again. Regards,
>
My mail box isn't full, but I haven't received anything. Sorry.
-> richard
> Rick
>
> -----Original Message-----
> From: Richard S. Hall [mailto:heavy@ungoverned.org]
> Sent: Friday, December 08, 2006 11:22 AM
> To: felix-dev@incubator.apache.org
> Subject: Re: Felix and Eclipse PDE roadblock
>
> Rick,
>
> As I suggested, send me the bundles (offline) and the steps to
reproduce
>
> and I will look at it some more. Everything I have seen up until this
> point appears to be related to conflicts between two versions of the
> same package.
>
> -> richard
>
> Rick Litton wrote:
>
>> I'm still trying to get the extension points registry to work in
Felix
>> and unfortunately, I have hit a roadblock. After trying out several
>> combinations and pruning the eclipse core bundle (as Richard Hall has
>> suggested) to remove redundant osgi core classes, I have created the
>> following dependency graph to help illustrate the problem:
>>
>>
>>
>> /---> org.osgi.compendium
>>
>> |
>>
>> | (requires: org.osgi.util.tracker package)
>>
>> |
>>
>> |---> org.osgi.core
>>
>> |
>>
>> | (requires: org.osgi.service.permissionadmin package)
>>
>> |
>>
>> | org.eclipse.osgi_3.2.1R32x <----\
>>
>> | ^ |
>>
>> | (requires:|org.eclipse.osgi.service.urlconversion package)
>>
>>
>> | | |
>>
>> |---- org.eclipse.equinox.common |
>>
>> | ^ |
>>
>> | | |
>>
>> | | |
>>
>> \---- org.eclipse.equinox.registry |
>>
>> | |
>>
>> | |
>>
>> \---------------------/
>>
>> (requires: org.eclipse.osgi.service.datalocation package)
>>
>> I hope the graph is displayed correctly by your mail client. Anyhow,
>>
> I
>
>> was getting quite a few BundleExceptions "Unable to resolve due to
>> constraint violation"). So I removed all the optional bundles and
>> proceeded to test each one. Immediately, the BundleException came up
>> after I had just added/started the org.osgi.core bundle. I
>>
> certainly
>
>> would welcome any suggestion to resolve this problem.
>>
>> Rick Litton
>>
>>
>>
>>
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Rick Litton wrote:
> Richard,
>
> Actually I did send it via your personal email (mail full? Or got into
> your junk email? ;) I will send it again. Regards,
>
My mail box isn't full, but I haven't received anything. Sorry.
-> richard
> Rick
>
> -----Original Message-----
> From: Richard S. Hall [mailto:heavy@ungoverned.org]
> Sent: Friday, December 08, 2006 11:22 AM
> To: felix-dev@incubator.apache.org
> Subject: Re: Felix and Eclipse PDE roadblock
>
> Rick,
>
> As I suggested, send me the bundles (offline) and the steps to reproduce
>
> and I will look at it some more. Everything I have seen up until this
> point appears to be related to conflicts between two versions of the
> same package.
>
> -> richard
>
> Rick Litton wrote:
>
>> I'm still trying to get the extension points registry to work in Felix
>> and unfortunately, I have hit a roadblock. After trying out several
>> combinations and pruning the eclipse core bundle (as Richard Hall has
>> suggested) to remove redundant osgi core classes, I have created the
>> following dependency graph to help illustrate the problem:
>>
>>
>>
>> /---> org.osgi.compendium
>>
>> |
>>
>> | (requires: org.osgi.util.tracker package)
>>
>> |
>>
>> |---> org.osgi.core
>>
>> |
>>
>> | (requires: org.osgi.service.permissionadmin package)
>>
>> |
>>
>> | org.eclipse.osgi_3.2.1R32x <----\
>>
>> | ^ |
>>
>> | (requires:|org.eclipse.osgi.service.urlconversion package)
>>
>>
>> | | |
>>
>> |---- org.eclipse.equinox.common |
>>
>> | ^ |
>>
>> | | |
>>
>> | | |
>>
>> \---- org.eclipse.equinox.registry |
>>
>> | |
>>
>> | |
>>
>> \---------------------/
>>
>> (requires: org.eclipse.osgi.service.datalocation package)
>>
>> I hope the graph is displayed correctly by your mail client. Anyhow,
>>
> I
>
>> was getting quite a few BundleExceptions "Unable to resolve due to
>> constraint violation"). So I removed all the optional bundles and
>> proceeded to test each one. Immediately, the BundleException came up
>> after I had just added/started the org.osgi.core bundle. I
>>
> certainly
>
>> would welcome any suggestion to resolve this problem.
>>
>> Rick Litton
>>
>>
>>
>>
RE: Felix and Eclipse PDE roadblock
Posted by Rick Litton <Ri...@ktd-kyocera.com>.
Richard,
Actually I did send it via your personal email (mail full? Or got into
your junk email? ;) I will send it again. Regards,
Rick
-----Original Message-----
From: Richard S. Hall [mailto:heavy@ungoverned.org]
Sent: Friday, December 08, 2006 11:22 AM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick,
As I suggested, send me the bundles (offline) and the steps to reproduce
and I will look at it some more. Everything I have seen up until this
point appears to be related to conflicts between two versions of the
same package.
-> richard
Rick Litton wrote:
> I'm still trying to get the extension points registry to work in Felix
> and unfortunately, I have hit a roadblock. After trying out several
> combinations and pruning the eclipse core bundle (as Richard Hall has
> suggested) to remove redundant osgi core classes, I have created the
> following dependency graph to help illustrate the problem:
>
>
>
> /---> org.osgi.compendium
>
> |
>
> | (requires: org.osgi.util.tracker package)
>
> |
>
> |---> org.osgi.core
>
> |
>
> | (requires: org.osgi.service.permissionadmin package)
>
> |
>
> | org.eclipse.osgi_3.2.1R32x <----\
>
> | ^ |
>
> | (requires:|org.eclipse.osgi.service.urlconversion package)
>
>
> | | |
>
> |---- org.eclipse.equinox.common |
>
> | ^ |
>
> | | |
>
> | | |
>
> \---- org.eclipse.equinox.registry |
>
> | |
>
> | |
>
> \---------------------/
>
> (requires: org.eclipse.osgi.service.datalocation package)
>
> I hope the graph is displayed correctly by your mail client. Anyhow,
I
> was getting quite a few BundleExceptions "Unable to resolve due to
> constraint violation"). So I removed all the optional bundles and
> proceeded to test each one. Immediately, the BundleException came up
> after I had just added/started the org.osgi.core bundle. I
certainly
> would welcome any suggestion to resolve this problem.
>
> Rick Litton
>
>
>
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Rick,
As I suggested, send me the bundles (offline) and the steps to reproduce
and I will look at it some more. Everything I have seen up until this
point appears to be related to conflicts between two versions of the
same package.
-> richard
Rick Litton wrote:
> I'm still trying to get the extension points registry to work in Felix
> and unfortunately, I have hit a roadblock. After trying out several
> combinations and pruning the eclipse core bundle (as Richard Hall has
> suggested) to remove redundant osgi core classes, I have created the
> following dependency graph to help illustrate the problem:
>
>
>
> /---> org.osgi.compendium
>
> |
>
> | (requires: org.osgi.util.tracker package)
>
> |
>
> |---> org.osgi.core
>
> |
>
> | (requires: org.osgi.service.permissionadmin package)
>
> |
>
> | org.eclipse.osgi_3.2.1R32x <----\
>
> | ^ |
>
> | (requires:|org.eclipse.osgi.service.urlconversion package)
>
>
> | | |
>
> |---- org.eclipse.equinox.common |
>
> | ^ |
>
> | | |
>
> | | |
>
> \---- org.eclipse.equinox.registry |
>
> | |
>
> | |
>
> \---------------------/
>
> (requires: org.eclipse.osgi.service.datalocation package)
>
> I hope the graph is displayed correctly by your mail client. Anyhow, I
> was getting quite a few BundleExceptions "Unable to resolve due to
> constraint violation"). So I removed all the optional bundles and
> proceeded to test each one. Immediately, the BundleException came up
> after I had just added/started the org.osgi.core bundle. I certainly
> would welcome any suggestion to resolve this problem.
>
> Rick Litton
>
>
>
Re: Reminder of the Apache Way [was; Felix and Eclipse PDE roadblock]
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Niclas Hedhman wrote:
> On Monday 11 December 2006 17:29, Karl Pauls wrote:
>
>> I think you miss-read Ricks comment. There is a branch of the
>> framework core under sandbox/rickhall/framework-require-bundle which
>> has been announced by Rick as the place he is going to start
>> implementing required-bundle and fragments.
>>
>
> Then I am so sorry... and let this be a general reminder... ;o)
Yes, Karl's comments are accurate. When we set up the Felix repo we did
not opt for a "branches" directory and instead said the "sandbox" would
be for experimentation. Thus, that is where I did my experimentation. My
"branch" has been committed and publicly available for quite some
time...check FELIX-28...
No biggie.
-> richard
Re: Reminder of the Apache Way [was; Felix and Eclipse PDE roadblock]
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Monday 11 December 2006 17:29, Karl Pauls wrote:
> I think you miss-read Ricks comment. There is a branch of the
> framework core under sandbox/rickhall/framework-require-bundle which
> has been announced by Rick as the place he is going to start
> implementing required-bundle and fragments.
Then I am so sorry... and let this be a general reminder... ;o)
Cheers
Niclas
Re: Reminder of the Apache Way [was; Felix and Eclipse PDE roadblock]
Posted by Karl Pauls <ka...@gmail.com>.
I think you miss-read Ricks comment. There is a branch of the
framework core under sandbox/rickhall/framework-require-bundle which
has been announced by Rick as the place he is going to start
implementing required-bundle and fragments. The reason for a branch is
that it is no small task and quite a lot of other people rely on a
working version of the core.
In other words and for the record, there are no "external sandboxes"
nor "external laboratories" and the development happens on the
"mailing list" and in the "source repositories".
As someone who has contributed to the Felix core framework by means of
patches and direct svn commits I can state that I encountered no
problems doing so and didn't had no felling that whoever sees my
contributions as a "scary" development.
Frankly, I personally don't see that there is any reminder of the
Apache ways necessary at the moment. I'm sure that if you, Niclas, or
anybody else is interested and/or willing to work on fragments and
require-bundle this will be much appreciated and present no problem
(until today, however, nobody volunteered to participate hence, the
Rick centric repo layout).
regards,
Karl
On 12/11/06, Niclas Hedhman <ni...@hedhman.org> wrote:
> On Sunday 10 December 2006 23:45, Richard S. Hall wrote:
> > Currently, I have a prototype of RB working in my sandbox, which will be
> > the pattern I use to extend the trunk on the road to 1.0.0...if all goes
> > well.
>
> For the record and future reference,
> ASF doesn't expect external "sandboxes" or "laboratories" to exist. All
> development are expected to happen on the "mailing list" and in the "source
> repositories". Officially, if a codebase doesn't follow these principles,
> then it needs to be vetted thru the Incubator (never mind we are there now).
>
> Exactly what consitutes a "codebase" is of course very subjective. The intent
> of the principle is to allow collaboration among interested parties. Island
> development and "mine vs yours" is greatly discouraged, even frowned upon at
> the ASF.
>
> Letting others into the Felix core framework is perhaps a scary proposition,
> but absolutely necessary for greater acceptance among the peers, avoidance of
> dependency on your well-being, and reduction of the total work load required.
>
> Mentors, anything you would like to add in this regard??
>
>
> Cheers
> Niclas
>
--
Karl Pauls
karlpauls@gmail.com
Reminder of the Apache Way [was; Felix and Eclipse PDE roadblock]
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sunday 10 December 2006 23:45, Richard S. Hall wrote:
> Currently, I have a prototype of RB working in my sandbox, which will be
> the pattern I use to extend the trunk on the road to 1.0.0...if all goes
> well.
For the record and future reference,
ASF doesn't expect external "sandboxes" or "laboratories" to exist. All
development are expected to happen on the "mailing list" and in the "source
repositories". Officially, if a codebase doesn't follow these principles,
then it needs to be vetted thru the Incubator (never mind we are there now).
Exactly what consitutes a "codebase" is of course very subjective. The intent
of the principle is to allow collaboration among interested parties. Island
development and "mine vs yours" is greatly discouraged, even frowned upon at
the ASF.
Letting others into the Felix core framework is perhaps a scary proposition,
but absolutely necessary for greater acceptance among the peers, avoidance of
dependency on your well-being, and reduction of the total work load required.
Mentors, anything you would like to add in this regard??
Cheers
Niclas
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Jeff McAffer wrote:
> Anyway, if Felix supports Require-Bundle then this should all just work
> (i.e., we are not doing anything Eclipse-specific in this area). According
> to the R4 spec, Require-Bundle is the only way to join two or more package
> fragments from different bundles.
>
For a reminder/status report on that...
Require-Bundle will be one of my priorities after we get 0.8.0 out the
door and possibly a graduation attempt...
Currently, I have a prototype of RB working in my sandbox, which will be
the pattern I use to extend the trunk on the road to 1.0.0...if all goes
well.
-> richard
> Jeff
>
>
>
>
> "Rick Litton" <Ri...@ktd-kyocera.com>
> 12/10/2006 03:06 AM
> Please respond to
> felix-dev@incubator.apache.org
>
>
> To
> <fe...@incubator.apache.org>, <fe...@incubator.apache.org>,
> <fe...@incubator.apache.org>
> cc
>
> Subject
> RE: Felix and Eclipse PDE roadblock
>
>
>
>
>
>
> I finally got the equinox extension point registry running. It was not
> easy to say the least. I had to make some changes to the equinox code and
> manifest files. It's still a long way off from being perfect but it seems
> to work (see below)!
>
> -> ps
> START LEVEL 1
> ID State Level Name
> [ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
> [ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
> [ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
> [ 3] [Active ] [ 1] Apache Felix Bundle Repository
> (0.8.0.SNAPSHOT)
> [ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
> [ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
> [ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
> [ 7] [Active ] [ 1] Eclipse Equinox Supplement
> (1.0.0.200612091415)
> [ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
> [ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
> [ 10] [Active ] [ 1] Eclipse Equinox Registry
> (3.2.100.200612091419)
> [ 11] [Active ] [ 1] Application Plug-in (1.0.0)
> ->
>
> Will need to add the equinox http bundles in lieu of the felix http since
> my example requires this service. One issue that could have been avoided
> was the doubling of the package name "org.eclipse.core.runtime" in two
> equinox bundles (common and registry). From experience with Oscar, this
> can be problematic. If there is an area for "examples" in the Felix
> repository I can probably check in the files with a readme to explain what
> was done.
>
> Thanks to Richard and Jeff ("the McAffer guy")!
>
> -- rick
>
>
> -----Original Message-----
> From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
> Sent: Sat 12/9/2006 10:14 AM
> To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
> Subject: RE: Felix and Eclipse PDE roadblock
>
> Hi Jeff,
>
> Thanks for the tip. I will try it...
>
> Regards,
>
> Rick
>
>
> -----Original Message-----
> From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
> Sent: Fri 12/8/2006 8:09 PM
> To: felix-dev@incubator.apache.org
> Subject: Re: Felix and Eclipse PDE roadblock
>
> Rick
>
> As a point of interest, you should be able to use the Equinox Supplement
> bundle
> http://www.eclipse.org/equinox/bundles#supplement
> rather than org.eclipse.osgi. This bundle is designed to supply the bits
> of the Equinox framework that are needed in other OSGi scenarios.
>
> I believe some folks in Equinox land have gotten the registry working on
> Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
> on the equinox newsgroup for some guidance. I'm sure they would be happy
> to compare notes
>
> Jeff
>
>
>
>
>
> "Rick Litton" <Ri...@ktd-kyocera.com>
> 12/08/2006 01:57 PM
> Please respond to
> felix-dev@incubator.apache.org
>
>
> To
> <fe...@incubator.apache.org>
> cc
>
> Subject
> Felix and Eclipse PDE roadblock
>
>
>
>
>
>
> I'm still trying to get the extension points registry to work in Felix
> and unfortunately, I have hit a roadblock. After trying out several
> combinations and pruning the eclipse core bundle (as Richard Hall has
> suggested) to remove redundant osgi core classes, I have created the
> following dependency graph to help illustrate the problem:
>
>
>
> /---> org.osgi.compendium
>
> |
>
> | (requires: org.osgi.util.tracker package)
>
> |
>
> |---> org.osgi.core
>
> |
>
> | (requires: org.osgi.service.permissionadmin package)
>
> |
>
> | org.eclipse.osgi_3.2.1R32x <----\
>
> | ^ |
>
> | (requires:|org.eclipse.osgi.service.urlconversion package)
>
>
> | | |
>
> |---- org.eclipse.equinox.common |
>
> | ^ |
>
> | | |
>
> | | |
>
> \---- org.eclipse.equinox.registry |
>
> | |
>
> | |
>
> \---------------------/
>
> (requires: org.eclipse.osgi.service.datalocation package)
>
> I hope the graph is displayed correctly by your mail client. Anyhow, I
> was getting quite a few BundleExceptions "Unable to resolve due to
> constraint violation"). So I removed all the optional bundles and
> proceeded to test each one. Immediately, the BundleException came up
> after I had just added/started the org.osgi.core bundle. I certainly
> would welcome any suggestion to resolve this problem.
>
> Rick Litton
>
>
>
>
>
>
>
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Chris Custine wrote:
> I started looking at bundle localization this morning and I think I
> can be
> done today if I get enough time. I will get back to Richard when I get
> something working.
Sounds great. Thanks.
If you get something working, just attach a patch to the JIRA issue.
-> richard
>
> On 12/18/06, Richard S. Hall <he...@ungoverned.org> wrote:
>>
>> Rick Litton wrote:
>> > Richard,
>> >
>> > The Equinox bundle manifest uses either a system or global variable
>> > (e.g. "%Variable%") from recollection. It appeared unchanged on the
>> > shell display when the "ps" command is executed. I'm not sure if this
>> > will be the norm in Felix. But I will continue to test the original
>> > Equinox bundles as you suggested and report back to the group. I hope
>> > we can at least uncover where the disconnects lie.
>> >
>>
>> Bundle localization entries start with a '%'...I imagine that is what it
>> is. We will get this implemented in Felix and then it shouldn't be an
>> issue, I think.
>>
>> -> richard
>> > Rick Litton
>> >
>> > -----Original Message-----
>> > From: Richard S. Hall [mailto:heavy@ungoverned.org]
>> > Sent: Monday, December 18, 2006 7:28 AM
>> > To: felix-dev@incubator.apache.org
>> > Subject: Re: Felix and Eclipse PDE roadblock
>> >
>> > rl16783@sbcglobal.net wrote:
>> >
>> >> Also: hardcoded bundle names to manifest of the 3 eclipse bundles as
>> >>
>> > this is customary in
>> >
>> >> Apache Felix.
>> >>
>> >
>> > Was the issue here that the bundle names were appearing
>> incorrectly? If
>> > so, I think this is related to bundle localization, which still
>> needs to
>> >
>> > be implemented in Felix...
>> >
>> > Rick, as we start to implement the require-bundle functionality, it
>> > would be nice if you could continue to try to get the original bundles
>> > working on top of that and report back on your progress, since that
>> will
>> >
>> > help us work out the kinks.
>> >
>> > For everyone else, don't use require-bundle... :-)
>> >
>> > -> richard
>> >
>>
>
Re: Felix and Eclipse PDE roadblock
Posted by Chris Custine <ch...@gmail.com>.
I started looking at bundle localization this morning and I think I can be
done today if I get enough time. I will get back to Richard when I get
something working.
On 12/18/06, Richard S. Hall <he...@ungoverned.org> wrote:
>
> Rick Litton wrote:
> > Richard,
> >
> > The Equinox bundle manifest uses either a system or global variable
> > (e.g. "%Variable%") from recollection. It appeared unchanged on the
> > shell display when the "ps" command is executed. I'm not sure if this
> > will be the norm in Felix. But I will continue to test the original
> > Equinox bundles as you suggested and report back to the group. I hope
> > we can at least uncover where the disconnects lie.
> >
>
> Bundle localization entries start with a '%'...I imagine that is what it
> is. We will get this implemented in Felix and then it shouldn't be an
> issue, I think.
>
> -> richard
> > Rick Litton
> >
> > -----Original Message-----
> > From: Richard S. Hall [mailto:heavy@ungoverned.org]
> > Sent: Monday, December 18, 2006 7:28 AM
> > To: felix-dev@incubator.apache.org
> > Subject: Re: Felix and Eclipse PDE roadblock
> >
> > rl16783@sbcglobal.net wrote:
> >
> >> Also: hardcoded bundle names to manifest of the 3 eclipse bundles as
> >>
> > this is customary in
> >
> >> Apache Felix.
> >>
> >
> > Was the issue here that the bundle names were appearing incorrectly? If
> > so, I think this is related to bundle localization, which still needs to
> >
> > be implemented in Felix...
> >
> > Rick, as we start to implement the require-bundle functionality, it
> > would be nice if you could continue to try to get the original bundles
> > working on top of that and report back on your progress, since that will
> >
> > help us work out the kinks.
> >
> > For everyone else, don't use require-bundle... :-)
> >
> > -> richard
> >
>
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Rick Litton wrote:
> Richard,
>
> The Equinox bundle manifest uses either a system or global variable
> (e.g. "%Variable%") from recollection. It appeared unchanged on the
> shell display when the "ps" command is executed. I'm not sure if this
> will be the norm in Felix. But I will continue to test the original
> Equinox bundles as you suggested and report back to the group. I hope
> we can at least uncover where the disconnects lie.
>
Bundle localization entries start with a '%'...I imagine that is what it
is. We will get this implemented in Felix and then it shouldn't be an
issue, I think.
-> richard
> Rick Litton
>
> -----Original Message-----
> From: Richard S. Hall [mailto:heavy@ungoverned.org]
> Sent: Monday, December 18, 2006 7:28 AM
> To: felix-dev@incubator.apache.org
> Subject: Re: Felix and Eclipse PDE roadblock
>
> rl16783@sbcglobal.net wrote:
>
>> Also: hardcoded bundle names to manifest of the 3 eclipse bundles as
>>
> this is customary in
>
>> Apache Felix.
>>
>
> Was the issue here that the bundle names were appearing incorrectly? If
> so, I think this is related to bundle localization, which still needs to
>
> be implemented in Felix...
>
> Rick, as we start to implement the require-bundle functionality, it
> would be nice if you could continue to try to get the original bundles
> working on top of that and report back on your progress, since that will
>
> help us work out the kinks.
>
> For everyone else, don't use require-bundle... :-)
>
> -> richard
>
RE: Felix and Eclipse PDE roadblock
Posted by Rick Litton <Ri...@ktd-kyocera.com>.
Richard,
The Equinox bundle manifest uses either a system or global variable
(e.g. "%Variable%") from recollection. It appeared unchanged on the
shell display when the "ps" command is executed. I'm not sure if this
will be the norm in Felix. But I will continue to test the original
Equinox bundles as you suggested and report back to the group. I hope
we can at least uncover where the disconnects lie.
Rick Litton
-----Original Message-----
From: Richard S. Hall [mailto:heavy@ungoverned.org]
Sent: Monday, December 18, 2006 7:28 AM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
rl16783@sbcglobal.net wrote:
> Also: hardcoded bundle names to manifest of the 3 eclipse bundles as
this is customary in
> Apache Felix.
Was the issue here that the bundle names were appearing incorrectly? If
so, I think this is related to bundle localization, which still needs to
be implemented in Felix...
Rick, as we start to implement the require-bundle functionality, it
would be nice if you could continue to try to get the original bundles
working on top of that and report back on your progress, since that will
help us work out the kinks.
For everyone else, don't use require-bundle... :-)
-> richard
Re: Felix and Eclipse PDE roadblock
Posted by "Richard S. Hall" <he...@ungoverned.org>.
rl16783@sbcglobal.net wrote:
> Also: hardcoded bundle names to manifest of the 3 eclipse bundles as this is customary in
> Apache Felix.
Was the issue here that the bundle names were appearing incorrectly? If
so, I think this is related to bundle localization, which still needs to
be implemented in Felix...
Rick, as we start to implement the require-bundle functionality, it
would be nice if you could continue to try to get the original bundles
working on top of that and report back on your progress, since that will
help us work out the kinks.
For everyone else, don't use require-bundle... :-)
-> richard
Re: Launch Felix with PDE
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Jeff McAffer wrote:
> Just for a point of reference, what some of the folks in the Spring OSGi
> world have been doing is just putting the "bin" (whatever) dirs on the
> Bundle-Classpath in the manifest. That works at dev time and at regular
> runtime that dir does not exist. This is basically a hack equivalent of
> the dev classpath support we have talked about in the past. Implementing
> the dev classpath support is not that complex so I would go that route.
>
Yeah, I forgot about that "trick"...
-> richard
> Jeff
>
>
>
>
> Thomas Watson <tj...@us.ibm.com>
> 12/19/2006 12:09 AM
> Please respond to
> felix-dev@incubator.apache.org
>
>
> To
> felix-dev@incubator.apache.org
> cc
>
> Subject
> Re: Launch Felix with PDE
>
>
>
>
>
>
> "Richard S. Hall" <he...@ungoverned.org> wrote on 12/18/2006 02:01:34 PM:
>
>
>> Reading your issue about slow start up due to having to create bundle
>> JAR files...I think this can be partially avoided by doing install by
>> reference (i.e., "reference:"); however, as I understand it, this would
>> require that you structure your project a little differently, such as
>> having your classes compiled into the root or something (Tom might be
>> able to explain).
>>
>
> Without dev classpath support in the framework you need to place all you
> source and output folders at the root of your projects. Then you should
> be able to use a reference: URL to install the project directory as a
> bundle. This only works because the root of the project will look like
> a bundle to the framework with the META-INF/MANIFEST.MF and .class files
> located directly from your project directory. Another limitation is
> you must only put '.' on your Bundle-ClassPath (or do not
> define a Bundle-ClassPath since this is the default).
>
> HTH
>
> Tom
>
>
>> There was some discussion about getting Felix to support a
>> development-time class path, but this hasn't been prioritized yet. See:
>>
>> http://issues.apache.org/jira/browse/FELIX-136
>>
>> -> richard
>>
>>
>
>
>
Re: Launch Felix with PDE
Posted by Jeff McAffer <Je...@ca.ibm.com>.
Just for a point of reference, what some of the folks in the Spring OSGi
world have been doing is just putting the "bin" (whatever) dirs on the
Bundle-Classpath in the manifest. That works at dev time and at regular
runtime that dir does not exist. This is basically a hack equivalent of
the dev classpath support we have talked about in the past. Implementing
the dev classpath support is not that complex so I would go that route.
Jeff
Thomas Watson <tj...@us.ibm.com>
12/19/2006 12:09 AM
Please respond to
felix-dev@incubator.apache.org
To
felix-dev@incubator.apache.org
cc
Subject
Re: Launch Felix with PDE
"Richard S. Hall" <he...@ungoverned.org> wrote on 12/18/2006 02:01:34 PM:
> Reading your issue about slow start up due to having to create bundle
> JAR files...I think this can be partially avoided by doing install by
> reference (i.e., "reference:"); however, as I understand it, this would
> require that you structure your project a little differently, such as
> having your classes compiled into the root or something (Tom might be
> able to explain).
Without dev classpath support in the framework you need to place all you
source and output folders at the root of your projects. Then you should
be able to use a reference: URL to install the project directory as a
bundle. This only works because the root of the project will look like
a bundle to the framework with the META-INF/MANIFEST.MF and .class files
located directly from your project directory. Another limitation is
you must only put '.' on your Bundle-ClassPath (or do not
define a Bundle-ClassPath since this is the default).
HTH
Tom
>
> There was some discussion about getting Felix to support a
> development-time class path, but this hasn't been prioritized yet. See:
>
> http://issues.apache.org/jira/browse/FELIX-136
>
> -> richard
>
Re: Launch Felix with PDE
Posted by Thomas Watson <tj...@us.ibm.com>.
"Richard S. Hall" <he...@ungoverned.org> wrote on 12/18/2006 02:01:34 PM:
> Reading your issue about slow start up due to having to create bundle
> JAR files...I think this can be partially avoided by doing install by
> reference (i.e., "reference:"); however, as I understand it, this would
> require that you structure your project a little differently, such as
> having your classes compiled into the root or something (Tom might be
> able to explain).
Without dev classpath support in the framework you need to place all you
source and output folders at the root of your projects. Then you should
be able to use a reference: URL to install the project directory as a
bundle. This only works because the root of the project will look like
a bundle to the framework with the META-INF/MANIFEST.MF and .class files
located directly from your project directory. Another limitation is
you must only put '.' on your Bundle-ClassPath (or do not
define a Bundle-ClassPath since this is the default).
HTH
Tom
>
> There was some discussion about getting Felix to support a
> development-time class path, but this hasn't been prioritized yet. See:
>
> http://issues.apache.org/jira/browse/FELIX-136
>
> -> richard
>
Re: Launch Felix with PDE
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Felix Cuadrado wrote:
> Hi all,
>
> To celebrate the recent public release of Apache Felix I have released an
> adaptation of eLuzien that works with the new functionality coming in Eclipse
> 3.3. This version adds Felix launch support to the standard PDE launch
> configuration. The plugin requires Eclipse 3.3 (tested with 3.3M4), and can
> be downloaded at:
> http://forge.os4os.org/frs/shownotes.php?release_id=59
>
> To install it just unzip the file in your Eclipse folder. Feel free to try it
> and tell me what you think :)
>
Sounds pretty cool. Thanks.
Reading your issue about slow start up due to having to create bundle
JAR files...I think this can be partially avoided by doing install by
reference (i.e., "reference:"); however, as I understand it, this would
require that you structure your project a little differently, such as
having your classes compiled into the root or something (Tom might be
able to explain).
There was some discussion about getting Felix to support a
development-time class path, but this hasn't been prioritized yet. See:
http://issues.apache.org/jira/browse/FELIX-136
-> richard
Launch Felix with PDE
Posted by Felix Cuadrado <fc...@dit.upm.es>.
Hi all,
To celebrate the recent public release of Apache Felix I have released an
adaptation of eLuzien that works with the new functionality coming in Eclipse
3.3. This version adds Felix launch support to the standard PDE launch
configuration. The plugin requires Eclipse 3.3 (tested with 3.3M4), and can
be downloaded at:
http://forge.os4os.org/frs/shownotes.php?release_id=59
To install it just unzip the file in your Eclipse folder. Feel free to try it
and tell me what you think :)
Best regards,
Félix
P.S. For more information see the release notes of the file and the bug opened
at the Eclipse bugzila:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=152315
Re: Felix and Eclipse PDE roadblock
Posted by rl...@sbcglobal.net.
FW: Felix and Eclipse PDE roadblockYalcin and Jeff,
I have attached a short summary of the changes made to the Eclipse bundles to get the Equinox extension registry working in Felix. I apologize for the delay as other projects were in the way. I'm not sure at this stage what bug reports I need to open. I suggest that we discuss this summary over at the Equinox mailing list instead. Regards.
Rick Litton
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Sun 12/10/2006 6:01 AM
To: felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Great news! Can you open bug reports in Eclipse/Equinox/Bundles for any
changes that you think should be made in Equinox to make this work more
seamlessly? Please send me or equinox-dev any additional info you might
have so we can add this to the wiki and others can benefit.
As for the "split package" (org.eclipse.core.runtime) we certainly did not
do this willingly. We tried and tried to avoid it but in the end could
not without breaking backwards compatibility. The extension registry API
have been around for many years and are widely used. Unfortunately, the
registry APIs were tightly coupled with the original Eclipse runtime API
(we never envisioned that the runtime would exist independent of the
registry) so are stuck. This is similar the the way the OSGi service
registry APIs are coupled to the OSGi modularity APIs.
Anyway, if Felix supports Require-Bundle then this should all just work
(i.e., we are not doing anything Eclipse-specific in this area). According
to the R4 spec, Require-Bundle is the only way to join two or more package
fragments from different bundles.
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/10/2006 03:06 AM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>, <fe...@incubator.apache.org>,
<fe...@incubator.apache.org>
cc
Subject
RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not
easy to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems
to work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository
(0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement
(1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry
(3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since
my example requires this service. One issue that could have been avoided
was the doubling of the package name "org.eclipse.core.runtime" in two
equinox bundles (common and registry). From experience with Oscar, this
can be problematic. If there is an area for "examples" in the Felix
repository I can probably check in the files with a readme to explain what
was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
Re: Felix and Eclipse PDE roadblock
Posted by Jeff McAffer <Je...@ca.ibm.com>.
I look forward to seeing what you have done.
Note that the bundles involved here are completely standard in terms of
their dependency markup and are known to work unchanged on Knopflerfish.
As Richard mentioned in another post, he is actively working on some of
the Felix support needed here.
Jeff
<rl...@sbcglobal.net>
12/10/2006 08:26 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Re: Felix and Eclipse PDE roadblock
FW: Felix and Eclipse PDE roadblockJeff,
I will be happy to oblige. Unfortunately, I was not very systematic in my
approach and my notes are somewhat convoluted at the moment. But I will
try to clean things up and open an issue report as soon as possible. Aside
from the "split package" issue, I was somewhat concerned with the usage of
the manifest declarations. For example, I noticed that a couple of the
import-package declarations were not working when set with some options.
Since I was not sure if those options were supported in R4 or were
specific to Eclipse, I took the KISS approach ("Keep it stupidly simple")
and removed the optional labels. Thereafter, the imports worked.
Unfortunately, I did not keep a copy of the original manifests so my task
is to download them again and do a diff.
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Sun 12/10/2006 6:01 AM
To: felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Great news! Can you open bug reports in Eclipse/Equinox/Bundles for any
changes that you think should be made in Equinox to make this work more
seamlessly? Please send me or equinox-dev any additional info you might
have so we can add this to the wiki and others can benefit.
As for the "split package" (org.eclipse.core.runtime) we certainly did not
do this willingly. We tried and tried to avoid it but in the end could
not without breaking backwards compatibility. The extension registry API
have been around for many years and are widely used. Unfortunately, the
registry APIs were tightly coupled with the original Eclipse runtime API
(we never envisioned that the runtime would exist independent of the
registry) so are stuck. This is similar the the way the OSGi service
registry APIs are coupled to the OSGi modularity APIs.
Anyway, if Felix supports Require-Bundle then this should all just work
(i.e., we are not doing anything Eclipse-specific in this area). According
to the R4 spec, Require-Bundle is the only way to join two or more package
fragments from different bundles.
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/10/2006 03:06 AM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>, <fe...@incubator.apache.org>,
<fe...@incubator.apache.org>
cc
Subject
RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not
easy to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems
to work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository
(0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement
(1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry
(3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since
my example requires this service. One issue that could have been avoided
was the doubling of the package name "org.eclipse.core.runtime" in two
equinox bundles (common and registry). From experience with Oscar, this
can be problematic. If there is an area for "examples" in the Felix
repository I can probably check in the files with a readme to explain what
was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
Re: Felix and Eclipse PDE roadblock
Posted by rl...@sbcglobal.net.
FW: Felix and Eclipse PDE roadblockJeff,
I will be happy to oblige. Unfortunately, I was not very systematic in my approach and my notes are somewhat convoluted at the moment. But I will try to clean things up and open an issue report as soon as possible. Aside from the "split package" issue, I was somewhat concerned with the usage of the manifest declarations. For example, I noticed that a couple of the import-package declarations were not working when set with some options. Since I was not sure if those options were supported in R4 or were specific to Eclipse, I took the KISS approach ("Keep it stupidly simple") and removed the optional labels. Thereafter, the imports worked. Unfortunately, I did not keep a copy of the original manifests so my task is to download them again and do a diff.
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Sun 12/10/2006 6:01 AM
To: felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Great news! Can you open bug reports in Eclipse/Equinox/Bundles for any
changes that you think should be made in Equinox to make this work more
seamlessly? Please send me or equinox-dev any additional info you might
have so we can add this to the wiki and others can benefit.
As for the "split package" (org.eclipse.core.runtime) we certainly did not
do this willingly. We tried and tried to avoid it but in the end could
not without breaking backwards compatibility. The extension registry API
have been around for many years and are widely used. Unfortunately, the
registry APIs were tightly coupled with the original Eclipse runtime API
(we never envisioned that the runtime would exist independent of the
registry) so are stuck. This is similar the the way the OSGi service
registry APIs are coupled to the OSGi modularity APIs.
Anyway, if Felix supports Require-Bundle then this should all just work
(i.e., we are not doing anything Eclipse-specific in this area). According
to the R4 spec, Require-Bundle is the only way to join two or more package
fragments from different bundles.
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/10/2006 03:06 AM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>, <fe...@incubator.apache.org>,
<fe...@incubator.apache.org>
cc
Subject
RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not
easy to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems
to work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository
(0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement
(1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry
(3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since
my example requires this service. One issue that could have been avoided
was the doubling of the package name "org.eclipse.core.runtime" in two
equinox bundles (common and registry). From experience with Oscar, this
can be problematic. If there is an area for "examples" in the Felix
repository I can probably check in the files with a readme to explain what
was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
RE: Felix and Eclipse PDE roadblock
Posted by Jeff McAffer <Je...@ca.ibm.com>.
Great news! Can you open bug reports in Eclipse/Equinox/Bundles for any
changes that you think should be made in Equinox to make this work more
seamlessly? Please send me or equinox-dev any additional info you might
have so we can add this to the wiki and others can benefit.
As for the "split package" (org.eclipse.core.runtime) we certainly did not
do this willingly. We tried and tried to avoid it but in the end could
not without breaking backwards compatibility. The extension registry API
have been around for many years and are widely used. Unfortunately, the
registry APIs were tightly coupled with the original Eclipse runtime API
(we never envisioned that the runtime would exist independent of the
registry) so are stuck. This is similar the the way the OSGi service
registry APIs are coupled to the OSGi modularity APIs.
Anyway, if Felix supports Require-Bundle then this should all just work
(i.e., we are not doing anything Eclipse-specific in this area). According
to the R4 spec, Require-Bundle is the only way to join two or more package
fragments from different bundles.
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/10/2006 03:06 AM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>, <fe...@incubator.apache.org>,
<fe...@incubator.apache.org>
cc
Subject
RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not
easy to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems
to work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository
(0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement
(1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry
(3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since
my example requires this service. One issue that could have been avoided
was the doubling of the package name "org.eclipse.core.runtime" in two
equinox bundles (common and registry). From experience with Oscar, this
can be problematic. If there is an area for "examples" in the Felix
repository I can probably check in the files with a readme to explain what
was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
Re: Felix and Eclipse PDE roadblock
Posted by rl...@sbcglobal.net.
FW: Felix and Eclipse PDE roadblockHi Yalcin,
I'm looking into the possibility of using extension points in the front end since we have this approach working in the back end using a home grown solution. The front end is a browser based application (JSF/JSP) and not a rich client. I'm trying to recap the changes I made so I will have to get back to you on the specifics of those changes. I had to back out some of them and then put them back only to back them out again in the end. In short, it was an iterative approach. These changes involved the supplemental, common, and registry bundles. At some point I had to pull some classes from the eclipse core but I think I backed those out. Hopefully, I can put together an explanation in a succinct readme file.
Regards,
Rick
-----Original Message-----
From: Yalcin Akdogan [mailto:yalcin.akdogan@chello.at]
Sent: Sun 12/10/2006 5:56 AM
To: felix-dev@incubator.apache.org
Subject: AW: Felix and Eclipse PDE roadblock
Good work Rick, I appreciate it.
Just couple questions:
You made some changes to source files and manifest file. Are your changes
only in supplemental bundle?
I assume your application is a web application. Do you plan to run an
eRCP/RCP application with your changes?
- Yalcin
-----Ursprüngliche Nachricht-----
Von: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Gesendet: Sunday, December 10, 2006 9:07 AM
An: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org;
felix-dev@incubator.apache.org
Betreff: RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not easy
to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems to
work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository (0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement (1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry (3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since my
example requires this service. One issue that could have been avoided was
the doubling of the package name "org.eclipse.core.runtime" in two equinox
bundles (common and registry). From experience with Oscar, this can be
problematic. If there is an area for "examples" in the Felix repository I
can probably check in the files with a readme to explain what was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
AW: Felix and Eclipse PDE roadblock
Posted by Yalcin Akdogan <ya...@chello.at>.
Good work Rick, I appreciate it.
Just couple questions:
You made some changes to source files and manifest file. Are your changes
only in supplemental bundle?
I assume your application is a web application. Do you plan to run an
eRCP/RCP application with your changes?
- Yalcin
-----Ursprüngliche Nachricht-----
Von: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Gesendet: Sunday, December 10, 2006 9:07 AM
An: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org;
felix-dev@incubator.apache.org
Betreff: RE: Felix and Eclipse PDE roadblock
I finally got the equinox extension point registry running. It was not easy
to say the least. I had to make some changes to the equinox code and
manifest files. It's still a long way off from being perfect but it seems to
work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository (0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement (1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry (3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since my
example requires this service. One issue that could have been avoided was
the doubling of the package name "org.eclipse.core.runtime" in two equinox
bundles (common and registry). From experience with Oscar, this can be
problematic. If there is an area for "examples" in the Felix repository I
can probably check in the files with a readme to explain what was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
RE: Felix and Eclipse PDE roadblock
Posted by Rick Litton <Ri...@ktd-kyocera.com>.
I finally got the equinox extension point registry running. It was not easy to say the least. I had to make some changes to the equinox code and manifest files. It's still a long way off from being perfect but it seems to work (see below)!
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (0.8.0.SNAPSHOT)
[ 1] [Active ] [ 1] Apache Felix Shell Service (0.8.0.SNAPSHOT)
[ 2] [Active ] [ 1] Apache Felix Shell TUI (0.8.0.SNAPSHOT)
[ 3] [Active ] [ 1] Apache Felix Bundle Repository (0.8.0.SNAPSHOT)
[ 4] [Active ] [ 1] OSGi R4 Core Bundle (4)
[ 5] [Active ] [ 1] OSGi R4 Compendium Bundle (4)
[ 6] [Active ] [ 1] Servlet 2.1 API (0.8.0.SNAPSHOT)
[ 7] [Active ] [ 1] Eclipse Equinox Supplement (1.0.0.200612091415)
[ 8] [Active ] [ 1] HTTP Service (0.8.0.SNAPSHOT)
[ 9] [Active ] [ 1] Eclipse Equinox Common (3.3.0.200612091417)
[ 10] [Active ] [ 1] Eclipse Equinox Registry (3.2.100.200612091419)
[ 11] [Active ] [ 1] Application Plug-in (1.0.0)
->
Will need to add the equinox http bundles in lieu of the felix http since my example requires this service. One issue that could have been avoided was the doubling of the package name "org.eclipse.core.runtime" in two equinox bundles (common and registry). From experience with Oscar, this can be problematic. If there is an area for "examples" in the Felix repository I can probably check in the files with a readme to explain what was done.
Thanks to Richard and Jeff ("the McAffer guy")!
-- rick
-----Original Message-----
From: Rick Litton [mailto:Rick.Litton@ktd-kyocera.com]
Sent: Sat 12/9/2006 10:14 AM
To: felix-dev@incubator.apache.org; felix-dev@incubator.apache.org
Subject: RE: Felix and Eclipse PDE roadblock
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
RE: Felix and Eclipse PDE roadblock
Posted by Rick Litton <Ri...@ktd-kyocera.com>.
Hi Jeff,
Thanks for the tip. I will try it...
Regards,
Rick
-----Original Message-----
From: Jeff McAffer [mailto:Jeff_McAffer@ca.ibm.com]
Sent: Fri 12/8/2006 8:09 PM
To: felix-dev@incubator.apache.org
Subject: Re: Felix and Eclipse PDE roadblock
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton
Re: Felix and Eclipse PDE roadblock
Posted by Jeff McAffer <Je...@ca.ibm.com>.
Rick
As a point of interest, you should be able to use the Equinox Supplement
bundle
http://www.eclipse.org/equinox/bundles#supplement
rather than org.eclipse.osgi. This bundle is designed to supply the bits
of the Equinox framework that are needed in other OSGi scenarios.
I believe some folks in Equinox land have gotten the registry working on
Knopflerfish. Not sure if they have tried Felix. Perhaps you should ask
on the equinox newsgroup for some guidance. I'm sure they would be happy
to compare notes
Jeff
"Rick Litton" <Ri...@ktd-kyocera.com>
12/08/2006 01:57 PM
Please respond to
felix-dev@incubator.apache.org
To
<fe...@incubator.apache.org>
cc
Subject
Felix and Eclipse PDE roadblock
I'm still trying to get the extension points registry to work in Felix
and unfortunately, I have hit a roadblock. After trying out several
combinations and pruning the eclipse core bundle (as Richard Hall has
suggested) to remove redundant osgi core classes, I have created the
following dependency graph to help illustrate the problem:
/---> org.osgi.compendium
|
| (requires: org.osgi.util.tracker package)
|
|---> org.osgi.core
|
| (requires: org.osgi.service.permissionadmin package)
|
| org.eclipse.osgi_3.2.1R32x <----\
| ^ |
| (requires:|org.eclipse.osgi.service.urlconversion package)
| | |
|---- org.eclipse.equinox.common |
| ^ |
| | |
| | |
\---- org.eclipse.equinox.registry |
| |
| |
\---------------------/
(requires: org.eclipse.osgi.service.datalocation package)
I hope the graph is displayed correctly by your mail client. Anyhow, I
was getting quite a few BundleExceptions "Unable to resolve due to
constraint violation"). So I removed all the optional bundles and
proceeded to test each one. Immediately, the BundleException came up
after I had just added/started the org.osgi.core bundle. I certainly
would welcome any suggestion to resolve this problem.
Rick Litton