Opened a JIRA to keep track of this -
https://issues.apache.org/jira/browse/GERONIMO-2892
Cheers
Prasad
On 2/22/07, Anita Kulshreshtha [EMAIL PROTECTED] wrote:
After few build problems (see another thread) I got
test-ear-j2ee_1.4 to deploy and undeploy. The following files are left
in
On Feb 21, 2007, at 10:59 PM, Prasad Kashyap wrote:
Verified this on the same windows machine using M1
( http://apache.ziply.com/geronimo/2.0-M1/ )
Used the same test app (
http://people.apache.org/~prasad/test-ear-j2ee_1.4-2.0-SNAPSHOT.ear )
The undeploy completely cleans the G repo of all
OK. I see the issue. PersistentUnitGBean is cloning the EAR
classloader and giving it to OpenJPA. I don't see where this CL will
ever be destroyed. Will need to work through the lifecycle...
--kevan
After few build problems (see another thread) I got
test-ear-j2ee_1.4 to deploy and undeploy. The following files are left
in geronimo repo. The ejb-cpm2.jar is locked and can not be deleted.
The following files/dirs are left in var\temp
OpenEJB_Generated_43980.jar
Can somebody please verify that the undeploy works (on Windows) ?
Using the command line, I deploy and undeploy an app. The entry gets
removed in the config.xml. However, the files in the Geronimo repo
gets left behind. These files are locked and they can't even be
manually deleted. The server
Verified this on the same windows machine using M1
( http://apache.ziply.com/geronimo/2.0-M1/ )
Used the same test app (
http://people.apache.org/~prasad/test-ear-j2ee_1.4-2.0-SNAPSHOT.ear )
The undeploy completely cleans the G repo of all traces of the app.
Cheers
Prasad
On 2/21/07, Prasad
