t; >>
> >> context.getRouteDefinition("i4ip-order-publish-route").advic
> >> eWith(context,
> >> new AdviceWithRouteBuilder() {
> >> @Override
> >> public void configure() throws Exception {
&g
quot;).after().to("mock:out");
>> }
>> });
>>
>> Also I am drawing the same conclusion about the XML only approach. Could
>> you kind enough to post and example to how to bootstrap the Java DSL from
>> the Blueprint XML
replaceFromWith("direct:in");
>> weaveById("publishedMessage").after().to("mock:out");
>> }
>> });
>>
>> Also I am drawing the same conclusion about the XML only approach. Could
>> you kind enough to post and example to how to bootstrap the Java DSL from
>> the Blueprint XML.
>>
>> Thanks for your help. I will try putting it in a new project and see if
>> that
>> was the problem. In a single xml file.
>>
>> O.
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.
>> com/org-osgi-service-blueprint-container-ComponentDefinition
>> Exception-Unable-to-validate-xml-tp5787642p5787758.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
ut the XML only approach. Could
> you kind enough to post and example to how to bootstrap the Java DSL from
> the Blueprint XML.
>
> Thanks for your help. I will try putting it in a new project and see if
> that
> was the problem. In a single xml file.
>
> O.
>
>
>
ntext:
http://camel.465427.n5.nabble.com/org-osgi-service-blueprint-container-ComponentDefinitionException-Unable-to-validate-xml-tp5787642p5787758.html
Sent from the Camel - Users mailing list archive at Nabble.com.
nt(1);
>
> context.start();
> template.sendBody("direct:in", BODY);
>
> assertMockEndpointsSatisfied();
> assertEquals(BODY, mockOut.getExchanges().get(0).getIn().getBody());
>
> }
>
> On Mon, Sep 19, 2016 at 5:31 AM, owain
> wrote:
>
>
ad,
>
> Thank you for your response. Yes the default property in
> cm:default-properties is over-ridden in the .cfg loaded in
> loadConfigAdminConfigurationFile(). I was then logging {{foo}} in the
> route.
>
> All of this appears to be working correctly.
>
> I took y
do with properties and I
still get an "unable to validate xml" and test still passing.
It is a bit infuriating since the route is now so simple and one would have
hoped the xml validation would have chucked out some more info on the error.
The xml validates correctly in IntelliJ IDEA.
P
can run the test and it passes but in the log
>> I get:
>>
>> 2016-09-15 11:10:40,542 [int Extender: 2] ERROR BlueprintContainerImpl
>> - Unable to start blueprint container for bundle
>> i4ip-order/1.0.0.SNAPSHOT
>> org.osgi.service.blueprint.container.ComponentDefinitionException:
>
nable to start blueprint container for bundle
> i4ip-order/1.0.0.SNAPSHOT
> org.osgi.service.blueprint.container.ComponentDefinitionException: Unable
> to validate xml
> at org.apache.aries.blueprint.parser.Parser.validate(Parser.
> java:317)[org.apache.aries.blueprint.core-1.4.4.ja
.SNAPSHOT
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to
validate xml
at org.apache.aries.blueprint.parser.Parser.validate(Parser.java:317)[org.apac
he.aries.blueprint.core-1.4.4.jar:1.4.4]
at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun
exception, all my functions can be done in Camel nicely without
> messing with CXF.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736662.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
information to build the InvalidPayloadException without triggering
this new exception, all my functions can be done in Camel nicely without
messing with CXF.
--
View this message in context:
http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736662.html
Sent from the Camel - Users mailing
Camel]
[mailto:ml-node+s465427n5736622...@n5.nabble.com]
Sent: Thursday, August 1, 2013 2:29 AM
To: bocamel
Subject: Re: Validate Xml
Hi
I think there is 2 other CXF options you can use to turn of exception
message and/or stacktraces in the response message. They are turned
off by default to
etty.http.HttpParser.parseAvailable(HttpParser.java:240)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at
> org.eclipse.jetty.io.nio
nnection$RequestHandler.content(AbstractHttpConnection.java:998)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
> at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
&g
fault message.
If that is the case, any CXF out fault interceptor probably would not get
control anyway. Any suggestion?
Thanks!
From: Raul Kripalani [via Camel]
[mailto:ml-node+s465427n5736589...@n5.nabble.com]
Sent: Wednesday, July 31, 2013 1:37 PM
To: bocamel
Subject: Re: Validate Xml
java:998)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:856)
> at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
> at
>
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
>
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at
>
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
> at
>
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
>
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:722)
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736587.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:722)
--
View this message in context:
http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736587.html
Sent from the Camel
ian,
>
> Do you have some examples handy for how to use CXF to validate a PAYLOAD
> request?
>
> Thanks!
> John
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736583.html
> Sent from the Camel
Hi Christian,
Do you have some examples handy for how to use CXF to validate a PAYLOAD
request?
Thanks!
John
--
View this message in context:
http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736583.html
Sent from the Camel - Users mailing list archive at Nabble.com.
nto CxfPayload class, which might
> assume that the content must be XML.
>
>
>
> Thanks!
>
> John
>
> From: Raul Kripalani [via Camel] [mailto:
> ml-node+s465427n5736507...@n5.nabble.com]
> Sent: Tuesday, July 30, 2013 3:42 PM
> To: bocamel
> Subject: Re: Valid
the
> HTTP
> code to 400.
>
> If there is a better way to do this, I would like to know.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736492.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
+s465427n5736507...@n5.nabble.com]
Sent: Tuesday, July 30, 2013 3:42 PM
To: bocamel
Subject: Re: Validate Xml
Try converting the body to a Document.class explicitly (before calling the
validator) and handling the InvalidPayloadException.
For example:
onException
.
>
> If there is a better way to do this, I would like to know.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736492.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
an builds a SOAP fault message and sets the HTTP
code to 400.
If there is a better way to do this, I would like to know.
--
View this message in context:
http://camel.465427.n5.nabble.com/Validate-Xml-tp472122p5736492.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I think you can do it with camel validation component.
You can find more information about how to use it here[1]
[1] http://camel.apache.org/validation.html
Willem
jpcook wrote:
Hi,
I noticed you had a validation component for validating xml against xsds.
But I wondered if there was a ni
in context:
http://old.nabble.com/Validate-Xml-tp27276794p27276794.html
Sent from the Camel - Users mailing list archive at Nabble.com.
28 matches
Mail list logo
