[
https://issues.apache.org/jira/browse/GERONIMO-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647653#action_12647653
]
Lin Sun commented on GERONIMO-4395:
-----------------------------------
BTW, I forgot to mention - I think a better approach is to allow users to
config their own groupid (currently has to be console.db), version (currently
has to be 1.0) and artifactId, from the portlet page. Ivan, if you like you
are welcome to submit a patch for that.
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
> 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.
