geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1421) DB portlet failure in Tomcat only
Date Thu, 27 Apr 2006 17:12:37 GMT
     [ ]

Aaron Mulder updated GERONIMO-1421:

    Fix Version: 1.1
                     (was: 1.2)
      Assign To: Aaron Mulder
       Priority: Blocker  (was: Major)

Someone commented on either the Pluto or Tomcat issue that Tomcat definitely was not responsible
for encoding and it was just a fluke that Jetty did it for you and it was clearly either Pluto
or the end user that should do the encoding.  I believe a workaround has been put in the portlet
code; need to confirm for 1.1.

> DB portlet failure in Tomcat only
> ---------------------------------
>          Key: GERONIMO-1421
>          URL:
>      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:
For more information on JIRA, see:

View raw message