svn commit: r1297426 - in /camel/trunk/components/camel-fop: ./ src/main/resources/META-INF/LICENSE.txt src/main/resources/META-INF/NOTICE.txt src/test/resources/log4j.properties
Author: davsclaus Date: Tue Mar 6 11:17:42 2012 New Revision: 1297426 URL: http://svn.apache.org/viewvc?rev=1297426view=rev Log: CAMEL-3551: Polished Added: camel/trunk/components/camel-fop/src/main/resources/META-INF/LICENSE.txt (with props) camel/trunk/components/camel-fop/src/main/resources/META-INF/NOTICE.txt (with props) camel/trunk/components/camel-fop/src/test/resources/log4j.properties (with props) Modified: camel/trunk/components/camel-fop/ (props changed) Propchange: camel/trunk/components/camel-fop/ -- --- svn:ignore (added) +++ svn:ignore Tue Mar 6 11:17:42 2012 @@ -0,0 +1,17 @@ +.pmd +.checkstyle +.ruleset +target +.settings +.classpath +.project +.wtpmodules +prj.el +.jdee_classpath +.jdee_sources +velocity.log +eclipse-classes +*.ipr +*.iml +*.iws +*.idea Added: camel/trunk/components/camel-fop/src/main/resources/META-INF/LICENSE.txt URL: http://svn.apache.org/viewvc/camel/trunk/components/camel-fop/src/main/resources/META-INF/LICENSE.txt?rev=1297426view=auto == --- camel/trunk/components/camel-fop/src/main/resources/META-INF/LICENSE.txt (added) +++ camel/trunk/components/camel-fop/src/main/resources/META-INF/LICENSE.txt Tue Mar 6 11:17:42 2012 @@ -0,0 +1,203 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + License shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + Licensor shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + Legal Entity shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + control means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + You (or Your) shall mean an individual or Legal Entity + exercising permissions granted by this License. + + Source form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + Object form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + Work shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + Derivative Works shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + Contribution shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, submitted + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as Not a Contribution. + + Contributor shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions
[CONF] Apache Camel Camel 2.9.1 Release
Camel 2.9.1 Release Page edited by Babak Vahdat Changes (3) ... h2. Known Issues * See [Camel 2.9.01 Release] h2. Important changes to consider when upgrading * See [Camel 2.9.01 Release] h2. Notice * See [Camel 2.9.01 Release] h2. Getting the Distributions ... Full Content Camel 2.9.1 release New and Noteworthy Welcome to the 2.9.1 release which is mainly a bug fix release with 109 issues resolved. For more details see the JIRA tickets Known Issues See Camel 2.9.1 Release Important changes to consider when upgrading See Camel 2.9.1 Release Notice See Camel 2.9.1 Release Getting the Distributions Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-camel-2.9.1.zip apache-camel-2.9.1.zip.asc Unix/Linux/Cygwin Distribution apache-camel-2.9.1.tar.gz apache-camel-2.9.1.tar.gz.asc The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox Source Distributions Description Download Link PGP Signature file of download Source (zip) apache-camel-2.9.1-src.zip apache-camel-2.9.1-src.zip.asc Getting the Binaries using Maven 2 To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is: dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.9.1/version /dependency SVN Tag Checkout svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.9.1 Changelog For a more detailed view of new features and bug fixes, see the: release notes for 2.9.1 Change Notification Preferences View Online | View Changes | Add Comment
[CONF] Apache Camel Camel 2.9.1 Release
Camel 2.9.1 Release Page edited by Babak Vahdat Changes (3) ... h2. Known Issues * See [Camel 2.9.10 Release] h2. Important changes to consider when upgrading * See [Camel 2.9.10 Release] h2. Notice * See [Camel 2.9.10 Release] h2. Getting the Distributions ... Full Content Camel 2.9.1 release New and Noteworthy Welcome to the 2.9.1 release which is mainly a bug fix release with 109 issues resolved. For more details see the JIRA tickets Known Issues See Camel 2.9.0 Release Important changes to consider when upgrading See Camel 2.9.0 Release Notice See Camel 2.9.0 Release Getting the Distributions Binary Distributions Description Download Link PGP Signature file of download Windows Distribution apache-camel-2.9.1.zip apache-camel-2.9.1.zip.asc Unix/Linux/Cygwin Distribution apache-camel-2.9.1.tar.gz apache-camel-2.9.1.tar.gz.asc The above URLs use redirectionThe above URLs use the Apache Mirror system to redirect you to a suitable mirror for your download. Some users have experienced issues with some versions of browsers (e.g. some Safari browsers). If the download doesn't seem to work for you from the above URL then try using FireFox Source Distributions Description Download Link PGP Signature file of download Source (zip) apache-camel-2.9.1-src.zip apache-camel-2.9.1-src.zip.asc Getting the Binaries using Maven 2 To use this release in your maven project, the proper dependency configuration that you should use in your Maven POM is: dependency groupIdorg.apache.camel/groupId artifactIdcamel-core/artifactId version2.9.1/version /dependency SVN Tag Checkout svn co http://svn.apache.org/repos/asf/camel/tags/camel-2.9.1 Changelog For a more detailed view of new features and bug fixes, see the: release notes for 2.9.1 Change Notification Preferences View Online | View Changes | Add Comment
[CONF] Apache Camel Mail
Mail
Page edited by Glen Mazza
Comment:
Removed Camel 1.x references.
Changes (27)
...
We have discovered that the geronimo mail {{.jar}} (v1.6) has a bug when polling mails with attachments. It cannot correctly identify the {{Content-Type}}. So, if you attach a {{.jpeg}} file to a mail and you poll it, the {{Content-Type}} is resolved as {{text/plain}} and not as {{image/jpeg}}. For that reason, we have added an {{org.apache.camel.component.ContentTypeResolver}} SPI interface which enables you to provide your own implementation and fix this bug by returning the correct Mime type based on the file name. So if the file name ends with {{jpeg/jpg}}, you can return {{image/jpeg}}.
You can set your custom resolver on the {{MailComponent}} instance or on the {{MailEndpoint}} instance. This feature is added in Camel 1.6.2/2.0.
{warning}
...
h4. {anchor:DefaultPorts}Default ports
As of Camel 1.4, default Default port numbers are supported. If the port number is omitted, Camel determines the port number to use based on the protocol.
{div:class=confluenceTableSmall} || Protocol || Default Port Number ||
...
| {{ignoreUriScheme}} | {{false}} | If {{false}}, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.) | | {{defaultEncoding}} | {{null}} | The default encoding to use for Mime Messages. |
| {{contentType}} | {{text/plain}} | New option in *Camel 1.5*. The mail message content type. Use {{text/html}} for HTML mails. |
| {{folderName}} | {{INBOX}} | The folder to poll. | | {{destination}} | {{username@host}} | *@deprecated* Use the {{to}} option instead. The {{TO}} recipients (receivers of the email). |
| {{to}} | {{username@host}} | As of *Camel 1.4*, the The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
| {{replyTo}} | {{alias@host}} | As of *Camel 2.8.4, 2.9.1\+*, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma. |
| {{CC}} | {{null}} | As of *Camel 1.4*, the |The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
| {{BCC}} | {{null}} | As of *Camel 1.4*, the The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma. |
| {{from}} | {{camel@localhost}} | The FROM email address. | | {{subject}} | | As of *Camel 2.3*, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option. |
| {{deleteProcessedMessages}} | {{true}}/{{false}} | Deletes the messages after they have been processed. This is done by setting the {{DELETED}} flag on the mail message. If {{false}}, the {{SEEN}} flag is set instead. As of *Camel 1.5*, the default setting is {{false}}. This option is named {{delete}} in Camel 2.0 onwards. |
| {{delete}} | {{false}} | *Camel 2.0*: Deletes the messages after they have been processed. This is done by setting the {{DELETED}} flag on the mail message. If {{false}}, the {{SEEN}} flag is set instead. |
| {{processOnlyUnseenMessages}} | {{false}}/{{true}} | As of *Camel 1.4*, it is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. Setting this option to {{true}} will filter to only unseen messages. As of Camel 1.5, the default setting is {{true}}. POP3 does not support the {{SEEN}} flag, so this option is not supported in POP3; use IMAP instead. This option is named {{unseen}} in Camel 2.0 onwards. | | {{unseen}} | {{true}} | *Camel 2.0*: Is used to fetch only unseen messages (that is, new messages). Note that POP3 does not support the {{SEEN}} flag; use IMAP instead. |
| {{unseen}} | {{true}} | It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of {{true}} will filter to only unseen messages. POP3 does not support the {{SEEN}} flag, so this option is not supported in POP3; use IMAP instead. |
| {{fetchSize}} | {{\-1}} | As of *Camel 1.4*, this option sets Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of {{\-1}} means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all. |
| {{alternativeBodyHeader}} |
svn commit: r1297832 - /camel/website/
Author: dkulp Date: Wed Mar 7 01:57:50 2012 New Revision: 1297832 URL: http://svn.apache.org/viewvc?rev=1297832view=rev Log: Place to add code to generate the website Added: camel/website/
[CONF] Apache Camel Error handling in Camel
Error handling in Camel
Page edited by Ben ODay
Comment:
revised example for 2.0+
Changes (5)
...
- per route (using spring transaction policy)
h3. How does it work
h3. How does the [Dead Letter Channel] error handler work
When Camel is started it will inspect the routes and weave in the error handling into the routing. With up to 3 supported scopes, the error handling can be quite complex. And on top of that you have inherited error handling and you can even configure [Exception Clause]s to handle specific exception types differently. So yes its advanced but very powerful when you get the grip of it.
...
An example illustrating this: {code:java}
errorHandler(deadLetterChannel(jms:queue:dead));
from(seda:newOrder).to(bean:validateOrder)
...
{code}
In this route we have 3 nodes (the dots) where the [Error Handler] is watching us (The AOP around stuff). So when an order arrives on the seda queue we consume it and send it to the validateOrder bean. In case the validation bean processed ok, we move on to the next node. In case the storeOrder bean failed and throws an exception its caught by the [Error Handler] [Dead Letter Channel] that decides what to do next. Either it does a:
- redeliver - or move it to dead letter queue
It will continue to do redeliveries based on the policy configured. By default Camel [Dead Letter Channel] will attempt at most 6 redeliveries with 1 second delay. So if the storeOrder bean did succeed at the 3rd attempt the routing will continue to the next node the confirmOrder bean. In case all redeliveries failed the Exchange is regarded as failed and is moved to the dead letter queue and the processing of this exchange stops. By default the dead letter queue is just a ERROR logger.
{info:Applies for all components}
...
Full Content
Error handling in Camel
Error handling in Camel can roughly be separated into two distinct types:
non transactional
transactional
Where non transactional is the most common type that is enabled out-of-the-box and handled by Camel itself. The transaction type is handled by a backing system such as a J2EE application server.
Using try ... catch ... finallyRelated to error handling is the Try Catch Finally feature in Camel.
When does an error happen
An error happens when
any uncaught exception is thrown during routing and processing of messages within Camel
So think of this as a big exception interceptor that catches all exceptions and handles what to do.
Non transactional
By default Camel uses the non transaction type and orchestrates the error handling during processing and routing.
As there isn't a single error handling configuration that suites all uses cases, you should consider altering the default configurations to better suit you needs.
Camel 1.x default error handler
In Camel 1.x a global Dead Letter Channel is setup as the Error Handler by default. It's configured as:
redeliver up to 6 times
pause 1 second between each redelivery attempt
if all redelivery attempts failed then move exchange into the dead letter queue
the default dead letter queue is a logger that logs the exchange at ERROR level
Dead Letter Queue A dead letter queue is like a black hole, it will consume the Exchange and the Exchange routing is ended with no indication that it failed.
This works great in the JMS Messaging world where we don't want a bad message to cause endless retries and causing the system to exhaust. The message is said to be poison and thus we want to move it to a dead letter queue so the system can continue to operate and work with the next message.
This default does not go well with other transports using in a request/reply messaging style. If the Exchange failed then the original caller want to be alter it failed.
So the bottom line is that you must configure and setup the error handling strategies that suits your business needs.
Camel 2.0 onwards default error handler
In Camel 2.0 onwards a global DefaultErrorHandler is setup as the Error Handler by default. It's configured as:
no redeliveries
no deal letter queue
if the exchange failed an exception is thrown and propagated back to the original caller wrapped in a RuntimeCamelException.
Scopes
Camel supports 2 scopes for the non transactional type:
global
per route
And the same 2 scopes for transactional type:
global
per route (using spring transaction policy)
How does the Dead Letter Channel error handler work
When Camel is started it will inspect the routes and weave in the error handling into the routing. With up
