geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only
Date Sat, 29 Apr 2006 19:53:38 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1421?page=comments#action_12377120 ] 

Aaron Mulder commented on GERONIMO-1421:
----------------------------------------

Currently we have a very limited workaround to substitute %3B for ; and nothing else.  Will
try a more general fix of URL-Encoding the JDBC URL to handle & and so on.

> 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


Mime
View raw message