Hey
One of the things we have bragged about is the hot deployment features.
Unfortunately it was only half-working: when a .jar file was deployed
through the filesystem it got locked by the classloader, so it couldn't
be updated. This effectively made hot updates of .jar files impossible.
This has now been fixed! The .jar file is first copied to a temporary
file and deployed from there. This means that you are free to update
your .jar (for example you can edit the deployment descriptor in the EJX
GUI) while it is deployed. When you replace it ("Save" in EJX for
example) it will be redeployed (undeploy followed by deploy).
Fix is in CVS.
Have a good one,
Rickard
ps. This is only a temporary fix as it unfortunately removes the EJB
security restrictions capability. If you really really want to restrict
your beans from doing bad things you'll have to wait :-)
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
