Exception when accessing resource file in osgi bundle

[edebar]

Hi,

I'm trying fuse 6.1 on a AIX server and having a little problem in a bean initialization :

I created a spring-dm bundle, based on the "com.fusesource.byexample.hellocamel".

I just add a bean BranchXmlSchemaValidatorBean, wich is declared as follow :

<bean id="BranchXmlSchemaValidatorBean"

class="com.fusesource.byexample.hellocamel.impl.XmlSchemaValidatorBean">

<property name="schemaPath" value="classpath:DocrouterBranch.xsd" />

</bean>

In the class, the method setSchemaPath is : public void setSchemaPath(Resource schemaPath)

Locally on my pc in eclipse, the route is working fine, BUT on the fuse 6.1 beta server, the route is NOT starting, see the stacktrace below.

I can say that in the jar file, the xsd is there in the root.

Can someone tell me the problem ?

Thanks a lot !

• org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'BranchXmlSchemaValidatorBean' defined in URL [bundle://282.0:0/META-INF/spring/camel-context.xml]: Error setting property values; nested exception is org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'schemaPath' threw exception; nested exception is java.io.FileNotFoundException: OSGi resource[classpath:DocrouterBranch.xsd|bnd.id=282|bnd.sym=com.fusesource.byexample.hellocamel.HelloCamel] cannot be resolved to absolute file path
• 1423
• 1128
• 519
• 458
• 295
• 223
• 292
• 194
• 628
• 932
•   at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:69)[org.springframework.osgi:spring-osgi-core:1.2.1]
•   at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:355)[org.springframework.osgi:spring-osgi-core:1.2.1]
•   at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)[org.springframework.osgi:spring-osgi-core:1.2.1]
•   at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)[org.springframework.osgi:spring-osgi-core:1.2.1]
•   at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)[org.springframework.osgi:spring-osgi-extender:1.2.1]
•   at java.lang.Thread.run(Thread.java:761)[:1.6.0]
• Caused by: org.springframework.beans.PropertyBatchUpdateException; nested PropertyAccessExceptions (1) are: PropertyAccessException 1: org.springframework.beans.MethodInvocationException: Property 'schemaPath' threw exception; nested exception is java.io.FileNotFoundException: OSGi resource[classpath:DocrouterBranch.xsd|bnd.id=282|bnd.sym=com.fusesource.byexample.hellocamel.HelloCamel] cannot be resolved to absolute file path
• 101
• 57
• 1420
• ... 15 more

[davsclaus]

What build number of JBoss Fuse 6.1 are you using?

You can try with latest build 379 which is the release candidate for GA

https://repository.jboss.org/nexus/content/repositories/ea/org/jboss/fuse/jboss-fuse-full/

[edebar]

Hi,

I also tested yesterday with the build 379 with the same behaviour.

It seems that this way of working (resource in the classpath) is not possible with osgi bundle. I should be possible to access the resource via the bundle context (bundle.getResource(xxx)).

But I solve my problem by reading the resource files on the filesystem rather than in the bundle. It is quite easy and more flexible in case of ...

Thanks for your help.

[davsclaus]

And just to be sure, you included your DocrouterBranch.xsd file in the root of the JAR which contained your code. eg so the file was in the root of this bundles classpath?

eg its not included in another bundle?

Its a bit odd as you are using Spring's Resource API which spring-dm ought to be load from the classpath if its in the same bundle as where the spring xml file is.

[edebar]

Indeed, it is included in the root of this bundle, and nowhere else.

I confirm that was not the usual way of doing. I'm starting with all that stuff ...

Thanks for helping me !