Hi
Yeah the pdf was linking to the Camel 1.x file/ftp components.
Have changed that to link to Camel 2.x in the future.
The file/ftp components has been redone in Camel 2.0 so many options
is not the same.
Glad you got it sorted using the correct values.
On Mon, Aug 3, 2009 at 3:51 PM, SoaMatt
I have tried all of the escaping of special characters that does not seem to
be the problem.
That was one of the very first things I did when I first wrote the end
Point.
The escaping is noise to the real problem!!
The problem is the documentation I have is not quite right .
page 301 of ht
On Mon, Aug 3, 2009 at 2:03 PM, Roman
Kalukiewicz wrote:
> When you use & in XML document it has to be written as & as single
> & starts escape sequences in XML. The same goes to '<' that is written
> as < and to other special symbols.
>
Ah yeah how many times have people not been fooled with the
The #{} is my custom place holder configurer.
If I put a & in as aseperator I get validation error:
The reference to entity "moveNamePrefix" must End with the ';' delimiter
and the following Exception:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration
When you use & in XML document it has to be written as & as single
& starts escape sequences in XML. The same goes to '<' that is written
as < and to other special symbols.
Roman
2009/8/3 SoaMattH :
>
> The #{} is my custom place holder configurer.
>
>
> uri="file://#{omsws.incident.file.landing
Hi
Is the syntax #{ } some sort of Spring property place holders?
Its definitely not Camel using this syntax.
But the problem looks like its this mehanism that cannot set the
replaced values correctly.
Since it gets dual options combined into a single option
preMoveNamePrefix=D:/matt-dev/inciden
I am A little confuses as to how my Enpoint should be configured
when trying to add properties and delimiters?
I am Utilising Camel 2.0M3
If I say
Every thing works fine .
If I say
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incide
Yes Claus. Unfortunately, I work on a Windows XP machine.
I confirm that sometimes I have the error and sometimes I don't.
Claus Ibsen-2 wrote:
>
> Hi
>
> Are you by any chance running on Windows platform? I am just curious
> as we have got a report on windows with 1.x sometimes can not move
Hi
Are you by any chance running on Windows platform? I am just curious
as we have got a report on windows with 1.x sometimes can not move
file after processing.
On Tue, Mar 3, 2009 at 11:31 AM, cmoulliard wrote:
>
> You are right ;-) The file was locked by another application.
>
>
> Claus Ibse
You are right ;-) The file was locked by another application.
Claus Ibsen-2 wrote:
>
> It is trying to delete the file first. Are you sure its not locked or
> something by another app.
>
> Could you try again and be sure the existing file is not open by some
> other apps.
>
>
> On Tue, Mar 3
It is trying to delete the file first. Are you sure its not locked or
something by another app.
Could you try again and be sure the existing file is not open by some
other apps.
On Tue, Mar 3, 2009 at 10:36 AM, cmoulliard wrote:
>
> I don't if this point must be fixed or not but when a file alr
I don't if this point must be fixed or not but when a file already exist in
the 'done' directory, then the following error is generated :
2009-03-03 10:34:00,937 ERROR FileConsumer - Cannot rename file:
GenericFile[d:\temp\data\csv.txt] to: GenericFile[d:\temp\done\csv.txt]
org.apache.camel.comp
On Tue, Mar 3, 2009 at 10:32 AM, cmoulliard wrote:
>
> OK. By the way it works fine with absolute paths.
I will commit a fix in a few mins with the patch for the relative to
work as well.
Could you try this on your system?
>
>
> Claus Ibsen-2 wrote:
>>
>> The problem is that you mix and match abs
OK. By the way it works fine with absolute paths.
Claus Ibsen-2 wrote:
>
> The problem is that you mix and match absolute with relative.
>
> I will add a fix but you should also use absolute paths for the move
> expression as a workaround.
>
>
> On Tue, Mar 3, 2009 at 10:16 AM, cmoulliard w
The problem is that you mix and match absolute with relative.
I will add a fix but you should also use absolute paths for the move
expression as a workaround.
On Tue, Mar 3, 2009 at 10:16 AM, cmoulliard wrote:
>
> Hi claus,
>
> I receive the following error :
>
> 2009-03-03 10:09:41,859 ERROR F
Hi claus,
I receive the following error :
2009-03-03 10:09:41,859 ERROR FileConsumer -
java.lang.NullPointerException
at
org.apache.camel.component.file.GenericFile.changeFileName(GenericFile.java:119)
at
org.apache.camel.component.file.strategy.GenericFileExpressionRenamer.ren
Hi
The option for file have changed in camel 2.0. See:
http://camel.apache.org/file2.html
All the pre/postfix etc. is based on expressions now. So it should be
something like this:
moveExpression=../done/${file:name}
preMoveExpression=inprogress/${file:name}
On Mon, Mar 2, 2009 at 5:40 PM, cmo
Hi,
The following error is reported when I deploy a camel project on Service Mix
Kernel 1.1.0 snashot where Camel-2.0 SNAPSHOT osgi bundle is deployed ?
17:36:17,640 | ERROR | xtenderThread-15 | OsgiBundleXmlApplicationContext |
gatedExecutionApplicationContext 366 | Post refresh error
org.apa
18 matches
Mail list logo
