On Fri, Oct 22, 2010 at 8:13 PM, Mark Webb wrote:
> With the default ActiveMQ configuration, that stack trace is not sent
> to the console. So if people send text messages longer than 1024
> characters to ActiveMQ the messages will not get processed and there
> will be no log entry as to why.
>
Current camel-cxf component just treat the MEP as InOut, so you can get
the such error.
Please feel free to create a JIRA[1], so we can keep track of this issue.
[1]https://issues.apache.org/activemq/browse/CAMEL
On 10/23/10 7:34 PM, Jérémie wrote:
Hello,
I'm using a jaws proxy with camel tra
I have created CAMEL-3269
https://issues.apache.org/activemq/browse/CAMEL-3269
On Sat, Oct 23, 2010 at 4:13 PM, Willem Jiang wrote:
> Current camel-cxf component just treat the MEP as InOut, so you can get the
> such error.
> Please feel free to create a JIRA[1], so we can keep track of this iss
Hello,
We were using fusesource 4.2 SP 1 and have some cxf endpoint that can be
deployed into SMX 4.2 SP 1 with no problem. Just switching to fusesource 4.3
which includes camel 2.4 and running into issue deploying into SMX. I think
this has to do with schema being used, but don't really know how
Hi All,
we are getting
org.apache.camel.component.file.org.apache.camel.component.file.GenericFileOperationFailedException:
File operation failed: File operation failed exception with different
messages but underlying cause showing is
org.apache.camel.component.file.GenericFileOperationFailedExc
Looks like my messup was with the client code, but I am now getting this
error
[New I/O server worker #1-1] ServerChannelHandler DEBUG
Incoming message: BigEndianHeapChannelBuffer(ridx=0, widx=544, cap=544)
[New I/O server worker #1-1] DefaultErrorHandlerDEBUG Failed
And I just solved it with this :-)
On 23 October 2010 22:00, Yiannis Mavroukakis <
imavrouka...@gameaccountnetwork.com> wrote:
> Looks like my messup was with the client code, but I am now getting this
> error
>
>
> [New I/O server worker #1-1] ServerChannelHandler
Not sure if this resolve the issue, but you should remove the '-2.5' in your
Spring bean schema location (because you use Spring 3).
Christian
Am 23.10.2010 20:05 schrieb "Hossein" :
Hello,
We were using fusesource 4.2 SP 1 and have some cxf endpoint that can be
deployed into SMX 4.2 SP 1 with
I thought Camel 2.x supports Spring 2.5 and 3.0 and we can still use Spring
2.5 in Camel 2.4 and Spring 3.0 features will later be used by Camel 3.0. Is
this incorrect?
---
Hossein.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-4-and-cxf-issue-works-in-2-2-tp3233662
