[
https://issues.jboss.org/browse/JBOSGI-699?page=com.atlassian.jira.plugin...
]
Ampie Barnard commented on JBOSGI-699:
--------------------------------------
Thomas, I see you are awaiting volunteers. Depending on the nature of the beast, I may be
able offer some of my (albeit limited) skills. How were you thinking of implementing this
requirement? What is currently the main obstacle?
My understanding was, and I may be wrong, that the Weld OSGi OSGi/CDI integration was
going to be used. I have tested the weld-osgi-2.x branch on JBosgi 2 and Wildfly 8 Alpha
3, but I could not get Weld OSGi and the Weld subsystem to run side by side. I described
my attempt in more detail on the Weld forum at
[
https://community.jboss.org/thread/231047]. What I don't understand though, is what
JBoss OSGi can do to resolve this conflict. Is it merely a packaging issue, packaging Weld
OSGi as modules and enabling them as a cability? Or does it involve re-implementing some
of the Weld-OSGi logic in a more Wildfly-friendly way? Or did you have an entirely
different approach in mind?
Initial OSGi / CDI Integration
-------------------------------
Key: JBOSGI-699
URL:
https://issues.jboss.org/browse/JBOSGI-699
Project: JBoss OSGi
Issue Type: Feature Request
Components: cdi
Reporter: Thomas Diesler
Provide an example test that shows CDI integration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira