[jboss-as7-dev] datasource/connection-url reference to interfaces/ports

[Emanuel Muckenhuber]

I think that's a valid point. Having a comprehensive view and consistent 
configuration mechanism for ports was the underlying use-case and 
motivation behind the socket-bindings.

Although i agree that what we have does not really seem to good fit for 
describing something like datasource connection. If this is something we 
would like to do, we can perhaps look into extending the socket-binding 
concepts?

On 07/19/2011 08:28 PM, Scott Stark wrote:
> So combining Jaikiran's and Jesper's posts, the connection-url is
> different from the existing interface/socket binding group usage in that
> there may not be a service in the server which is providing the socket
> binding. This is a possibly external/remote endpoint that still should
> be captured in the domain metadata as I would want a comprehensive view
> of the endpoints in use in the domain.
>
> Right now it sounds like how I can capture this would be to define
> system properties and then reference them in the connection-url.
>
> On 7/19/11 10:24 AM, Jesper Pedersen wrote:
>> 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
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev