users@javaee-spec.java.net

[javaee-spec users] Re: Digest for list users_at_javaee-spec.java.net

From: Adam Bien <abien_at_adam-bien.com>
Date: Fri, 12 Aug 2016 06:49:45 +0200

HI Arjan,

separation between pool and datasource properties is a good idea.

Programmatic configuration would be useful as well.

cheers,

adam

> On 11.08.2016, at 22:42, users-request_at_javaee-spec.java.net wrote:
>
> Table of contents:
>
> 1. [javaee-spec users] Updating DataSourceDefinition in Common Annotations - arjan tijms <arjan.tijms_at_gmail.com>
>
>
> From: arjan tijms <arjan.tijms_at_gmail.com>
> Subject: [javaee-spec users] Updating DataSourceDefinition in Common Annotations
> Date: 10. August 2016 um 23:58:41 MESZ
> To: users <users_at_javaee-spec.java.net>
> Reply-To: users_at_javaee-spec.java.net
>
>
> Hi,
>
> The @DataSourceDefinition (and corresponding DD equivalent) has an attribute called properties.
>
> In practice these properties are intended for either the data source itself (as JavaBean properties on the class identified by "className"), OR for the pool that manages connection for that data source.
>
> This fact however is not entirely clear. The javadoc only refers to them being "vendor-specific properties".
>
> What about one or more of the following:
>
> A) Clarifying existing properties are properties for either the datasource or the pool managing it
> B) Introducing new "dataSourceProperties" and "poolProperties" attributes
> C) Some handle for programmatically providing pool properties, e.g. an attribute taking a class name which implement Supplier<Map<String, String>>
>
> Thoughts?
>
> Kind regards,
> Arjan Tijms
>
>
>
>
>
>
> End of digest for list users_at_javaee-spec.java.net - Thu, 11 Aug 2016