[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
David Jencks updated GERONIMO-2006:
---
Attachment: badPlan.xml
Updated badPlan.xml with configId >> moduleId change and
context-priority-classloader removed.
> Deploying an application wit
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
---
Patch Info: [Patch Available]
> Deploying an application with an incorrect deployment plan results in
> non-functional admin console panel
> -
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
---
Attachment: deployment_portlet.jpg
attaching screenshot of deployment portlet shown providing an upgraded plan
> Deploying an application with an inco
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Paul McMahan updated GERONIMO-2006:
---
Attachment: GERONIMO-2006.patch
I was able to recreate the problem on tomcat. It is caused by a buffer overrun
when render parameters that are set du
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Aaron Mulder updated GERONIMO-2006:
---
Component: deployment
Priority: Blocker (was: Major)
> Deploying an application with an incorrect deployment plan results in
> non-functional ad
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Erin Mulder updated GERONIMO-2006:
--
Fix Version: 1.1
Assign To: Aaron Mulder
While trying to reproduce this, I discovered different behavior in Tomcat vs.
Jetty, and in web console v
[ http://issues.apache.org/jira/browse/GERONIMO-2006?page=all ]
Dave Colasurdo updated GERONIMO-2006:
-
Summary: Deploying an application with an incorrect deployment plan results
in non-functional admin console panel (was: Deploying an application w
