Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » TCCL Headache
TCCL Headache [message #870657] Wed, 09 May 2012 05:07 Go to next message
Johan Eriksson is currently offline Johan Eriksson
Messages: 17
Registered: May 2012
Junior Member
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.

Report message to a moderator

Re: TCCL Headache [message #870664 is a reply to message #870657] Wed, 09 May 2012 05:36 Go to previous messageGo to next message
Johan Eriksson is currently offline Johan Eriksson
Messages: 17
Registered: May 2012
Junior Member
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)

Report message to a moderator

Re: TCCL Headache [message #871039 is a reply to message #870664] Thu, 10 May 2012 11:34 Go to previous message
Glyn Normington is currently offline Glyn Normington
Messages: 1186
Registered: July 2009
Senior Member
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.

Report message to a moderator

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

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Sat May 18 10:58:55 EDT 2013

Powered by FUDForum. Page generated in 0.01688 seconds