camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Freeman Fang <freeman.f...@gmail.com>
Subject Re: [DISCUSS] Extract camel-validator from camel-core
Date Mon, 14 Nov 2011 06:17:08 GMT
Yeah, pax-url absolutely is appropriate here.

Freeman
On 2011-11-13, at 上午10:07, Raul Kripalani wrote:

> Hi,
>
> Since we are talking OSGi, this looks like an appropriate use case for
> the PAX URL classpath protocol. It provides means to lookup resources
> in any other deployed bundle, either by specifying its symbolic name
> or by performing a container-wide search.
>
> It worked like a charm for me with a use case that involved Facelets
> and loading taglibs from other bundles under Karaf.
>
> -- Raul.
>
> On 13 Nov 2011, at 00:02, "Christian Müller"
> <christian.mueller@gmail.com> wrote:
>
>> We found another library/dependency which JB can bundle... :-) I will
>> provide a patch for it later...
>> I discussed this with JB that this should of cure also work in OSGI  
>> in
>> different scenarios:
>> 1) the XSD is packaged together with the route in an OSGI bundle
>> 2) the XSD is packages in another OSGI bundle (because it is used in
>> multiple different OSGI bundles)
>> 3) the XSD is located somewhere in the file system
>> 4) the XSD is available somewhere over http
>>
>> All this should be possible. For 2), the user may have to use  
>> fragment
>> bundles or "require bundle". I will work on it later...
>>
>> Best,
>> Christian

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com










Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message