|
|
|
|
|
|
|
|
|
| Re: Vaadin + Virgo not working... [message #676695 is a reply to message #676680] |
Mon, 06 June 2011 04:18   |
|
Glyn Normington wrote on Mon, 06 June 2011 08:15Does this FAQ help? You can use the technique to import your application's packages into Vaadin.
Hi Glyn,
doesn't that lead to a cyclic dependency? The WAB imports Vaadin packages and at the same time the Vaadin fragment is going to import the WAP packages into the Vaadin bundle. Maybe I'm missing something here but I thought that's not possible.
One thing I've tried yesterday evening after I've read Arnold's post is to make the WAB (the one Arnold has provided in the Vaadin forum) a fragment of Vaadin but that didn't work. I have to admit I didn't check the spec but from the behaviour I've seen in Virgo I think that's not possible is it?
Another thing I wanted to try today is the following. Specify a custom classloader in the WAB and make this CL available via OSGi services. Then create a fragment (host is the Vaadin bundle) with a class that has the same name as the custom classloader specified in the web.xml (that's what the Vaadin bundle is looking for). This class then has the responsibility to get the custom classloader of the WAB via an OSGi service reference. I didn't try this approach yet but that's the only scenario I can come up with at the moment. If there is a better/easier approach for this I'm eager to hear it.
Regards
Frieder
|
|
|
|
|
|
| Re: Vaadin + Virgo not working... [message #681970 is a reply to message #676709] |
Fri, 10 June 2011 03:06  |
|
Glyn Normington wrote on Mon, 06 June 2011 11:12Hi Frieder
Cyclic dependencies are ok in OSGi. Usually they are a problem for build, but since a host bundle does not depend on its fragment, fragments break the cycle in this situation at build time.
Regards,
Glyn
Hi Glyn,
thank you for the clarification. Looks like I confused the issue.
Bye
Frieder
|
|
|
Powered by
FUDForum. Page generated in 0.02464 seconds