The behavior is changed between v2 to v3. When you try to modify the
primary key of the resource, in this case the pool name, v2 disallows it
but in v3 a decision was made to allow the change. Hence the test will
fail in v2 and pass in v3.
-Sankar
On 8/19/2010 3:45 PM, Lidia Marchioni wrote:
> Hi all
>
> We have the following test from v2 test base:
>
> asadmin set --user admin --host asqe-xeon-1 --port 4848
> sa_server1.resources.jdbc-resource.jdbc/jdbcresDB.pool_name=NewPool
> Deprecated syntax, instead use:
> asadmin --port 4848 --host asqe-xeon-1 --user admin set [options] ...
> sa_server1 :
> sa_server1.resources.jdbc-resource.jdbc/jdbcresDB.pool-name=NewPool
>
> sa_server1.resources.jdbc-resource.jdbc/jdbcresDB.pool-name=NewPool
>
> Command set executed successfully.
>
>
> The issue is that the above test expects the command to fail and the
> following output string:
>
> is not found in list of jdbc connection pools
>
> I thought perhaps the command was wrong, but verified on v2.1 branch
> and the test looks the same there. Could someone please let me know
> if this change of behaviour is expected or an unwanted regression?
> I'll update the test accordingly.
>
> Thanks
> Lidia
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>