Camel 2.8.2. Any help would be greatly appreciated.
>
> Thanks,
> Dave
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Extract-camel-validator-from-camel-core-tp4986357p5489891.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
dator in a Camel route in a
different bundle.
I'm using Camel 2.8.2. Any help would be greatly appreciated.
Thanks,
Dave
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-Extract-camel-validator-from-camel-core-tp4986357p5489891.html
Sent from the Camel Developme
Hi,
the more I think of this, the more I prefer a simple solution with
just a catalog resource resolver (through xml-resolver).
That's because it's (to my knowledge) a de facto standard to map
public and system ids and in this case it would be a perfect
opportunity to follow the principle of "conv
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 specif
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
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 b
Let's discuss this later by having breakfest together and afterwards we
will share our opinions here...
Sent from a mobile device
Hi Christian,
it sounds good, but the question is: how to load/look up the XSD in the
validator component ?
I mean, in Karaf, to validate a feature XML, we use the following code:
SchemaFactory factory =
SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
// root
Does Apache XML Resolver work with OSGi ?
But seems like a good idea so a +1 from me.
On Sat, Nov 12, 2011 at 7:02 AM, Christian Müller
wrote:
> Hello all!
>
> With [1], we add the functionality to Camel to validate XML files against
> nested schema files with the camel validator component. So f
Hello all!
With [1], we add the functionality to Camel to validate XML files against
nested schema files with the camel validator component. So far so good...
We couldn't do this in the best possible way without to introduce an
additional dependency to xml-resolver. The current implementation doe
10 matches
Mail list logo
