Show Table of Contents
10.25. Configuring the Enterprise Service Bus
All components within the core of the product receive their configuration parameters as XML. How these parameters are provided to the system is hidden by the
org.jboss.soa.esb.parameters.ParamRepositoryFactory:
public abstract class ParamRepositoryFactory
{
public static ParamRepository getInstance();
}
This instruction returns implementations of the
org.jboss.soa.esb.parameters.ParamRepository interface which allows for different implementations:
public interface ParamRepository
{
public void add(String name, String value) throws
ParamRepositoryException;
public String get(String name) throws ParamRepositoryException;
public void remove(String name) throws ParamRepositoryException;
}
Within the JBoss Enterprise SOA Platform, there is only a single implementation (the
org.jboss.soa.esb.parameters.ParamFileRepository) which expects to be able to load the parameters from a file. The implementation to use this may be over-ridden using the org.jboss.soa.esb.paramsRepository.class property.
Note
Red Hat recommends that you construct your ESB configuration file using JBoss Developer Studio or an XML editor of your choice. The JBossESB configuration information is supported by an annotated XSD, which should be of help if you are using a more basic editor.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.