[jira] [Commented] (CAMEL-6174) camel-avro does not support Avro reflection schemas
[ https://issues.apache.org/jira/browse/CAMEL-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606180#comment-13606180 ] Vitalii Tymchyshyn commented on CAMEL-6174: --- Possible. I am still not sure how to introduce this option better. I will think on it. camel-avro does not support Avro reflection schemas --- Key: CAMEL-6174 URL: https://issues.apache.org/jira/browse/CAMEL-6174 Project: Camel Issue Type: Improvement Reporter: Vitalii Tymchyshyn Currently SpecificDatumReader/SpecificDatumWriter are fixed in camel-avro. This prevents usage of reflection schema for POJOs that are supported by ReflectDatumReader / ReflectDatumWriter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6056) Moving files on FTP not working
[
https://issues.apache.org/jira/browse/CAMEL-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606185#comment-13606185
]
Robin Lutter commented on CAMEL-6056:
-
i have tested 2.10.5-SNAPSHOT and 2.11-SNAPSHOT on windows client against RHEL
and Windows FTP server. The error is gone, but files are not moved.
Moving files on FTP not working
---
Key: CAMEL-6056
URL: https://issues.apache.org/jira/browse/CAMEL-6056
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.3, 2.10.4, 2.11.0
Reporter: Christian Schaefer
Assignee: Claus Ibsen
Labels: file, ftp, move
Fix For: 2.10.5, 2.11.0
Attachments: CAMEL-6056.zip
Moving files stored on a ftp server to another directory specified by the
move parameter is not working in camel versions 2.10.3, 2.10.4-SNAPSHOT and
2.11-SNAPSHOT.
(The ftp user got write permission.)
Whereas the file is moved as expected when using version 2.10.2
*The stacktrace I got when executing the test on camel version 2.10.3:*
{quote}
11:04:56,822 WARN [org.apache.camel.component.file.GenericFileOnCompletion]
(Camel (camel-1) thread #1 - ftp://myftp.com) Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - File
operation failed: 550 Failed to change directory.
Cannot change directory to: \\. Code: 550]:
org.apache.camel.component.file.GenericFileOperationFailedException: File
operation failed: 550 Failed to change directory.
Cannot change directory to: \\. Code: 550
at
org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:704)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:660)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.remote.FtpOperations.buildDirectory(FtpOperations.java:284)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:100)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:86)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:82)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:53)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:55)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:226)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.doneUow(UnitOfWorkProcessor.java:199)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.processSync(UnitOfWorkProcessor.java:139)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:115)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:336)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
[jira] [Work started] (CAMEL-6175) camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value
[ https://issues.apache.org/jira/browse/CAMEL-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-6175 started by Claus Ibsen. camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value Key: CAMEL-6175 URL: https://issues.apache.org/jira/browse/CAMEL-6175 Project: Camel Issue Type: Bug Components: camel-jetty Affects Versions: 2.10.4 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.10.5 Related to CAMEL-6173 but the jetty http producer in camel-jetty has a problem as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-6175) camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value
[ https://issues.apache.org/jira/browse/CAMEL-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6175: --- Fix Version/s: 2.11.0 camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value Key: CAMEL-6175 URL: https://issues.apache.org/jira/browse/CAMEL-6175 Project: Camel Issue Type: Bug Components: camel-jetty Affects Versions: 2.10.4 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.10.5, 2.11.0 Related to CAMEL-6173 but the jetty http producer in camel-jetty has a problem as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6175) camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value
[ https://issues.apache.org/jira/browse/CAMEL-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6175. Resolution: Fixed camel-jetty - Issue when bridging with jetty http producer and uri query parameter has encoded value Key: CAMEL-6175 URL: https://issues.apache.org/jira/browse/CAMEL-6175 Project: Camel Issue Type: Bug Components: camel-jetty Affects Versions: 2.10.4 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.10.5, 2.11.0 Related to CAMEL-6173 but the jetty http producer in camel-jetty has a problem as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-6056) Moving files on FTP not working
[
https://issues.apache.org/jira/browse/CAMEL-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606185#comment-13606185
]
Robin Lutter edited comment on CAMEL-6056 at 3/19/13 12:51 PM:
---
i have tested 2.10.5-SNAPSHOT and 2.11-SNAPSHOT on windows client against RHEL
FTP server. The exception is gone, but files are not moved.
Working with windows client and ftp server still works as expected.
was (Author: rlu):
i have tested 2.10.5-SNAPSHOT and 2.11-SNAPSHOT on windows client against
RHEL and Windows FTP server. The error is gone, but files are not moved.
Moving files on FTP not working
---
Key: CAMEL-6056
URL: https://issues.apache.org/jira/browse/CAMEL-6056
Project: Camel
Issue Type: Bug
Components: camel-ftp
Affects Versions: 2.10.3, 2.10.4, 2.11.0
Reporter: Christian Schaefer
Assignee: Claus Ibsen
Labels: file, ftp, move
Fix For: 2.10.5, 2.11.0
Attachments: CAMEL-6056.zip
Moving files stored on a ftp server to another directory specified by the
move parameter is not working in camel versions 2.10.3, 2.10.4-SNAPSHOT and
2.11-SNAPSHOT.
(The ftp user got write permission.)
Whereas the file is moved as expected when using version 2.10.2
*The stacktrace I got when executing the test on camel version 2.10.3:*
{quote}
11:04:56,822 WARN [org.apache.camel.component.file.GenericFileOnCompletion]
(Camel (camel-1) thread #1 - ftp://myftp.com) Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - File
operation failed: 550 Failed to change directory.
Cannot change directory to: \\. Code: 550]:
org.apache.camel.component.file.GenericFileOperationFailedException: File
operation failed: 550 Failed to change directory.
Cannot change directory to: \\. Code: 550
at
org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:704)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:660)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.remote.FtpOperations.buildDirectory(FtpOperations.java:284)
[camel-ftp-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:100)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:86)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:82)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:53)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.util.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:55)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.impl.DefaultUnitOfWork.done(DefaultUnitOfWork.java:226)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.doneUow(UnitOfWorkProcessor.java:199)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.processSync(UnitOfWorkProcessor.java:139)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:115)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
[camel-core-2.10.4-SNAPSHOT.jar:2.10.4-SNAPSHOT]
at
[jira] [Commented] (CAMEL-5837) Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2
[
https://issues.apache.org/jira/browse/CAMEL-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606346#comment-13606346
]
Johan Mörén commented on CAMEL-5837:
Managed to build from 2.11-SNAPSHOT from source and managed to start the route
successfully. When trying against my live-code however the fault persisted. I
then discovered that the schema import structure in the example wasn't quite
right. In my live-code and in the attached image both 1.xsd and 2.xsd imports
4.xsd. When i corrected 2.xsd to reflect this in the example code it refused to
run.
To fix 2.xsd please replace it's content with the following code:
{code:xml}
?xml version=1.0 encoding=UTF-8?
xs:schema
xmlns:xs=http://www.w3.org/2001/XMLSchema;
elementFormDefault=qualified
targetNamespace=example.2
xs:import schemaLocation=../../common/3.xsd namespace=example.3/
xs:import schemaLocation=../common/4.xsd namespace=example.4/
/xs:schema
{code}
When debugging this i found that the baseURI, used as key in the relatedURIMap,
is not correct (the start and end of the path is correct but it is lacking path
elements in the middle). I'm not sure if this is the cause of the problem.
Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2
--
Key: CAMEL-5837
URL: https://issues.apache.org/jira/browse/CAMEL-5837
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.10.2
Environment: MacOS X, java 7
Reporter: Johan Mörén
Assignee: Willem Jiang
Fix For: 2.10.4, 2.11.0
Attachments: xsd-import_example 2.zip, xsd-import_example-reopen.zip,
xsd_import_problem.png
Hello
I'm experiencing trouble with the validiator component when upgrading from
2.8.6 to 2.10.2.
The problem seems to be related to imported schemas that does additional
imports (all using relative paths). XSD A importing XSD B works fine. But if
B in turn imports XSD C. That import seems to be resolved with the base path
of A.
All works fine in 2.8.6 but breaks when upgrading to 2.10.2.
I will attach an example project where you can just switch version to verify
the scenario.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6179) Simple expression in spring XML not work if it come in multiple xml lines
Othmna Darwish created CAMEL-6179: - Summary: Simple expression in spring XML not work if it come in multiple xml lines Key: CAMEL-6179 URL: https://issues.apache.org/jira/browse/CAMEL-6179 Project: Camel Issue Type: Bug Affects Versions: 2.10.1 Reporter: Othmna Darwish Priority: Minor http://camel.465427.n5.nabble.com/Simple-expression-in-spring-XML-not-work-if-it-come-in-multiple-xml-line-td5729408.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6176) Camel 2.10.1 incapable of working with + in endpoint URIs
[
https://issues.apache.org/jira/browse/CAMEL-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606413#comment-13606413
]
Daniel Goering commented on CAMEL-6176:
---
similar problem exists for {{}}
* if not escaped it will be used to split parameters which leads to errors
* if escaped once it will be decoded before splitting and the URI is still
split in the middle of passwords or similar values
* encoding it twice does not work because of the workaround for CAMEL-4954
Camel 2.10.1 incapable of working with + in endpoint URIs
-
Key: CAMEL-6176
URL: https://issues.apache.org/jira/browse/CAMEL-6176
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.10.1
Environment: Linux Java 1.6.0_35
Reporter: Daniel Goering
Assignee: Hadrian Zbarcea
Priority: Critical
In the class org.apache.camel.util.URISupport which will be used to resolve
endpoints (DefaultCamelContext#normalizeEndpointUri) the method
parseParameters will be called.
At first the java.net.Uri#getQuery will be called with according to the
javadoc Returns the decoded query component of this URI returns a decoded
URI. If that fails the java.net.Uri#getSchemeSpecificPart method will be
called which according to the javadoc Returns the decoded scheme-specific
part of this URI. returns a decoded URI.
So to summarize we get in any case a decoded URI.
As workaround for CAMEL-4954 all % are encoded, i.e. replaced by %25.
The URI will then be decoded again in the method
org.apache.camel.util.URISupport#parseQuery(String) with
java.net.URLDecoder#decode(String,String).
This code leads to the following behaviour:
If a + is properly encoded with foo%2Bbar the foo%2Bbar will be substituted
by the first call with foo+bar and then decoded again which leads to foo bar.
If the + is not encoded at all foo+bar will be decoded to foo bar in the
first step and not be changed again in the second step.
If the + is double encoded to foo%252Bbar the first call will transform it
to foo%2Bbar, then the workaround for CAMEL-4954 will change it back to
foo%252Bbar and the final decode will change it again to foo%2Bbar.
Thus, currently there is no way to use a + in passwords or similar parameter
values if the parameter has to be supplied via endpoint URIs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6108) Support XA Transactions in SJMS
[ https://issues.apache.org/jira/browse/CAMEL-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606481#comment-13606481 ] Matt Pavlovich commented on CAMEL-6108: --- I agree, the sjms component can't have any feature-loss if it will become the 'jms' component for 3.0. Additionally, I agree that a spring-less solution would be ideal. I'm tied up on projects, but please update this ticket when you'd like more testing to occur. I can definitely help then. Support XA Transactions in SJMS --- Key: CAMEL-6108 URL: https://issues.apache.org/jira/browse/CAMEL-6108 Project: Camel Issue Type: Sub-task Components: camel-sjms Reporter: Chris Geer Assignee: Scott England-Sullivan Fix For: 3.0.0 We love contributions as you know. May you find time to work on it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6149) Karaf command for backlog tracer
[ https://issues.apache.org/jira/browse/CAMEL-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6149. Resolution: Fixed Karaf command for backlog tracer Key: CAMEL-6149 URL: https://issues.apache.org/jira/browse/CAMEL-6149 Project: Camel Issue Type: Sub-task Components: karaf Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.11.0 This allows people using karaf / SMX to have Camel message tracing from their shell command. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-6148) BacklogTracer - Allow to capture message tracers and store in backlog for retrieval on demand (pull based)
[ https://issues.apache.org/jira/browse/CAMEL-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-6148. Resolution: Fixed We have a basic implementation now. That is good for now. Can always improve if needed. For example with more options on the Karaf command, such as filtering messages etc. BacklogTracer - Allow to capture message tracers and store in backlog for retrieval on demand (pull based) -- Key: CAMEL-6148 URL: https://issues.apache.org/jira/browse/CAMEL-6148 Project: Camel Issue Type: New Feature Components: camel-core, jmx Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.11.0 A new type of message tracer in Camel that stores the traced messages in an internal backlog queue, which can be access on demand by management API. This allows us to build a karaf command to show messages traces, and allow end users to integrate this easier with their JMX tooling etc. The name BacklogTracer was chosen as MessageTracer would be ambiguous with the existing Tracer. The existing Tracer is too fine grained and has some awkward issues as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-6180) SJMS Component behavior suggestions to improve upon the standard JMS component
Matt Pavlovich created CAMEL-6180: - Summary: SJMS Component behavior suggestions to improve upon the standard JMS component Key: CAMEL-6180 URL: https://issues.apache.org/jira/browse/CAMEL-6180 Project: Camel Issue Type: Improvement Components: camel-sjms Reporter: Matt Pavlovich The SJMS component should not suffer any feature loss from the standard JMS component, for best user experience in 3.0. A random mix of suggested behavior changes/enhancements: 1. Supporting things like consume from multiple destinations using wildcards... from jms:queue:US_TICKETS_* 2. Support dynamic destination on a to uri=.. by using the same header from the existing JMS component. CamelJmsDestination javax.jms.DestinationA destination object. CamelJmsDestinationName String The destination name. 3. I suggest making 'request-reply' be explicit, since implicit is really painful for new users. The magic temp destination listener is not confusing and the user has nothing in the route to go on as to why that is happening. 4. Along w/ #3, don't kill the QoS headers by default. It makes setting up proxies really complicated. 5. Support MQ Series 'weirdness' that current component handles.. see 'Setting JMS provider options on the destination' here: http://camel.apache.org/jms.html Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-6180) SJMS Component behavior suggestions to improve upon the standard JMS component
[ https://issues.apache.org/jira/browse/CAMEL-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott England-Sullivan reassigned CAMEL-6180: - Assignee: Scott England-Sullivan SJMS Component behavior suggestions to improve upon the standard JMS component -- Key: CAMEL-6180 URL: https://issues.apache.org/jira/browse/CAMEL-6180 Project: Camel Issue Type: Improvement Components: camel-sjms Reporter: Matt Pavlovich Assignee: Scott England-Sullivan The SJMS component should not suffer any feature loss from the standard JMS component, for best user experience in 3.0. A random mix of suggested behavior changes/enhancements: 1. Supporting things like consume from multiple destinations using wildcards... from jms:queue:US_TICKETS_* 2. Support dynamic destination on a to uri=.. by using the same header from the existing JMS component. CamelJmsDestination javax.jms.DestinationA destination object. CamelJmsDestinationName String The destination name. 3. I suggest making 'request-reply' be explicit, since implicit is really painful for new users. The magic temp destination listener is not confusing and the user has nothing in the route to go on as to why that is happening. 4. Along w/ #3, don't kill the QoS headers by default. It makes setting up proxies really complicated. 5. Support MQ Series 'weirdness' that current component handles.. see 'Setting JMS provider options on the destination' here: http://camel.apache.org/jms.html Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6180) SJMS Component behavior suggestions to improve upon the standard JMS component
[ https://issues.apache.org/jira/browse/CAMEL-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606651#comment-13606651 ] Raul Kripalani commented on CAMEL-6180: --- Hi Matt, Regarding point #3, would you mind elaborating a bit further? Providing a small example may help. Thanks, Raúl. SJMS Component behavior suggestions to improve upon the standard JMS component -- Key: CAMEL-6180 URL: https://issues.apache.org/jira/browse/CAMEL-6180 Project: Camel Issue Type: Improvement Components: camel-sjms Reporter: Matt Pavlovich Assignee: Scott England-Sullivan The SJMS component should not suffer any feature loss from the standard JMS component, for best user experience in 3.0. A random mix of suggested behavior changes/enhancements: 1. Supporting things like consume from multiple destinations using wildcards... from jms:queue:US_TICKETS_* 2. Support dynamic destination on a to uri=.. by using the same header from the existing JMS component. CamelJmsDestination javax.jms.DestinationA destination object. CamelJmsDestinationName String The destination name. 3. I suggest making 'request-reply' be explicit, since implicit is really painful for new users. The magic temp destination listener is not confusing and the user has nothing in the route to go on as to why that is happening. 4. Along w/ #3, don't kill the QoS headers by default. It makes setting up proxies really complicated. 5. Support MQ Series 'weirdness' that current component handles.. see 'Setting JMS provider options on the destination' here: http://camel.apache.org/jms.html Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6171) camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
[
https://issues.apache.org/jira/browse/CAMEL-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606692#comment-13606692
]
Aki Yoshida commented on CAMEL-6171:
Hi Willem,
you mean cxf's rt-transport-http, no?
or you want to add an workaround in camel-cxf?
i think we should fix this in cxf, by replacing the above if-line with this one:
if (connection.getRequestProperty(User-Agent) == null) {
regards, aki
camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
--
Key: CAMEL-6171
URL: https://issues.apache.org/jira/browse/CAMEL-6171
Project: Camel
Issue Type: Bug
Components: camel-cxf
Reporter: Claus Ibsen
Assignee: Willem Jiang
Priority: Minor
Fix For: 2.11.0
See nabble
http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6171) camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
[ https://issues.apache.org/jira/browse/CAMEL-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606698#comment-13606698 ] Daniel Kulp commented on CAMEL-6171: Actually, I think Camel should NOT by copying the User-Agent header over unless it's in RAW/MESSAGE mode. The server may be using the User-Agent header to change how the response is sent or similar if it knows that a particular client type may have issues. Thus, if CXF is going to be processing the response (POJO, CXF_MESSAGE, PAYLOAD), then the User-Agent should be set to CXF. If in RAW/MESSAGE, then likely the original agent should be retained. camel-cxf - Should detect existing User-Agent header to avoid adding duplicate -- Key: CAMEL-6171 URL: https://issues.apache.org/jira/browse/CAMEL-6171 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Claus Ibsen Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 See nabble http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CAMEL-6171) camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
[ https://issues.apache.org/jira/browse/CAMEL-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606698#comment-13606698 ] Daniel Kulp edited comment on CAMEL-6171 at 3/19/13 7:35 PM: - Actually, I think Camel should NOT be copying the User-Agent header over unless it's in RAW/MESSAGE mode. The server may be using the User-Agent header to change how the response is sent or similar if it knows that a particular client type may have issues. Thus, if CXF is going to be processing the response (POJO, CXF_MESSAGE, PAYLOAD), then the User-Agent should be set to CXF. If in RAW/MESSAGE, then likely the original agent should be retained. was (Author: dkulp): Actually, I think Camel should NOT by copying the User-Agent header over unless it's in RAW/MESSAGE mode. The server may be using the User-Agent header to change how the response is sent or similar if it knows that a particular client type may have issues. Thus, if CXF is going to be processing the response (POJO, CXF_MESSAGE, PAYLOAD), then the User-Agent should be set to CXF. If in RAW/MESSAGE, then likely the original agent should be retained. camel-cxf - Should detect existing User-Agent header to avoid adding duplicate -- Key: CAMEL-6171 URL: https://issues.apache.org/jira/browse/CAMEL-6171 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Claus Ibsen Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 See nabble http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5837) Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2
[ https://issues.apache.org/jira/browse/CAMEL-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607241#comment-13607241 ] Willem Jiang commented on CAMEL-5837: - Hi Johan, I just did a quick fix for the issue that you found yesterday. Please feel free to check it out for verification. Willem Problem with nested schema imports when upgrading from 2.8.6 to 2.10.2 -- Key: CAMEL-5837 URL: https://issues.apache.org/jira/browse/CAMEL-5837 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 2.10.2 Environment: MacOS X, java 7 Reporter: Johan Mörén Assignee: Willem Jiang Fix For: 2.10.4, 2.11.0 Attachments: xsd-import_example 2.zip, xsd-import_example-reopen.zip, xsd_import_problem.png Hello I'm experiencing trouble with the validiator component when upgrading from 2.8.6 to 2.10.2. The problem seems to be related to imported schemas that does additional imports (all using relative paths). XSD A importing XSD B works fine. But if B in turn imports XSD C. That import seems to be resolved with the base path of A. All works fine in 2.8.6 but breaks when upgrading to 2.10.2. I will attach an example project where you can just switch version to verify the scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6171) camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
[ https://issues.apache.org/jira/browse/CAMEL-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607288#comment-13607288 ] Willem Jiang commented on CAMEL-6171: - Hi Aki, The code that I showed is from Headers.java in cxf-rt-transports-http, I will follow it and did some update on cxf code repository. camel-cxf - Should detect existing User-Agent header to avoid adding duplicate -- Key: CAMEL-6171 URL: https://issues.apache.org/jira/browse/CAMEL-6171 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Claus Ibsen Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 See nabble http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-6171) camel-cxf - Should detect existing User-Agent header to avoid adding duplicate
[ https://issues.apache.org/jira/browse/CAMEL-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607301#comment-13607301 ] Willem Jiang commented on CAMEL-6171: - Hi Dan, I agree with you and will commit a quick fix for it. camel-cxf - Should detect existing User-Agent header to avoid adding duplicate -- Key: CAMEL-6171 URL: https://issues.apache.org/jira/browse/CAMEL-6171 Project: Camel Issue Type: Bug Components: camel-cxf Reporter: Claus Ibsen Assignee: Willem Jiang Priority: Minor Fix For: 2.11.0 See nabble http://camel.465427.n5.nabble.com/CXF-proxy-route-creates-multiple-two-user-agent-HTTP-headers-tp5729137.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
