camel cxf https server endpoint

I wanted to configure in camel a cxf https endpoint. Normally I do it the forceful way to update the jdk certificates but it can be done in another way.
Define the jax-ws contract first endpoint, although that can be done also in a code first manner.

This is the defined endpoint, it is directly taken from a camel sample named ‘camel-cxf-contract-first-blueprint’.

<blueprint xmlns=""
	xmlns:xsi="" xmlns:cxf=""
	xmlns:camel="" xmlns:sec=""
	<cxf:cxfEndpoint id="reportEndpoint"
			<entry key="loggingFeatureEnabled" value="true"/>
	<httpj:engine-factory bus="cxf">
		<httpj:engine port="9080">
				<sec:keyManagers keyPassword="changeit">
					<sec:keyStore type="JKS" password="changeit" resource="certs/keystore.jks" />
	<camelContext xmlns="">
        <from uri="cxf:bean:reportEndpoint"/>
        <convertBodyTo type="org.apache.camel.example.reportincident.InputReportIncident"/>
        <log message="Received report incident ${body.incidentId}"/>
        <setHeader headerName="Exchange.FILE_NAME">
        <to uri="file:work/incident"/>
        <log message="Stored a copy of the incident as ${header.CamelFileNameProduced}"/>
                <to uri="seda:emailMe"/>
                <to uri="seda:callMe"/>
        <to uri="language:constant:classpath:ok.xml"/>
        <convertBodyTo type="org.apache.camel.example.reportincident.OutputReportIncident"/>
        <from uri="seda:callMe"/>
        <log message="We are going to call ${}"/>
        <from uri="seda:emailMe"/>
        <log message="We are going to email ${}"/>

Update the xml code snippet to make it readable again. (2015/01/25)

JAAS authorization with JBoss Fuse

The customer I was working with had a need for JAAS Authorization for the ActiveMQ broker in his JBoss Fuse install. I thought I did it by the book. But it was at the end not enough. I had done this configuration for a FuseSource installation version 7.1.x but it didn’t work for a 7.2.x (JBoss Fuse 6.0.0.redhat-024). For the current, at this writing, version of JBoss Fuse you have to do it like this:

Add or change the plugins settings of etc/activemq.xml into:

<jaasAuthenticationPlugin configuration=”karaf”/>
<authorizationMap groupClass=”org.apache.karaf.jaas.boot.principal.RolePrincipal”><authorizationEntries><authorizationEntry queue=”>” read=”admin,broker” write=”admin,broker” admin=”admin,broker”/>

<authorizationEntry topic=”>” read=”admin,broker” write=”admin,broker” admin=”admin,broker”/>
<authorizationEntry topic=”ActiveMQ.Advisory.>” read=”admin,broker” write=”admin,broker” admin=”admin,broker”/>
It is all about the ‘groupClass’ attribute inside the ‘authorizationMap’ element.
You can read more about this at

Creating a osgi jdbc driver

For work I have to work with different datasource connections. Not only in a JEE environment but also in a OSGI environment. A datasource needs also a jdbc connection. And a jdbc driver jar bundled in osgi format is not always available. I normally try to find a osgi jdbc jar in the servicemix repository but that will work only for OSS drivers.

For a closed source jdbc driver to be converted to a bundle version of the jar you could use a maven plugin. But that is more work then the following:

Fire up a Fusesource or JBoss Fuse instance and have the jdbc driver available on the disk. Inside the fuse console execute the command ‘osgi:install wrap:file:///tmp/ojdbc6.jar’.  When the command finished it will return a number.

Use this number to go to the cache directory with this number (data/cache/bundlexxx/version0.0). Inside the directory you will find the ojdbc6.jar named as bundle.jar. Take the bundle.jar and rename it (back) to ojdbc6-osgi.jar. The -osgi addition is just a naming convention I adopted. Place ojdbc6-osgi.jar in your package manager.