You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Paul McMahan (JIRA)" <de...@geronimo.apache.org> on 2006/04/27 23:05:37 UTC

[jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only

    [ http://issues.apache.org/jira/browse/GERONIMO-1421?page=comments#action_12376823 ] 

Paul McMahan commented on GERONIMO-1421:
----------------------------------------

This works ok now.  i.e. in the tomcat version you can add ";create=true" for the generated URL without getting punted out of the wizard, the test connection succeeds, and the new db shows up in the db manager.

> DB portlet failure in Tomcat only
> ---------------------------------
>
>          Key: GERONIMO-1421
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1421
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: console, Tomcat
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>     Priority: Blocker
>      Fix For: 1.1

>
>  - create a new database pool using the DB portlet
>  - select the "Derby Embedded" type
>  - pick the derby or derby-client JAR
>  - give it a new or existing database name
>  - add ;create=true to the end of the generated URL
>  - click test
> This procedure works in the Jetty build but does not work in the Tomcat build.  In Tomcat, it just redirects to the main screen for that portlet without any error message.  The database is actually created (visible in the DB Manager portlet).  This does not happen if you remove ;create=true from the URL and use an existing database.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira