[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015307#comment-13015307
]
Gert Vanthienen commented on CAMEL-3763:
In order to fully leverage the
[
https://issues.apache.org/jira/browse/CAMEL-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015335#comment-13015335
]
Joshua Watkins commented on CAMEL-3824:
---
Sorry, I should have posted the producer
[
https://issues.apache.org/jira/browse/CAMEL-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015389#comment-13015389
]
Hadrian Zbarcea commented on CAMEL-3830:
As the number of dependencies can quickly
Yay, just what I needed :). I will start making changes to the other components.
Thanks,
Hadrian
On Apr 1, 2011, at 3:03 PM, Stan Lewis wrote:
+1 that looks way better...
On Thu, Mar 31, 2011 at 10:10 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
I made to changes from the original
Hi,
There are a few dependencies that are used with camel that we don't support as
mentioned on the SMX mailing list and CAMEL-3830.
I think we should support at least:
* slf4j 1.6.x
* jetty 7.3.1.v20110307
* cxf 2.4.x
* (if you know of other dependencies that should be upgraded, please
+1
Regards
JB
On 04/04/2011 04:20 PM, Hadrian Zbarcea wrote:
Hi,
There are a few dependencies that are used with camel that we don't support as
mentioned on the SMX mailing list and CAMEL-3830.
I think we should support at least:
* slf4j 1.6.x
* jetty 7.3.1.v20110307
* cxf 2.4.x
* (if you
What do we do with the karaf feature file?
The camel-cxf features are not suitable for cxf 2.4. On the other hand
CXF 2.4 brings it´s own feature file. So if the cxf feature is installed
camel-cxf can just be installed.
Any ideas?
Christian
Am 04.04.2011 16:20, schrieb Hadrian Zbarcea:
Yes we need a new camel release to be compatible with cxf 2.4. The
question is only if we can also do something with the feature file to
make it compatible with cxf 2.3 and 2.4.
Christian
Am 04.04.2011 16:24, schrieb Jean-Baptiste Onofré:
Hi Christian,
I guess that the camel-cxf POM should
Christian, can we get some sort of commitment from the cxf community that cxf
2.4.x will be backwards compatible with 2.3.x? I saw that you made the
following change on trunk:
org.apache.cxf.*;version=[2.3.2,2.5)
Are there any other dependencies we need to upgrade?
Hadrian
On Apr 4, 2011, at
OK,
sorry I have misunderstood you.
Sure, we can review the camel features descriptor to align camel and cxf
ones. It makes sense to reference the CXF features in camel-cxf one.
Regards
JB
On 04/04/2011 04:32 PM, Christian Schneider wrote:
Yes we need a new camel release to be compatible
2.4.3 will need some api changes on in/out interceptors.
Otherwise an upgrade is pretty easy.
Also 2.4 is going to contain plenty more BP stuff.
That features file just started working 3 days ago.
On Apr 4, 2011, at 8:38 AM, Hadrian Zbarcea wrote:
Christian, can we get some sort of commitment
Oh, correction, the interceptors changes came in 2.3.x...
/je
On Apr 4, 2011, at 8:38 AM, Hadrian Zbarcea wrote:
Christian, can we get some sort of commitment from the cxf community that cxf
2.4.x will be backwards compatible with 2.3.x? I saw that you made the
following change on trunk:
We need to make sure camel-cxf works with both 2.3.x and 2.4.x, correct?
Hadrian
On Apr 4, 2011, at 10:49 AM, Johan Edstrom wrote:
2.4.3 will need some api changes on in/out interceptors.
Otherwise an upgrade is pretty easy.
Also 2.4 is going to contain plenty more BP stuff.
That features
If cxf:endpoint is tested as is against 2.4.0-SNAPSHOT, i.e the spring code, we
should be home-free.
On Apr 4, 2011, at 8:56 AM, Hadrian Zbarcea wrote:
We need to make sure camel-cxf works with both 2.3.x and 2.4.x, correct?
Hadrian
On Apr 4, 2011, at 10:49 AM, Johan Edstrom wrote:
I did not have to make code changes to make it compile against cxf 2.4.
If got one test error and one test failure. Dan Kulp already looked into
these and said that they should be rather problems in the tests than
with the
code. We will do more tests as soon as the snapshots are built.
[
https://issues.apache.org/jira/browse/CAMEL-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015458#comment-13015458
]
Marco Crivellaro commented on CAMEL-3795:
-
I am still experiencing the same issue
This probably means that we can release camel-2.7.1 before cxf-2.4.0 is out.
Maybe you guys can make the cxf community aware of the camel changes (well, I
guess I could do that too), so that they have a chance to test.
I will create a branch off of the camel-2.7.0 tag, start applying patches
Major +1 on this!
On Apr 4, 2011, at 10:49 AM, Hadrian Zbarcea wrote:
This probably means that we can release camel-2.7.1 before cxf-2.4.0 is out.
Maybe you guys can make the cxf community aware of the camel changes (well, I
guess I could do that too), so that they have a chance to test.
SmppProducer sends incorrect data_coding parameter
--
Key: CAMEL-3834
URL: https://issues.apache.org/jira/browse/CAMEL-3834
Project: Camel
Issue Type: Bug
Components: camel-smpp
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heath Kesler updated CAMEL-3781:
Attachment: patch-3781.diff
added a new option for disableExpiration per the suggestion in the
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heath Kesler updated CAMEL-3781:
Attachment: patch-3781.diff
attaching with ASF
Add option to disable expiration on JMS component
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heath Kesler updated CAMEL-3781:
Attachment: (was: patch-3781.diff)
Add option to disable expiration on JMS component
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015704#comment-13015704
]
Hadrian Zbarcea commented on CAMEL-3781:
Heath, what about using the
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015709#comment-13015709
]
Heath Kesler commented on CAMEL-3781:
-
Hadrian,
Thanks for looking at it and for your
On 4/4/11 10:25 PM, Christian Schneider wrote:
What do we do with the karaf feature file?
The camel-cxf features are not suitable for cxf 2.4. On the other hand
CXF 2.4 brings it´s own feature file. So if the cxf feature is installed
camel-cxf can just be installed.
Any ideas?
There are some
On 4/4/11 10:20 PM, Hadrian Zbarcea wrote:
Hi,
There are a few dependencies that are used with camel that we don't support as
mentioned on the SMX mailing list and CAMEL-3830.
I think we should support at least:
* slf4j 1.6.x
Is there any plan to upgrade Karaf with slf4j 1.6.x ?
* jetty
It could be no easy to support CXF 2.3.x and CXF 2.4.x at same time by
reference the CXF feature in apache-camel feature. You have to deal with
the repo reference url and CXF vesion in the apache-camel feature.
In most case, the container which provides the runtime of camel and cxf
does the
What's the support plan of Camel 2.7.1 ?
Will we release Camel 2.7.2 some days later or just move on to Camel 2.8.x ?
On 4/5/11 12:49 AM, Hadrian Zbarcea wrote:
This probably means that we can release camel-2.7.1 before cxf-2.4.0 is out.
Maybe you guys can make the cxf community aware of the
[
https://issues.apache.org/jira/browse/CAMEL-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day reassigned CAMEL-3539:
Assignee: Ben O'Day
Add route endpoint to let end users send messages to other routes using route
Development for 2.8.0 should continue without any change. Until then we cannot
support cxf 2.4, slf4j, amq 5.5, etc. This patch release will provide it.
If/when there will be a 2.7.2, too early to tell. We know there are users who
still use older versions of camel. Ideally we should have patch
We don't need to support cxf 2.3.x and 2.4.x at the same time. The current
camel-2.7.0 release does not support cxf 2.4.x at all now, because of the
following line in camel.osgi.import.defaults:
org.apache.cxf.*;version=[2.3.2,2.4)
Hadrian
On Apr 4, 2011, at 10:00 PM, Willem Jiang wrote:
Actually, were is the difficulty in supporting both?
Asking as a complete ignoramus that has swapped quite a few projects,
if we follow CXF conventions and respect bus creation I do not see where it'll
be that hard?
On Apr 4, 2011, at 9:09 PM, Hadrian Zbarcea wrote:
We don't need to
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015738#comment-13015738
]
Hadrian Zbarcea commented on CAMEL-3781:
Heath, I am not disagreeing with you. I
All the better. You're the experts.
(And now I saw that I misspelled 'proposal').
Hadrian
On Apr 4, 2011, at 11:14 PM, Johan Edstrom wrote:
Actually, were is the difficulty in supporting both?
Asking as a complete ignoramus that has swapped quite a few projects,
if we follow CXF conventions
It also looks like the camel-dns component has some issues with my machine :(
Hadrian
On Apr 4, 2011, at 11:14 PM, Johan Edstrom wrote:
Actually, were is the difficulty in supporting both?
Asking as a complete ignoramus that has swapped quite a few projects,
if we follow CXF conventions
Testing wise?
I think I disabled all tests that would require a recursive resolver.
On Apr 4, 2011, at 9:33 PM, Hadrian Zbarcea wrote:
It also looks like the camel-dns component has some issues with my machine :(
Hadrian
On Apr 4, 2011, at 11:14 PM, Johan Edstrom wrote:
Actually,
Yes, a bunch of tests fail trying to figure out what 'localhost' means :).
Caused by: java.net.UnknownHostException: unknown host
at org.xbill.DNS.Address.lookupHostName(Address.java:239)
at org.xbill.DNS.Address.getByName(Address.java:264)
at
[
https://issues.apache.org/jira/browse/CAMEL-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015760#comment-13015760
]
Bryan Keller commented on CAMEL-3781:
-
Message expiration is something handled by the
camel-cache osgi metadata isn't correct
---
Key: CAMEL-3835
URL: https://issues.apache.org/jira/browse/CAMEL-3835
Project: Camel
Issue Type: Bug
Reporter: Freeman Fang
1. export package
[
https://issues.apache.org/jira/browse/CAMEL-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-3835:
Component/s: camel-cache
camel-cache osgi metadata isn't correct
[
https://issues.apache.org/jira/browse/CAMEL-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-3835:
Attachment: CAMEL-3835.patch
camel-cache osgi metadata isn't correct
41 matches
Mail list logo
