-
1. Re: DataSource creation using Java API
jaikiran Nov 14, 2011 7:53 AM (in response to beve)Is this against latest AS7 upstream?
-
2. Re: DataSource creation using Java API
beve Nov 14, 2011 8:09 AM (in response to jaikiran)Yes I think so, as I updated this morning. I'll update again just in case.
Thanks,
/Daniel
-
3. Re: DataSource creation using Java API
beve Nov 14, 2011 8:58 AM (in response to beve)Is this against latest AS7 upstream?
I've updated and there was nothing new pulled from upstream.
-
4. Re: DataSource creation using Java API
maeste Nov 14, 2011 8:59 AM (in response to beve)It's intentional: if you read operation description for add you can see that enabled is no more a parameter.
All DataSources are added as NOT enbled and the user have to explicit invoke enable operation to get it deployed (and register to jndi).
The reason for that is we need this deployed-but-not-enabled state to add connection-properties if they are needed (and xa-datasurce-properties for XA ds).Moreover this state permit to edit any attribute and add/remove subresources (connection-properties and xa-datasource-properties) without reload all tje server. We provide both enable and disable operation to manage transitions.
AFAIK web console is hiding this double operation and also cli should do that in future. Also xml parsing is hiding this double operation in case the ds is declared enabled in standalone.xml.
Of course if you are using directly API you have to take care of this extra effort.
best regards
S.
-
5. Re: DataSource creation using Java API
beve Nov 14, 2011 9:05 AM (in response to maeste)Of course if you are using directly API you have to take care of this extra effort.
Ok, no problem with that.
Thanks for the detailed description!
/Daniel