A strange thought occurred to me now that we have undeploy
functionality. We previously had (and still have) the ability to
scrape the system classpath for ejb-jar.xmls or beans that are
annotated. It's not technically the system classpath, more like the
classpath of OpenEJB itself. This could be stuff in the lib dir etc.
So here's the interesting question. Should we allow these things to
be undeployed? We could get rid of everything but the classes
themselves, those would more or less be stuck. It could technically
be possible to reload any ejb-jar.xml data they have if someone
wanted to have them deployed again.
It could be messy, not sure what to think.
Thoughts?
-David
