Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
When you use in XML document it has to be written as amp; as single
starts escape sequences in XML. The same goes to '' that is written
as lt; and to other special symbols.
Roman
2009/8/3 SoaMattH matt...@netpacket.com.au:
The #{} is my custom place holder configurer.
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/;/
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 problem: Failed to import bean definitions from relative
location [Camel-Context.xml]
Offending resource: ServletContext resource
[/WEB-INF/ApplicationContext.xml]; nested exception is
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
30 in XML document from ServletContext resource [/WEB-INF/Camel-Context.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: The reference
to entity moveNamePrefix must end with the ';' delimiter.
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
Thanks Matt
SoaMattH wrote:
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException:
Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
What should I defint it as?
Thanks Matt
cmoulliard wrote:
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.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: There are 2 parameters that couldn't be set on the endpoint.
Check the uri if the parameters are spelt correctly and that they are
properties of the endpoint. Unknown parameters=[{moveNamePrefix=../done/,
preMoveNamePrefix=inprogress/}]
at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
The #{} is my custom place holder configurer.
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/;/
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 problem: Failed to import bean definitions from relative
location [Camel-Context.xml]
Offending resource: ServletContext resource
[/WEB-INF/ApplicationContext.xml]; nested exception is
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
30 in XML document from ServletContext resource [/WEB-INF/Camel-Context.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: The reference
to entity moveNamePrefix must end with the ';' delimiter.
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
Thanks Matt
SoaMattH wrote:
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException:
Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
What should I defint it as?
Thanks Matt
cmoulliard wrote:
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.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: There are 2 parameters that couldn't be set on the endpoint.
Check the uri if the parameters are spelt correctly and that they are
properties of the endpoint. Unknown parameters=[{moveNamePrefix=../done/,
preMoveNamePrefix=inprogress/}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:356)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55)
at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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 http://camel.apache.org/manual/camel-manual-2.0-SNAPSHOT.pdf
Under the heading
Camel 2.x URI Options
is telling me to use preMoveNamePrefix and moveNamePrefix
Where I should be using
preMove and move
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMove=#{omsws.incident.file.processing}amp;move=#{omsws.incident.file.processed}/
http://camel.apache.org/file2.html is more upto date than the PDF.
Matt
RomKal wrote:
When you use in XML document it has to be written as amp; as single
starts escape sequences in XML. The same goes to '' that is written
as lt; and to other special symbols.
Roman
2009/8/3 SoaMattH matt...@netpacket.com.au:
The #{} is my custom place holder configurer.
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/;/
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 problem: Failed to import bean definitions from relative
location [Camel-Context.xml]
Offending resource: ServletContext resource
[/WEB-INF/ApplicationContext.xml]; nested exception is
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
Line
30 in XML document from ServletContext resource
[/WEB-INF/Camel-Context.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: The
reference
to entity moveNamePrefix must end with the ';' delimiter.
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
Thanks Matt
SoaMattH wrote:
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException:
Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint.
Check
the uri if the parameters are spelt correctly and that they are
properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
What should I defint it as?
Thanks Matt
cmoulliard wrote:
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
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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, SoaMattHmatt...@netpacket.com.au wrote:
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 http://camel.apache.org/manual/camel-manual-2.0-SNAPSHOT.pdf
Under the heading
Camel 2.x URI Options
is telling me to use preMoveNamePrefix and moveNamePrefix
Where I should be using
preMove and move
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMove=#{omsws.incident.file.processing}amp;move=#{omsws.incident.file.processed}/
http://camel.apache.org/file2.html is more upto date than the PDF.
Matt
RomKal wrote:
When you use in XML document it has to be written as amp; as single
starts escape sequences in XML. The same goes to '' that is written
as lt; and to other special symbols.
Roman
2009/8/3 SoaMattH matt...@netpacket.com.au:
The #{} is my custom place holder configurer.
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/;/
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 problem: Failed to import bean definitions from relative
location [Camel-Context.xml]
Offending resource: ServletContext resource
[/WEB-INF/ApplicationContext.xml]; nested exception is
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
Line
30 in XML document from ServletContext resource
[/WEB-INF/Camel-Context.xml]
is invalid; nested exception is org.xml.sax.SAXParseException: The
reference
to entity moveNamePrefix must end with the ';' delimiter.
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
Thanks Matt
SoaMattH wrote:
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint: incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException:
Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint.
Check
the uri if the parameters are spelt correctly and that they are
properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException: Failed
to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
What should I defint it as?
Thanks Matt
cmoulliard wrote:
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.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: There are 2 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{moveNamePrefix=../done/,
preMoveNamePrefix=inprogress/}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:356)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55)
at org.apache.camel.model.RouteType.resolveEndpoint(RouteType.java:133)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:103)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109)
at org.apache.camel.model.FromType.resolveEndpoint(FromType.java:72)
at
org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:78)
at org.apache.camel.model.RouteType.addRoutes(RouteType.java:302)
at org.apache.camel.model.RouteType.addRoutes(RouteType.java:121)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:459)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:735)
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:717)
at
org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165)
at
org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:50)
at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;
eg the above two options should be separated with and not semi colon.
On Mon, Aug 3, 2009 at 6:57 AM, SoaMattHmatt...@netpacket.com.au wrote:
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
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/ /
Every thing works fine .
If I say
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/moveNamePrefix=#{omsws.incident.file.processed}/
/
where in my properties
#
# Incident File Processing.
#
omsws.incident.file.landingzone=D:/matt-dev/incident/landingzone
omsws.incident.file.processing=D:/matt-dev/incident/processing
omsws.incident.file.processed=D:/matt-dev/incident/processed
omsws.incident.file.deadletter=D:/matt-dev/incident/deadletter
I get a validation Error
The reference to entity moveNamePrefix must end with the ';' delimiter.
If I change it to
camel:endpoint id=incidentFileEndpoint
uri=file://#{omsws.incident.file.landingzone}/?preMoveNamePrefix=#{omsws.incident.file.processing}/;moveNamePrefix=#{omsws.incident.file.processed}/;
/
No validation errors, I rebuild and deploy I get:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
incidentFileEndpoint due to: Error creating bean with name
'incidentFileEndpoint': FactoryBean threw exception on object creation;
nested exception is org.apache.camel.ResolveEndpointFailedException: Failed
to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: Failed to resolve endpoint:
file://D:/matt-dev/incident/landingzone/?preMoveNamePrefix=D%3A%2Fmatt-dev%2Fincident%2Fprocessing%2F%3BmoveNamePrefix%3DD%3A%2Fmatt-dev%2Fincident%2Fprocessed%2F%3B
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown
parameters=[{preMoveNamePrefix=D:/matt-dev/incident/processing/;moveNamePrefix=D:/matt-dev/incident/processed/;}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:404)
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
org.springframework.beans.factory.support.FactoryBeanRegistrySupport$1.run(FactoryBeanRegistrySupport.java:127)
at java.security.AccessController.doPrivileged(Native Method)
What should I defint it as?
Thanks Matt
cmoulliard wrote:
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.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: There are 2 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{moveNamePrefix=../done/,
preMoveNamePrefix=inprogress/}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:356)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55)
at org.apache.camel.model.RouteType.resolveEndpoint(RouteType.java:133)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:103)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109)
at org.apache.camel.model.FromType.resolveEndpoint(FromType.java:72)
at
org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:78)
at org.apache.camel.model.RouteType.addRoutes(RouteType.java:302)
at org.apache.camel.model.RouteType.addRoutes(RouteType.java:121)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:459)
at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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 cmoulli...@gmail.com wrote:
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.renameFile(GenericFileExpressionRenamer.java:41)
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:57)
at
org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231)
at
org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185)
at
org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57)
at
org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:106)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
at
org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87)
at
org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82)
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
at
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170)
at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103)
at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
with the following configuration :
from uri=file://d:/temp/data/?moveExpression=../done/${file:name} /
Any idea ?
Regards,
Claus Ibsen-2 wrote:
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, cmoulliard cmoulli...@gmail.com wrote:
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.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve
endpoint:
file://d:/temp/data/?preMoveNamePrefix=inprogress/moveNamePrefix=../done/
due to: There are 2 parameters that couldn't be set on the endpoint.
Check
the uri if the parameters are spelt correctly and that they are
properties
of the endpoint. Unknown parameters=[{moveNamePrefix=../done/,
preMoveNamePrefix=inprogress/}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:356)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:55)
at
org.apache.camel.model.RouteType.resolveEndpoint(RouteType.java:133)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:103)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109)
at
org.apache.camel.model.FromType.resolveEndpoint(FromType.java:72)
at
org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:78)
at
org.apache.camel.model.RouteType.addRoutes(RouteType.java:302)
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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.component.file.GenericFileOperationFailedException: Cannot rename file: GenericFile[d:\temp\data\csv.txt] to: GenericFile[d:\temp\done\csv.txt] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.renameFile(GenericFileRenameProcessStrategy.java:82) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:58) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) cmoulliard wrote: 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 cmoulli...@gmail.com wrote: 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.renameFile(GenericFileExpressionRenamer.java:41) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:57) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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 cmoulli...@gmail.com wrote: 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.component.file.GenericFileOperationFailedException: Cannot rename file: GenericFile[d:\temp\data\csv.txt] to: GenericFile[d:\temp\done\csv.txt] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.renameFile(GenericFileRenameProcessStrategy.java:82) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:58) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) cmoulliard wrote: 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 cmoulli...@gmail.com wrote: 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.renameFile(GenericFileExpressionRenamer.java:41) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:57) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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, 2009 at 10:36 AM, cmoulliard cmoulli...@gmail.com wrote: 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.component.file.GenericFileOperationFailedException: Cannot rename file: GenericFile[d:\temp\data\csv.txt] to: GenericFile[d:\temp\done\csv.txt] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.renameFile(GenericFileRenameProcessStrategy.java:82) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:58) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) cmoulliard wrote: 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 cmoulli...@gmail.com wrote: 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.renameFile(GenericFileExpressionRenamer.java:41) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:57) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at
Re: Camel 2.0-snapshot deployed on SMKNL4 - There are 2 parameters that couldn't be set on the endpoint
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 cmoulli...@gmail.com wrote: 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, 2009 at 10:36 AM, cmoulliard cmoulli...@gmail.com wrote: 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.component.file.GenericFileOperationFailedException: Cannot rename file: GenericFile[d:\temp\data\csv.txt] to: GenericFile[d:\temp\done\csv.txt] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.renameFile(GenericFileRenameProcessStrategy.java:82) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:58) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.process(StreamCachingInterceptor.java:82) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52) at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:170) at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:103) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) cmoulliard wrote: 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 cmoulli...@gmail.com wrote: 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.renameFile(GenericFileExpressionRenamer.java:41) at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:57) at org.apache.camel.component.file.GenericFileConsumer.processStrategyCommit(GenericFileConsumer.java:231) at org.apache.camel.component.file.GenericFileConsumer$1.done(GenericFileConsumer.java:185) at org.apache.camel.processor.UnitOfWorkProcessor$1.done(UnitOfWorkProcessor.java:57) at org.apache.camel.management.InstrumentationProcessor$1.done(InstrumentationProcessor.java:74) at org.apache.camel.processor.Pipeline.process(Pipeline.java:106) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.processor.interceptor.StreamCachingInterceptor.proceed(StreamCachingInterceptor.java:87) at
