camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Babak Vahdat <>
Subject Re: Access XSD (Resources) in from an OSGI bundle
Date Wed, 03 Oct 2012 08:57:51 GMT
Sorry ... I missed the line of your post that says you've already tried the
2.10.1 release. That said IMHO a quick try of 2.10.2-SNAPSHOT or
2.11-SNAPSHOT would be worth it.


Babak Vahdat wrote
> Hi Patrik,
> what do you exactly mean with:
> // begin-quote
>   I checked the availability of th xsd with the following code in the same
> configure() methode of my RouteBuilder()
>   InputStream is =
> this.getClass().getClassLoader().getResourceAsStream("resources/Msg_template.xsd");
>   It works. So the resource is in the classpath.
> // end-quote
> Did you check if the returned InputStream is really *not* null as you will
> not see any exception being thrown if loading of the resource fails with
> the code above.
> Also as Christian has already mentioned the 2.9.2 release is "old" and we
> did *not* test it on JDK 7 at all (the JDK 7 support started first with
> 2.10.0). So better update to 2.10.1 if you can and see if you can still
> reproduce the problem. If yes then maybe give the snapshot of the upcoming
> 2.10.2 also a try as well containing the following fix:
> Which I think it could be relevant for your case.
> The link below explains the Maven-Repo required to include inside your POM
> or ~/.m2/settings.xml so that Maven can download 2.10.2-SNAPSHOT for you,
> assuming you make use of Maven :-)
> @Raul after looking at ResourceHelper source I don't think that dropping
> the "classpath:" prefix would make any change at all but maybe I'm
> wrong...
> Babak

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message