It's always seemed like a feature to me that you only
have to deal with one
concept instead of two.
I'm with you. I have always used the GlassFish
connection pool+resource with a 1:1 relationship.
It's quite good indeed to be able to have them in a
single artefact. In fact, lots of (smaller) applications
even have the trio pool, datasource, persistence unit always
in a 1:1:1 relation, and it would be great if we can think
of something to accommodate these applications and make the
config even simpler for them.
Yet, as mentioned in the previous email, with the current
DataSourceDefinition there's really no (official) way to get
to the pool. In Payara we use a prefix scheme to distinguish
the two sets of properties, but having to attributes would
probably be a bit clearer. Also, for advanced cases (think
frameworks such as OmniFaces), it would actually be great if
there was some kind of type that could be obtained
representing the pool, so this could be wrapped if needed.
Maybe this is thinking a few steps too far for now though ;)
Kind regards,
Arjan Tijms
