quickfix 1.5.2_1 bundle is on the way, we could wait for it a while.
On 6/12/12 5:44 AM, Christian Müller wrote:
$camel/platforms/karaf>mvn clean install -Pvalidate
...
[INFO] BUILD FAILURE
because we refer already to
org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.
For the camel-cdi, current we don't have the cdi container works in
OSGi,
I also checked the code of camel-cdi, it is related on Apache
detaspike, we may need some time to get it work with other cdi
container.
On Tue Jun 12 05:56:56 2012, Christian Müller wrote:
We have a similar issue for c
Karaf features validate plugin cannot load the full features which was
included. As the camel-itest-osgi can vaild the CXF related feature
works, we can revisit it after fixing the issue of validate plugin.
On 6/12/12 5:50 AM, Christian Müller wrote:
$camel/platforms/karaf>mvn clean install -P
We have a similar issue for camel-cdi. I opened a ticket for it:
https://issues.apache.org/jira/browse/CAMEL-5360
Best,
Christian
On Mon, Jun 11, 2012 at 11:50 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> $camel/platforms/karaf>mvn clean install -Pvalidate
> ...
> [WARNING] Faile
$camel/platforms/karaf>mvn clean install -Pvalidate
...
[WARNING] Failed to validate feature camel-cxf
[WARNING] No export found to match
org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.bus.
$camel/platforms/karaf>mvn clean install -Pvalidate
...
[INFO] BUILD FAILURE
because we refer already to
org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
which isn't released until now...
Best,
Christian
On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen wrote:
> On F
This does make a lot of sense to me. websocket is really a standard for
which there could be multiple implementations. Thus, the component name
really should be the implementation, not the standard. Otherwise you get
into the whole "camel-http" issue again of having multiple things that CO
This is not a new topic, but it looks like it's coming back in different
threads. Since this is is the underlying issue, I'd suggest clarifying
this first.
At the core of the issue is a call to
UnsafeUriCharactersEncoder.encode(uri) in
DefaultComponent.createEndpoint(String), that made camel
Hi Claus,
I completely agree on your proposition as we reuse pieces of code between
the different (same) camel components (jetty, websocket but also cometd) as
they increase "maintenance" costs.
Point 1) --> +1 to merge camel-jetty, camel-websocket and camel-cometd
The most important thing will
Hi
In Camel 2.10 we introduce a new component: camel-websocket.
Its currently based on Jetty, and thus requires jetty to be used.
In recent time the component was enhanced to support SSL with websocket as
well. That change brings in a lot of code that was
copied directly from the existing camel-j
10 matches
Mail list logo
