[
https://issues.jboss.org/browse/AS7-2681?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-2681:
--------------------------------
Assignee: (was: Thomas Diesler)
The jaxr client can be configured via system properties like this
{code}
<system-properties>
<property name="javax.xml.registry.ConnectionFactoryClass"
value="org.apache.ws.scout.registry.ConnectionFactoryImpl"/>
<property name="jaxr.publish.url"
value="http://localhost:8080/juddi/publish"/>
<property name="jaxr.query.url"
value="http://localhost:8080/juddi/inquiry"/>
<property name="scout.proxy.transportClass"
value="org.jboss.as.jaxr.scout.SaajTransport"/>
</system-properties>
{code}
The UDDI registry HTTP endpoint is not intended to get distributed, so hard coded values
for
* juddi/publish
* juddi/inquiry
are ok for now.
Make JAXR http endpoint configurable
------------------------------------
Key: AS7-2681
URL:
https://issues.jboss.org/browse/AS7-2681
Project: Application Server 7
Issue Type: Task
Components: JAXR
Reporter: Thomas Diesler
Fix For: 7.1.0.CR1
Currently, the HTTP endpoint and database services are installed based on
{code}
if (config.getDataSourceBinding() != null) {
newControllers.add(JAXRDatasourceService.addService(serviceTarget,
config, verifyHandler));
newControllers.add(JAXRHttpEndpointService.addService(serviceTarget,
config, verifyHandler));
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira