Posts
Latest posts with tag filters.
Filter by tag
Advanced Apache Camel logging and best practices
Apache Camel supports a [mapped diagnostic context](http://camel.apache.org/mdc-logging.html) which can be used to improve log entries, but also there is a [log component](http://camel.apache.org/log) 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.
Apache Aries under Apache Tomcat
Few months ago I've read an article written by my friend [Jacek Laskowski](http://jlaskowski.blogspot.com) \- [Enterprise OSGi runtime setup with Apache Aries Blueprint](http://www.jaceklaskowski.pl/wiki/Enterprise_OSGi_runtime_setup_with_Apache_Aries_Blueprint "Enterprise OSGi runtime setup with Apache Aries Blueprint"). In his article Jacek describes which bundles should be installed to get the blueprint working. As IBM employee Jacek can always promote IBM WebSphere in version X or Y which started (or will start) supporting blueprint as dependency injection mechanism. That's not fine for these who do not run IBM producs and want something light. As you know, Aries and OSGi Blueprint is an alternative for old-fashion Spring approach.
Running aspects under OSGi 4.2 with Karaf
One of bigest benefits of Java is byte code manipulation. You can change everything you want in your application without touching source code. That's usefull for many cases, starting from legacy code, where we can't simply modify and recompile library up to modern applications where aspects can be used to handle runtime exceptions. The most popular project is [AspectJ](http://eclipse.org/aspectj/) which is part of [Eclipse](http://eclipse.org) ecosystem, in this post I going to show you how to use AspectJ with Karaf.
Preserving message order in ActiveMQ
Introduction to Karaf WebConsole
Building sample middleware - producer
XML Schema Design Patterns
Building sample middleware – data structures
Building sample middleware - broker
At end of the May I had great time in United Kingdom providing consulting. After this I started thinking about sharing an idea of middleware application based on ActiveMQ and Camel features. I've spent few days to create sufficient example. # What middleware is? Middleware is a general term, about some software which is some kind of proxy between other systems. What for? - you could ask. Generally because communication from point to point is not the best to build bigger applications, and some components in middle of communication allows us to inject new logic without changing source systems. Could you imagine situation where you have a number of system producing messages and an number of consumers of these messages written in different languages? That's typical case where middleware is going to be usefull. There is number of middleware tools from various categories, in this post we'll learn how to use ActiveMQ to build message oriented middleware. What does the MOM means? Generally that we have asynchronous communication without direct method invocations. Producer don't know anything about consumer and vice versa. If you are interested in MOM - pick up " [ActiveMQ in Action](http://manning.com/snyder/)" book (written by commiters of ActiveMQ) from [Manning Publications Co.](http://manning.com) where this term is described in greater detail.