[jira] Resolved: (CAMEL-1281) ConsumerTemplate
[
https://issues.apache.org/activemq/browse/CAMEL-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1281.
Resolution: Fixed
Fix Version/s: (was: Future)
2.0.0
Wiki updated at Polling Consumer EIP
ConsumerTemplate
Key: CAMEL-1281
URL: https://issues.apache.org/activemq/browse/CAMEL-1281
Project: Apache Camel
Issue Type: New Feature
Components: camel-core
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0
We could use a nice consumer template for nice one liners consume endpoints.
Suppose I want to consume a file based on a dynamic filename I get from a
Exchange message passed on to my from a JMS Queue or the like
Then I do some custom coding in a processor to read the file.
Helping me would be a consumerTemplate where I can consume the file endpoint
in one liner
Something like this:
{code}
String context =
consumerTemplate.receive(file://inbox/foo.txt?directory=false,
String.class);
{code}
Beware if we want to receive/poll an entire directory etc, it will generate
several Exchanges. For that we might wanna group them in a GroupedExchange or
support a ListExchange as return type or whatnot.
Just adding it here as in idea
Any thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1499) LDAP documentation could be improved
[
https://issues.apache.org/activemq/browse/CAMEL-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50888#action_50888
]
Claus Ibsen commented on CAMEL-1499:
Christopher, you can get karma to be able to edit the wiki pages directly.
See more here
http://camel.apache.org/contributing.html
LDAP documentation could be improved
Key: CAMEL-1499
URL: https://issues.apache.org/activemq/browse/CAMEL-1499
Project: Apache Camel
Issue Type: Improvement
Components: camel-ldap
Affects Versions: 1.6.0, 2.0-M1
Environment: Wiki pages
Reporter: Christopher Hunt
On familiarising myself with the ldap component I found that I had to trawl
through the source code to gain a good understanding of how it should be used.
For example (http://camel.apache.org/ldap.html):
In the sample below we fetch the rows from the customer table.
First we register our datasource in the Camel registry as testdb:
is entirely incorrect. Perhaps it should say:
In the sample below we create a JNDI DirContext and register it with our
Camel context's JNDI registry. The key used for registration is the remaining
part of the ldap URI i.e. the part without the ldap: and URI parameters. The
DirContext should establish any authentication requirements with the LDAP
repository.
I then think that the example should illustrate how an anonymous DirContext
can be established outside of any ApacheDS dependencies e.g.:
{code}
HashtableObject, Object env = new HashtableObject, Object();
env.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
env.put(Context.PROVIDER_URL, providerURL);
env.put(Context.SECURITY_AUTHENTICATION, none);
DirContext ctx = new InitialDirContext(env);
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (CAMEL-1499) LDAP documentation could be improved
Please may I receive some karma then so that I can update the wiki pages. :working: -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28CAMEL-1499%29-LDAP-documentation-could-be-improved-tp22766622p22777494.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: [jira] Commented: (CAMEL-1499) LDAP documentation could be improved
On Mon, Mar 30, 2009 at 9:14 AM, huntc hu...@mac.com wrote: Please may I receive some karma then so that I can update the wiki pages. :working: Karma granted -- View this message in context: http://www.nabble.com/-jira--Created%3A-%28CAMEL-1499%29-LDAP-documentation-could-be-improved-tp22766622p22777494.html Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
[jira] Updated: (CAMEL-1500) Set jaxb encoding with spring
[ https://issues.apache.org/activemq/browse/CAMEL-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1500: --- Component/s: (was: camel-spring) camel-jaxb Affects Version/s: 1.6.0 Fix Version/s: 1.6.1 Set jaxb encoding with spring - Key: CAMEL-1500 URL: https://issues.apache.org/activemq/browse/CAMEL-1500 Project: Apache Camel Issue Type: Task Components: camel-jaxb Affects Versions: 1.6.0 Environment: - eclipse v3.3.2 Reporter: Tobias Emmerich Assignee: Claus Ibsen Fix For: 2.0.0, 1.6.1 I can set the encoding in Jaxb with the marshaller: jaxb.getMarshaller().setProperty(Marshaller.JAXB_ENCODING, iso-8859-15); But the problem is i don´t know how to set this in spring. The source in spring till now is like this: route from uri=x/ marshal jaxb id=myJaxb prettyPrint=true contextPath=acknowledgement/ /marshal to ref=y /route I think we need somthing like: jaxb id=myJaxb prettyPrint=true contextPath=acknowledgement encoding=iso-8859-15/ Thanks for help Tobias -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1501) camel-mail - Better re connect in case some servers throw exception in isConnected test
[
https://issues.apache.org/activemq/browse/CAMEL-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1501.
Resolution: Fixed
trunk at apache: 759931
1.x at apache: 759933
camel-mail - Better re connect in case some servers throw exception in
isConnected test
---
Key: CAMEL-1501
URL: https://issues.apache.org/activemq/browse/CAMEL-1501
Project: Apache Camel
Issue Type: Bug
Components: camel-mail
Affects Versions: 1.6.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0, 1.6.1
In case some mail servers throws exception for {{isConnected}} test. We
should better cater for that with a try .. catch and re connect in case of
exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1500) Set jaxb encoding with spring
Set jaxb encoding with spring - Key: CAMEL-1500 URL: https://issues.apache.org/activemq/browse/CAMEL-1500 Project: Apache Camel Issue Type: Task Components: camel-spring Environment: - eclipse v3.3.2 Reporter: Tobias Emmerich Fix For: 2.0.0 I can set the encoding in Jaxb with the marshaller: jaxb.getMarshaller().setProperty(Marshaller.JAXB_ENCODING, iso-8859-15); But the problem is i don´t know how to set this in spring. The source in spring till now is like this: route from uri=x/ marshal jaxb id=myJaxb prettyPrint=true contextPath=acknowledgement/ /marshal to ref=y /route I think we need somthing like: jaxb id=myJaxb prettyPrint=true contextPath=acknowledgement encoding=iso-8859-15/ Thanks for help Tobias -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1496) Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters
[ https://issues.apache.org/activemq/browse/CAMEL-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Reijn updated CAMEL-1496: Component/s: camel-rss Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters - Key: CAMEL-1496 URL: https://issues.apache.org/activemq/browse/CAMEL-1496 Project: Apache Camel Issue Type: Bug Components: camel-atom, camel-rss Affects Versions: 2.0-M1 Reporter: Jeroen Reijn While configuring a route like: route from uri=atom://http://somehost/?feed=1234567/ to uri=seda:feeds/ /route camel throws an exception with: Failed to resolve endpoint due to: org.apache.camel.ResolveEndpointFailedException: There are 1 parameters that couldn't be set on the endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1496) Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters
[ https://issues.apache.org/activemq/browse/CAMEL-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Reijn updated CAMEL-1496: Attachment: CAMEL-1496.patch.txt Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters - Key: CAMEL-1496 URL: https://issues.apache.org/activemq/browse/CAMEL-1496 Project: Apache Camel Issue Type: Bug Components: camel-atom, camel-rss Affects Versions: 2.0-M1 Reporter: Jeroen Reijn Attachments: CAMEL-1496.patch.txt While configuring a route like: route from uri=atom://http://somehost/?feed=1234567/ to uri=seda:feeds/ /route camel throws an exception with: Failed to resolve endpoint due to: org.apache.camel.ResolveEndpointFailedException: There are 1 parameters that couldn't be set on the endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1496) Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters
[ https://issues.apache.org/activemq/browse/CAMEL-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Reijn updated CAMEL-1496: Patch Info: [Patch Available] Using request parameters in the feed url will result in ResolveEndpointFailedException for Unknown parameters - Key: CAMEL-1496 URL: https://issues.apache.org/activemq/browse/CAMEL-1496 Project: Apache Camel Issue Type: Bug Components: camel-atom, camel-rss Affects Versions: 2.0-M1 Reporter: Jeroen Reijn Attachments: CAMEL-1496.patch.txt While configuring a route like: route from uri=atom://http://somehost/?feed=1234567/ to uri=seda:feeds/ /route camel throws an exception with: Failed to resolve endpoint due to: org.apache.camel.ResolveEndpointFailedException: There are 1 parameters that couldn't be set on the endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1351) camel-cxf should preserve user-* phase interceptors (in PAYLOAD and MESSAGE mode)
[ https://issues.apache.org/activemq/browse/CAMEL-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam resolved CAMEL-1351. Resolution: Fixed camel-cxf should preserve user-* phase interceptors (in PAYLOAD and MESSAGE mode) - Key: CAMEL-1351 URL: https://issues.apache.org/activemq/browse/CAMEL-1351 Project: Apache Camel Issue Type: Improvement Components: camel-cxf Affects Versions: 1.5.0 Reporter: William Tam Assignee: William Tam Priority: Minor Fix For: 2.0.0, 1.6.1 Camel-cxf should preserve user-* phase interceptors so that users can add their own interceptor if they choose to. One usecase is to be able to use LoggingOutInterceptor in MESSAGE mode. Since LoggingOutInterceptor is PRE_STREAM phase by default and it is removed in MESSAGE mode, it would be nice to enable LoggingOutInterceptor by just changed it to USER_STREAM phase like: bean class=...LoggingOutInterceptor constructor-arg value=write/ /bean -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CAMEL-1502) Bean component should propagate headers
Bean component should propagate headers --- Key: CAMEL-1502 URL: https://issues.apache.org/activemq/browse/CAMEL-1502 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions: 1.6.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0, 1.6.1 When doing a route an you invoke a bean that sets a response on the OUT body it does not propagate the headers from the IN body. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1502) Bean component should propagate headers
[ https://issues.apache.org/activemq/browse/CAMEL-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1502. Resolution: Fixed Bean component should propagate headers --- Key: CAMEL-1502 URL: https://issues.apache.org/activemq/browse/CAMEL-1502 Project: Apache Camel Issue Type: Improvement Components: camel-core Affects Versions: 1.6.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.0.0, 1.6.1 When doing a route an you invoke a bean that sets a response on the OUT body it does not propagate the headers from the IN body. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[DISCUSS] - Default error handler in Camel 2.0, what should we do?
Hi As we work on the Camel 2.0 I would suggest that we start a discussion what should be the preferred error handler defaults in Camel 2.0. What we currently have is the DLC is default and it does 6 retries with 1 sec apart and then just log an ERROR and ends the exchange. We have 3 different error handler types - no error handler (= disabled) - DeadLetterChannel (= default in 1.x) - TransactionErrorHandler (= using Spring TX) As people can use Camel in different runtimes and with different needs for error handling we cannot have a default that fits all situations. We could for instance do 1) Disable error handling by default. This would be the least surprises for end users. If there is some exception then it would be propagated back to the caller. We could even optimize the logic in Camel to avoid adding the interceptor that adds the noErrorHandler. +1 from me 2) Keep it as is big -1 from me. We have the luxury of being able to change defaults before 2.0 is released. So we should do it!!! 3) Use DeadLetterChannel but add a feature so it avoids failure handling it by default. So it will be able to do retries but if it fails all together it will propagate the exception back to the caller as if the have been no error handler at all. This feature could also be useable for end users in other situations, eg retry IOExceptions and in case of a all attempts failed then propgate the excpetion back to the caller. What should the option name be: - moveToDeadLetterQueue=false - handled=false (like the handled we have at onException) +1 as well. We can even do #1 and #3 4) For TX its mostly all the Spring XML garbage that is needed to setup TX that can be a bit hard to get configure correct. So the JMS component have a transacted=true option to allow to do this itself or discover if there is a Spring TX manager already. Maybe we can default to use transactionErrorHandler if we can find a Spring TX manager. But this would only work for certain transports that support TX, and that is mostly only JMS and JDBC. So what should happens for routing not involving those, eg camel-cxf, over file to a mail etc? Could be confusing, if Camel uses TX for certain routes and the other for the other routes. So what we have now with the transacted=true option is good as end users need to explicit declare this option. We could maybe add this for the JDBC based components as well: JPA, JDBC, SQL. Any thoughts? -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
