On Monday, July 18, 2011 04:31:35 PM Scott Stark wrote:
The datasource/connection-url property in the domain model is outside
of
the interfaces and socket-binding-group usage. The current
datasource_1_0.xsd does not have a reference to sockets or interfaces.
No, as you know the connection url is built differently for each database, so
we would have to put in markers to substitute values.
We also don't seem to be setting jboss.server.* system properties
that
could be used to create a configuration fragment like:
<datasource jndi-name="java:jboss/datasources/MysqlDS"
enabled="true"
use-java-context="true" pool-name="H2DS">
<connection-url>jdbc:mysql://${jboss.server.default.interface}:${jboss.serv
er.socket-binding-group.mysql}/database</connection-url>
<driver>mysql</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
What is the plan to allow jca connection factories to integrate into the
interfaces/ports part of the domain model?
This came up as we add support for mysql in the openshift express
cartridge, and modification of the connection-url for the host the
server is running on requires changes in two parts of the standalone.xml
configuration rather than one.
System property substitution works on all elements/attributes in the
datasource definition. So I think it is a matter of finding out which
elements/attributes we want to expose as system properties in the domain
model.
Maybe even define them as system properties in the first place and then use
those values in the various subsystems. Others can comment on that idea.
Best regards,
Jesper