The attribute (loggingFeatureEnabled) already exists. in camel-cxf
endpoint Please check out http://camel.apache.org/cxf.html.
On 11/08/2011 05:43 AM, Willem Jiang wrote:
Hi Claus,
CXF has the log feature can avoid us to configure lots of
interceptors. but it could be more handy if we add an
[
https://issues.apache.org/jira/browse/CAMEL-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102076#comment-13102076
]
William Tam commented on CAMEL-4436:
r1167555 - 2.9.0.x
r1167556 - 2.8
[
https://issues.apache.org/jira/browse/CAMEL-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-4436.
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.2
Committed revision 1167448
[
https://issues.apache.org/jira/browse/CAMEL-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4436 started by William Tam.
> CxfRsProducer clientFactoryBean's bus should be ini
: Bug
Components: camel-cxf
Affects Versions: 2.8.0
Reporter: William Tam
Assignee: William Tam
Priority: Minor
This defect only manifests itself if an application hosts more than one
CamelContext. The first CamelContext contained by a Spring application context
I really don't think so. The CXF component have unique and important
features that simply cannot be replaced by other components in camel-cxf.
Camel transport is a CXF transport that can be plugged into CXF stack.
It is a building block for other components (e.g. cxfbean) and other use
case,
[
https://issues.apache.org/jira/browse/CAMEL-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-4079.
Resolution: Fixed
2.7.3.x
Committed revision 1134060
2.8.0.x
Committed revision 1134059.
>
[
https://issues.apache.org/jira/browse/CAMEL-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-4079 started by William Tam.
> Bug in CxfConsumer.asyncInvoke that causes setResponseBack to be called tw
Issue Type: Bug
Components: camel-cxf
Affects Versions: 2.7.2, 2.6.0, 2.8.0
Reporter: William Tam
Assignee: William Tam
Fix For: 2.7.3, 2.8.0
Bug in CxfConsumer.asyncInvoke that causes setResponseBack to be called twice.
The asyncInvoke should
[
https://issues.apache.org/jira/browse/CAMEL-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-3927.
Resolution: Fixed
Committed revision 1098630. Thanks Aki Yoshida for the Jira and the patch
[
https://issues.apache.org/jira/browse/CAMEL-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-3927:
--
Assignee: William Tam
> CXF's Provider service using the payload data-format may not
[
https://issues.apache.org/jira/browse/CAMEL-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-3810:
--
Assignee: Willem Jiang (was: William Tam)
> At payload model, set soap body element to hea
[
https://issues.apache.org/jira/browse/CAMEL-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-3810:
--
Assignee: William Tam (was: Willem Jiang)
> At payload model, set soap body element to hea
[
https://issues.apache.org/jira/browse/CAMEL-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3808:
---
Issue Type: Bug (was: Improvement)
It looks we have documented this feature (setting CamelHttpQuery
[
https://issues.apache.org/jira/browse/CAMEL-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-3808.
Resolution: Fixed
Committed revision 1085543.
> Restlet Producer to add query to request
Project: Camel
Issue Type: Improvement
Components: camel-restlet
Reporter: William Tam
Assignee: William Tam
Priority: Minor
Fix For: 2.8.0
Currently, custom queries to be sent in the request URI must be defined in the
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-3778.
Resolution: Fixed
Committed revision 1084433. Thanks Aki Yoshida for the patch.
> Support
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009539#comment-13009539
]
William Tam commented on CAMEL-3778:
@Willem
Yea, it "could", b
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3778:
---
Attachment: CAMEL-3778-2.patch
Revised with no new user visible option. (CAMEL-3778-2.patch
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009521#comment-13009521
]
William Tam commented on CAMEL-3778:
@Willem
Not quite sure what you meant.
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009238#comment-13009238
]
William Tam edited comment on CAMEL-3778 at 3/21/11 5:5
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009238#comment-13009238
]
William Tam commented on CAMEL-3778:
@Aki,
I am OK with killing the endpoint op
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009227#comment-13009227
]
William Tam edited comment on CAMEL-3778 at 3/21/11 5:3
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009229#comment-13009229
]
William Tam edited comment on CAMEL-3778 at 3/21/11 5:3
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009229#comment-13009229
]
William Tam commented on CAMEL-3778:
BTW, I don't think it has anything t
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009227#comment-13009227
]
William Tam commented on CAMEL-3778:
@Aki, Here is what I think ... I don
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009227#comment-13009227
]
William Tam edited comment on CAMEL-3778 at 3/21/11 5:3
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009195#comment-13009195
]
William Tam edited comment on CAMEL-3778 at 3/21/11 4:2
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009195#comment-13009195
]
William Tam commented on CAMEL-3778:
@Aki
I don't think the option is confu
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008874#comment-13008874
]
William Tam edited comment on CAMEL-3778 at 3/20/11 5:1
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3778:
---
Attachment: CAMEL-3778.patch
> Support CXF Dispatch mode at CXF Endpoi
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008874#comment-13008874
]
William Tam edited comment on CAMEL-3778 at 3/20/11 4:0
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008874#comment-13008874
]
William Tam edited comment on CAMEL-3778 at 3/20/11 3:5
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008874#comment-13008874
]
William Tam commented on CAMEL-3778:
Here is the mail thread related to this i
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3778:
---
Attachment: CAMEL-3386.patch
> Support CXF Dispatch mode at CXF Endpoi
+1
On 03/18/2011 01:09 AM, Hadrian Zbarcea wrote:
A new release apache-camel-2.7.0 is out with approximately 171 issues resolved:
new features, improvements and bug fixes.
The issue with the previous release candidate related to karaf-2.2.0 is now
resolved. The manual download/generation prob
[
https://issues.apache.org/jira/browse/CAMEL-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-3778:
--
Assignee: William Tam
> Support CXF Dispatch mode at CXF Endpoi
+1
On 01/24/2011 10:14 PM, Hadrian Zbarcea wrote:
A new release apache-camel-2.6.0 is out with approximately 297 issues resolved:
new features, improvements and bug fixes.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-073/
The tarballs are
[
https://issues.apache.org/jira/browse/CAMEL-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3420:
---
Fix Version/s: 2.6.0
Assignee: William Tam
> CXF component should be smarter in determin
Project: Camel
Issue Type: Improvement
Components: camel-cxf
Reporter: William Tam
Priority: Minor
Please see the cross reference in
org.apache.camel.component.cxf.CxfMixedModeRouterTest. We set the data format
in the exchange properties
[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969066#action_12969066
]
William Tam commented on CAMEL-3386:
@Willem
I removed the client cach
[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969030#action_12969030
]
William Tam commented on CAMEL-3386:
Hi Willem,
Even the interceptor chain is cre
[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-3386.
Resolution: Fixed
Committed to trunk revision 1042677.
> Support destination address override
[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-3386:
--
Assignee: William Tam
> Support destination address override by CxfProvider and CxfrsProvi
[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-3386:
---
Attachment: CAMEL-3386.patch
> Support destination address override by CxfProvider and CxfrsProvi
Feature
Components: camel-cxf
Reporter: William Tam
Priority: Minor
Fix For: 2.6.0
So far, users can only send requests to REST/SOAP service endpoints that have
been explicitly defined in Camel routes. Sometimes, it is useful to override
the
camel-cxf work with CXF 2.2.x and CXF
2.3.x at the same time.
The user can make their own choice now :)
On 11/5/10 4:33 AM, William Tam wrote:
I think there are reasons not to (not sure if they are good reasons
though)
* Don't have to touch Camel 2.x camel-cxf component We can then direc
should not be a problem. In a
webapp it could be a bit problematic, but if the camel piece is in a separate
war, that should be fine too.
By the way, this is a discussion for dev@, not us...@.
Cheers
Hadrian
On Nov 4, 2010, at 10:40 AM, William Tam wrote:
Willem and I would like to start a
[
https://issues.apache.org/activemq/browse/CAMEL-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63054#action_63054
]
William Tam commented on CAMEL-3308:
@dan
Junit tests only test against CXF 2.3,
[
https://issues.apache.org/activemq/browse/CAMEL-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63048#action_63048
]
William Tam commented on CAMEL-3308:
@clause
we brought up the question to user
Willem and I would like to start a discussion regarding which release of
Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
https://is
[
https://issues.apache.org/activemq/browse/CAMEL-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63037#action_63037
]
William Tam commented on CAMEL-3308:
Just stating the obvious, but please make
+1
It looks good.
On Mon, Oct 25, 2010 at 5:19 PM, Hadrian Zbarcea wrote:
> A new release apache-camel-2.5.0 is out with approximately 300 issues
> resolved: new features, improvements and bug fixes.
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/org
[
https://issues.apache.org/activemq/browse/CAMEL-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61238#action_61238
]
William Tam commented on CAMEL-3055:
svn ci -m "[CAMEL-3
[
https://issues.apache.org/activemq/browse/CAMEL-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-3055 started by William Tam.
> camel-cxf component to support SOAP with Attachment in Payload m
[
https://issues.apache.org/activemq/browse/CAMEL-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-3055.
Resolution: Fixed
Committed revision 985362.
> camel-cxf component to support SOAP w
Type: New Feature
Components: camel-cxf
Reporter: William Tam
Assignee: William Tam
Fix For: 2.5.0
camel-cxf component to support SOAP with Attachment in Payload mode
--
This message is automatically generated by JIRA.
-
You can reply to this email to
Reporter: William Tam
Fix For: 2.5.0
The change (r979549) made by CAMEL-2991 causes every single endpoint to be
recreated instead of restarted which takes Camel a (quite big) step back. It
is bad for the following reasons:
1) recreating services associated could be
On 07/26/2010 01:15 AM, Claus Ibsen wrote:
On Mon, Jul 26, 2010 at 1:27 AM, William Tam wrote:
On 07/25/2010 01:56 PM, Claus Ibsen wrote:
On Sun, Jul 25, 2010 at 6:18 PM, William Tamwrote:
Hi Claus,
Thanks for your response.
* A ProcessorEndpoint is a hybrid
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-2991:
--
Assignee: Claus Ibsen (was: William Tam)
@claus I tried your fixes but my route is still
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2991:
---
Attachment: (was: CAMEL-2991.patch)
> Restart CamelContext won't restart ser
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2991:
---
Attachment: CAMEL-2991-test-case.txt
> Restart CamelContext won't restart ser
Claus, thanks for your experiment.
On 07/25/2010 02:01 PM, Claus Ibsen wrote:
On Sun, Jul 25, 2010 at 6:18 PM, William Tam wrote:
Hi Claus,
Thanks for your response.
* A ProcessorEndpoint is a hybrid between a Processor and a Endpoint.
Therefore, SendProcessor does have a child if the
On 07/25/2010 01:56 PM, Claus Ibsen wrote:
On Sun, Jul 25, 2010 at 6:18 PM, William Tam wrote:
Hi Claus,
Thanks for your response.
* A ProcessorEndpoint is a hybrid between a Processor and a Endpoint.
Therefore, SendProcessor does have a child if the destination is a
started" state when
someone tries to use it. Accessing a stopped DefaultTypeConverter is
bad to say the least. You don't get an error, you just get
different/wrong result.
Cheers,
William
On 07/25/2010 02:46 AM, Claus Ibsen wrote:
On Sun, Jul 25, 2010 at 5:55 AM, William Tam wro
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-2991:
--
Assignee: William Tam
> Restart CamelContext won't restart services on CxfBean
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2991:
---
Attachment: CAMEL-2991.patch
> Restart CamelContext won't restart services on CxfBean
I observed some issue regarding restarting Camel Context that I want to
discuss. The detail is in the CAMEL-2991.
* First off, any objection if SendProcessor implements Navigate? It
allows services associated with the destination endpoint to be restarted.
* There is a problem with type conv
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2991:
---
Attachment: (was: CAMEL-2991.patch)
> Restart CamelContext won't restart ser
[
https://issues.apache.org/activemq/browse/CAMEL-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2991:
---
Attachment: CAMEL-2991.patch
> Restart CamelContext won't restart services on CxfBean
: Bug
Components: camel-core, camel-cxf
Reporter: William Tam
Fix For: 2.5.0
A route that sends to a CxfBean destination is unusable after the CamelContext
has been stopped and re-started. The following is an example of a route that
demonstrates the problem.
+1
On 07/12/2010 11:27 AM, Hadrian Zbarcea wrote:
A new release apache-camel-2.4.0 is out with approximately 181 issues resolved:
new features, improvements and bug fixes.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-053/
The tarballs are
+1
On 06/12/2010 07:46 AM, Jon Anstey wrote:
+1
On Fri, Jun 11, 2010 at 3:22 PM, Hadrian Zbarcea wrote:
Hi,
We just released Camel 1.6.3 with only 39 issues resolved in about 6
months. Given that:
* 1.x is quite stable
* 2.x is more feature rich
* most of the projects that use Camel we
[
https://issues.apache.org/activemq/browse/CAMEL-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-2802.
Resolution: Fixed
Committed revision 953122.
> Camel-cxf does not properly popul
[
https://issues.apache.org/activemq/browse/CAMEL-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-2802 started by William Tam.
> Camel-cxf does not properly populate MessageContentList for PAYLOAD m
[
https://issues.apache.org/activemq/browse/CAMEL-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2802:
---
Description:
Currently, CxfEndpoint.CamelCxfClientImpl does not leave place holder for SOAP
Issue Type: Bug
Components: camel-cxf
Reporter: William Tam
Assignee: William Tam
Fix For: 2.4.0
Currently, CxfEndpoint.CamelCxfClientImpl does not leave place holder for SOAP
header in MessageContentList. It could be a problem when CXF tries to
Hi Willem,
I would suggest changing the property names to defaultOperationName and
defaultOperationNamespace to avoid confusion. They are really the
default if the respective headers are not set.
Thanks,
William
On 06/02/2010 07:44 AM, ningji...@apache.org wrote:
Author: ningjiang
Date: We
+1
On 05/31/2010 09:04 PM, Hadrian Zbarcea wrote:
A new maintenance release of apache-camel-1.6.3 is out with approximately 39
issues resolved: new features, improvements and bug fixes.
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-024/
Th
+1
On 05/25/2010 07:31 AM, Jon Anstey wrote:
+1
On Sat, May 22, 2010 at 10:26 PM, Hadrian Zbarceawrote:
The second release candidate of apache-camel-2.3.0 is out with
approximately 276 issues resolved: new features, improvements and bug fixes.
Please find the staging repo here:
https://r
On 05/13/2010 09:20 AM, William Tam wrote:
I had a quick chat with Willem. (thanks Willem) In this case, the
Camel converter framework will invoke the CxfPayload.toString() method
if no better suit converter is found. The toString method of
CxfPayload is as follow.
public String
[
https://issues.apache.org/activemq/browse/CAMEL-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59328#action_59328
]
William Tam commented on CAMEL-2714:
email thread:
http://old.nabble.com/CxfExchang
Camel converter will call the CxfPayLoad.toString() method to do this
kind job.
But if you just want to get the payload body, I'm afraid you still
need to use the below code to do the job.
Willem
William Tam wrote:
I need to correct my previous reply. Are you using PAYLOAD or POJO
mode? (I assume you
od takes a list of Element
and convert them to a String. I created a Jira for adding a converter
that converts a CxfPayload to a String so it is not needed in the
future.(https://issues.apache.org/activemq/browse/CAMEL-2714)
On 05/12/2010 11:54 AM, William Tam wrote:
You can do someth
Components: camel-cxf
Reporter: William Tam
Priority: Minor
Fix For: 2.3.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
You can do something like this:
Message message = exchange.getIn();
String request = message.getBody(String.class);
if (request == null) {
Source source = message.getBody(Source.class);
if (source != null) {
request = getRequestFromSource(source);
}
}
If we had a converter to covert fr
[
https://issues.apache.org/activemq/browse/CAMEL-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59237#action_59237
]
William Tam commented on CAMEL-1893:
I checked all three components (cxf, cxfbean, c
[
https://issues.apache.org/activemq/browse/CAMEL-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-1893.
Resolution: Cannot Reproduce
> camel-cxf - Setting HTTP response code tw
,
William
On 05/05/2010 08:28 PM, Willem Jiang wrote:
There is a CXF related issue[1] need CXF 2.2.8.
It could be great if we release Camel 2.2.3 after CXF 2.2.8.
[1] https://issues.apache.org/activemq/browse/CAMEL-2614
Willem
William Tam wrote:
+1
On 05/05/2010 12:28 PM, Christian Schneider
[
https://issues.apache.org/activemq/browse/CAMEL-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-1893 started by William Tam.
> camel-cxf - Setting HTTP response code twice
>
>
>
[
https://issues.apache.org/activemq/browse/CAMEL-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2620:
---
Fix Version/s: (was: 2.3.0)
2.4.0
> Preserve streaming behavior in ca
[
https://issues.apache.org/activemq/browse/CAMEL-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-2614.
Resolution: Fixed
> Camel-cxf can't handle multi part message in PAYL
+1
On 05/05/2010 12:28 PM, Christian Schneider wrote:
Hi Claus,
one interesting thing could be to wait for CXF 2.2.8 and use this. Dan
just proposed a release next week. So it is just a matter of days.
Apart from this I am really looking forward to the new release the
sooner the better.
Gre
[
https://issues.apache.org/activemq/browse/CAMEL-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam resolved CAMEL-2638.
Fix Version/s: 2.3.0
Resolution: Fixed
Patch applied with thanks to Rich Bolen
[
https://issues.apache.org/activemq/browse/CAMEL-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam reassigned CAMEL-2638:
--
Assignee: William Tam
> Restlet component is URL encoding the POST message body.
-form-urlencoded. What should
we do with the headers for PUT, DELETE, and non-form POSTs?
Should I move this thread to the developers forum? I wasn't sure if only
jira stuff went there.
William Tam wrote:
I see. The method probably should have called request.setEntity(Sting,
MediaType)
Components: camel-cxf
Reporter: William Tam
Assignee: William Tam
Fix For: 2.3.0
Dan Kulp pointed out in https://issues.apache.org/jira/browse/CXF-2753 that
Camel should preserve the streaming behavior by setting message part type
class to Source.class (so the
[
https://issues.apache.org/activemq/browse/CAMEL-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58675#action_58675
]
William Tam commented on CAMEL-2614:
@clause
The commented line should have
We discussed in this mailing list that the camel-cxf component (in
particularly, the PAYLOAD mode implementation) was unnecessarily
complicated. Here is a quick update. Using Dispatch APIs is probably
still a long term goal. As fixing the defect
https://issues.apache.org/activemq/browse/CAME
[
https://issues.apache.org/activemq/browse/CAMEL-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-2614:
---
Attachment: CAMEL-2614.patch
> Camel-cxf can't handle multi part message in PAYL
1 - 100 of 308 matches
Mail list logo
