The issue with win32 in general is that programs tend to acquire exclusive
locks on files whereas *nix does not.
----- Original Message -----
From: "David Maplesden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 20, 2001 8:29 PM
Subject: RE: [JBoss-dev] RH, Jetty, Service Archives...
> It definately happens my Windows 2000 system, I don't know if it happens
> under other OS's or not. The basic solution (I believe) is as you say, to
> copy the original then open the copy.
>
> David
>
> > -----Original Message-----
> > From: David Jencks [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, September 21, 2001 3:33 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-dev] RH, Jetty, Service Archives...
> >
> >
> > <snip>
> > > All the jars in the sar are also copied to
> > > ${jboss.system.deployed}\sarname
> > > to avoid the file sharing violations that prevent the user
> > from simply
> > > moving the original file to undeploy. This is under the
> > assumption that
> > > all
> > > required classes are now in jars, I guess we can copy plain
> > class files
> > > too,
> > > but jars would be neater I reckon.
> >
> >
> > Is this (file sharing violations) some kind of windows-only problem? I
> > haven't had it yet or I would have fixed it ;-). Is the fix
> > to copy the
> > original, then open the copy?
> >
> > david jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
