You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Daniel Kulp <dk...@apache.org> on 2010/07/21 19:16:40 UTC
Latest components cannot work on equinox.....
With the update of the smx components to use blueprint, I can no longer get
them to work with the latest equinox release that is used as part of Helios.
The basic reason is that the xbean-blueprint bundle that is now required
REQUIRES org.osgi.service.cm_1.3.0, but equinox provides 1.2.1.
Is there a way to back out the xbean-blueprint requirements, particularly for
servicemix-http so that it can work?
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Latest components cannot work on equinox.....
Posted by Guillaume Nodet <gn...@gmail.com>.
Well, we can easily fix xbean-blueprint too if the problem is there.
I really doubt the requirement isreally on CM 1.3.
I'm already in vacation, but ask djencks, i'm sure he can fix that very easily.
The code is at the following location fwiw:
http://svn.apache.org/repos/asf/geronimo/xbean/trunk/xbean-blueprint
If you can make him change this bit, please also ask him to make sure
that jexl becomes an optional package.
On Wed, Jul 21, 2010 at 21:00, Daniel Kulp <dk...@apache.org> wrote:
> On Wednesday 21 July 2010 2:47:00 pm Guillaume Nodet wrote:
>> Switching to blueprint should solve a bunch of problems, including
>> some you have reported, such as ordering problems at startup.
>> Checking servicemix-http manifest, there's no dependency on
>> ConfigAdmin package directly. However it uses the cm namespace from
>> aries blueprint, which seems to depend on 1.3, but I don't think this
>> is a hard requirement. I think it should work if the requirement is
>> downgraded to cm 1.2 without any problems, so i'd raise a JIRA issue
>> on aries.
>> Last, you could always use a different CM implementation if needed.
>>
>> So I agree we should fix that, but I don't think switching back to
>> spring-dm dependency is a good solution.
>
> I'm not arguing about going back to spring-dm. I'm just wondering if it's at
> all possible to NOT require xbeans.blueprint. That's where the problem
> stems.
>
> It's not a problem in Aries. I had the NMR and JBI and CXF bundles and such
> all working fine with the Aries blueprint implementation, but it didn't need
> the xbeans.blueprint. It's a problem with the xbeans.blueprint bundle.
>
> If the blueprint specification in smx-http (and it's deps) could not require
> that, then I'd be all set.
>
> Dan
>
>
>
>>
>> On Wed, Jul 21, 2010 at 19:16, Daniel Kulp <dk...@apache.org> wrote:
>> > With the update of the smx components to use blueprint, I can no longer
>> > get them to work with the latest equinox release that is used as part of
>> > Helios. The basic reason is that the xbean-blueprint bundle that is now
>> > required REQUIRES org.osgi.service.cm_1.3.0, but equinox provides 1.2.1.
>> >
>> > Is there a way to back out the xbean-blueprint requirements, particularly
>> > for servicemix-http so that it can work?
>> >
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org
>> > http://dankulp.com/blog
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Latest components cannot work on equinox.....
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 21 July 2010 2:47:00 pm Guillaume Nodet wrote:
> Switching to blueprint should solve a bunch of problems, including
> some you have reported, such as ordering problems at startup.
> Checking servicemix-http manifest, there's no dependency on
> ConfigAdmin package directly. However it uses the cm namespace from
> aries blueprint, which seems to depend on 1.3, but I don't think this
> is a hard requirement. I think it should work if the requirement is
> downgraded to cm 1.2 without any problems, so i'd raise a JIRA issue
> on aries.
> Last, you could always use a different CM implementation if needed.
>
> So I agree we should fix that, but I don't think switching back to
> spring-dm dependency is a good solution.
I'm not arguing about going back to spring-dm. I'm just wondering if it's at
all possible to NOT require xbeans.blueprint. That's where the problem
stems.
It's not a problem in Aries. I had the NMR and JBI and CXF bundles and such
all working fine with the Aries blueprint implementation, but it didn't need
the xbeans.blueprint. It's a problem with the xbeans.blueprint bundle.
If the blueprint specification in smx-http (and it's deps) could not require
that, then I'd be all set.
Dan
>
> On Wed, Jul 21, 2010 at 19:16, Daniel Kulp <dk...@apache.org> wrote:
> > With the update of the smx components to use blueprint, I can no longer
> > get them to work with the latest equinox release that is used as part of
> > Helios. The basic reason is that the xbean-blueprint bundle that is now
> > required REQUIRES org.osgi.service.cm_1.3.0, but equinox provides 1.2.1.
> >
> > Is there a way to back out the xbean-blueprint requirements, particularly
> > for servicemix-http so that it can work?
> >
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://dankulp.com/blog
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Re: Latest components cannot work on equinox.....
Posted by Guillaume Nodet <gn...@gmail.com>.
Switching to blueprint should solve a bunch of problems, including
some you have reported, such as ordering problems at startup.
Checking servicemix-http manifest, there's no dependency on
ConfigAdmin package directly. However it uses the cm namespace from
aries blueprint, which seems to depend on 1.3, but I don't think this
is a hard requirement. I think it should work if the requirement is
downgraded to cm 1.2 without any problems, so i'd raise a JIRA issue
on aries.
Last, you could always use a different CM implementation if needed.
So I agree we should fix that, but I don't think switching back to
spring-dm dependency is a good solution.
On Wed, Jul 21, 2010 at 19:16, Daniel Kulp <dk...@apache.org> wrote:
>
> With the update of the smx components to use blueprint, I can no longer get
> them to work with the latest equinox release that is used as part of Helios.
> The basic reason is that the xbean-blueprint bundle that is now required
> REQUIRES org.osgi.service.cm_1.3.0, but equinox provides 1.2.1.
>
> Is there a way to back out the xbean-blueprint requirements, particularly for
> servicemix-http so that it can work?
>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com