+1
regards, aki
2016-03-22 13:48 GMT+01:00 Gregor Zurowski :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.17.0, a new minor version
> with ~450 improvements, fixes and new features. This is the second
> attempt which fixes a NPE in camel-jaxb when used with
> CamelTestBlueprint/OS
Hi Christian,
But if we follow this rule literally, we would need to bump the major
version every time when we do a minor release like we do now. In each
minor release, we are introducing a bunch of binary incompatibilities
that require updates of the underlining libraries. The servers
document[1]
+1
regards, aki
2016-01-23 12:08 GMT+01:00 Gregor Zurowski :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.16.2 that has 70+ fixes and
> improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12334167
>
> Staging reposit
Hi Andrea,
no problem.
By the way, the version range could be changed to include 2.3.x in the
future, as I have recently added some classes in both atmosphere 2.3.x
and 2.4.x to somewhat hide this incompatible (unfortunate but thought
necessary
https://groups.google.com/forum/#!topic/atmosphere-fr
+1
thanks.
aki
2015-11-23 23:50 GMT+01:00 Gregor Zurowski :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.15.5 that has 19 fixes and
> improvements.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12333895
>
> Staging reposito
Hi
you can change the permission behavior globally or customize it at the
instance level.
at the bottom of this document it is described how:
http://camel.apache.org/xstream.html
->Setting the type permissions of Xstream DataFormat.
regards, aki
2015-11-23 20:47 GMT+01:00 Krzysztof Sobkowiak :
+1
thanks
2015-11-19 8:16 GMT+01:00 Claus Ibsen :
> Hi
>
> Ah yeah I have just fixed those unit tests. It is only for a
> representation of the uri that was affected, the logic should work as
> before.
>
>
> On Wed, Nov 18, 2015 at 6:25 PM, Aki Yoshida wrote:
>&g
I am still in the middle of testing but noticed one thing.
Could it be that the recent change[1] in ServletComponent that removes
some leading slashes from the endpoint url might have introduced some
regression elsewhere?
Concretely, I noticed that camel-gae's GHttpComponent is getting the
endpoin
thanks.
2015-11-17 8:53 GMT+01:00 Gregor Zurowski :
> Alright, I can start rebuilding 2.16.1 in a few hours in order to
> include the commons-collection upgrade. Is that OK for everyone?
>
>
> On Mon, Nov 16, 2015 at 8:48 PM, Claus Ibsen wrote:
>> Hi
>>
>> Yeah we would need to do a 2.15.x relea
I just noticed that I don't see the 2.16.x jenkins job where i thought
i could find it along with the trunk and 2.15.x jobs.
Is is somewhere else?
2015-11-13 9:26 GMT+01:00 Gregor Zurowski :
> Hi Everyone:
>
> I plan to build the Camel 2.16.1 release later today. Please let me
> know if you stil
No. The order of calling those allow and deny methods is significant.
See http://x-stream.github.io/security.html#framework
> The sequence of registration is essential. The most recently registered
> permission will be evaluated first.
And the two test cases in my original patch file demonstrate
+1
regards,
aki
2015-10-06 3:21 GMT+09:00 Daniel Kulp :
>
> This is a vote to release Apache Camel 2.16.0. There was a TON of work done
> over the last 6 months to get this ready so it’s time to get it out.
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=cad9dc2be555b746
+1
regards, aki
2015-09-30 10:25 GMT+09:00 Daniel Kulp :
> This is a vote to release Apache Camel 2.16.0. There was a TON of work done
> over the last 6 months to get this ready so it’s time to get it out.
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=a9ddbc94874817ab4
hi smalik,
it is true as Sergey mentioned that the current camel-cxf 2.15.x
brings both jaxws and jaxrs minimal requirements and that is too much
when you want to use only one or the other.
But you still won't be needing a hundred of jars to just run a plain
soap based service call, though.
When u
Hi,
Currently, the default conversion from Map or List to String is based
on the JDK's default serialization. So, if you have a map having
entries "name"="peach", "taste"="sweet", you get
{name=peach, taste=sweet}
This representation is somewhat useless except for the logging
purpose. This format
+1 (non-binding)
Aki
2015-08-18 8:18 GMT+02:00 Willem Jiang :
>
> I just ran unit tests of camel in action with this kit, everything looks good.
> Here is my +1.
>
> --
> Willem Jiang
>
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
>
-05 9:32 GMT+02:00 Claus Ibsen :
> On Fri, Jul 31, 2015 at 3:10 PM, Aki Yoshida wrote:
>> For a short term, we can have camel also use 2.4.0 so that installing
>> a camel feature won't lead to this situation.
>> Is anyone against going for 2.4.0 in master and in camel-2.
ent/pom.xml#L430
>
> On Thu, Jul 23, 2015 at 6:53 PM, Aki Yoshida wrote:
>> I am wondering if there is a way to avoid this awkward situation.
>>
>> When you install camel-cxf 2.15.2 feature on a freshly setup karaf
>> 3.0.3, it will end up with two versions of Service
this information to the documentation.
regards, aki
2015-07-27 13:54 GMT+02:00 Aki Yoshida :
> Hi Franz,
> but the headers were transferred when you had the CXFPayload message
> directly transferred from one end to the other, no? In other words,
> that was the case when the scenari
h just
> forwards the header to the SOAP server. This happened before the patch
> and the same will happen after the patch.
>
> Regards Franz
>
>
>
> On Fri, Jul 24, 2015 at 4:27 PM, Aki Yoshida wrote:
>> Hi Franz,
>> I wanted to look at this but had not had time
Hi Franz,
I wanted to look at this but had not had time and a little late to comment.
One question or concern that I had wasthat this would change the
behavior of the existing tunneling scenarios using some soap headers,
no?
In other other words, some unwanted headers might tunnel through and
show
I am wondering if there is a way to avoid this awkward situation.
When you install camel-cxf 2.15.2 feature on a freshly setup karaf
3.0.3, it will end up with two versions of ServiceMix Stax API
bundles.
karaf@root()> feature:repo-add camel 2.15.2
Adding feature url mvn:org.apache.camel.karaf/ap
using CXF 3.0.x. And now Camel 2.16 is using CXF
> 3.1.x.
>
> We do not want to tie to old versions that cripple us such as CXF 2.x
> requiring Jetty 8.x etc.
>
> If you want to use CXF 2.7.x then use the already released versions of
> Camel that supports this.
>
>
>
Hi Claus,
could you look at my comment on this ticket regarding the cxf's
osgi-version range?
I think we should keep the range as before, that is to have [2.7,4.0).
So I am interested in hearing the argument for updating the range.
thanks.
regards, aki
2015-07-09 15:35 GMT+02:00 Aki Yoshida
I can look into it tomorrow unless someone is already working on it or
planning to do so.
let me know.
regards, aki
2015-07-09 8:03 GMT+02:00 Claus Ibsen :
> Hi
>
> Wonder if any of the CXF guys can upgrade Camel master branch to the
> new 3.1.x versions of Apache CXF.
>
> There may be more than j
Hi Sergey,
I can take it, if no one else has started on it.
regards, aki
2015-02-20 13:49 GMT+01:00 Sergey Beryozkin :
> Hi
>
> Can someone please help with getting CAMEL-8372 [1] resolved for 2.15.0 ?
>
> It's a safe patch that only affects a 'model-only' CXFRS consumer option.
> Currently only a
i think someone has fixed it already ;-)
2015-02-11 11:05 GMT+01:00 Aki Yoshida :
> i can look into it.
>
>
> 2015-02-11 8:16 GMT+01:00 Claus Ibsen :
>> Hi
>>
>> I think this causes camel-ahc-ws to not compile anymore.
>>
>> [ERROR]
>> /Users/davsc
i can look into it.
2015-02-11 8:16 GMT+01:00 Claus Ibsen :
> Hi
>
> I think this causes camel-ahc-ws to not compile anymore.
>
> [ERROR]
> /Users/davsclaus/workspace/camel/components/camel-ahc-ws/src/main/java/org/apache/camel/component/ahc/ws/WsEndpoint.java:[215,8]
> error: method does not ov
+1 (non-binding)
tested the unit tests with the src.zip and tested some cxf and
websocket tests on karaf 3.0.2
2014-12-11 12:24 GMT+01:00 Willem Jiang :
> This is a vote to release Apache Camel 2.14.1, a patch release coming
> with about 139 issues fixed.
>
> Release notes:
> 2.14.1
> https://is
I replied to your "camel -xsd" thread at users@camel.
I think that clarifies your question.
regards, aki
2014-12-10 10:27 GMT+01:00 Aki Yoshida :
> The test cases are spread in several places depending on the test types.
>
> For the iterator-level tests, those XMLTokenExpressio
The test cases are spread in several places depending on the test types.
For the iterator-level tests, those XMLTokenExpressionIterator*Test.java in
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tree;f=camel-core/src/test/java/org/apache/camel/support/
For the xtokenizer-level tests, tho
ration of Ekstazi in pom.xml, as
> suggested by Henryk (i.e., removing "excludesFile" and "argLine").
>
> Looking forward to more feedback on the Google group,
> Thanks,
> Milos
>
>> p.s. by the way, the profile has been added in master.
>
> Great
@Milos,
+1 for using a dedicated jira and forum.
regards, aki
p.s. by the way, the profile has been added in master.
2014-11-20 23:04 GMT+01:00 Henryk Konsek :
> Hi Milos,
>
>> in the next version (which I plan to release
>> before the end of the month) no change to the existing pom files wil
Hi Camel-Team,
I have been talking with Milos about this ekstazi tool.
Although we have identified a few shortcomings in some cases during
our tests and discussion, I think this tool offers an interesting test
option for Camel developers. And I believe It will be a mutual benefit
for us to use this
+1
I thought this switch had already taken place with 2.14 because not
all components of 2.14 was compatible with jdk 1.6.
http://camel.465427.n5.nabble.com/jenkins-full-test-build-error-at-camel-barcode-td5752260.html
2014-09-19 14:31 GMT+02:00 Daniel Kulp :
>
> With Camel 2.14 out, can we now
+1 (non-binding)
regards, aki
2014-09-16 4:17 GMT+02:00 Willem Jiang :
> I ran the test with camel inaction and camel cookbook codes. All tests were
> passed after I updated the codes.
>
> Here is my +1.
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemj
For the tests that I usually ran, everything was okay.
But I noticed the following problem. There seems to be an issue in
some components under OSGi.
Concretely, I noticed that camel-google-drive has still 2.14-SNAPSHOT
dependency wired, so you get
Error executing command: Could not start bundle
I just looked at the camel-mqtt component.
Could it be that the authentication and transport security part is
already supported, no?
The configuration class MQTTConfiguration just extends
org.fusesource.mqtt.client.MQTT which has all the setters and getters,
so I think it is supported (at least sup
n should be wider, and be [2.11,3). This
> just bites next time there is a jline / karaf / whatever upgrade
> somewhere.
>
>
> On Wed, Aug 6, 2014 at 11:26 AM, Aki Yoshida wrote:
>> I am getting this error when using camel feature for 2.14-SNAPSHOT on
>> karaf-3.0.1.
&
I just saw some messages on dev@karaf.
I could try replacing Jline manually in karaf-3.0.1 for now.
2014-08-06 11:26 GMT+02:00 Aki Yoshida :
> I am getting this error when using camel feature for 2.14-SNAPSHOT on
> karaf-3.0.1.
>
> Error executing command: Could not
I am getting this error when using camel feature for 2.14-SNAPSHOT on
karaf-3.0.1.
Error executing command: Could not start bundle
mvn:org.apache.camel.karaf/camel-karaf-commands/2.14-SNAPSHOT in
feature(s) camel-core-2.14-SNAPSHOT: Unresolved constraint in bundle
org.apache.camel.karaf.camel-kara
+1 (non-binding)
I tried 2.13.2 for mvn install with osx jdk7; some manual cxf and core
scenarios on karaf. All fine.
regards, aki
2014-07-02 4:18 GMT+02:00 Willem Jiang :
> Hi
>
> This is a vote to release Apache Camel 2.13.2 and 2.12.4.
>
> Release notes:
> 2.13.2
> https://issues.apache.org/j
Execution.post(AbstractBuild.java:725)
> at hudson.model.Run.execute(Run.java:1701)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Ex
ng.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On June 17, 2014 at 9:34:03 PM, Aki Yoshida (elak...@gmail.com) wrote:
>> Hi Babak,
>> thanks for the detail.
>>
>> In that case, I hope someone is d
d, there was an old attempt to
> stabilize it
> https://issues.apache.org/jira/browse/INFRA-6218
>
> Babak
>
> Aki Yoshida-3 wrote
>> 2014-06-13 12:43 GMT+02:00 Babak Vahdat <
>
>> babak.vahdat@
>
>> >:
>>>
>>>
>>> Am 13.06.14 12:23
2014-06-13 12:43 GMT+02:00 Babak Vahdat :
>
>
> Am 13.06.14 12:23 schrieb "Aki Yoshida" unter :
>
>>I noticed the full test has been red for some time at camel-barcode.
>>
>>Today, I noticed that this test is using mvn:com.google.zxing/core/3.0.0
>&g
I noticed this error a few days ago and the errors are still there as of today.
It looks like the changes come from Dhiraj, so I'm cc'ing him.
The commit log shows him as the author and committer of the change and
I am wondering if this was a pull request and merged without resetting
the commiter/
Hi Gregor,
This change is adding the operationName and operationNamespace properties
to be included in the camel-cxf's configuration documentation.
If these properties are mentioned (and in that way, their use as
recommended), we need to be clear on its semantic when there is a conflict,
namely the
I noticed the full test has been red for some time at camel-barcode.
Today, I noticed that this test is using mvn:com.google.zxing/core/3.0.0
and this core-3.0.0.jar was built with jdk 7
so it can't be used with the current jdk6 camel build.
I don't know if there is a jdk6 compatible jar.
Or el
gt;> Red Hat, Inc.
>> Web: http://www.redhat.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.iteye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>>
>>
>> On May 28, 2014 at 7:09:24 PM, Aki Yoshida (elak...@gmail.com)
Hi,
I saw Willem fixing some of my checkstyle violation (Thanks Willem)
and realized belately that the checkstyle is not active by default in
camel when doing mvn clean install.
I thought that the checkstyle was enabled as in cxf by default.
When I ran mvn -Psourcecheck, I saw some additional che
+1 (non-binding)
used the tarball 2.13.1-src and ran the whole unit tests with OSX JDK 1.7.0_51.
also ran some cxf manual tests with karaf using camel features.
looked all good.
regards, aki
2014-05-08 3:48 GMT+02:00 Willem Jiang :
>
> This is a vote to release Apache Camel 2.13.1, a patch relea
;
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Wed, Apr 2, 2014 at 3:00 PM, Aki Yoshida wro
I may be looking at the wrong apache repo location but I was expecting
to find 2.14-SNAPSHOT jars at
https://repository.apache.org/content/groups/snapshots/org/apache/camel/camel-core/
but I found only 2.13-SNAPSHOT and 2.13.1-SNAPSHOT but not the current
2.14-SNAPSHOT.
Was something forgot to be
+1 (non-binding)
tested with some cxf scenarios on karaf 3.0.0.
aki
2014-03-18 6:19 GMT+01:00 Willem Jiang :
> This is a vote to release Apache Camel 2.13.0, a major release coming
> with about 480 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version
Hi Claus, Willem,
you are right. I'll postpone it.
As I had the components sitting for a long, I thought I should ask but
I realize it was too late.
Regards,, Aki
2014-03-17 9:14 GMT+01:00 Claus Ibsen :
> On Mon, Mar 17, 2014 at 9:11 AM, Aki Yoshida wrote:
>> Hi Willem, all,
>&
Hi Willem, all,
have you started on cutting out a release?
I would like to push the the websocket client component.
Additionally, the servlet based websocket server-sider component.
If there is an objection or you have already started cutting out a
release, I will postpone it.
thanks.
regards, aki
ttp://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Fri, Mar 14, 2014 at 7:14 PM, Aki Yoshida wrote:
>
>> Hi,
>> I noticed com.ning/async-http-client/1.8.3 has optional import of
>> pack
Hi,
I noticed com.ning/async-http-client/1.8.3 has optional import of
packages exported by io.netty/netty of version version="[3.9,4)".
Currently, camel trunk uses 3.8.0.Final for io.netty/netty
3.8.0.Final
I would like to upgrade this to 3.9.0.Final to be consistent with what
we have for the
ues/errors are you seeing?
regards, aki
2014-02-28 15:21 GMT+01:00 Aki Yoshida :
> Hi Claus,
> I can take a look at it. Just a moment.
> regards, aki
>
>
> 2014-02-28 15:12 GMT+01:00 Claus Ibsen :
>> I ran all the tests in tests and many tests failed in that cxf-blueprint.
Hi Claus,
I can take a look at it. Just a moment.
regards, aki
2014-02-28 15:12 GMT+01:00 Claus Ibsen :
> I ran all the tests in tests and many tests failed in that cxf-blueprint.
>
> Wonder if you have the same issue on your computer?
>
> I am working on CAMEL-7156 and wanted to ensure I didn't
+1 (non-binding)
aki
2014-02-16 5:16 GMT+01:00 Hadrian Zbarcea :
> This is a vote to release Apache Camel 2.12.3, a patch release coming with
> about 128 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593
>
> Staging repo:
Hi Camel-team,
I would like to integrate the atmosphere based websocket component to
camel. I posted messages regarding this topic several times and most
recent one some months ago [1].
I would like to briefly summarize the current status and propose a few
options about how we can proceed. I woul
l. So, I'll be
adding the range.
regards, aki
2013/11/26 Christian Schneider :
> We can do this but I think it is not necessary.
> Implementations like pax web support the old package versions too to be
> compatible with old builds.
>
> Christian
>
> Am 26.11.2013 12:3
Hi,
I noticed this a while ago but forgot to bring it up or ask.
Currently, the import version range of javax.servlet is not explicitly
given in camel-servlet's pom and as a result, camel-servlet is
importing javax.servlet with range "[2.6,3)".
Could we set the range explicitly to something like
+1 (non-binding)
ran the install test and some cxf osgi tests. All OK.
the only thing I noticed was one unit test in camel-dns that seems to
fail in sometimes semi-permanently.
if your run from your console
dig +short txt monkey.wp.dg.cx
and that is not returning the string
"A Macaque, ... http
Hi Willem,
I agree with you that netty should use the path.
but what is the benefit of using the full url? I guess the http 1.1
was changed to allow the full url so that the proxy doesn't need to
rewrite the request, could it be? in that case, that will be another
argument for the client to be actu
Hi Charles and team,
After our discussion
http://irclogs.dankulp.com/logs/irclogger_log/camel?date=2013-11-05,Tue
and the original mail thread.
http://camel.465427.n5.nabble.com/update-of-websocket-td5740578.html
I thought about how to merge or integrate the atmosphere based
server-side websocket
Hi Charles,
okay.
will talk to you next week.
regards, aki
2013/10/30 Charles Moulliard :
> Hi Aki,
>
> Sorry but I'm in vacations this week. Can you ping me next week (IRC :
> ch007m) to discuss that.
>
> Regards,
>
> Charles
>
>
> On Tue, Oct 29, 2013 at 1:
hanks.
regards, aki
2013/9/30 Aki Yoshida :
> Hi,
> A few weeks ago, I posted to this list about my thought on the camel-websocket
> http://camel.465427.n5.nabble.com/thoughts-on-the-camel-websocket-component-td5739005.html#a5739013
>
> I did some prototyping and I wanted to share
Hi,
A few weeks ago, I posted to this list about my thought on the camel-websocket
http://camel.465427.n5.nabble.com/thoughts-on-the-camel-websocket-component-td5739005.html#a5739013
I did some prototyping and I wanted to share this with you to get some
feedback. But I will be on vacation and not
l.git;a=blob;f=apache-camel/src/main/descriptors/src.xml;h=beb9610b3113ab2c83032e2e030b3bcb702856f6;hb=HEAD
>>
>> Best,
>> Christian
>> -
>>
>> Software Integration Specialist
>>
>> Apache Camel committer: https://camel.apache.org/team
+1 (non-binding)
used the source tar.gz from the other directory
https://repository.apache.org/content/repositories/orgapachecamel-077/org/apache/camel/camel/2.11.2/
and performed the usual tests (the unit tests + some additional tests
on equinox)
as i mentioned in my earlier mail, the src.zip in
+1 (non-binding)
the same thing with the src.zip, which i mentioned for 2.11.2 but
otherwise fine.
aki
2013/9/19 Christian Müller :
> After 9 days of development, we have a new bug fix release candidate
> apache-camel-2.12.1 ready.
> It comes with 47 issues resolved: new features, improvements a
i have a question about the tarball source versions.
since i seem to have downloaded the wrong one today.
what is the difference between
apache-camel-2.11.2-src.zipThu Sep 19 09:37:49 UTC 2013 22188570
camel-2.11.2-source-release.zip Thu Sep 19 06:25:46 UTC 2013 21892865
i mi
Tue, Sep 10, 2013 at 3:23 PM, Aki Yoshida wrote:
>
>> Hi Charles,
>>
>> If we only support jetty, that will be fine. But to support tomcat, we
>> need a component that avoids using jetty's websocket API directly.
>> In this aspect, camel-cxf is different beca
gt;
> On Tue, Sep 10, 2013 at 12:00 PM, Aki Yoshida wrote:
>
>> I have been looking into the websocket component and I was wondering
>> about a few things.
>>
>> First of all, I would like to make the component use the framework's
>> servlet if it's
I have been looking into the websocket component and I was wondering
about a few things.
First of all, I would like to make the component use the framework's
servlet if it's running in e.g., an OSGi container like karaf that has
jetty or another container that uses geminiweb/tomcat. I was using
A
+1 (non binding)
Aki
2012/12/3 Hadrian Zbarcea :
> A new patch release candidate apache-camel-2.10.3 final is out with
> approximately 74 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapacheca
;s open.
>> I will look for a good bar for Tuesday and Wednesday and will post the
>> details here.
>>
>> Best,
>> Christian
>>
>>
>> On Thu, Oct 25, 2012 at 2:22 PM, Aki Yoshida wrote:
>>
>>> Hi,
>>> I will be at the conference an
Hi,
I will be at the conference and would like to join the event too if it's open.
thanks.
regards, aki
2012/9/26 Christian Müller :
> planners@ wrote yesterday:
> The conference is taking place from Monday 5th to Thursday 8th November. On
> the Monday we have hackathons, coding sprints etc, to wh
Hi,
.gitignore currently includes entry *.i?? and this is filtering out
securityconfig.ini that is located in camel-shiro.
Could you replace this pattern (I suppose this entry was intended for
filtering out intelijIDEA files) with more selective patterns?
e.g., CXF uses
*.iml
*.ipr
*.iws
CXF als
+1 (non-binding)
tested 2.10.1 with cxf 2.6.2 setup.
2012/8/24 Daniel Kulp :
>
> It's been quite a while since 2.9.2. We're long overdue for 2.9.3. It's
> also a good time for 2.10.1.
>
> We've fixed over 135 JIRA issues for 2.9.3:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
+1 (non-binding)
Aki
2012/6/28 Hadrian Zbarcea :
> A new release candidate apache-camel-2.10.0 final is out with approximately
> 483 issues resolved so far: improvements and bug fixes [1].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-2
2012/5/10 Daniel Kulp :
>
> We discussed a while ago how the Camel CXF component's modes don't really
> "match" what CXF can provide. It currently has two modes:
>
> 1) Message mode - it provides the full message kind of as a stream.
> However, it specifically DISABLES much of the CXF processing
[
https://issues.apache.org/jira/browse/CAMEL-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106007#comment-13106007
]
Aki Yoshida commented on CAMEL-4452:
Hi Willem,
Checking boi.getOutput() != null
[
https://issues.apache.org/jira/browse/CAMEL-4452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-4452:
---
Attachment: test.tar.gz
Hi Willem,
thanks for looking into this.
Attached is a tar.gz file
-4452
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.8.0
Reporter: Aki Yoshida
Fix For: 2.8.2, 2.9.0
CAMEL-4030 with Revision 1129070 in trunk changed the way how the response
message is retrieved from the
[
https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-4429:
---
Attachment: camel-4429-new.patch.txt
Hi Willem,
I am attaching a patch for
Hi Willem,
I found where this 500 originally comes from (there is an NPE raised
in RawMessageContentRedirectInterceptor when no PR is returned). I
will verify this condition a little more and will update the ticket
with the patch.
thanks.
regards, aki
2011/9/14 Aki Yoshida :
> Hi Willem,
>
eration as it doesn't check
> the underlay input steam, I still need to use the option to let HttpConduit
> do not consume the underlay message.
>
> Willem
>
> On 9/14/11 6:33 PM, Aki Yoshida wrote:
>>
>> Hi Willem,
>>
>> I updated the patch for CXF-3788
Hi Willem,
I updated the patch for CXF-3788 to avoid the problem you discovered
for the original patch. I have tested the updated patch against a jaxw
disptach test case in CXF. I would like to verify that this correction
works for the test case you had without using this request property
setting.
[
https://issues.apache.org/jira/browse/CAMEL-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-4207:
---
Attachment: patch.txt
a minor correcton and cleanup to the spring beans xml and the test program.
M
Project: Camel
Issue Type: Test
Components: camel-cxf
Affects Versions: 2.7.2
Reporter: Aki Yoshida
Priority: Minor
Fix For: 2.7.3, 2.8.0
I noticed a minor deficiency in one of the CXF spring configuration tests in
the current
I agree with you and I am also for a single unix-type source assembly.
saving energy and resources.
regards, aki
2011/6/22 Daniel Kulp :
>
> Question:
>
> Does anyone really feel strongly that we need separate windows and unix SOURCE
> distributions? We can easily chop a minute or two off the a
[
https://issues.apache.org/jira/browse/CAMEL-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-3927:
---
Attachment: camel-cxf-20110429b-patch.txt
M
trunk/components/camel-cxf/src/test/java/org
-3927
Project: Camel
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.7.1
Reporter: Aki Yoshida
Fix For: 2.8.0
When using the Provider based service (i.e., one using the Provider's
invoke(Source m) signature), I observed that t
[
https://issues.apache.org/jira/browse/CAMEL-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-3917:
---
Attachment: camel-cxf-20110429-patch.txt
M
trunk/components/camel-cxf/src/main/java/org
: Bug
Components: camel-cxf
Affects Versions: 2.7.1
Reporter: Aki Yoshida
Fix For: 2.8.0
There is an issue with CxfPayloadConverter that can lead to a failure in
converting the CxfPayload into something which is actually convertible.
This problem happens
[
https://issues.apache.org/jira/browse/CAMEL-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida updated CAMEL-3842:
---
Attachment: patch-trunk-20110407.zip
the zip file including the following changes
M
trunk
1 - 100 of 105 matches
Mail list logo
