Hi Claus,
Thanks for the ticket.
You were faster than me !
metatech
Claus Ibsen-2 wrote
> I logged a ticket
> https://issues.apache.org/jira/browse/CAMEL-9116
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-SJMS-cannot-convert-Jetty-objects-to-JMS-
asyncRoute"/>
It would be nice if the Camel-SJMS would handle this case, as the Camel-JMS
component does.
Thanks in advance,
metatech
Caused by: org.apache.camel.component.sjms.jms.IllegalHeaderException:
Failed to set the header CamelHttpServletRequest h
Hello,
After some more thinking, I found another solution : defining an alternate
wildcard in the CXF blueprint support.
I created a ticket in the CXF with the patch :
https://issues.apache.org/jira/browse/CXF-6567
Best regards,
metatech
--
View this message in context:
http://camel.465427
legant solution, but it is less ugly to relax validation for
a single attribute than for the entire XML.
Regards,
metatech
---
blueprint-core/src/main/resources/org/apache/aries/blueprint/blueprint.xsd
2015-08-27 10:38:55.329361900 +0200
+++
blueprint-core/src/main/resources/org/ap
Hello,
My understanding is that there is no simple solution to this problem.
I propose I will create a JIRA ticket so that anyone can investigate it
further later.
Best regards,
metatech
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Transport-works-within
?
Also, the schema http://cxf.apache.org/schemas/blueprint/camel.xsd is not
published on this URL, is this normal ?
Thanks in advance,
Best regards,
metatech
[1]
2015-08-11 17:10:16,014 [int Extender: 1] ERROR BlueprintContainerImpl
- Unable to st
d add a "jaxb.properties" next to each "jaxb.index".
metatech
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-on-deploying-Camel-on-Weblogic-12c-Name-Collision-tp5720837p5722613.html
Sent from the Camel - Users mailing list archive at Nabble.com.
p.
Go to package org/apache/camel/spring
Drag and drop file "jaxb.properties" next to "jaxb.index" already present in
archive.
Go to package org/apache/camel/osgi
Drag and drop file "jaxb.properties" next to "jaxb.index" already present in
archive.
Rebuild applica
art-up, but they are reliable for the next start-ups. Only a programmatic
call in an OSGi activator for the application can wait for the camel-spring
bundle be fully activated, but it is a bit cumbersome.
Regards,
metatech
Start-level can't really be trusted, especially if you use blueprin
he only solution I can think of is that the bundle cache should be built in
a first phase, then the bundle are started in a second phase.
Regards,
metatech
metatech wrote
>
> However, the Camel initialization is not finished yet, it is performed in
> the "addingBundle" m
:
Broker-side :
Regards,
metatech
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-documentation-update-tp5148751p5151779.html
Sent from the Camel - Users mailing list archive at Nabble.com.
OSGi container, add the following line
before the CamelContext definition :
This allows any pre-configured instance of the ActiveMQComponent deployed in
the container to take precedence on the default ActiveMQComponent.
===
Thanks in advance,
metatech
--
View this messa
ragment.MF
Hope this helps,
Regards,
metatech
On Mon, Jan 9, 2012 at 9:30 AM, metatech <metatechbe@> wrote:
> Hi Claus,
>
> I tried the "depends-on" solution but unfortunately the camel context is
> started asynchronously after the Spring context is initialized.
> T
pendencies between camel
contexts ?
Thanks,
metatech
Claus Ibsen-2 wrote
>
> In Spring XML you should be able to use the depends-on attribute to
> say that your bean depends on Camel.
>
>
>
>
>
>
>
>
--
View this message in context:
http://camel.465
l 60 and all Camel
bundles are configured at start-level 50, therefore it shows that the fix
below might reduce the window of race condition, but will not guarantee that
it does not happen anymore :
https://issues.apache.org/jira/browse/SMX4-744
Should I create a bug in JIRA ?
Regards,
metatech
--
Gert Vanthienen wrote
>
> I just raised https://issues.apache.org/jira/browse/CAMEL-4147 to keep
> track of this request.
>
Even in a Spring application in ServiceMix (4.3), this error can also occur.
This seems to be a race condition, when camel-core is not yet fully started
and an application
16 matches
Mail list logo