| Riena 1.0.M2 and required bundles vs import [message #2846] |
Tue, 20 May 2008 17:18  |
Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
common bundles like Hessian, Log4J or so which are not part of eclipse SDK,
I'm using from the SpringSource Enterprise Bundle Repository.
http://www.springsource.com/repository/app/
if I'm using
com.springsource.com.caucho-3.1.5
com.springsource.org.apache.log4j-1.2.15
this won't work with Riena, because Riena uses
'Required bundle' in MANIFEST.MF
if you would use 'Import' instead, then I could use the bundles from
SpringSource with Riena, too
ekke
|
|
|
|
|
| Re: Riena 1.0.M2 and required bundles vs import [message #4420 is a reply to message #4209] |
Wed, 04 June 2008 12:45  |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
hi christian,
thanks for making things clearer.
of course the buddy is not part of the SpringSource repository,
because it doesn't depend on equinox ;-)
so in this case we need the Riena-bundle
I think its always good to use Import where possible because
then its easier to replace a bundle.
and from my opinion its always good to use an existing bundle from a
repository (orbit or springsource or bnd) instead of creating
an own.
otherwise there can be much chaos ;-)
I'm just testing and integrating Easybeans OSGI with equinox
instead of felix. but thats only the first part.
next one is integrating this with Riena
so for common bundles like log4j, commons-xxx, hibernate, etc
I prefer to use them only one time in the whole system (my osgi server)
and so I like import, which gives enough stability in these cases
if the import is combined with a version number (if a special one is
needed)
I'll open a bugzilla for using import with logging
thx again for your detailed informations
ekke
btw: if you have read the german osgi book from gerd wütherich, chapter
5.4 - they also prefer import before require bundle
Christian Campo wrote:
> Sorry I didn't reply to your question in the first place.
> This is a tricky one which I briefly discussed with a collegue but forget to
send you about it.
> Hessian is a bundle that we put in the Riena project at least currently
because no other project currently uses it. So
> it didnt end up in Orbit the Eclipse equivalent of the SpringSource
Repository.
> Up to now we have not modified the source code of hessian itself because it
wasn't necessary. I am not absolutly sure
> that we can always be sure that it stays that way. Another issue is the
MANFEST.MF in hessian. Ours defined
> Eclipse-BuddyPolicy: register which I have no idea that I can rely on that
Springsource has the same.
> I am also not sure why you want to use the one from SpringSource if Riena is
already bringing on. Are you using other
> components outside from Riena that also need hessian ? Even then 2 hessian
components can coexist, ok I agree that this
> is not very nice.
> I am not sure if you should change all required bundle entries to import
package for all externall packages. The risk is
> that Riena wont run and somebody will have a hard time to find out why.
> For Logging I think we could change that because if logging doesnt output
anything, that is not as critical as if remote
> services dont work anymore. Please add a bugzilla asking for that change.
> You can also add another bugzilla for the hessian issue. Please give some
more details why you prefer to use the hessian
> implementation from SpringSource and how we can be sure that the manifest
allows to register buddies.
> Are there any performance issues when using Imports over Requires-Bundle ?
Not sure.
> regards
> christian
> ekke schrieb:
>> what do you think about this ?
>> should I open a bugzilla ?
>>
>> ekke
>>
|
|
|
|
|
| Re: Riena 1.0.M2 and required bundles vs import [message #571832 is a reply to message #4209] |
Wed, 04 June 2008 12:45 |
| Eclipse User |
|
|
|
Originally posted by: ekkehard.gentz-software.de
hi christian,
thanks for making things clearer.
of course the buddy is not part of the SpringSource repository,
because it doesn't depend on equinox ;-)
so in this case we need the Riena-bundle
I think its always good to use Import where possible because
then its easier to replace a bundle.
and from my opinion its always good to use an existing bundle from a
repository (orbit or springsource or bnd) instead of creating
an own.
otherwise there can be much chaos ;-)
I'm just testing and integrating Easybeans OSGI with equinox
instead of felix. but thats only the first part.
next one is integrating this with Riena
so for common bundles like log4j, commons-xxx, hibernate, etc
I prefer to use them only one time in the whole system (my osgi server)
and so I like import, which gives enough stability in these cases
if the import is combined with a version number (if a special one is
needed)
I'll open a bugzilla for using import with logging
thx again for your detailed informations
ekke
btw: if you have read the german osgi book from gerd wütherich, chapter
5.4 - they also prefer import before require bundle
Christian Campo wrote:
> Sorry I didn't reply to your question in the first place.
> This is a tricky one which I briefly discussed with a collegue but forget to
send you about it.
> Hessian is a bundle that we put in the Riena project at least currently
because no other project currently uses it. So
> it didnt end up in Orbit the Eclipse equivalent of the SpringSource
Repository.
> Up to now we have not modified the source code of hessian itself because it
wasn't necessary. I am not absolutly sure
> that we can always be sure that it stays that way. Another issue is the
MANFEST.MF in hessian. Ours defined
> Eclipse-BuddyPolicy: register which I have no idea that I can rely on that
Springsource has the same.
> I am also not sure why you want to use the one from SpringSource if Riena is
already bringing on. Are you using other
> components outside from Riena that also need hessian ? Even then 2 hessian
components can coexist, ok I agree that this
> is not very nice.
> I am not sure if you should change all required bundle entries to import
package for all externall packages. The risk is
> that Riena wont run and somebody will have a hard time to find out why.
> For Logging I think we could change that because if logging doesnt output
anything, that is not as critical as if remote
> services dont work anymore. Please add a bugzilla asking for that change.
> You can also add another bugzilla for the hessian issue. Please give some
more details why you prefer to use the hessian
> implementation from SpringSource and how we can be sure that the manifest
allows to register buddies.
> Are there any performance issues when using Imports over Requires-Bundle ?
Not sure.
> regards
> christian
> ekke schrieb:
>> what do you think about this ?
>> should I open a bugzilla ?
>>
>> ekke
>>
|
|
|
Powered by
FUDForum. Page generated in 0.03518 seconds
] 
Search
Help
Register
Login
Home
