openejb-client has OSGi Require-Bundle without a maven dependency.

[Rick McGuire]

I ran into a little issue with the bundlized version of the
openejb-client jar.  This jar has a Require-Bundle dependency on
org.apache.openejb.openebj-core, but the project pom does not specify a
maven dependency on openejb-core.  This is causing a bit of an issue
when used in Geronimo 3.0 because the framework is using the maven
dependencies to determine the install/start order for the different
bundles we're using.  Since there's no maven dependency, the
openejb-client is giving a resolution constraint failure on the required
jar depending on the relative order the different openejb bundles get
started.  Having the correct maven dependency in the pom would sort all
of that out.

Is there some reason why this was done this way, or is it just an oversight?

Rick

[Rick McGuire]

Ok, this is an even more fundamental error here...the symbolic name
specified on the Require-Bundle is wrong.  This should be
org.apache.openejb.core, not org.apache.openejb.openejb-core.  The
missing dependency is still a problem though.

Rick

Rick McGuire wrote:

> I ran into a little issue with the bundlized version of the
> openejb-client jar.  This jar has a Require-Bundle dependency on
> org.apache.openejb.openebj-core, but the project pom does not specify
> a maven dependency on openejb-core.  This is causing a bit of an issue
> when used in Geronimo 3.0 because the framework is using the maven
> dependencies to determine the install/start order for the different
> bundles we're using.  Since there's no maven dependency, the
> openejb-client is giving a resolution constraint failure on the
> required jar depending on the relative order the different openejb
> bundles get started.  Having the correct maven dependency in the pom
> would sort all of that out.
>
> Is there some reason why this was done this way, or is it just an
> oversight?
>
> Rick
>

[David Blevins]

On Nov 3, 2009, at 7:27 AM, Rick McGuire wrote:

> I ran into a little issue with the bundlized version of the openejb-
> client jar.  This jar has a Require-Bundle dependency on  
> org.apache.openejb.openebj-core, but the project pom does not  
> specify a maven dependency on openejb-core.  This is causing a bit  
> of an issue when used in Geronimo 3.0 because the framework is using  
> the maven dependencies to determine the install/start order for the  
> different bundles we're using.  Since there's no maven dependency,  
> the openejb-client is giving a resolution constraint failure on the  
> required jar depending on the relative order the different openejb  
> bundles get started.  Having the correct maven dependency in the pom  
> would sort all of that out.
>
> Is there some reason why this was done this way, or is it just an  
> oversight?

I'm not sure why there is a Require-Bundle dep on openejb-core.  Maybe  
someone else can comment on that.

Code-wise, the client jar is designed to work without any other  
OpenEJB libraries or third party dependencies (except for specs), so  
that explains why there is not a maven dep.


-David

[Jacek Laskowski]

On Tue, Nov 3, 2009 at 9:12 PM, David Blevins <david.blevins@...> wrote:

> I'm not sure why there is a Require-Bundle dep on openejb-core.  Maybe
> someone else can comment on that.
>
> Code-wise, the client jar is designed to work without any other OpenEJB
> libraries or third party dependencies (except for specs), so that explains
> why there is not a maven dep.

Uff, I'm relieved. I thought it was me who introduced it, but don't
see myself listed in the svn log pom.xml. The openejb-client module is
not yet used in the osgification and I could only envision its use in
a remote client which uses OSGi and openejb in a standalone mode,
remotely. I don't think anybody has given it a try yet.

I've just committed a change so core is no longer listed as a required
bundle (it turned out someone had changed it before I could:))

------------------------------------------------------------------------
r832492 | rickmcguire | 2009-11-03 19:12:44 +0100 (Tue, 03 Nov 2009) | 1 line

Some changes to cleanup osgi package import issues

Thanks for a heads-up.

Jacek

--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl