[
https://issues.apache.org/jira/browse/GERONIMO-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645776#action_12645776
]
Lin Sun commented on GERONIMO-4395:
-----------------------------------
How about either options below -
1. Whenever user enters a non-unique database pool name, we warn the user
immediately (for example, when they click on the Next button)
2. Only generate random artifactid when there the artifactid is not going to be
unique since this is a very rare case. I like the preserve the current
behavior because there is nothing wrong with it and I don't want to surprise
our users to hunt for the artifact id.
Thanks
Lin
> EmployeeDatasource and jdbc/EmployeeDatasource create the same files under
> $geronimo_install_dir/repository/console/dbpool directory
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4395
> URL: https://issues.apache.org/jira/browse/GERONIMO-4395
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: databases
> Affects Versions: 2.1.3
> Environment: Any platform
> Reporter: viola.lu
> Priority: Minor
> Attachments: Geronimo-4395.patch
>
>
> Steps:
> 1.Login geronimo, go to database pool, create a "EmployeeDatasource"
> datasource with any db type.
> 2.create another "jdbc/EmployeeDatasource" datasource with any db type. But
> some read error display that
> EmployeeDatasource has existed in database pool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
