[jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only
[ 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
[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
[jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only
[ http://issues.apache.org/jira/browse/GERONIMO-1421?page=comments#action_12364018 ] Aaron Mulder commented on GERONIMO-1421: Entered Tomcat 5 bug 38390: http://issues.apache.org/bugzilla/show_bug.cgi?id=38390 DB portlet failure in Tomcat only - Key: GERONIMO-1421 URL: http://issues.apache.org/jira/browse/GERONIMO-1421 Project: Geronimo Type: Bug Components: console, Tomcat Versions: 1.0 Reporter: Aaron Mulder 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
[jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only
[ http://issues.apache.org/jira/browse/GERONIMO-1421?page=comments#action_12362147 ] David DeWolf commented on GERONIMO-1421: Render parameters are stored within the url so that they persist across render requests and do not rely on session state. The PortalControlParameter class is primarily responsible for converting render parameters, modes, window states, etc . . .to a portal url. See: http://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.0.2/portal/src/java/org/apache/pluto/portalImpl/core/PortalControlParameter.java Also See: http://svn.apache.org/repos/asf/portals/pluto/branches/pluto-1.0.2/portal/src/java/org/apache/pluto/portalImpl/core/PortalUrl.java I'm trying to think of any reasons why this conversion would be dependent upon the underlying servlet container. The only thing I can think of is that the two containers are returning different values from request.getPathInfo() (which is subsequently parsed back into modes, window states, and render parameters). I would be willing to bet that the issue is with the semi-colon in the parameter. A quick glance at the source code indicates that pluto does not treat it as a special character and thus it is not encoded within the url. If that is happening, I'll bet that tomcat is truncating pathInfo at the semi colon and jetty is not. Let me know if you have any more follow up questions. . .I'll look into this a little bit more tomorrow as well. DB portlet failure in Tomcat only - Key: GERONIMO-1421 URL: http://issues.apache.org/jira/browse/GERONIMO-1421 Project: Geronimo Type: Bug Components: console, Tomcat Versions: 1.0 Reporter: Aaron Mulder 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
