Hide Forgot
Date of First Response: 2007-12-18 07:03:19 project_key: SOA When client uses ServiceInvoker then it searches for jboss-properties.xml file that is customized for client-side use. There are a lot of such files in sample dirs but there is no single one official to be used and to which classpath can be pointed.
The majority of these files are identical apart from whitespace. the trailblazer has <property name="org.jboss.soa.esb.persistence.db.conn.manager" value="org.jboss.internal.soa.esb.persistence.manager.StandaloneConnectionManager"/> moved but is otherwise identical ./quickstarts/webservice_consumer{12}/jbossesb-properties.xml have a different persistence url and no persistence.manager ./quickstarts/scripting_groovy/jbossesb-properties.xml and the transform ones have > <properties name="transformation"> > <property name="java.naming.provider.url" value="localhost"/> > </properties> ./quickstarts/helloworld_db_registration/jbossesb-properties.xml has <property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire"/> <property name="org.jboss.soa.esb.registry.lifeCycleManagerURI" value="org.apache.juddi.registry.local.PublishService#publish"/> indtead of <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/> <property name="org.jboss.soa.esb.scout.proxy.transportClass" value="org.apache.ws.scout.transport.LocalTransport"/> instead of org.apache.ws.scout.transport.RMITransport
What we're looking for are just the sensible defaults. The file is meant to be edited by the user if those aren't right. So there can never be one "official" one. The one in the install/conf directory is the closest we have to such a thing. That should be the one we recommend.
Hi, this file is not usable for client apps. For exmaple all registry realted params are set for local access to registry which does not work when used outside SOA/ESB process. Also dbstore cannot be used as the datasource is not accessible via JNDI to external clients.
This is the configuration file that ships with the ESB standalone. Are you suggesting that it does not work out-of-the-box in standalone, or when deployed into the application server?
I have created a separate template properties file in install/conf.
File is not in the packages
file is merged correctly into the platform branch, the esb install script is not installing it.
Is this done now?
jbossesb-properties.xml.template moved to quickstarts/conf, now appears in both standalone and embedded versions under quickstarts/conf
Verified in beta 2