Hi,
first of all, thanks to both of you, Gert and Willem, for the quick replies.
I saw that the jira was already fixed, great job.
Does this mean that the methods for disabling stream caching will be removed
in the future?
I have tried to use "noErrorHandler" but there was a special case that u
Hi,
I have tried to use the http component to download bigger files from a
server. Initially I thought that I would get the input stream from the
response in the body of the exchange. But as far as I can tell I'm always
getting a ByteArrayInputStream, which means the stream is somehow getting
cha
Hi Claus,
yes, it seems to have an effect because the lifecycle-strategy is different
when disabling JMX. The Constructor of the DefaultCamelContext uses either
DefaultLifecycleStrategy or InstrumentationLifecycleStrategy. This also has
influence on the error handling strategy.
Jens
--
View thi
Wow nice job! I'll make sure that I try 1.6.1 soon.
Thanks a lot Claus.
--
View this message in context:
http://www.nabble.com/StreamCaching-in-Camel-1.6-tp22305654p22581500.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Hi,
I ran into a problem with a route that called a seda endpoint. For some
reason the unit of work within the seda route was completed before the
actual route processing finished. Here's a simplified test case:
public class SedaUnitOfWorkTest {
private String lastOne;
@Test
pub
Hi,
I ran into a multi-threading problem with a web service that returned
multiple attachments. After playing around with this for some time I found
that data that is read from the PushbackInputStream often gets unread
shortly afterwards. When my problem occurred this did not happen, causing
the
Hi,
I posted this via the wrong Nabble Forum. This is of course a CXF issue.
Please ignore it.
Sorry for my confusion,
Jens
--
View this message in context:
http://www.nabble.com/Re%3A-Static-buffer-field-in-HTTPConduit-tp24809334p24809334.html
Sent from the Camel - Users mailing list archive
Hi,
What is the expected behavior in Camel 2.0 if no type converter is found for
a conversion? According to the http://camel.apache.org/type-converter.html
documentation starting with Camel 1.5 a NoTypeConversionAvailableException
should be thrown. This seems not to be the case in Camel 2.0 any
Hi,
in Camel 1.x you could write a simple HTTP bridge like this:
CamelContext camelContext = new DefaultCamelContext();
camelContext.addRoutes(new RouteBuilder() {
@Override
public void configure() throws Exception {
from("jetty:http://lo
Thinking a little bit more about this. Maybe this is just a special case for
header filtering strategies. In this case it seems a bit strange, because
you explicitly specify the endpoint address in the to() call. However, this
is the similar to the case where you want to send a message to an HTTP
Hi,
in 1.x we had access to the IoSession via the MinaExchange. Although this
wasn't the best way to get data from the IoSession, we were able to get
things like remote and local address, which are sometimes relevant to
routing. In 2.0 the MinaExchange is gone and access to the IoSession isn't
po
> // and we should add a nice type converter method so you can do
> without ugly casting
> MimaMessage mina = exchange.getIn(MinaMessage.class);
I don't think that this is supported by Exchange. There is only a getIn()
method that takes no parameters.
--
View this message in context:
http://www
Hi,
I just checked out the new example for the JMX management in Camel 2.1. When
I run the example and browse the MBeans with JConsole, I can see all the
processors of the route being instrumented. I then added a setHeader to the
route, but it was not shown in JConsole. However, a transform step
Just debugged this a bit and it seems that processors have to implement
Service to be instrumented. The processor for setHeader only implements
Processor, whereas TransformProcessor extends ServiceSupport.
_Jens wrote:
>
> Hi,
>
> I just checked out the new example for the JMX m
Hi Claus,
I simply changed the last route of the example:
100
bar
foobar
Jens
--
View this message in context:
http://www.nabble.com/JMX-i
numbers for it
(e.g. how often it was called). For such a case I would not necessarily be
interested in manipulating it (e.g. starting/stopping).
Jens
Claus Ibsen-2 wrote:
>
> On Thu, Oct 8, 2009 at 9:57 AM, _Jens wrote:
>>
>> Just debugged this a bit and it seems that processors
Hi,
I have run into an issue with a .recipientList() using Mina endpoints (Camel
2.1). Basically, I was changing a route from using static .to() calls into a
more dynamic .recipientList() call. With the .to() calls IoSessions were
reused to send data. However, with the .recipientList() it seems t
Hi,
it seems to me that the DefaultHTTPBinding again uses a CachedOutputStream.
This means that the binding cannot be used anymore with longer streams and
that the streamCache option on the CamelContext bean is ignored. Is this
going to be the way the caching is done in 2.3?
Thanks,
Jens
--
Vie
m message.
>
> You can still configure the CachedOutputStream by using the camelContext
> properties, I don't know what kind of issue that the changes introduced
> to you.
>
> Willem
>
> _Jens wrote:
>> Hi,
>>
>> it seems to me that the DefaultHTTPBindin
ssage error as it can dump the message into a file.
> I don't know why are your going to disable it.
>
> Willem
>
> _Jens wrote:
>> Hi Willem,
>>
>> thanks for your quick reply. The issue is that I cannot disable
>> streamCaching in 2.3-SNA
Hi Willem,
unfortunately I was not able to get this working. I saw the unit test that
you checked in for this. The test runs without an error. However, it does
not verify this completely. Although it is now possible to get the stream,
the stream has been read. I changed the route builder used in
Hi,
I have run into a problem with stream caching in Camel 1.6. I have a route
that reads data via streaming from an Http request. In some cases this can
be a large amount of data, so I cannot stream the data completely into
memory. I wrote this little test to demonstrate my problem:
@Test
22 matches
Mail list logo
