Eclipse Community Forums: Virgo

Home » Eclipse Projects » Virgo » TCCL Headache

Wed, 09 May 2012 05:07

Eclipse User

So I'm in the midst of porting a big OSGi-app to Virgo - and I'm having some headaches dealing with Virgos synthetic TCCL... I understand it's purpose and see how it helps in many ways. But it also creates issues (especially when porting things from a pure OSGi'world it sort of turns things upside down - if you are developing from scratch it will be easier). My particular headache is around the following:

Typically you'll have code, own or 3rd-party, that tries to load resources using the TCCL (configurations or other resources) - and these resources are typically held private (i.e. not part of your exports). If that is the case - the TCCL will not be able to locate the resourcs and you get failures. To workaround this I am now considering to forcefully set the TCCL in some appropriate places (to the bundles own classloader)...

Have I missed something ? Is there a better way of dealing with this ? I'm hoping so...

Insights would be appreciated.

Re: TCCL Headache [message #870664 is a reply to message #870657]

Wed, 09 May 2012 05:36

Eclipse User

I guess this problem can be generalized... How do you deal with the TCCL needing to load things (classes or resources) that are to be held private ? (i.e. not exported)

Re: TCCL Headache [message #871039 is a reply to message #870664]

Thu, 10 May 2012 11:34

Eclipse User

The design of Virgo's TCCL support is that if you want a class or resource to be loaded via the TCCL, then you really are exposing that class or resource outside its bundle and therefore it makes sense to export it.

You have the option of using an unscoped plan to avoid the synthetic context bundle altogether.

Previous Topic:	Virgo and binded ports
Next Topic:	@Autowired doesn't work when trying to wire a service

Goto Forum:

-=] Back to Top [=-

Current Time: Fri May 23 05:36:31 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter