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 easier to use without having to do URL encoding!
On Fri, Sep 2, 2011 at 4:36 AM, hadr...@apache.org
SInce I work pretty much 97.98% in osgi, I'll weigh in and say that I really
like this.
If XML is only used from Blueprint / Spring-DM, we provide those with the
features descriptors,
they import nothing - i.e. are model/api bundles, why make a jar bigger?
I really don't think we should refactor
Hi
At first I will say that when I replied to this it was late in the
evening, so I may not have been able to
pickup the correct words, when I wrote the mail. The tone was due
strong concerns what has
happened over the last period to the API in camel-core.
The following I write with the
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095823#comment-13095823
]
Sergey Zhemzhitsky commented on CAMEL-4371:
---
Hi Claus,
Advice with seems very
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
[
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
On Tue, Aug 30, 2011 at 3:29 PM, Hadrian Zbarcea hzbar...@gmail.com 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
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
[
https://issues.apache.org/jira/browse/CAMEL-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095873#comment-13095873
]
Andreas Kuhtz commented on CAMEL-4374:
--
Just noticed that the patch will not work for
[
https://issues.apache.org/jira/browse/CAMEL-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095877#comment-13095877
]
Willem Jiang commented on CAMEL-4363:
-
Current camel-jetty component just binds one
[
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
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré j...@nanthrax.net 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
[
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
[
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-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
[
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
[
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-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-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-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
[
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-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-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-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
[
https://issues.apache.org/jira/browse/CAMEL-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095900#comment-13095900
]
Freeman Fang commented on CAMEL-4406:
-
back port to 2.8.x branch
[
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
On 1 September 2011 02:01, Hadrian Zbarcea hzbar...@gmail.com 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
On Fri, Sep 2, 2011 at 11:18 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofré j...@nanthrax.net
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
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 +
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:
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 Ibsenclaus.ib...@gmail.com wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofréj...@nanthrax.net
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
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 Ibsenclaus.ib...@gmail.com wrote:
On Fri, Sep 2, 2011 at 10:11 AM, Jean-Baptiste Onofréj...@nanthrax.net wrote:
Hi guys,
I would
On Fri, Sep 2, 2011 at 2:20 PM, Hadrian Zbarcea hzbar...@gmail.com 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
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 Ibsenclaus.ib...@gmail.com
wrote:
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
On Thu, Sep 1, 2011 at 3:16 AM, Hadrian Zbarcea hzbar...@gmail.com 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
camel-script feature should ship script implementation bundles like
groovy/javascript/ruby
--
Key: CAMEL-4407
URL: https://issues.apache.org/jira/browse/CAMEL-4407
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
[
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
[
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
feature name=camel-script version=2.6.0
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095953#comment-13095953
]
Claus Ibsen commented on CAMEL-4407:
Groovy is osgi out of the box now. We use groovy
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
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 this
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095955#comment-13095955
]
Ashwin Karpe commented on CAMEL-4371:
-
Hi Hadrian,
I see your point with mutating
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=13095970#comment-13095970
]
Ashwin Karpe commented on CAMEL-4371:
-
@Hadrian, @Claus,
I looked over the
[
https://issues.apache.org/jira/browse/CAMEL-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095970#comment-13095970
]
Ashwin Karpe edited comment on CAMEL-4371 at 9/2/11 1:32 PM:
-
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
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
[
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
[
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
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
[
https://issues.apache.org/jira/browse/CAMEL-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095999#comment-13095999
]
Freeman Fang commented on CAMEL-4407:
-
Hi Claus,
Thanks for reminder.
Yeah, we need
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
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
[
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
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
[
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
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
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.
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.
[
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
On Fri, Sep 2, 2011 at 4:50 PM, Hadrian Zbarcea hzbar...@gmail.com 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
I have started the cxf:bean:B in the cxf.xml file as
jaxws:endpoint id=serviceEndpoint
implementor=...class name.../
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
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 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
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13096046#comment-13096046
]
Claus Ibsen commented on CAMEL-4408:
Hmm the trunk looks like
{code}
properties
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-tabpanelfocusedCommentId=13096073#comment-13096073
]
Andreas Kuhtz commented on CAMEL-4408:
--
@Claus
The trunk (2.9-SNAPSHOT, check the jar
[
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-tabpanelfocusedCommentId=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:comment-tabpanelfocusedCommentId=13096092#comment-13096092
]
Claus Ibsen commented on CAMEL-4408:
Its just a bit odd as every camel component has
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13096098#comment-13096098
]
Claus Ibsen commented on CAMEL-4408:
I could see that camel-rss, may have that as
[
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-tabpanelfocusedCommentId=13096104#comment-13096104
]
Andreas Kuhtz commented on CAMEL-4408:
--
Yes, that might be the reason. I also noticed
On Fri, Sep 2, 2011 at 6:41 AM, James Strachan ja...@fusesource.com 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
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
[
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
[
https://issues.apache.org/jira/browse/CAMEL-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13096183#comment-13096183
]
Andreas Kuhtz commented on CAMEL-4408:
--
Thank you very much!!!
Fix OSGi-exports of
[
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
[
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
[
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:
---
Attachment: camel-sql_keyOrderingTest_polished.patch
Here is a unit test to ensure
85 matches
Mail list logo
