[
https://issues.apache.org/jira/browse/GERONIMO-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated GERONIMO-4395:
---------------------------
Attachment: Geronimo-4395-1114-with-replace.patch
Geronimo-4395-1114-without-replace.patch
I create two patch, one is with the replacement code, another is not.
I added some extra codes to handle if the pool name is end with '/'.
I have run the console test suites, the patch does not cause any case fails.
By the way, I guess we need to put more validation logic on the client side,
not in the port lets, so that we could avoid too many codes in the port let to
handle all the user inputs.
Please help to review the patch, Thanks !
> 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
> Assignee: Lin Sun
> Priority: Minor
> Attachments: Geronimo-4395-1109.patch,
> Geronimo-4395-1114-with-replace.patch,
> Geronimo-4395-1114-without-replace.patch, 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.
