Well, good news/bad news. Good news is the new code fixes the mac copy problem when I run the prepackaged slide.war with tomcat. The bad news is when I integrate the jars with my app, I still can't copy files. I'm deep in the middle of things trying to track down what's different. Both are using the TxXMLFileDescriptorsStore and both are configured similarly (well, mostly - we do our own authentication). We are using Jetty as our servlet engine.
I'm sure it's something related to our configuration, but I haven't tracked it down yet. The search continues... John -----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 November 2004 5:43 PM To: Slide Users Mailing List Subject: Re: Mac OSX Issue This *might* be the issue we just fixed. If you know how to do this please check out latest sources eithre from CVS Head or the release branch for Slide 2.1 and see if this changes anything. If this is too much work or too complicated, please send an HTTP trace of the conversation between client and server. Thanks, Oliver On Wed, 10 Nov 2004 14:44:11 +1000, John Williams <[EMAIL PROTECTED]> wrote: > I've been trying to track down some info on this since I wasn't sure > if it was a Mac issue or a Slide issue. I've tried contacting Apple's > DTS but they haven't been too keen on helping yet. We'll see if that > changes. > > Some other details I've seen that may or may not help. This is all > using Slide 2.1b2. When running the server on a Mac or Linux box the > Mac clients work fine. When running the server on Windows, the mac > client cannot PUT files. By that I mean, dragging the file into a > folder starts the copy, but then promptly deletes the file after the > put finishes. However, If I mount the server using the IP address, the > drag-copy works fine. Unfortunately, other users at our beta sites > have not had any luck with mounting using the IP addresses. The big > difference I've seen between their setup & ours is that their macs are > on a different subnet than the server. > > Here is a brief summary of the webdav requests between a successful > PUT and a failing PUT. There's not much difference but the transaction > history just seems strange to me, regardless. > > Successful Sequence Failing Sequence > ===================================================================================== > PROPFIND /aa/Images/TestFile.xml PROPFIND /aa/Images/TestFile.xml > PROPFIND /aa/Images/Contents/PkgInfo PROPFIND /aa/Images/Contents/PkgInfo > PROPFIND /aa/Images/TestFile.xml PROPFIND /aa/Images/TestFile.xml > PUT /aa/Images/TestFile.xml PUT /aa/Images/TestFile.xml > PROPFIND /aa/Images/TestFile.xml PROPFIND /aa/Images/TestFile.xml > GET /aa/Images/TestFile.xml GET /aa/Images/TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > PUT /aa/Images/._TestFile.xml PUT /aa/Images/._TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > LOCK /aa/Images/._TestFile.xml LOCK /aa/Images/._TestFile.xml > GET /aa/Images/._TestFile.xml GET /aa/Images/._TestFile.xml > PUT /aa/Images/._TestFile.xml PUT /aa/Images/._TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > UNLOCK /aa/Images/._TestFile.xml UNLOCK /aa/Images/._TestFile.xml > PROPFIND /aa/Images/.DS_Store PROPFIND /aa/Images/.DS_Store > LOCK /aa/Images/._TestFile.xml LOCK /aa/Images/._TestFile.xml > GET /aa/Images/._TestFile.xml GET /aa/Images/._TestFile.xml > UNLOCK /aa/Images/._TestFile.xml UNLOCK /aa/Images/._TestFile.xml > DELETE /aa/Images/._TestFile.xml DELETE /aa/Images/._TestFile.xml > LOCK /aa/Images/TestFile.xml LOCK /aa/Images/TestFile.xml > GET /aa/Images/TestFile.xml GET /aa/Images/TestFile.xml > PUT /aa/Images/TestFile.xml PUT /aa/Images/TestFile.xml > PROPFIND /aa/Images/TestFile.xml PROPFIND /aa/Images/TestFile.xml > UNLOCK /aa/Images/TestFile.xml UNLOCK /aa/Images/TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > PROPFIND /aa/Images/TestFile.xml PROPFIND /aa/Images/TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > PROPFIND /aa/Images/._TestFile.xml PROPFIND /aa/Images/._TestFile.xml > PROPFIND /aa/Images DELETE /aa/Images/TestFile.xml > PROPFIND /aa/Images/._TestFile.xml > PROPFIND /aa/Images > PROPFIND /aa/Images/Images > > If necessary, I can try to capture more detailed info. > > John Williams > > > > -----Original Message----- > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > Sent: Sunday, 7 November 2004 11:13 PM > To: Slide Users Mailing List > Subject: Fwd: Mac OSX Issue > > ---------- Forwarded message ---------- > From: James Mason <[EMAIL PROTECTED]> > Date: Sat, 06 Nov 2004 23:43:27 -0800 > Subject: Re: Mac OSX Issue > To: Oliver Zeigermann <[EMAIL PROTECTED]> > > Maybe having someone setup a recording proxy and running through some > basic usage examples would be a good idea? That would give us some > traffic we could replay on other systems and even incorporate into the > testsuite. > > I know this idea has come up before, so can anyone with access to OS X > volunteer to record a session so the rest of us can help with the > debugging? > > -James > > On Sat, 2004-11-06 at 18:22 +0100, Oliver Zeigermann wrote: > > Folks, > > > > there have been many reports that there is something wrong with > > accessing Slide using Mac OSX. I would like to get this solved, but > > have got no access to a Mac, so I am of little help. > > > > I do not even know what exactly is the problem. So if anyone out > > there who knows, has access to OSX, and knows how to debug Slide > > would help with this issue I would greatly appreciate it. > > > > Certainly without having this solved we will not be able to release > > Slide 2.1 > > > > Oliver > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.792 / Virus Database: 536 - Release Date: 9/11/2004 > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.792 / Virus Database: 536 - Release Date: 9/11/2004 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.792 / Virus Database: 536 - Release Date: 9/11/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.792 / Virus Database: 536 - Release Date: 9/11/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
