OSGi JBossESB remote client

[blep]

Hello,

I'm building an OSGi bundle in which a class has to be able to call an ESB service.

So I embeded all client jars needed to make it happend and the jbossesb-properties.xml at the bundle's root.

But during runtime, in the OSGi container, the common error occured:

Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: Invocation exception. null

which the root cause is the jbossesb-properties.xml is not found in the classpath.

I did not find yet the way to make the jbossesb-properties.xml available in the classpath in OSGi environment, so is there any way to set the jbossesb-properties.xml file location?

[blep]

OK

After reading com.arjuna.common.util.FileLocator source code, I saw that if the System property org.jboss.soa.esb.propertyFile is preffixed by abs://, then the file is looked up through out the file system:

System.setProperty(Environment.PROPERTIES_FILE, "abs://c:/myfile.xml");

[rmolin]

I've been through all that:

I'm writing a Eclipse RCP application which interfaces with JBoss ESB for all backend services. I started out thinking it was better to use the ServiceInvoker class, but after the horrors of getting all jars included (with proper OSGi dependencies), getting all configuration files in place and then witnessing how slow and bloated it was, I resorted to invoking services using simple http, socket or perhaps JMS gateways.

My advice to you is that you give serious thoughts to doing the same

/Rune

[kconner]

Agreed, it is currently better to access the ESB through a gateway if the code is not executing within the ESB server.

This is one of the issues that we aim to address with the rewrite.

Kev

[blep]

Of course... I'll remember the advice...

One goal was to reuse an existing component which was directly connected to the ESB, so I did not think about the GWs!