Blueprint not loading bundle's beans on EAP 6.1

[guilhermeramos]

Ok. I'm sorry to write about this but I'm on a deadlock here.

I have been searching here and through Google but with no success.

Using Aries Blueprint is pretty straightforward, but for some unknow(to me) reason it's not working on JBoss EAP 6.1.

And beyond that, this very same bundle runs like a charm on Apache Karaf 2.3.0.

The bundle's Activator is called but the bean defined at OSGI-INF/blueprint/blueprint.xml is IGNORED.

And there is no sign of the Aries Blueprint Extender at the JBOSS Log although it's bundles is succesfully installed via capabilities as seen below:

     <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="eager">
            <properties>
                <property name="org.jboss.osgi.system.modules.extra">
                    org.apache.log4j
                </property>
                <property name="org.osgi.framework.startlevel.beginning">
                    1
                </property>
                <property name="org.osgi.framework.system.packages.extra">
                    org.apache.log4j;version=1.2
                </property>
            </properties>
            <capabilities>
                <capability name="javax.jws.api"/>
                <capability name="javax.persistence.api"/>
                <capability name="javax.servlet.api"/>
                <capability name="javax.transaction.api"/>
                <capability name="javax.ws.rs.api"/>
                <capability name="javax.xml.bind.api"/>
                <capability name="javax.xml.ws.api"/>
                <capability name="org.javassist"/>
                <capability name="org.apache.log4j"/>
                <capability name="org.slf4j"/>
                <capability name="org.hibernate"/>
                <capability name="org.apache.felix.log" startlevel="1"/>
                <capability name="org.jboss.osgi.logging" startlevel="1"/>
                <capability name="org.apache.felix.configadmin" startlevel="1"/>
                <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
                <capability name="org.jboss.as.osgi.http" startlevel="1"/>
                <capability name="org.jboss.as.osgi.jpa" startlevel="1"/>
                <capability name="org.apache.aries:org.apache.aries.util:0.4" startlevel="2"/>
                <capability name="org.apache.aries.proxy:org.apache.aries.proxy:0.4" startlevel="2"/>
                <capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:0.4" startlevel="2"/>
            </capabilities>
        </subsystem>

The bundle is attached.

Can you PLEASE HELP ME?

Thanks so such.

Regards from Brazil.

[ampiefnb]

Hi Guilherme,

Just a shot in the dark here, but try to increase the property org.osgi.framework.startlevel.beginning to 2.

Good luck

Ampie

[guilhermeramos]

Wow! It worked!

But why? Why changing this property to 2 will affect in blueprint extender behaviour?

[guilhermeramos]

And I can observe an unstable behaviour.

When starting JBoss and I got a lot of bundles deployed, sometimes blueprint extender runs fine (creating beans and services) and sometimes it doesn't work as expected. All I have to do is halt jboss and run it again until Aries do his job.

I can't find a reasonable cause for this. Maybe a bug?

[guilhermeramos]

All I'm trying to do is setup a OSGi service (managed by Aries) which holds a EntityManager.

This EntityManager is obviously builded by the persistence.xml whithin the META-INF folder.

This OSGi service will be consumed by another bundles. I don't want to use EJB.

With the current version EAP 6.1 is possible?

Can please somebody help me?