Re: Unable to reload bundles due to class loader issues around javax.transaction.xa.XAResource

[Mark Derricutt <ma...@talios.com>]

Refreshing was were we actually saw the problems manifest - I've just traced
it down to the package exporting javax.transaction not actually importing it
- so once the refresh occurred we had two copies being exported.

All sorted now :)

On Wed, Jan 14, 2009 at 9:50 PM, Felix Meschberger <fm...@gmail.com>wrote:

> Have you tried to refresh the packages ?
>
>

Re: Unable to reload bundles due to class loader issues around javax.transaction.xa.XAResource

[Mark Derricutt <ma...@talios.com>]

This type of problem is probably the most common I've encountered with OSGi
- so much so that a bundle audit tool comes to mind :)  Thankfully we only
have two bundles remaining that we're manually maintaining the .bnd file,
the maven-felix-plugin solves a lot of these issues (thou sometimes
introduces its own).

On Fri, Jan 16, 2009 at 8:35 PM, Felix Meschberger <fm...@gmail.com>wrote:

>
> Oh, yeah, this is a difficult one to track down ;-)
>

Re: Unable to reload bundles due to class loader issues around javax.transaction.xa.XAResource

[Felix Meschberger <fm...@gmail.com>]

Hi Mark

Cool. Thanks for the update.

Mark Derricutt schrieb:
> Refreshing was were we actually saw the problems manifest - I've just traced
> it down to the package exporting javax.transaction not actually importing it
> - so once the refresh occurred we had two copies being exported.

Oh, yeah, this is a difficult one to track down ;-)

Regards
Felix


> 
> All sorted now :)
> 
> On Wed, Jan 14, 2009 at 9:50 PM, Felix Meschberger <fm...@gmail.com>wrote:
> 
>> Have you tried to refresh the packages ?
>>
>>
>