[
https://issues.apache.org/jira/browse/CAMEL-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4409.
Resolution: Fixed
Fix Version/s: (was: Future)
2.9.0
Thanks Mathieu.
[
https://issues.apache.org/jira/browse/CAMEL-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu Lalonde updated CAMEL-4409:
---
Attachment: camel-sql_keyOrderingTest_polished.patch
Here is a unit test to ensure determinis
[
https://issues.apache.org/jira/browse/CAMEL-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu Lalonde updated CAMEL-4332:
---
Affects Version/s: (was: 2.8.0)
Issue Type: Test (was: Improvement)
[
https://issues.apache.org/jira/browse/CAMEL-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mathieu Lalonde updated CAMEL-4409:
---
Issue Type: Test (was: Task)
> Add unit test to camel-sql to ensure deterministic column ord
[
https://issues.apache.org/jira/browse/CAMEL-4409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4409 started by Mathieu Lalonde.
> Add unit test to camel-sql to ensure deterministic column order
> ---
Add unit test to camel-sql to ensure deterministic column order
---
Key: CAMEL-4409
URL: https://issues.apache.org/jira/browse/CAMEL-4409
Project: Camel
Issue Type: Task
C
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096183#comment-13096183
]
Andreas Kuhtz commented on CAMEL-4408:
--
Thank you very much!!!
> Fix OSGi-exports of
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4408.
Resolution: Fixed
Thanks Andreas. The 2.8.1 branch now has the version numbers.
> Fix OSGi-exports
How about adding a warning message for invalid URIs in 2.9.0 that tells
people that such URIs will be invalid in camel 3?
Christian
Am 02.09.2011 17:57, schrieb Claus Ibsen:
Frankly people have been using Camel for 4.5 years with url's just
like that without any problems.
I think its bad judg
On Fri, Sep 2, 2011 at 6:41 AM, James Strachan wrote:
> I'm also not sure how much smaller we can really get camel-core; since
> out of the box you'd assume camel can work with JMX, beans, files &
> implement the patterns and have the model in there. Shaving off
> 20-100k doesn't seem that big a d
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096104#comment-13096104
]
Andreas Kuhtz commented on CAMEL-4408:
--
Yes, that might be the reason. I also noticed
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-4408:
--
Assignee: Claus Ibsen
> Fix OSGi-exports of camel-soap
> --
>
>
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096098#comment-13096098
]
Claus Ibsen commented on CAMEL-4408:
I could see that camel-rss, may have that as well
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096092#comment-13096092
]
Claus Ibsen commented on CAMEL-4408:
Its just a bit odd as every camel component has t
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096086#comment-13096086
]
Claus Ibsen commented on CAMEL-4408:
Yeah OSGi has its moments.
camel-soap have been
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Kuhtz updated CAMEL-4408:
-
Issue Type: Improvement (was: Bug)
> Fix OSGi-exports of camel-soap
> --
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096073#comment-13096073
]
Andreas Kuhtz commented on CAMEL-4408:
--
@Claus
The trunk (2.9-SNAPSHOT, check the jar
Frankly people have been using Camel for 4.5 years with url's just
like that without any problems.
I think its bad judgment to create JIRA tickets with "critical" bugs
and mark them as fix for 2.8.1 etc,
as if the sky is falling down on people.
Instead as you write somewhere, it could be put as a
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096046#comment-13096046
]
Claus Ibsen commented on CAMEL-4408:
Hmm the trunk looks like
{code}
jav
I just build it with the latest trunk on windows with maven-2.2.1 and I see
the correct version numbers of the two exports, so I guess it's not a
windows problem.
I've seen that the maven-bundle-plugin has changed from 2.3.4 (on
2.8.1-SNAPSHOT) to 2.3.5 on trunk on 31.08.2011 but my previous build
Okay I got a bit upset here.
But I cant understand why you want to turn the blind eye to the fact
you introduced a leak, despite being careful.
What is the problem with that class being a service, which then have
callbacks (start/stop) where it can ensure
the cache is cleared when stopping.
What
I have started the "cxf:bean:B" in the cxf.xml file as
Is the above is the only way i can start or is there any way?
Now i am getting error at cxf:bean:B endpoint unmarshalling error. I have
correct object in the exchange from the cxf:bean:A. Any idea on this?
Thanks,
Santosh
On Fri, Sep 2, 2011 at 4:50 PM, Hadrian Zbarcea wrote:
> Moving to dev@.
>
> -1. Please revert your change and let's fix it properly. In the future
> please do not revert my changes without discussing that with me, even if
> you believe it's the right thing to do. The PropertyEditoryTypeConverter
[
https://issues.apache.org/jira/browse/CAMEL-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4396.
Resolution: Fixed
Fix Version/s: 2.8.1
Thanks for the 3rd patch. I have applied it to trunk.
Moving to dev@.
-1. Please revert your change and let's fix it properly. In the future
please do not revert my changes without discussing that with me, even if
you believe it's the right thing to do. The PropertyEditoryTypeConverter
and being a Service and leaks are two separate issues.
Hadri
In my current build from trunk I can reproduce the problem. I also do
not see version numbers on two of the exports.
Is this perhaps only on windows builds?
Christian
Am 02.09.2011 16:17, schrieb Willem Jiang:
I just checked the camel-soap bundle which I just built from trunk today.
org.a
Hi Willem,
Hh you are right, just checked my 2.9-SNAPSHOT and it's indeed in there.
Export-Package: org.apache.camel.dataformat.soap;uses:="javax.jws,org.ap
ache.camel.component.bean,org.apache.camel,org.apache.camel.converter.j
axb,org.apache.camel.dataformat.soap.name,org.slf4j,javax.xml.
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-4407.
-
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.1
commit fix
http://svn.apac
I just checked the camel-soap bundle which I just built from trunk today.
org.apache.camel.dataformat.soap {version=2.9.0.SNAPSHOT}
org.apache.camel.dataformat.soap.name {version=2.9.0.SNAPSHOT}
org.xmlsoap.schemas.soap.envelope {version=2.9.0.SNAPSHOT}
They look good :)
On 9/2/1
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Kuhtz updated CAMEL-4408:
-
Attachment: camel-4408.diff
Patch for 2.8.1-SNAPSHOT
> Fix OSGi-exports of camel-soap
>
First you route could be like this,
from(cxf:bean:A).to(cxf:bean:B).
from part is CXF server, to part is CXF client.
This route just redirect the request from A to B.
Now if you want the SOAP UI get the response, you need to start a Web
service for the CXF client B to access.
On 9/2/11 9:41
Fix OSGi-exports of camel-soap
--
Key: CAMEL-4408
URL: https://issues.apache.org/jira/browse/CAMEL-4408
Project: Camel
Issue Type: Bug
Components: camel-soap
Affects Versions: 2.8.0
Repor
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095999#comment-13095999
]
Freeman Fang commented on CAMEL-4407:
-
Hi Claus,
Thanks for reminder.
Yeah, we need u
Still not sure how to answer, but let me try. The issue(s) I created and
partially fixed are related to passing invalid URIs to Camel to create
endpoints. I could understand the questions in the following ways:
1. I don't see any problem.
2. I see a problem, but:
a. No need to fix it because it
[
https://issues.apache.org/jira/browse/CAMEL-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
metatech reopened CAMEL-4396:
-
Estimated Complexity: Novice (was: Moderate)
New patch is provided.
> XML validation errors should be n
[
https://issues.apache.org/jira/browse/CAMEL-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
metatech updated CAMEL-4396:
Attachment: camel_xml_exceptions3.patch
The 2 previous patches cover the case where the XSLT document itsel
Thanks Willem for your quick responses.
Then this case
1) routeEndPoint is listening at 9004 , this will consume the message from
soapui.
2) serviceEndPoint has to listen at 9000, this will invoke the actual
method.
Means for every web sevice with WSDL , there should be two port open inorder
to
Hi Andi,
yes I think they should.
Can you open an issue?
Christian
Am 02.09.2011 14:43, schrieb Andreas Kuhtz:
Hi,
I've a question regarding the OSGi exports of camel-soap. If I run exports
in karaf I get the following output.
karaf@localhost> exports 135
ID Packages
135 org.apach
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095970#comment-13095970
]
Ashwin Karpe edited comment on CAMEL-4371 at 9/2/11 1:32 PM:
-
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095970#comment-13095970
]
Ashwin Karpe commented on CAMEL-4371:
-
@Hadrian, @Claus,
I looked over the AdviceWith
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095955#comment-13095955
]
Ashwin Karpe edited comment on CAMEL-4371 at 9/2/11 1:11 PM:
-
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095955#comment-13095955
]
Ashwin Karpe commented on CAMEL-4371:
-
Hi Hadrian,
I see your point with mutating rou
You need to make sure there is a web service which listen to address of
serviceEndpoint.
On Fri Sep 2 20:52:05 2011, skompelly wrote:
yeah i sent the request to routerEndpoint,
its consumed and serviceEndpoint is throwing the error message as
"could not send message" in soapui
--
View thi
Hi,
I've a question regarding the OSGi exports of camel-soap. If I run exports
in karaf I get the following output.
karaf@localhost> exports 135
ID Packages
135 org.apache.camel.dataformat.soap; version="0.0.0"
135 org.apache.camel.dataformat.soap.name; version="0.0.0"
135 org.xmlsoa
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095953#comment-13095953
]
Claus Ibsen commented on CAMEL-4407:
Groovy is osgi out of the box now. We use groovy
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-4407:
Description:
the camel-script feature looks like
camel-core
mvn:org.apache.servic
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4407 started by Freeman Fang.
> camel-script feature should ship script implementation bundles like
> groovy/javascript/ruby
>
yeah i sent the request to routerEndpoint,
its consumed and serviceEndpoint is throwing the error message as
"could not send message" in soapui
--
View this message in context:
http://camel.465427.n5.nabble.com/cxf-bean-producer-consumer-tp4761986p4762239.html
Sent from the Camel Development
camel-script feature should ship script implementation bundles like
groovy/javascript/ruby
--
Key: CAMEL-4407
URL: https://issues.apache.org/jira/browse/CAMEL-4407
On Thu, Sep 1, 2011 at 3:16 AM, Hadrian Zbarcea wrote:
> Yes, I agree with that, reason why Registries that use caches *are* and
> should stay as Services. The PropertyEditorTypeConverter in particular
> doesn't need to be a Service, but the EndpointRegisty, ConsumerCache and
> ProducerCache shoul
It looks like you should send the request to routerEndpoint address
"http://localhost:9003/CamelContext/RouterPort";
On 9/2/11 8:19 PM, skompelly wrote:
Okay thanks,
How to invoke a webservice method (wsdl first) from the soapui?
Web service is published at 9004 as below, able to view the
You make my day Hadrian :)
Thanks ;)
Regards
JB
On 09/02/2011 02:31 PM, Hadrian Zbarcea wrote:
I will kick-off the release builds later today or tomorrow.
Cheers,
Hadrian
On 09/02/2011 07:02 AM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen
wrote:
On Fri, Sep 2, 2011 at
On Fri, Sep 2, 2011 at 2:20 PM, Hadrian Zbarcea wrote:
> Not sure I understand your request, please clarify.
>
Can you post on @dev what you see as problems with the endpoint uris.
You create a number of tickets and mark then as critical bugs, without
much details. People
have been using this wit
I will kick-off the release builds later today or tomorrow.
Cheers,
Hadrian
On 09/02/2011 07:02 AM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré wrote:
Hi guys,
I would like to release SMX 4.4 soon. For now,
Not sure I understand your request, please clarify.
Hadrian
On 09/02/2011 01:59 AM, Claus Ibsen wrote:
This seems over reacting.
Can you post on @dev why you suddenly change all the working unit
tests like this?
Camel end users have been using these components without problems, and
they are e
Okay thanks,
How to invoke a webservice method (wsdl first) from the soapui?
Web service is published at 9004 as below, able to view the wsdl in browser.
Not able to invoke the method exposed. For this do i have to do anything. i
was checking this example where i have one port for routerEndpoin
Great,
thanks, I'm updating in SMX trunk during this time to check the
examples, etc.
Regards
JB
On 09/02/2011 01:02 PM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré wrote:
Hi guys,
I would like to release S
Hi,
You misunderstand what the To means, the to(SERVICE_ENDPOINT_URI)
means it will connect to an external server which is listening on port
9000, this port isn't started by camel router, it should be some
external server already there.
Freeman
On 2011-9-2, at 下午7:19, skompelly wrote:
Hi
I am tring to invoke a webserive method from soapui
1) WSDL first approach , generated all the files using maven goal is
wsdl2java
2) In the route i have below code
ROUTER_ENDPOINT_URI = "cxf://" + ROUTER_ADDRESS + "?" + SERVICE_CLASS + "&"
+ WSDL_LOCATION + "&" + SERVICE_NAME + "&"
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen wrote:
> On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré
> wrote:
>> Hi guys,
>>
>> I would like to release SMX 4.4 soon. For now, the target is Camel 2.8.0. We
>> still have some time in SMX to update to Camel 2.8.1, but I think we
>> shouldn't
On 1 September 2011 02:01, Hadrian Zbarcea wrote:
> Personally, I don't think we need a big jar. My understanding is that
> Christian is looking for ways to *improve* modularity and reduce
> dependencies.
But he was suggesting making camel-core bigger & adding in more
dependencies by shoving came
[
https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CAMEL-4406:
Fix Version/s: 2.8.1
> use cxf feature from apache-cxf-features.xml
> -
[
https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095900#comment-13095900
]
Freeman Fang commented on CAMEL-4406:
-
back port to 2.8.x branch
http://svn.apache.org
[
https://issues.apache.org/jira/browse/CAMEL-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4252:
---
Fix Version/s: 2.8.1
> camel-ftp - Using tempFileName option should use the separator option to
> al
[
https://issues.apache.org/jira/browse/CAMEL-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4246:
---
Fix Version/s: 2.8.1
> TraceInterceptor does not work correctly for AsyncProcessing
> ---
[
https://issues.apache.org/jira/browse/CAMEL-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4269:
---
Fix Version/s: 2.8.1
> Connection to sftp server occasionally don't want to come back
> -
[
https://issues.apache.org/jira/browse/CAMEL-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4274:
---
Fix Version/s: 2.8.1
> MDCUnitOfWork behaviour incorrect with nested routes
> ---
[
https://issues.apache.org/jira/browse/CAMEL-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4265:
---
Fix Version/s: 2.8.1
> Fail to close stream in DefaultPropertiesResolver
> --
[
https://issues.apache.org/jira/browse/CAMEL-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4287:
---
Fix Version/s: 2.8.1
> camel-aws won't build offline
> -
>
>
[
https://issues.apache.org/jira/browse/CAMEL-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4293:
---
Fix Version/s: 2.8.1
> @Bean method name is ignored
>
>
>
[
https://issues.apache.org/jira/browse/CAMEL-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4305:
---
Fix Version/s: 2.8.1
> xslt component - Cannot load xslt file from file system
>
[
https://issues.apache.org/jira/browse/CAMEL-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4254:
---
Fix Version/s: 2.8.1
> Missing setter or constructor-argument for elementNameStrategyRef in
> SoapJa
[
https://issues.apache.org/jira/browse/CAMEL-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4311:
---
Fix Version/s: 2.8.1
> Camel Bindy Parser One to Many KvP Unmarshall Issue
>
[
https://issues.apache.org/jira/browse/CAMEL-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095886#comment-13095886
]
Claus Ibsen commented on CAMEL-4318:
Cannot backport to 2.8.1 as it has API changes.
[
https://issues.apache.org/jira/browse/CAMEL-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4319:
---
Fix Version/s: 2.8.1
> Example feature: wrong spring version
> -
[
https://issues.apache.org/jira/browse/CAMEL-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4325.
-
Resolution: Fixed
Applied patch with unit test into the trunk.
> Wrong exception uri when an HTT
[
https://issues.apache.org/jira/browse/CAMEL-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-4324.
-
Resolution: Fixed
Applied patch into trunk.
> Response body lost when an HTTP error code is retu
[
https://issues.apache.org/jira/browse/CAMEL-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4352:
---
Fix Version/s: 2.8.1
> Ftp consumer using done file should cater for if stepwise has been enabled,
>
[
https://issues.apache.org/jira/browse/CAMEL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-3510.
-
Resolution: Fixed
Fix Version/s: (was: Future)
Applied patch into trunk.
Now, you can
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> I would like to release SMX 4.4 soon. For now, the target is Camel 2.8.0. We
> still have some time in SMX to update to Camel 2.8.1, but I think we
> shouldn't wait too long ;)
>
I am backporting the fixes now. I would li
[
https://issues.apache.org/jira/browse/CAMEL-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4354:
---
Fix Version/s: 2.8.1
> header added using an EventNotifier is not present at AggregationStrategy for
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095877#comment-13095877
]
Willem Jiang commented on CAMEL-4363:
-
Current camel-jetty component just binds one se
[
https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095873#comment-13095873
]
Andreas Kuhtz commented on CAMEL-4374:
--
Just noticed that the patch will not work for
Hi guys,
I would like to release SMX 4.4 soon. For now, the target is Camel
2.8.0. We still have some time in SMX to update to Camel 2.8.1, but I
think we shouldn't wait too long ;)
Regards
JB
On 09/02/2011 10:00 AM, Claus Ibsen wrote:
On Tue, Aug 30, 2011 at 3:29 PM, Hadrian Zbarcea wrote
On Tue, Aug 30, 2011 at 3:29 PM, Hadrian Zbarcea wrote:
> I will and get ready for the 2.8.1 release.
> Hadrian
>
Did you have a change to do this?
A new ESB and AMQ releases is on the way and they would like to use
2.8.1 with the needed bug fixes.
Would be great to, yeah if possible, lets take
[
https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-4406.
-
Resolution: Fixed
Fix Version/s: 2.9.0
commit fix
http://svn.apache.org/viewvc?rev=1164383
Hi Claus,
it is great that you wear the community hat. This is a needed balance to
my refactorings that are of course rather architecture focused.
The good thing is that thanks to your comments many changes are now more
compatible than I originally did them.
So of course the big question is w
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095823#comment-13095823
]
Sergey Zhemzhitsky commented on CAMEL-4371:
---
Hi Claus,
Advice with seems very p
88 matches
Mail list logo
