background preloader

Apache Camel: Index

Apache Camel: Index
The Camel community announces the immediate availability of the new patch release Camel 2.11.4. Coming some 4 weeks after the 2.11.3 release, this 2.11.4 path release contains a total of 26 fixes applied in the past month by the community on the Camel 2.11.x maintenance branch. The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes. Many thanks to all who made this release possible. On behalf of the Camel PMC,Hadrian

http://camel.apache.org/

Related:  Integration & Middleware

JBoss Fuse - Overview JBoss Fuse is an open source, lightweight and modular integration platform with a new-style Enterprise Service Bus (ESB) that supports integration beyond the data center. The capability to connect all enterprise assets and the ability to deploy JBoss Fuse in several different configurations advances intelligent integration to all facets of your business – on premise or in the Cloud. JBoss Fuse for xPaaS extends the integration capabilities to OpenShift Platform-as-a-Service (PaaS) solution. Pattern based Integration framework Spring Web Flow The sweet spot for Spring Web Flow are stateful web applications with controlled navigation such as checking in for a flight, applying for a loan, shopping cart checkout, or even adding a confirmation step to a form. What these scenarios have in common is one or more of the following traits: There is a clear start and an end point.The user must go through a set of screens in a specific order.The changes are not finalized until the last step.Once complete it shouldn't be possible to repeat a transaction accidentally Spring Web Flow provides a declarative flow definition language for authoring flows on a higher level of abstraction. It allows it to be integrated into a wide range of applications without any changes (to the flow programming model) including Spring MVC, JSF, and even Portlet web applications. The following are common issues observed in stateful web applications with navigation requirements:

DeviceOrientation Event Specification Abstract This specification defines several new DOM events that provide information about the physical orientation and motion of a hosting device. Status of This Document This section describes the status of this document at the time of its publication. » Advanced Apache Camel logging and best practices Middleware Warez Apache Camel supports a mapped diagnostic context which can be used to improve log entries, but also there is a log component which makes it easier to create log entries. Together they can be used to create foundations of activity monitoring without need to deploy another tool or database. Logging anti patterns First of all let’s go throught logging anti patterns described years ago by Gojko Adzic.

Tuning Java Virtual Machines (JVMs) WebLogic Server Performance and Tuning The Java virtual machine (JVM) is a virtual "execution engine" instance that executes the bytecodes in Java class files on a microprocessor. How you tune your JVM affects the performance of WebLogic Server and your applications. The following sections discuss JVM tuning options for WebLogic Server:

Team Blog A bit over a year ago we released Vaadin 7 renewing the framework inside out. Then came push support with 7.1. Now what? Let’s take a look into the future. First off, we do not see C# coming up (who is this Nutella guy anyway?). Extract, transform, load In computing, extract, transform, and load (ETL) refers to a process in database usage and especially in data warehousing that: Extracts data from outside sourcesTransforms it to fit operational needs, which can include quality levelsLoads it into the end target (database, more specifically, operational data store, data mart, or data warehouse) ETL systems are commonly used to integrate data from multiple applications, typically developed and supported by different vendors or hosted on separate computer hardware. The disparate systems containing the original data are frequently managed and operated by different employees.

Writing large Files line by line with Apache Camel For a transformation with Smooks we had to parse the incoming EDI files line per line, to create a valid EDI source. For this we wrote a simple route like this: This route reads a file, splits it into line chuncks, each line will be parsed and finally the modified line will be added to a file in the destination folder. Really simple and it does what it was build for… But that approach is really slow. For each line we have a single write operation. Hostile Coding: JDeveloper: Deploy your project to an external WebLogic Server JDeveloper by default uses it's internal WebLogic Server to deploy your projects. When your project is completed presumably you will deploy your application to a production WebLogic Server. In this post I explain how to create a deployment profile and deploy your project to an external WebLogic Server. I use the previously created SSXA webpage sample as reference but the procedure is the same for other applications like ADF ones.

war plugin The WAR Plugin is responsible for collecting all artifact dependencies, classes and resources of the web application and packaging them into a web application archive. Usage General instructions on how to use the WAR Plugin can be found on the usage page. Setting Single Server Mode If you want to perform unit testing or quick restarts, you might find it more convenient to avoid the network and run in single-server mode. To constrain Coherence to run on a single server, set the multicast packet time-to-live to 0, and set the unicast IP address. You can configure these properties either by declaring system properties on the command line or by editing the values in the operational configuration descriptor, tangosol-coherence.xml file. Setting Single Server Mode in the Operation Configuration Descriptor In the tangosol-coherence.xml file, the multicast packet time to live value is defined by the <time-to-live> subelement of the <multicast-listener> element. The <time-to-live> value determines the maximum number of "hops" a packet may traverse between network segments.

Related:  ofbizIntegration