On 2001.11.27 17:23:32 -0500 Rickard Oberg wrote: > marc fleury wrote: > > > ok one of us doesn't get it, if you are "open most of the time" how do > you > > release the lock in the filesystem for anyone to overwrite the file ? > I > > could be missing it :) > > > 1. URLCL wants to access "custom://somejar.jar" > 2. It uses CustomURLHandler to get a connection to somejar.jar. This > connection is put in cache and is never let go of. > 3. The connection retrieved from CustomURLHandler is not a real > connection, but merely a wrapper to a file connection. Similar to how a > connection pool provides implementations of Connection that are only > wrappers for real connections that can be managed by the pool. > 4. Operations on the connection are passed on to the file connection. > 5. When redeploy of a JAR is to be done, the wrapper is told to close > its underlying connection > 6. At this point there are no open connections to the JAR, so it can be > replaced with a new file or removed. > 7. At some point the connection wrapper is called, either by the old > URLCL or a new one using the same connection. The file connection is > then re-acquired, only now to the new file. > > See?
So this requires an explicit undeploy of the old jar: it cannot work via an autodeployer watching for changed timestamps, because you have to undeploy the file first before you can change it. You sure this is better than copying? david jencks > > /Rickard > > > -- > Rickard Öberg > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
