These are proof-of-concepts for JBoss AS 7 with using Gemini Blueprint.
Build with mvn clean package, deploy with mvn jboss-as:deploy.
To install Gemini Blueprint to JBoss, you'll need
- get the aopalliance bundle
- get the commons-logging bundle
- get the spring-core
- get spring-aop
- get spring-beans
- get spring-context
- get spring-asm
- get spring-expression
- install the above
- get the actual gemini files
- install gemini-blueprint-io
- install gemini-blueprint-core
- install gemini-blueprint-extender
Then you'd be good to go.
Note that Gemini Blueprint is not directly interchangeable with other Blueprint implementations right now due to it not exporting org.osgi.service.blueprint yet.
Scope of these tests would be
| Capability | Status | Notes |
|---|---|---|
| OSGi bundle | OK | |
| OSGi composite bundle | OK | |
| war - osgibundle communication | OK | Using ServiceTracker, which is not optimal |
| ejb - osgibundle communication | OK | Using ServiceTracker, which is not optimal |
| wab (OSGi war) | tbd | Note really recommended in JBoss 7.1. JBoss does not directly support at that version, but forks a Jetty process for these, so they don't get the full set on features. Support will be in 7.2. |
| wab - osgibundle communication | tbd | |
| JNDI with OSGi bundle | OK | JBoss 7.1 does not support, needs Aries JNDI installed |
| JMS with OSGi bundle | OK | |
| JTA with OSGi bundle | OK | |
| JDBC with OSGi bundle | OK | |
| OSGi security | - | Related to bundle signing, similar to what applets have. JBoss does not implement. |
| Petclinic app - bundle communication | OK | Using ServiceTracker, which is not optimal |