Remove ExchangeProperty as it can cause unforseen side effect with double
registering from class initializers
-
Key: CAMEL-1591
URL: https://issues.apache.
TransactedErrorHandler - ExchangeProperty tries to double register transacted
-
Key: CAMEL-1592
URL: https://issues.apache.org/activemq/browse/CAMEL-1592
Project: Apache Camel
Hi,
Is it possible through camel endpoint, producer, consumer, ... (I don't know
exactly where in camel class), to parameter the output that we would like to
have from a component/endpoint ?
In the camel-quickfix component, the FIX server implemented (through
quickFix classes) receives messages i
[
https://issues.apache.org/activemq/browse/CAMEL-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1592.
Resolution: Fixed
1.x: 772869.
> TransactedErrorHandler - ExchangeProperty tries to double reg
[
https://issues.apache.org/activemq/browse/CAMEL-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1591.
Resolution: Fixed
trunk: 772873.
> Remove ExchangeProperty as it can cause unforseen side effe
Hi,
I just found the CamelTransportContants.CONTENT_TYPE is used by the
CamelTransport.
The integration test of CustomerServicesTest shows the user case.
Since there is no protocol header defined in Camel-xxx component, camel
transport need to copy the content-type between the CXF message and
Cam
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-1570:
--
Assignee: Claus Ibsen
> Jetty component is unable to be configured for security
> -
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51592#action_51592
]
Claus Ibsen commented on CAMEL-1570:
Applied patch to 2.0: 772891
>> See method setRefer
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1570.
Resolution: Fixed
Fix Version/s: 2.0.0
1.6.1
Thanks Christopher. I ha
[
https://issues.apache.org/activemq/browse/CAMEL-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51591#action_51591
]
Claus Ibsen commented on CAMEL-1570:
Applied patch to 1.x: 772883.
Thanks Christopher fo
[
https://issues.apache.org/activemq/browse/CAMEL-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51590#action_51590
]
Willem Jiang commented on CAMEL-1589:
-
I just found the CamelTransportContants.CONTENT_TY
On Fri, May 8, 2009 at 9:31 AM, Charles Moulliard wrote:
> Hi,
>
> Is it possible through camel endpoint, producer, consumer, ... (I don't know
> exactly where in camel class), to parameter the output that we would like to
> have from a component/endpoint ?
>
> In the camel-quickfix component, the
Hi,
My comments are in the mail.
Claus Ibsen wrote:
> On Fri, May 8, 2009 at 9:31 AM, Charles Moulliard
> wrote:
>> Hi,
>>
>> Is it possible through camel endpoint, producer, consumer, ... (I don't know
>> exactly where in camel class), to parameter the output that we would like to
>> have from
Something like the CXF component can do with its DataFormat type?
?dataFormat=String
?dataFormat=QuickFixMessage
I will check what is implemented in the camel-cxf component.
*Are you looking for another camel feedback concerning your proposal ?*
But why are you setting both the IN and OUT to the
Willem,
Any idea how to avoid to declare the beans in the spring xml file ?
http://camel.apache.org/schema/osgi";>
Normally, these classes should be instantiated by the camel endpoint (is is
correct what I say or I'm complete
Hi Charles,
Can you try the camel trunk's camel-quickfix component?
When I applied your patch , I found you did update the META-INF files
after rename the component's package name.
I test it with PAX-Exam, every thing looks good. You don't need to
declare the beans.
Willem
Charles Moulliard wrot
[
https://issues.apache.org/activemq/browse/CAMEL-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-1582:
--
Assignee: Claus Ibsen
> SimpleLanguage - Add better syntax error detection
> --
[
https://issues.apache.org/activemq/browse/CAMEL-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1582.
Resolution: Fixed
trunk :772927.
improved syntax validation for file and simple language, now
You should leverage Camels
- Producer
- Consumer
for whether its a ACCEPTOR or INITIATOR in QuickFix.
Producer = the one that spits out FIX messages
Consumer = the one that inputs FIX messages.
The Endpoint is the same for both of them.
Whether its a consumer or producer is usually defined how y
Charles Moulliard wrote:
> Something like the CXF component can do with its DataFormat type?
> ?dataFormat=String
> ?dataFormat=QuickFixMessage
>
> I will check what is implemented in the camel-cxf component.
> *Are you looking for another camel feedback concerning your proposal ?*
>
> But why ar
OK Willem I will test it.
Have you any idea about this ?
But why are you setting both the IN and OUT to the same message?
Good question. Anton is the author so I can't reply BUT what I can say is
that in quickfix, the application (
http://www.quickfixj.org/quickfixj/usermanual/usage/application.h
I have the same error when I remove the beans declaration in the spring XML
file :
org.apache.camel.NoSuchEndpointException: No endpoint could be found for:
quickfix-server:META-INF/examples/server.cfg, please check your classpath
contains the needed camel component jar.
at
org.apache.camel.ut
Hi
I suggest to take a look at camel-velocity endpoint how it extends
ResourceBasedEndpoint from camel-spring.
By doing this it gets all the resource loading for free.
Then loading your quickfix files from classpath, file system, OSGi
should work out of the box.
And we benefit from using the sam
Hi
Willem, just remember to remove the System.out when you got it working :)
On Fri, May 8, 2009 at 2:52 PM, wrote:
> Author: ningjiang
> Date: Fri May 8 12:52:14 2009
> New Revision: 772961
>
> URL: http://svn.apache.org/viewvc?rev=772961&view=rev
> Log:
> CAMEL-1350 update the TypeConverter
Hi Claus,
Thanks for pointing that out, I revert the changes which should not be
committed.
Willem
Claus Ibsen wrote:
> Hi
>
> Willem, just remember to remove the System.out when you got it working :)
>
> On Fri, May 8, 2009 at 2:52 PM, wrote:
>> Author: ningjiang
>> Date: Fri May 8 12:52:1
I see that the constructor of ResourceBasedEndpoint is different from the
one used now :
public ResourceBasedEndpoint(String endpointUri, Component component,
String resourceUri, Processor processor) {
super(endpointUri, component, processor);
this.resourceUri = resourceUri;
Hi
You can adjust the constructors and/or pass in the right arguments to super.
You are allowed to do changes in the camel-quickfix code. It is
afterall this new component we want to be part of the Camel family.
On Fri, May 8, 2009 at 3:18 PM, Charles Moulliard wrote:
> I see that the construc
I couldn't find where CamelTransport is referencing
CamelTransportContants.CONTENT_TYPE. Even if it is referenced, I
don't understand why we can have to use the constant of value
"content.type".
On Fri, May 8, 2009 at 3:56 AM, Willem Jiang wrote:
> Hi,
>
> I just found the CamelTransportContant
Hi Willem,
I think you meant CxfHeaderHelper rather than CamelTransport. I saw
your checkin. Changing the header name from "content.type" to
"CamelContentType" is fine, although it is not consistent with
DefaultCxfBinding where it just uses header name "Content-Type".
Also, should it be "CamelC
Hi William,
How about we store these Content-Type with the same key: "CamelConentType"?
In this way we don't need to write a long check list for looking up the
Content-Type in the Camel message header.
Any thought?
Willem
William Tam wrote:
> Hi Willem,
>
> I think you meant CxfHeaderHelper
That sounds fine to me.
- William
On Fri, May 8, 2009 at 9:49 PM, Willem Jiang wrote:
> Hi William,
>
> How about we store these Content-Type with the same key: "CamelConentType"?
>
> In this way we don't need to write a long check list for looking up the
> Content-Type in the Camel message head
Hi Charles,
Just one note, since we move the example into test directory,
camel-quickfix will not contain any file of META-INF/examples/server.cfg.
You may need to put the cfg file in to the bundle which contains your
routing rule.
Did you still have the trouble to resolved the quickfix-server e
davscl...@apache.org wrote:
> Author: davsclaus
> Date: Fri May 8 15:41:29 2009
> New Revision: 773035
>
> URL: http://svn.apache.org/viewvc?rev=773035&view=rev
> Log:
> CAMEL-1572: Added async sample for show and tell of the new Async API.
>
> +
> +// so we use the async extract body t
On Sat, May 9, 2009 at 5:29 AM, Willem Jiang wrote:
> davscl...@apache.org wrote:
>> Author: davsclaus
>> Date: Fri May 8 15:41:29 2009
>> New Revision: 773035
>>
>> URL: http://svn.apache.org/viewvc?rev=773035&view=rev
>> Log:
>> CAMEL-1572: Added async sample for show and tell of the new Async
On Sat, May 9, 2009 at 5:05 AM, William Tam wrote:
> That sounds fine to me.
+1
We had a initial discussion on whether to use a single name for common
types such as Content-Type for CXF, Restlet, Http, etc.
I guess it makes sense to do that. There are might other similar keys
such as: Content-Len
35 matches
Mail list logo
