marc fleury wrote: > I understand what you proposed what I don't understand is the above, see > below :)
Ah, sorry, now I understand. We're talking about slightly different things. > Question: can you overwrite the jar if the vm holds a open connection to it > and thus a lock to it in windows (file in usage)? No. > If no which is my assumption for this discussion then you don't know when > ANT is going to replace that file from JBoss, or when the user wants to drag > and drop, it is an asynchronous operation that happens without your > knowledge (won't happen in this case) I was thinking about the same case as now, where there is one original copy (in /deploy) and one copy being actually used. The original copy would never be locked, but currently the copy being used is. *That* is what this solution would fix. You'd still need two copies. For the other case, you'd simply not use auto deployment. Introduce an Ant target that does "JBoss Deploy" and which does undeploy-copy-deploy directly to the server. Then you can work with the original file without problems. Personally I'd prefer this explicit way of doing deploy, since auto deployment seems a little funky right now (we get dual deployments quite often). > |6. At this point there are no open connections to the JAR, so it can be > |replaced with a new file or removed. > > no see above, you don't know *when* someone is going to replace the file so > you can't be "open most of the time". > > Do we agree here? We were talking about different files, that was the problem. > almost, some googoo on my glasses still (or is it yours?) As above, we talked about different things. We were both "right" :-) /Rickard -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
