Hello,

I finally raised a thread into the JBoss Community forum as this integration is 
working well with JBoss EAP 6.1...

If you're interested you can follow it 
:https://community.jboss.org/thread/232486

Thank you for your help

Regards,

Mathilde

----------------------------------------------------------------------------------------

I've been running the latest iPOJO in an OSGi R5 env without any issues (at
least not that one ;) ).

@felix I thought of that possibility, but looking at the error it says that
the service reference points to a DefaultInstanceDeclaration object, where
a TypeDeclaration is expected.

java.lang.ClassCastException: org.apache.felix.ipojo.
extender.internal.declaration.DefaultInstanceDeclaration cannot be cast to
org.apache.felix.ipojo.extender.TypeDeclaration
        at
org.apache.felix.ipojo.extender.internal.linker.DeclarationLinker.addingService(DeclarationLinker.java:83)

This is really strange since we're using a ServiceTracker configured to be
notified when TypeDeclaration services are registered:
m_typeTracker = new ServiceTracker(m_bundleContext,
TypeDeclaration.class.getName(), this);

And when the addingService() method is called with the ServiceReference, it
turns out that this is not a typeDeclaration at all, but an
InstanceDeclaration...

There is something weird here.

--G


2013/9/12 Felix Meschberger<[email protected]>

 Hi

 I have the impression, this is something different.

 Could it be that the org.apache.felix.ipojo.extender.TypeDeclaration type
 is not being shared amongst the bundles ? This could be the case for
 example if it is exported multiple times by different bundles and consuming
 bundles are not wiring to the same provider. Or it could be that one bundle
 erroneously embeds it and does not use the export of the actual provider.

 Regards
 Felix

 Am 12.09.2013 um 00:33 schrieb Bertrand Quenin:

 >  I think I might have found the problem. In the iPojo main pom.xml we
 have:
 >
 >  <dependency>
 >             <groupId>org.osgi</groupId>
 >             <artifactId>org.osgi.core</artifactId>
 >             <version>4.3.1</version>
 >         </dependency>
 >         <dependency>
 >             <groupId>org.osgi</groupId>
 >             <artifactId>org.osgi.compendium</artifactId>
 >             <version>4.2.0</version>
 >         </dependency>
 >
 >  But Wildfly uses osgi version 5 (as seen in the stack traces in the
 log). Do you think that could be the issue cause and if yes, is there any
 OSGi 5 compatible iPojo around ?
 >
 >  Thanks,
 >  BQ.
 >

Reply via email to