[jira] [Commented] (CAMEL-7752) filter with camel sftp is returnin NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111914#comment-14111914
]
Claus Ibsen commented on CAMEL-7752:
And where is the NPE. You must report that, eg post the stacktrace you get.
Also next time use the user forum / mailing list first as we ask people to do.
And only report JIRAs if we say so
filter with camel sftp is returnin NullPointerException
---
Key: CAMEL-7752
URL: https://issues.apache.org/jira/browse/CAMEL-7752
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.0
Environment: Windows 7, RedHat Linux 5.x
Reporter: Raghavan
Labels: GenericFile, camel-ftp, filter, ftp
We are testing camel sftp with filter options to restrict the source files
using a pattern.
We get a NullPointerException when try to use a filter (CustomFilter)
Attached herewith the code snippet
[[CodeSnippet]]
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
camel:propertyPlaceholder id=ftpadapterProperty
location=classpath:ftpadapter.properties/
!-- The file filter is to be tested --
route
from
uri=sftp://{{ftp.user}}@{{ftp.host}}/{{ftp.remote.dir}}?password={{ftp.pwd}}amp;separator=UNIXamp;recursive={{ftp.dir.recursive}}amp;binary=trueamp;delete={{ftp.deletefiles}}amp;stepwise={{ftp.stepwise}}amp;delay={{ftp.pollinginterval}}amp;filter=#fileFilter/
to
uri=file://{{local.dir}}?fileName=${date:now:MMddhhmmss}_${file:onlyname.noext}.${file:ext}/
log message=Routing message from remote server to
target folder with data ${body} /
/route
/camelContext
bean id=fileFilter class=org.myapp.ftpadapter.FileFilter/
/beans
FileFilter src:
public class FileFilterT implements GenericFileFilterT {
private static Logger logger =
LoggerFactory.getLogger(FileFilter.class);
/* The purpose of this method is to apply a custom filter based on file
pattern
* This enables the ftp adapter to filter files based on the criteria
implemented here
* (non-Javadoc)
* @see
org.apache.camel.component.file.GenericFileFilter#accept(org.apache.camel.component.file.GenericFile)
*/
public boolean accept(GenericFileT file) {
if(logger.isDebugEnabled()) {
logger.debug(IsDirectory= + file.isDirectory());
logger.debug(FileName=+file.getFileName());
}
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
else {
return false;
}
}
}
[[/CodeSnippet]]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CAMEL-7673) subscribeTopicName leaks out as a property and used as a destination for mqtt producer, causes infinite delivery
[
https://issues.apache.org/jira/browse/CAMEL-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-7673.
-
Resolution: Fixed
Fix Version/s: 2.14.0
Introduced CamelMQTTSubscribeTopic for MQTTConsumer and CamelMQTTPublishTopic
MQTTProducer in camel master branch.
subscribeTopicName leaks out as a property and used as a destination for mqtt
producer, causes infinite delivery
Key: CAMEL-7673
URL: https://issues.apache.org/jira/browse/CAMEL-7673
Project: Camel
Issue Type: Bug
Components: camel-mqtt
Affects Versions: 2.12.2, 2.14.0
Reporter: Tomohisa Igarashi
Assignee: Willem Jiang
Fix For: 2.14.0
MQTT consumer sets its subscribeTopicName as a exchange property, and it will
be used by MQTT producer as a destination if it exists in the route.
If you have a following route:
{code}
from(mqtt:input?subscribeTopicName=topicIn)
.to(mqtt:output?publishTopicName=topicOut);
{code}
MQTT consumer put topicIn to MQTTTopicPropertyName exchange property, and
MQTT producer uses this property to determine a destination topic to publish.
Then MQTT producer ignores publishTopicName and send a message to topicIn,
so MQTT consumer consumes the message again, eventually it causes infinite
delivery. We need to stop this property to be used as a destination for
producer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7752) filter with camel sftp is returnin NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111944#comment-14111944
]
Raghavan commented on CAMEL-7752:
-
The NPE is raised under
return file.getFileName().endsWith(.xml);
So added the if condition to check the file object and observed that
getFileName was returning null
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
filter with camel sftp is returnin NullPointerException
---
Key: CAMEL-7752
URL: https://issues.apache.org/jira/browse/CAMEL-7752
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.0
Environment: Windows 7, RedHat Linux 5.x
Reporter: Raghavan
Labels: GenericFile, camel-ftp, filter, ftp
We are testing camel sftp with filter options to restrict the source files
using a pattern.
We get a NullPointerException when try to use a filter (CustomFilter)
Attached herewith the code snippet
[[CodeSnippet]]
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
camel:propertyPlaceholder id=ftpadapterProperty
location=classpath:ftpadapter.properties/
!-- The file filter is to be tested --
route
from
uri=sftp://{{ftp.user}}@{{ftp.host}}/{{ftp.remote.dir}}?password={{ftp.pwd}}amp;separator=UNIXamp;recursive={{ftp.dir.recursive}}amp;binary=trueamp;delete={{ftp.deletefiles}}amp;stepwise={{ftp.stepwise}}amp;delay={{ftp.pollinginterval}}amp;filter=#fileFilter/
to
uri=file://{{local.dir}}?fileName=${date:now:MMddhhmmss}_${file:onlyname.noext}.${file:ext}/
log message=Routing message from remote server to
target folder with data ${body} /
/route
/camelContext
bean id=fileFilter class=org.myapp.ftpadapter.FileFilter/
/beans
FileFilter src:
public class FileFilterT implements GenericFileFilterT {
private static Logger logger =
LoggerFactory.getLogger(FileFilter.class);
/* The purpose of this method is to apply a custom filter based on file
pattern
* This enables the ftp adapter to filter files based on the criteria
implemented here
* (non-Javadoc)
* @see
org.apache.camel.component.file.GenericFileFilter#accept(org.apache.camel.component.file.GenericFile)
*/
public boolean accept(GenericFileT file) {
if(logger.isDebugEnabled()) {
logger.debug(IsDirectory= + file.isDirectory());
logger.debug(FileName=+file.getFileName());
}
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
else {
return false;
}
}
}
[[/CodeSnippet]]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CAMEL-7628) Incorrect tests of quartz2 component
[ https://issues.apache.org/jira/browse/CAMEL-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7628. Resolution: Fixed Assignee: Claus Ibsen Thanks for the patch. Incorrect tests of quartz2 component Key: CAMEL-7628 URL: https://issues.apache.org/jira/browse/CAMEL-7628 Project: Camel Issue Type: Test Components: camel-quartz, camel-quartz2 Reporter: Nikolay Turpitko Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.0 Attachments: 0001-Fix-SpringQuartzPersistentStoreTest.patch, 0002-Fix-SpringQuartzPersistentStoreRestart-Test.patch There are errors in tests of quartz2 component with persistent store such as org.apache.camel.component.quartz2.SpringQuartzPersistentStoreTest. It's application context configuration resides in file org/apache/camel/component/quartz2/SpringQuartzPersistentStoreTest.xml. Which has a suspicious issue in it: scheduler bean, which is configured to use DB, further passed to bean with id quartz, but in the endpoint's uri in the route the bean with id quartz2 used. I'm afraid, this test ignores configured quartz bean, scheduler bean, datasource and database. I provided patches to fix incorrect tests. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7752) filter with camel sftp is returnin NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111955#comment-14111955
]
Claus Ibsen commented on CAMEL-7752:
Use getFileNameOnly()
filter with camel sftp is returnin NullPointerException
---
Key: CAMEL-7752
URL: https://issues.apache.org/jira/browse/CAMEL-7752
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.0
Environment: Windows 7, RedHat Linux 5.x
Reporter: Raghavan
Labels: GenericFile, camel-ftp, filter, ftp
We are testing camel sftp with filter options to restrict the source files
using a pattern.
We get a NullPointerException when try to use a filter (CustomFilter)
Attached herewith the code snippet
[[CodeSnippet]]
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
camel:propertyPlaceholder id=ftpadapterProperty
location=classpath:ftpadapter.properties/
!-- The file filter is to be tested --
route
from
uri=sftp://{{ftp.user}}@{{ftp.host}}/{{ftp.remote.dir}}?password={{ftp.pwd}}amp;separator=UNIXamp;recursive={{ftp.dir.recursive}}amp;binary=trueamp;delete={{ftp.deletefiles}}amp;stepwise={{ftp.stepwise}}amp;delay={{ftp.pollinginterval}}amp;filter=#fileFilter/
to
uri=file://{{local.dir}}?fileName=${date:now:MMddhhmmss}_${file:onlyname.noext}.${file:ext}/
log message=Routing message from remote server to
target folder with data ${body} /
/route
/camelContext
bean id=fileFilter class=org.myapp.ftpadapter.FileFilter/
/beans
FileFilter src:
public class FileFilterT implements GenericFileFilterT {
private static Logger logger =
LoggerFactory.getLogger(FileFilter.class);
/* The purpose of this method is to apply a custom filter based on file
pattern
* This enables the ftp adapter to filter files based on the criteria
implemented here
* (non-Javadoc)
* @see
org.apache.camel.component.file.GenericFileFilter#accept(org.apache.camel.component.file.GenericFile)
*/
public boolean accept(GenericFileT file) {
if(logger.isDebugEnabled()) {
logger.debug(IsDirectory= + file.isDirectory());
logger.debug(FileName=+file.getFileName());
}
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
else {
return false;
}
}
}
[[/CodeSnippet]]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7752) filter with camel sftp is returnin NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14111996#comment-14111996
]
Raghavan commented on CAMEL-7752:
-
Thanks Claus. Using getFileNameOnly() fixed the issue related to files
However with filter in place, even with recursive=true, the files under
subDirectories are not read in the filter.
For e.g.
/home/user1
a.xml [processed successfully]
b.txt[ignored as expected]
folder1/c.xml [not read]
folder2/d.xml [not read]
filter with camel sftp is returnin NullPointerException
---
Key: CAMEL-7752
URL: https://issues.apache.org/jira/browse/CAMEL-7752
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.0
Environment: Windows 7, RedHat Linux 5.x
Reporter: Raghavan
Labels: GenericFile, camel-ftp, filter, ftp
We are testing camel sftp with filter options to restrict the source files
using a pattern.
We get a NullPointerException when try to use a filter (CustomFilter)
Attached herewith the code snippet
[[CodeSnippet]]
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
camel:propertyPlaceholder id=ftpadapterProperty
location=classpath:ftpadapter.properties/
!-- The file filter is to be tested --
route
from
uri=sftp://{{ftp.user}}@{{ftp.host}}/{{ftp.remote.dir}}?password={{ftp.pwd}}amp;separator=UNIXamp;recursive={{ftp.dir.recursive}}amp;binary=trueamp;delete={{ftp.deletefiles}}amp;stepwise={{ftp.stepwise}}amp;delay={{ftp.pollinginterval}}amp;filter=#fileFilter/
to
uri=file://{{local.dir}}?fileName=${date:now:MMddhhmmss}_${file:onlyname.noext}.${file:ext}/
log message=Routing message from remote server to
target folder with data ${body} /
/route
/camelContext
bean id=fileFilter class=org.myapp.ftpadapter.FileFilter/
/beans
FileFilter src:
public class FileFilterT implements GenericFileFilterT {
private static Logger logger =
LoggerFactory.getLogger(FileFilter.class);
/* The purpose of this method is to apply a custom filter based on file
pattern
* This enables the ftp adapter to filter files based on the criteria
implemented here
* (non-Javadoc)
* @see
org.apache.camel.component.file.GenericFileFilter#accept(org.apache.camel.component.file.GenericFile)
*/
public boolean accept(GenericFileT file) {
if(logger.isDebugEnabled()) {
logger.debug(IsDirectory= + file.isDirectory());
logger.debug(FileName=+file.getFileName());
}
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
else {
return false;
}
}
}
[[/CodeSnippet]]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CAMEL-7753) xslt component - Store warning/errors etc as exchange properties so end users can get hold of those
Claus Ibsen created CAMEL-7753: -- Summary: xslt component - Store warning/errors etc as exchange properties so end users can get hold of those Key: CAMEL-7753 URL: https://issues.apache.org/jira/browse/CAMEL-7753 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.0 If you use xslt:message to output an error and terminate the xslt processing, then you cannot get hold of the message, just some generic exception about xslt terminated. We should capture those warnings/error/fatal error messages the listener emits and store on exchange so end users can get hold of those details. An example http://www.w3schools.com/xsl/el_message.asp We should be able to get that artist is empty text message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
Charles Moulliard created CAMEL-7754: Summary: Property Trigger.timerZone is declared as contant but not implemented Key: CAMEL-7754 URL: https://issues.apache.org/jira/browse/CAMEL-7754 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.13.2, 2.12.1 Reporter: Charles Moulliard Fix For: 2.14.0 Seems that we have a problem with Quartz/Quartz2 components. The doc claims that we can setup this property in the URI trigger.timeZone (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz don't use it even if a constant is defined :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 We have the same issue too with quartz2 -- https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112037#comment-14112037
]
Charles Moulliard commented on CAMEL-7754:
--
Test case used
{code}
public class CamelQuartzTest extends CamelTestSupport {
@Test
public void testQuartzCronRoute() throws Exception {
MockEndpoint mock = getMockEndpoint(mock:result);
mock.expectedMinimumMessageCount(3);
assertMockEndpointsSatisfied();
JobDetail job =
mock.getReceivedExchanges().get(0).getIn().getHeader(jobDetail,
JobDetail.class);
assertNotNull(job);
assertEquals(cron,
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_TYPE));
assertEquals(UTC,
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_CRON_TIMEZONE)); // ERROR
assertEquals(0/2 * * * * ?trigger.timeZone=UTC,
job.getJobDataMap().get(QuartzConstants.QUARTZ_TRIGGER_CRON_EXPRESSION));
}
@Override
protected RouteBuilder createRouteBuilder() {
return new RouteBuilder() {
public void configure() {
from(quartz2://myGroup/myTimerName?cron=0/2+*+*+*+*+?trigger.timeZone=UTC).to(mock:result);
}
};
}
}
{code}
Property Trigger.timerZone is declared as contant but not implemented
-
Key: CAMEL-7754
URL: https://issues.apache.org/jira/browse/CAMEL-7754
Project: Camel
Issue Type: Bug
Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Fix For: 2.14.0
Seems that we have a problem with Quartz/Quartz2 components. The doc claims
that we can setup this property in the URI trigger.timeZone
(http://camel.apache.org/quartz.html - see specifying timezone ) but quartz
don't use it even if a constant is defined
:https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
We have the same issue too with quartz2 --
https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[ https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard reassigned CAMEL-7754: Assignee: Charles Moulliard Property Trigger.timerZone is declared as contant but not implemented - Key: CAMEL-7754 URL: https://issues.apache.org/jira/browse/CAMEL-7754 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.12.1, 2.13.2 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.14.0 Seems that we have a problem with Quartz/Quartz2 components. The doc claims that we can setup this property in the URI trigger.timeZone (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz don't use it even if a constant is defined :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 We have the same issue too with quartz2 -- https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112090#comment-14112090
]
Charles Moulliard commented on CAMEL-7754:
--
For Quartz 1, we should improve the QuartzComponent class to add the
CamelProperty QUARTZ_TRIGGER_CRON_TIMEZONE
{code}
// enrich job data map with trigger information
if (cron != null) {
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_TYPE,
cron);
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_EXPRESSION,
cron);
String timeZone =
EndpointHelper.resloveStringParameter(getCamelContext(),
(String)triggerParameters.get(timeZone), String.class);
if (timeZone != null) {
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_TIMEZONE,
timeZone);
}
}
{code}
Property Trigger.timerZone is declared as contant but not implemented
-
Key: CAMEL-7754
URL: https://issues.apache.org/jira/browse/CAMEL-7754
Project: Camel
Issue Type: Bug
Components: camel-quartz, camel-quartz2
Affects Versions: 2.12.1, 2.13.2
Reporter: Charles Moulliard
Fix For: 2.14.0
Seems that we have a problem with Quartz/Quartz2 components. The doc claims
that we can setup this property in the URI trigger.timeZone
(http://camel.apache.org/quartz.html - see specifying timezone ) but quartz
don't use it even if a constant is defined
:https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
We have the same issue too with quartz2 --
https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CAMEL-7755) Fix all karaf feature definitions
Guillaume Nodet created CAMEL-7755: -- Summary: Fix all karaf feature definitions Key: CAMEL-7755 URL: https://issues.apache.org/jira/browse/CAMEL-7755 Project: Camel Issue Type: Bug Components: karaf Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.14.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[ https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-7754 started by Charles Moulliard. Property Trigger.timerZone is declared as contant but not implemented - Key: CAMEL-7754 URL: https://issues.apache.org/jira/browse/CAMEL-7754 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.12.1, 2.13.2 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.14.0 Seems that we have a problem with Quartz/Quartz2 components. The doc claims that we can setup this property in the URI trigger.timeZone (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz don't use it even if a constant is defined :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 We have the same issue too with quartz2 -- https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[ https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles Moulliard resolved CAMEL-7754. -- Resolution: Fixed Property Trigger.timerZone is declared as contant but not implemented - Key: CAMEL-7754 URL: https://issues.apache.org/jira/browse/CAMEL-7754 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.12.1, 2.13.2 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.14.0 Seems that we have a problem with Quartz/Quartz2 components. The doc claims that we can setup this property in the URI trigger.timeZone (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz don't use it even if a constant is defined :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 We have the same issue too with quartz2 -- https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7754) Property Trigger.timerZone is declared as contant but not implemented
[ https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112116#comment-14112116 ] Charles Moulliard commented on CAMEL-7754: -- For Quartz2, the TimeZone property must be pass as parameter to the Trigger.newBuilder() Property Trigger.timerZone is declared as contant but not implemented - Key: CAMEL-7754 URL: https://issues.apache.org/jira/browse/CAMEL-7754 Project: Camel Issue Type: Bug Components: camel-quartz, camel-quartz2 Affects Versions: 2.12.1, 2.13.2 Reporter: Charles Moulliard Assignee: Charles Moulliard Fix For: 2.14.0 Seems that we have a problem with Quartz/Quartz2 components. The doc claims that we can setup this property in the URI trigger.timeZone (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz don't use it even if a constant is defined :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 We have the same issue too with quartz2 -- https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7756) org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency
Kevin Earls created CAMEL-7756: -- Summary: org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency Key: CAMEL-7756 URL: https://issues.apache.org/jira/browse/CAMEL-7756 Project: Camel Issue Type: Test Reporter: Kevin Earls Priority: Minor This test fails intermittently with the error below as it is using MockEndpoint.expectedBodiesReceived() even though it uses parallelProcessing() in the route. The test should use MockEndpoint.expectedBodiesReceivedInAnyOrder() instead java.lang.AssertionError: mock://complete Body of message: 0. Expected: finish but was: stop at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333) at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315) at org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628) at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:188) at org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:343) at org.apache.camel.issues.OnCompletionIssueTest.testOnCompletionIssue(OnCompletionIssueTest.java:39) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7756) org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency
[ https://issues.apache.org/jira/browse/CAMEL-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112132#comment-14112132 ] ASF GitHub Bot commented on CAMEL-7756: --- GitHub user kevinearls opened a pull request: https://github.com/apache/camel/pull/255 Fix for CAMEL-7756 OnCompletionIssueTest fails because of order dependen... ...cy You can merge this pull request into a Git repository by running: $ git pull https://github.com/kevinearls/camel CAMEL-7756 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/255.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #255 commit 2d7a2194c80fe7ffcd094b5cc343fd21104270d1 Author: Kevin Earls ke...@kevinearls.com Date: 2014-08-27T10:58:38Z Fix for CAMEL-7756 OnCompletionIssueTest fails because of order dependency org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency --- Key: CAMEL-7756 URL: https://issues.apache.org/jira/browse/CAMEL-7756 Project: Camel Issue Type: Test Reporter: Kevin Earls Priority: Minor This test fails intermittently with the error below as it is using MockEndpoint.expectedBodiesReceived() even though it uses parallelProcessing() in the route. The test should use MockEndpoint.expectedBodiesReceivedInAnyOrder() instead java.lang.AssertionError: mock://complete Body of message: 0. Expected: finish but was: stop at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333) at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315) at org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628) at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:188) at org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:343) at org.apache.camel.issues.OnCompletionIssueTest.testOnCompletionIssue(OnCompletionIssueTest.java:39) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated CAMEL-7750: - Attachment: camel-async-response-test.zip Incorrect response in case of using AsyncResponse-enabled JAX-RS2 endpoint. Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112145#comment-14112145 ] Michael B commented on CAMEL-7750: -- Not sure about the enhancement you mean, but i tried to reduce my project to demonstrate my issue and my error changed. Earlier no response was sent back when using AsyncResponse-enabled JAX-RS endpoint. But in the reduced example an another error occurs: a strange response is returned instead of the expected one. See the attached demo maven project. Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated CAMEL-7750: - Comment: was deleted (was: Incorrect response in case of using AsyncResponse-enabled JAX-RS2 endpoint.) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7753) xslt component - Store warning/errors etc as exchange properties so end users can get hold of those
[ https://issues.apache.org/jira/browse/CAMEL-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112162#comment-14112162 ] Claus Ibsen commented on CAMEL-7753: Saxon is a bit special, so we need to do some special code to hook it into use the jaxp error listener for xslt messages. https://stackoverflow.com/questions/4695489/capture-xslmessage-output-in-java xslt component - Store warning/errors etc as exchange properties so end users can get hold of those --- Key: CAMEL-7753 URL: https://issues.apache.org/jira/browse/CAMEL-7753 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.0 If you use xslt:message to output an error and terminate the xslt processing, then you cannot get hold of the message, just some generic exception about xslt terminated. We should capture those warnings/error/fatal error messages the listener emits and store on exchange so end users can get hold of those details. An example http://www.w3schools.com/xsl/el_message.asp We should be able to get that artist is empty text message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7757) camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream
Sandeep Poreddy created CAMEL-7757: -- Summary: camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream Key: CAMEL-7757 URL: https://issues.apache.org/jira/browse/CAMEL-7757 Project: Camel Issue Type: Bug Components: camel-restlet Affects Versions: 2.13.1 Environment: Windows 7 Professional 64 Bit, JBOSS EAP 6.1, Java 1.7.0_65, Camel 2.13.1 Reporter: Sandeep Poreddy Please refer to : http://camel.465427.n5.nabble.com/Came-2-13-1-Reading-ZipInputStream-EOFException-tt5755726.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112184#comment-14112184 ] Michael B commented on CAMEL-7750: -- Ah, the demo above gives different error probably because it is fully processed in the original http thread. And my app is doing some async backend calls, so end of the route actually should be called in another thread. I'll make additional demo project for that. Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7753) xslt component - Store warning/errors etc as exchange properties so end users can get hold of those
[ https://issues.apache.org/jira/browse/CAMEL-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7753. Resolution: Fixed xslt component - Store warning/errors etc as exchange properties so end users can get hold of those --- Key: CAMEL-7753 URL: https://issues.apache.org/jira/browse/CAMEL-7753 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.14.0 If you use xslt:message to output an error and terminate the xslt processing, then you cannot get hold of the message, just some generic exception about xslt terminated. We should capture those warnings/error/fatal error messages the listener emits and store on exchange so end users can get hold of those details. An example http://www.w3schools.com/xsl/el_message.asp We should be able to get that artist is empty text message. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7756) org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency
[ https://issues.apache.org/jira/browse/CAMEL-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112198#comment-14112198 ] ASF GitHub Bot commented on CAMEL-7756: --- Github user asfgit closed the pull request at: https://github.com/apache/camel/pull/255 org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency --- Key: CAMEL-7756 URL: https://issues.apache.org/jira/browse/CAMEL-7756 Project: Camel Issue Type: Test Reporter: Kevin Earls Priority: Minor This test fails intermittently with the error below as it is using MockEndpoint.expectedBodiesReceived() even though it uses parallelProcessing() in the route. The test should use MockEndpoint.expectedBodiesReceivedInAnyOrder() instead java.lang.AssertionError: mock://complete Body of message: 0. Expected: finish but was: stop at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333) at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315) at org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628) at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:188) at org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:343) at org.apache.camel.issues.OnCompletionIssueTest.testOnCompletionIssue(OnCompletionIssueTest.java:39) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7757) camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream
[ https://issues.apache.org/jira/browse/CAMEL-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Poreddy updated CAMEL-7757: --- Patch Info: Patch Available Labels: patch (was: ) camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream Key: CAMEL-7757 URL: https://issues.apache.org/jira/browse/CAMEL-7757 Project: Camel Issue Type: Bug Components: camel-restlet Affects Versions: 2.13.1 Environment: Windows 7 Professional 64 Bit, JBOSS EAP 6.1, Java 1.7.0_65, Camel 2.13.1 Reporter: Sandeep Poreddy Labels: patch Attachments: DefaultRestletBinding.java Please refer to : http://camel.465427.n5.nabble.com/Came-2-13-1-Reading-ZipInputStream-EOFException-tt5755726.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7757) camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream
[ https://issues.apache.org/jira/browse/CAMEL-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Poreddy updated CAMEL-7757: --- Attachment: DefaultRestletBinding.java Patch for the fix. camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream Key: CAMEL-7757 URL: https://issues.apache.org/jira/browse/CAMEL-7757 Project: Camel Issue Type: Bug Components: camel-restlet Affects Versions: 2.13.1 Environment: Windows 7 Professional 64 Bit, JBOSS EAP 6.1, Java 1.7.0_65, Camel 2.13.1 Reporter: Sandeep Poreddy Labels: patch Attachments: DefaultRestletBinding.java Please refer to : http://camel.465427.n5.nabble.com/Came-2-13-1-Reading-ZipInputStream-EOFException-tt5755726.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7756) org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency
[ https://issues.apache.org/jira/browse/CAMEL-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7756. Resolution: Fixed Fix Version/s: 2.14.0 Assignee: Claus Ibsen Thanks org.apache.camel.issues.OnCompletionIssueTest fails because of order dependency --- Key: CAMEL-7756 URL: https://issues.apache.org/jira/browse/CAMEL-7756 Project: Camel Issue Type: Test Reporter: Kevin Earls Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.0 This test fails intermittently with the error below as it is using MockEndpoint.expectedBodiesReceived() even though it uses parallelProcessing() in the route. The test should use MockEndpoint.expectedBodiesReceivedInAnyOrder() instead java.lang.AssertionError: mock://complete Body of message: 0. Expected: finish but was: stop at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333) at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315) at org.apache.camel.component.mock.MockEndpoint$5.run(MockEndpoint.java:628) at org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:394) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350) at org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:188) at org.apache.camel.ContextTestSupport.assertMockEndpointsSatisfied(ContextTestSupport.java:343) at org.apache.camel.issues.OnCompletionIssueTest.testOnCompletionIssue(OnCompletionIssueTest.java:39) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7403) Update camel-hl7 to support HAPI v2.2
[ https://issues.apache.org/jira/browse/CAMEL-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112325#comment-14112325 ] Claus Ibsen commented on CAMEL-7403: Tests still fail. Doing a mvn clean install on the camel-hl7 module. Using mvn 3.1.1 on osx with java 7 Update camel-hl7 to support HAPI v2.2 - Key: CAMEL-7403 URL: https://issues.apache.org/jira/browse/CAMEL-7403 Project: Camel Issue Type: Improvement Components: camel-hl7 Affects Versions: 2.13.0 Reporter: Christian Ohr Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.0 Attachments: 0073-Update-to-HAPI-2.2-use-HapiContext-as-primary-config.patch, 0074-use-of-HapiContext-throughout-the-component.patch, MessageValidator.patch Update camel-hl7 to the current HAPI version, introducing the concept of a HapiContext to bundle all configurations related to HL7 message handling (cf. http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/HapiContext.html). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7403) Update camel-hl7 to support HAPI v2.2
[
https://issues.apache.org/jira/browse/CAMEL-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112327#comment-14112327
]
Claus Ibsen commented on CAMEL-7403:
{code}
Running org.apache.camel.component.hl7.MessageValidatorTest
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.631 sec
FAILURE! - in org.apache.camel.component.hl7.MessageValidatorTest
testDynamicCustomHapiContext(org.apache.camel.component.hl7.MessageValidatorTest)
Time elapsed: 44.399 sec ERROR!
java.lang.Exception: Unexpected exception,
expectedorg.apache.camel.CamelExecutionException but
wasjava.lang.AssertionError
at
org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:1333)
at
org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:1315)
at
org.apache.camel.component.mock.MockEndpoint.doAssertIsSatisfied(MockEndpoint.java:383)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:362)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:350)
at
org.apache.camel.component.mock.MockEndpoint.assertIsSatisfied(MockEndpoint.java:188)
at
org.apache.camel.test.junit4.CamelTestSupport.assertMockEndpointsSatisfied(CamelTestSupport.java:675)
at
org.apache.camel.component.hl7.MessageValidatorTest.testDynamicCustomHapiContext(MessageValidatorTest.java:124)
{code}
Update camel-hl7 to support HAPI v2.2
-
Key: CAMEL-7403
URL: https://issues.apache.org/jira/browse/CAMEL-7403
Project: Camel
Issue Type: Improvement
Components: camel-hl7
Affects Versions: 2.13.0
Reporter: Christian Ohr
Assignee: Claus Ibsen
Priority: Minor
Fix For: 2.14.0
Attachments:
0073-Update-to-HAPI-2.2-use-HapiContext-as-primary-config.patch,
0074-use-of-HapiContext-throughout-the-component.patch, MessageValidator.patch
Update camel-hl7 to the current HAPI version, introducing the concept of a
HapiContext to bundle all configurations related to HL7 message handling (cf.
http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/HapiContext.html).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7403) Update camel-hl7 to support HAPI v2.2
[ https://issues.apache.org/jira/browse/CAMEL-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112332#comment-14112332 ] Claus Ibsen commented on CAMEL-7403: Thanks for that missing test. I pushed the code changes to master. Update camel-hl7 to support HAPI v2.2 - Key: CAMEL-7403 URL: https://issues.apache.org/jira/browse/CAMEL-7403 Project: Camel Issue Type: Improvement Components: camel-hl7 Affects Versions: 2.13.0 Reporter: Christian Ohr Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.0 Attachments: 0073-Update-to-HAPI-2.2-use-HapiContext-as-primary-config.patch, 0074-use-of-HapiContext-throughout-the-component.patch, MessageValidator.patch Update camel-hl7 to the current HAPI version, introducing the concept of a HapiContext to bundle all configurations related to HL7 message handling (cf. http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/HapiContext.html). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CAMEL-7752) filter with camel sftp is returnin NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-7752.
Resolution: Invalid
Assignee: Claus Ibsen
filter with camel sftp is returnin NullPointerException
---
Key: CAMEL-7752
URL: https://issues.apache.org/jira/browse/CAMEL-7752
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.0
Environment: Windows 7, RedHat Linux 5.x
Reporter: Raghavan
Assignee: Claus Ibsen
Labels: GenericFile, camel-ftp, filter, ftp
We are testing camel sftp with filter options to restrict the source files
using a pattern.
We get a NullPointerException when try to use a filter (CustomFilter)
Attached herewith the code snippet
[[CodeSnippet]]
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
camelContext xmlns=http://camel.apache.org/schema/spring;
camel:propertyPlaceholder id=ftpadapterProperty
location=classpath:ftpadapter.properties/
!-- The file filter is to be tested --
route
from
uri=sftp://{{ftp.user}}@{{ftp.host}}/{{ftp.remote.dir}}?password={{ftp.pwd}}amp;separator=UNIXamp;recursive={{ftp.dir.recursive}}amp;binary=trueamp;delete={{ftp.deletefiles}}amp;stepwise={{ftp.stepwise}}amp;delay={{ftp.pollinginterval}}amp;filter=#fileFilter/
to
uri=file://{{local.dir}}?fileName=${date:now:MMddhhmmss}_${file:onlyname.noext}.${file:ext}/
log message=Routing message from remote server to
target folder with data ${body} /
/route
/camelContext
bean id=fileFilter class=org.myapp.ftpadapter.FileFilter/
/beans
FileFilter src:
public class FileFilterT implements GenericFileFilterT {
private static Logger logger =
LoggerFactory.getLogger(FileFilter.class);
/* The purpose of this method is to apply a custom filter based on file
pattern
* This enables the ftp adapter to filter files based on the criteria
implemented here
* (non-Javadoc)
* @see
org.apache.camel.component.file.GenericFileFilter#accept(org.apache.camel.component.file.GenericFile)
*/
public boolean accept(GenericFileT file) {
if(logger.isDebugEnabled()) {
logger.debug(IsDirectory= + file.isDirectory());
logger.debug(FileName=+file.getFileName());
}
if(file !=null file.getFileName() != null) {
return file.getFileName().endsWith(.xml);
}
else {
return false;
}
}
}
[[/CodeSnippet]]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CAMEL-7403) Update camel-hl7 to support HAPI v2.2
[ https://issues.apache.org/jira/browse/CAMEL-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112382#comment-14112382 ] christian ohr commented on CAMEL-7403: -- Strange things going on here. mvn works for me (same version, just win7), but inside Idea I can reproduce your problem. In general the assumption for this test must be mock.expectedMessageCount(0);, not (1); but that does not fix it. Will look into it. Update camel-hl7 to support HAPI v2.2 - Key: CAMEL-7403 URL: https://issues.apache.org/jira/browse/CAMEL-7403 Project: Camel Issue Type: Improvement Components: camel-hl7 Affects Versions: 2.13.0 Reporter: Christian Ohr Assignee: Claus Ibsen Priority: Minor Fix For: 2.14.0 Attachments: 0073-Update-to-HAPI-2.2-use-HapiContext-as-primary-config.patch, 0074-use-of-HapiContext-throughout-the-component.patch, MessageValidator.patch Update camel-hl7 to the current HAPI version, introducing the concept of a HapiContext to bundle all configurations related to HL7 message handling (cf. http://hl7api.sourceforge.net/base/apidocs/ca/uhn/hl7v2/HapiContext.html). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14112484#comment-14112484 ] Michael B commented on CAMEL-7750: -- Ok, I managed to make a simple project that demonstrates async variant handing forever while sync one working well. It started to hand after I added a call to a backend webservice. See the attached camel-async-response-test-that-hangs.zip. Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7750) Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints
[ https://issues.apache.org/jira/browse/CAMEL-7750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated CAMEL-7750: - Attachment: camel-async-response-test-that-hangs.zip Enhance CXF RS Invoker to support AsyncResponse-enabled JAX-RS endpoints Key: CAMEL-7750 URL: https://issues.apache.org/jira/browse/CAMEL-7750 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Sergey Beryozkin Attachments: camel-async-response-test-that-hangs.zip, camel-async-response-test.zip It appears the invoker does not recognize the endpoints depending on a new suspended invocations feature of JAX-RS 2.0. We can tweak CXF JAXRSInvoker a bit if needed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CAMEL-7757) camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream
[ https://issues.apache.org/jira/browse/CAMEL-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-7757: --- Assignee: Willem Jiang camel-restlet 2.13.1 throwing EOFException on reading ZipInputStream Key: CAMEL-7757 URL: https://issues.apache.org/jira/browse/CAMEL-7757 Project: Camel Issue Type: Bug Components: camel-restlet Affects Versions: 2.13.1 Environment: Windows 7 Professional 64 Bit, JBOSS EAP 6.1, Java 1.7.0_65, Camel 2.13.1 Reporter: Sandeep Poreddy Assignee: Willem Jiang Labels: patch Attachments: DefaultRestletBinding.java Please refer to : http://camel.465427.n5.nabble.com/Came-2-13-1-Reading-ZipInputStream-EOFException-tt5755726.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7758) The asService() method should be protected in CamelBlueprintTestSupport
Jean-Baptiste Onofré created CAMEL-7758: --- Summary: The asService() method should be protected in CamelBlueprintTestSupport Key: CAMEL-7758 URL: https://issues.apache.org/jira/browse/CAMEL-7758 Project: Camel Issue Type: Bug Components: camel-blueprint, tests Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 2.12.5, 2.13.3, 2.14.1, 2.15.0 In order to easily register startup services in end user Camel Test Blueprint, the asService() method should be protected (instead of default). -- This message was sent by Atlassian JIRA (v6.2#6252)
