Hi,
I had the same problem and the solution is easy. Just create a class
that implements PackageScanClassResolver and define it as bean [1].
Camel will find it during startup of the context and use this bean
instead of creating the DefaultPackageScanClassResolver that scans the
classpath. Maybe
Hi Charles,
yes that's the way i did it. I've found yesterday the solution to my
problem; in the import package part of my OSGi bundle, i had to add the
packages:
org.apache.camel, org.apache.camel.model, org.apache.camel.model.config,
org.apache.camel.model.dataformat,
On Fri, May 27, 2011 at 4:38 AM, Jim Newsham jnews...@referentia.com wrote:
Hi Willem,
We do not want to use a temporary queue for replies, because it is scoped to
the lifetime of the connection, and any data sent to that queue will be lost
if the connection gets lost for some reason.
We
On Friday, May 27, 2011, peterjca pete...@ukgateway.net wrote:
Hi Ashwin,
Thanks for the response. However, I don't think this is what I need as this
appears to simply be a queue to queue communication which I can already do
with ActiveMQ. My situation has a connection factory that looks
On Thursday, May 26, 2011, Samuel Cox crankydi...@gmail.com wrote:
Hi,
I've created a black-box request/response facade around a Camel route. Think:
class BlackBox {
function process(request: Request): Response
}
This thing lives in a spring environment and is getting the
CamelContext
Nice. Do you mind creating a jira ticket and attach you source. Then
we can use it as a contribution.
On Thursday, May 26, 2011, Mond Raymond mondraym...@gmail.com wrote:
Claus,
Just thought I would follow up.
I don't know if this counts as a contribution, but I ended up doing this as
a
,
it format the value 20110527 into a date, but it picks up 50001440 instead.
I am using version 2.7.1,
is FixedLength unmarshalling a supported feature?
is this a known issue or I may be defining something incorrectly?
Caused by: java.text.ParseException: Unparseable date: 50001440
The bean
On Thursday, May 26, 2011, Zhemzhitsky Sergey
sergey_zhemzhit...@troika.ru wrote:
Is it possible to instantiate a jdk proxy based on the interface of the
service? If so, the code would be cleaner because there will no dummy service
implementations?
Yep that would be lovely. Also the cxf rs
Thanks for the confirmation. This is exactly what I had expected. The client
will either have to accept queue manager to queue manager, or buy another
copy of WebSphere MQ :)
Thanks.
--
View this message in context:
00015000144687451015000L X45011S**SCPFI20110527RT
It seems that the BindyFixedLengthFactory is not obtaining correctly the
value for field9,
it format the value 20110527 into a date, but it picks up 50001440 instead.
I am using version 2.7.1,
is FixedLength unmarshalling
Hi all,
As suggested by book/documentation I'm using adviceWith method to add
interceptors to my existing routes, like this:
for (int i = 0; i camelContext.getRouteDefinitions().size();
i++) {
Hi,
As previously stated[1] I'm creating a RESTful webservice, defined by this :
public class RestComputationService implements ComputationService {
@POST
@Path(/computation)
@Consumes(text/xml)
@Produces(text/xml)
@Override
public Response compute(Request request) {
p
This is my route configuration for test. I think I am using the rigth
bindy..
/p
code
@Configuration
public static class ContextConfig extends SingleRouteCamelConfiguration
{
BindyFixedLengthDataFormat camelDataFormat = new
BindyFixedLengthDataFormat(
Dear list,
Looking at Bindy [1], I wondered whether it had sub-byte support. Let
me explain:
Imagine two 4-bit Integers, packed as one byte. Could you use Bindy to
extract both of them?
Cheers,
Johannes
[1] http://camel.apache.org/bindy.html
Think green - keep it on the screen.
On Friday, May 27, 2011, Klug, Johannes johannes.k...@logica.com wrote:
Dear list,
Looking at Bindy [1], I wondered whether it had sub-byte support. Let
me explain:
Imagine two 4-bit Integers, packed as one byte. Could you use Bindy to
extract both of them?
No that is not possible. We
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
On Friday, May 27, 2011, Klug, Johannes johannes.k...@logica.com wrote:
Looking at Bindy [1], I wondered whether it had sub-byte support.
Let me explain:
Imagine two 4-bit Integers, packed as one byte. Could you use Bindy
to extract
Hi
Yeah it seems odd why the field at position 9 is not grabbing further
into the text, where the date is.
Fell free to create a JIRA ticket and attach an unit test showing the
problem. Then we can use that to fix the bug.
On Fri, May 27, 2011 at 11:41 AM, cconesa
Hi, is there a straightforward way to define a bidirectional route? This
would greatly simplify maintenance by avoiding duplicate definitions of
the entities like in the example below.
!-- ICF --
route
from
Hi,
I did a little digging and it turns out that the QuickfixJ Converter creates
an in-only exchange... Not sure why, but then again I am not very conversant
with Quickfix and the message exchange patterns it supports.
If the exchange can be made to be an in-out exchange and the the Quickfix
Hi,
There are 2 ways to do this.
a Static: You do not get rid of the interceptor (i.e the interceptor does
get invoked but you eject immediately if a header value (boolean) is set in
the payload. This will allow you to switch the interceptor code on/off on
demand.
b Dynamic: You stop to the
Hi,
The Camel documentation contains the following statement about the Loop
pattern:
The Loop allows to process a message a number of times and possibly process
them in a different way.
This seems to imply that the same input message will be processed by the
downstream pipeline with each
How about using Exchange.copy() to pass a copy of the exchange to the
downstream processor, so that the original exchange doesn't get
changed?
Don
On Fri, May 27, 2011 at 12:36 PM, Greg McFall gregory.mcf...@gmail.com wrote:
Hi,
The Camel documentation contains the following statement about
Don,
I don't understand what you are proposing. How would I swap out the
exchange?
~ Greg
On Fri, May 27, 2011 at 12:54 PM, Donald Whytock dwhyt...@gmail.com wrote:
How about using Exchange.copy() to pass a copy of the exchange to the
downstream processor, so that the original exchange
Create a CopyProcessor, along the lines of:
public class CopyProcessor implements Processor
{
Processor processor;
public CopyProcessor(Processor processor)
{ this.processor = processor; }
public void process(Exchange exchange) throws Exception
{
I tried based on your suggestions I got ConnectException connection refused
:connect
java.net.ConnectException: Connection refused: connect
I am sure email address is correct and password is correct , Please tell
me what could cause connection problems and
I am testing this with my work
Also try IMAP
See here for details; http://camel.apache.org/mail.html
If the defaults are no good, your admin guy should be able to help.
Taariq
On 27 May 2011, at 9:02 PM, fachhoch fachh...@gmail.com wrote:
I tried based on your suggestions I got ConnectException connection refused
:connect
Don,
Yes, that might work. But I have two issues:
1. This solution requires that I somehow build the downstream Processor
that I will pass as an argument to the constructor. This is certainly
possible, but it does not mesh well with the fluid Java DSL.
2. It seems to me that I should not
OK. It's done
https://issues.apache.org/jira/browse/CAMEL-4024
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-to-HDFS-large-gzipped-files-tp3192431p4433386.html
Sent from the Camel - Users mailing list archive at Nabble.com.
1. The CopyProcessor, yes, that doesn't currently exist. The
processor to hand to the CopyProcessor should be whatever you're using
already. If you're just sending the message to an endpoint over and
over, it could be an instance of SendProcessor(endpoint).
2. I don't think it's a bug. A given
Don,
If the LoopProcessor was intentionally designed so that the output from one
iteration is used as input to the next iteration, then the documentation
should say so.
The current documentation is misleading because it implies a different
behavior. It implies that the original message is
Have you tried using inOnly()? As in
from(start).loop(3).inOnly().to(endpoint);
On Fri, May 27, 2011 at 5:34 PM, Greg McFall gregory.mcf...@gmail.com wrote:
Don,
If the LoopProcessor was intentionally designed so that the output from one
iteration is used as input to the next iteration, then
I just tried it. Sadly, the inOnly() trick does not work.
On Fri, May 27, 2011 at 5:50 PM, Donald Whytock dwhyt...@gmail.com wrote:
Have you tried using inOnly()? As in
from(start).loop(3).inOnly().to(endpoint);
On Fri, May 27, 2011 at 5:34 PM, Greg McFall gregory.mcf...@gmail.com
wrote:
Hi Andreas,
Thanks for the feedback.
1. So from what you are saying, it seems the classpath scanning is
broken for webstart. I searched for jira issues and the only one I
found is CAMEL-522 (reported by you; closed as fixed in Camel 1.5.0).
Is this a regression of the same issue? Should
Hmm... the proposed resolution did not work for me after all. I'm not
using xml configuration, so I didn't define the resolver as a bean,
however it's my understanding that I can call
context.setPackageScanClassResolver(). For example, my new test code:
CamelContext context = new
FYI I opened a new JIRA issue at
https://issues.apache.org/jira/browse/CAMEL-4026.
On 5/26/2011 9:23 PM, Kuhtz, Andreas wrote:
Hi,
I had the same problem and the solution is easy. Just create a class
that implements PackageScanClassResolver and define it as bean [1].
Camel will find it
35 matches
Mail list logo
