Main

Navigation:

Jean-Baptiste Onofré's blog

SMX and DTD validation

I have add a new property in ServiceMix utils (1.2.0-SNAPSHOT) to define if a XML has to be validated using a DTD or not. By default, ServiceMix doesn't validate but you can turn this feature on using:

-Dorg.apache.servicemix.default.validating-dtd=true

Connect to SMX4 JMX

If you encounter issue to remotely connect to your SMX4, I can be due to a mistake in the hostname.
http://java.sun.com/javase/6/docs/technotes/guides/management/faq.html#linux1

ServiceMix Exec and ServiceMix LDAP components are now in the ASF SVN repo (2009-04-23)

I have migrated the servicemix-exec and servicemix-ldap components to the ASF SVN repo. A first usable snapshot of servicemix-exec is available. You can find the source here:
http://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-exec/trunk/

http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-ldap/trunk/

BuildProcess AutoDeploy is now under Apache license (2009-02-08)

A deep change is in progress on the AutoDeploy head branch. AutoDeploy (new 1.0 release) will use the Apache license (in preparation of the migration to the Apache Software Foundation under the name of Apache Kalumet) and a new project layer is in progress (using separate POM).
You can see the progress of the change on the subversion repo :
http://buildprocess.svn.sourceforge.net/viewvc/buildprocess/AutoDeploy/trunk/

ServiceMix Exec Component (2009-02-08)

I have begun a new ServiceMix component : the Exec one.
This component is a Service Engine allowing to execute a system command using arguments provided in an incoming normalized message, and return back a normalized message with the system command execution results.
For now, the component is on my local subversion repo :
http://svn.nanthrax.net/servicemix-exec/trunk/

Discussion around how to share Camel components and ServiceMix JBI components (2009-02-03)

The new ServiceMix components proposal includes the LDAP one. Camel already provides a LDAP component.
So the coming question is : why to create a ServiceMix JBI LDAP component whereas Camel already provide one and that ServiceMix includes Camel ?
The main difference between Camel component and a ServiceMix one is that a Camel component doesn't include a live cycle as a JBI component supports.
Nevertheless, we can add this component live cycle over a Camel component.
The ServiceMix LDAP component will be a candidate of this implementation. Comparing the ServiceMix and Camel components, we can define a design to do it.

ServiceMix LDAP Component (2009-02-03)

A new ServiceMix binding component is on the road. The LDAP Binding Component is able to poll and send on a LDAP directory server. The LDAP is polled using a base search and filter, the returning entries with attributes are formated in XML and send into the NMR. In the same way, the component are able to receive a message from the NMR, construct an entry and add in the LDAP directory.
For now, it's in early alpha stage.
http://svn.nanthrax.net/servicemix-ldap/trunk/

ServiceMix SMPP Component (2009-01-31)

I have developed a SMPP binding component for ServiceMix. This component is able to send and poll mobile SMS (using a SMPP gateway server) into the ServiceMix NMR.
The component itself is quite complete now, I need to add deeper unit tests (especially providing a SMPP server mock).
http://issues.apache.org/activemq/browse/SM-1623

http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-smpp/

ServiceMix SU Classpath Extension (2009-01-23)

Currently, in ServiceMix, it's possible to use <classpath/> tag in a SU xbean.xml to extend the SU classloader (with a location, sharedlib, component, etc). The problem is that, currently, the <location/> takes File object. I'm going to extend this to use JarUrlConnection to be able to use Jar entries (for exemple inside an ear). With this patch, user will be able to use :

<classpath>
  <location>jar:file:/path/to/my.ear!/lib/my.jar</location>
</classpath>

http://issues.apache.org/activemq/browse/SM-1771

BuildProcess AutoDeploy becomes Apache Kalumet ? (2009-01-20)

BuildProcess AutoDeploy is a automatic environment upgrade tool mainly focus in the JEE world. It supports main JEE application servers (RedHat JBoss, Oracle Weblogic, IBM Websphere) and covers extra middlewares (such as static content (batches, etc), CMS, configuration files, etc).
AUtoDeploy is now developed since 4 years and already provides stable production release used by several customers (Fimasys, Vodacom South Africa, Mayo Clinic USA, etc).
To speed up the development of AutoDeploy and increase the popularity of the tool, I have proposed Kalumet to the Apache Software Foundation. Apache Kalumet is the port of AutoDeploy to the ASF. In fact, it's the 0.6 release of AutoDeploy (based more on Spring, Java5, etc).
There is a discussion thread in the Apache Incubator mailing list.
I hope that the proposal vote will be plan soon.
http://wiki.apache.org/incubator/KalumetProposal

Fimasys FSB based on Apache ServiceMix (2008-12-20)

A first release of the FSB (Fimasys Service Bus) has been released. It's an ESB oriented to business (financial/credit). It allows to easily integrate Fimasys ProFinance and WebEpargne products (SOI) in existing software environment. The FSB is based (of course :)) on Apache ServiceMix 3.3.0.
http://www.fimasys.com

Edit This Page More Info Attached A File

This page has been modified 04-Jun-2009 17:06:30 CEST by Nanthrax.

NanthraxWiki

Blog