[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
[jira] Commented: (GERONIMO-851) Move Geronimo Build to M2 (Maven 2)
[ http://issues.apache.org/jira/browse/GERONIMO-851?page=comments#action_12319123 ] David DeWolf commented on GERONIMO-851: --- I just got done converting Pluto's 1.1 branch to maven to and would be willing to help out. I'm not that familiar with Geronimo's code base but maybe this would be a good opportunity to get my feet wet so that I can eventually help upgrade the web console to use Pluto 1.1. . .If you have any spefics you'd like me to submit patches for, let me know ([EMAIL PROTECTED]). Otherwise I'll take a look a look and see where I may be able to help. > Move Geronimo Build to M2 (Maven 2) > --- > > Key: GERONIMO-851 > URL: http://issues.apache.org/jira/browse/GERONIMO-851 > Project: Geronimo > Type: Task > Components: buildsystem > Reporter: John Sisson > Assignee: John Sisson > Fix For: 1.0 > > Created this issue to keep track of the status of work to move the Geronimo > build to Maven 2. Does anyone know the status of this effort? I believe some > work was done in OpenEJB? When is the move to M2 planned for? 1.0 or 1.1 > FYI.. In June I attempted to use Maven 1.1 beta 1 to build geronimo and got > some parse exceptions in maven. As a result, some small changes were made to > some project.xml files by David Jencks, which fixed the parse problem, but we > then ran into another problem where we were getting a > java.lang.NoSuchMethodError in maven. This should now be fixed using an > updated artifact plugin, see http://jira.codehaus.org/browse/MAVEN-1625 (but > I have not verified this). -- 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-859) Remove SNAPSHOT dependency on Pluto
[ http://issues.apache.org/jira/browse/GERONIMO-859?page=comments#action_12318254 ] David DeWolf commented on GERONIMO-859: --- I have uploaded the most recent SNAPSHOT distributions to the cvs.apache.org repository. Thanks to Jeremy for the pluto patch. > Remove SNAPSHOT dependency on Pluto > --- > > Key: GERONIMO-859 > URL: http://issues.apache.org/jira/browse/GERONIMO-859 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0-M5 > Reporter: Jeremy Boynes > Fix For: 1.0-M5 > > Replace the dependency on a SNAPSHOT version of Pluto with a release version. > Currently using a SNAPSHOT version as that supports upload of its artifacts > to a maven repo. -- 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
