[POLL] Do you still rely on JDK 1.3?
We were having a discussion if we should switch to JDK 1.4 with the next Slide release. The question is how many of you still rely on JDK 1.3. Thanks for participating and cheers, Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Slide and XP drive mapping
XP without 3rd party software will only mount a non IIS WebDAV 'share' as a WebFolder. This is only accesible from Office products and products with built-in WebDAV client. Normal windows programs such as notepad, wordpad will not. However, if you use IIS 6, the WebDAV 'share' gets automatically exported as a normal windows 'share' so a site http://machine/WebDAV can be connected as net use w: \\machine\WebDAV using IIS WebDAV Redirector. Nice! -Original Message- From: Glen Stampoultzis [mailto:[EMAIL PROTECTED] Sent: Monday, May 17, 2004 6:27 AM To: [EMAIL PROTECTED] Subject: Slide and XP drive mapping XP supports drive mapping of webdav shares. I was wondering whether slide supports this? I'm having authentication problems when I try this. Web Folders work fine however. Regards, Glen Stampoultzis [EMAIL PROTECTED] - 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]
RE: [POLL] Do you still rely on JDK 1.3?
We use slide in one of our products. We are upgrading to slide 2.x and we do have to support JDK 1.3. Thanks, Kiran. -Original Message- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 12:01 AM To: Slide Users Mailing List Subject: [POLL] Do you still rely on JDK 1.3? We were having a discussion if we should switch to JDK 1.4 with the next Slide release. The question is how many of you still rely on JDK 1.3. Thanks for participating and cheers, Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] If you have received this e-mail in error, please delete it and notify the sender as soon as possible. The contents of this e-mail may be confidential and the unauthorized use, copying, or dissemination of it and any attachments to it, is prohibited. Internet communications are not secure and Hyperion does not, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses. The views expressed here do not necessarily represent those of Hyperion. For more information about Hyperion, please visit our Web site at www.hyperion.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Do you still rely on JDK 1.3?
I'm rolling out slide under jdk 1.4. I can understand people wanting to keep compatibility though. Could those wanting 1.3 compatibility stick with slide 2.0 until they can upgrade to jdk 1.4? Maybe new features / bug fixes in subsequent versions of slide could be back-ported to 2.0 if they were really needed? Jamie. -Original Message- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 8:01 AM To: Slide Users Mailing List Subject: [POLL] Do you still rely on JDK 1.3? We were having a discussion if we should switch to JDK 1.4 with the next Slide release. The question is how many of you still rely on JDK 1.3. Thanks for participating and cheers, 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]
Re: Slide and XP drive mapping
Paul Hussein wrote: XP without 3rd party software will only mount a non IIS WebDAV 'share' as a WebFolder. This is only accesible from Office products and products with built-in WebDAV client. Normal windows programs such as notepad, wordpad will not. However, if you use IIS 6, the WebDAV 'share' gets automatically exported as a normal windows 'share' so a site http://machine/WebDAV can be connected as net use w: \\machine\WebDAV using IIS WebDAV Redirector. I think this is incorrect. The Windows XP Webdav redirector indeed mounts a WebDAV server as a drive, but it does not depend on IIS6 (for instance, I think it may work with Apache/moddav). Rather than that, the issue is that is so buggy that it fails to work with many compliant servers, for various different reasons (authentication, port number != 80, root URL not WebDAV-aware). As far as I understand the situation, Microsoft is aware of the problems but does not plan to resolve them in the foreseeable future. Funny enough, Microsoft's own marketing material mentions the WebDAV Redirector as new XP feature, so it's definitively a documented and advertised feature that's plainly broken (see http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/xptechov.mspx#XSLTsection126121120120). Best regards, Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JSR 170 available for Public Review
http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) -- Davide Savazzi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Slide and XP drive mapping
As far as I am aware, the WebDAV Redirector is a IIS 6 thing. It exports IIS WebDAV folders as Windows Network shares. It is custom MS stuff. WebDAV is built-in to IIS5 (5.1) which ships with XP Pro. However, as a server I am not sure the WebDAV Redirection works. I have seen no documentation for this feature in 5.x. PLease correct me if I am wrong. WebFolders are XP builtin WebDAV client functionality. WebFolders will connect to any WebDAV server, it then comes down to compatibility issues. Using XP Clients you can connect to WebDAV Redirector redirected Shares using normal NET or Map Network Drive functionaility. I have not seen anywhere in the documentation for microsoft any mention of the WebDAV redirector functionaility being interoperable with another implementation of a WebDAV server. If anyone has managed to get a network drive from a slide WebDAV implementation other than using 3rd party software, please tell us. Cheers Paul. -Original Message- From: Julian Reschke [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 9:38 AM To: Slide Users Mailing List Subject: Re: Slide and XP drive mapping Paul Hussein wrote: XP without 3rd party software will only mount a non IIS WebDAV 'share' as a WebFolder. This is only accesible from Office products and products with built-in WebDAV client. Normal windows programs such as notepad, wordpad will not. However, if you use IIS 6, the WebDAV 'share' gets automatically exported as a normal windows 'share' so a site http://machine/WebDAV can be connected as net use w: \\machine\WebDAV using IIS WebDAV Redirector. I think this is incorrect. The Windows XP Webdav redirector indeed mounts a WebDAV server as a drive, but it does not depend on IIS6 (for instance, I think it may work with Apache/moddav). Rather than that, the issue is that is so buggy that it fails to work with many compliant servers, for various different reasons (authentication, port number != 80, root URL not WebDAV-aware). As far as I understand the situation, Microsoft is aware of the problems but does not plan to resolve them in the foreseeable future. Funny enough, Microsoft's own marketing material mentions the WebDAV Redirector as new XP feature, so it's definitively a documented and advertised feature that's plainly broken (see http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/xp techov.mspx#XSLTsection126121120120). Best regards, Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - 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]
Re: Cutom authentication for Slide
Thank you so much ! I had not expected such a complete, accurate - and fast ! - answear :) If I may go further, I have a few more questions. I want to allow users to access Slide from a web frontend (actually a customized Jetspeed portal), from a 'heavy' (client side) Java client AND from some non-browser clients (e.g OpenOffice.org). I had this solution in mind: - The heavy client would access Slide after having authenticated itself to the CAS. In this case, Slide would only ask the CAS to check the validity of the ticket; - The web portal would use CAS as its core authentication service, so there is no problem here; - The non-browser clients would access the resource in Slide through an URL provided by the portal. This URL would contain a portal-generated session ID and Slide - or the request dispatcher - would detect it and use it to authenticate the client. This is summarized in the following architecture (hope it will be readable - please view with fixed width font): ***-**-* | Java || Browser || OOo | | Client |*-**-* ** ^^ ^ ^ || |\ v| | v** S.Id | | *-*---| Portal |--o | | CAS | ** | | *-* ^| | ^|| v vvv *-* | S L I D E | *-* If I understand well, this approach is quite similar to your third proposition. Please correct me if not :) Where should I go for more doc about filters ? I was going to have a look at Tomcat's documentation and/or J2EE docs at java.sun.com, but it would be great if I had some precise pointers :) Again thanks a lot ! Regards, Jean-Baptiste Ben Alex wrote: Hi Jean I'm using Slide 2.0 within Tomcat 5.0.19, JDK 1.4.2_03. I would like to use a custom (SSO) authentication mechanism to control access to the Slide server. Actually, I want to totally get rid of the simple HTTP auth mechanism and use an external tool - for information, the Central Authentication Service (CAS - https://www.yale.edu/tp/cas). Is there any roadmap to follow / featured API to help with this task ? I integrated CAS support into the Acegi Security System (http://acegisecurity.sourceforge.net), which I've also integrated into Slide, so hopefully I can offer some pointers. Slide has a utility class, org.apache.slide.webdav.util.WebdavUtils, which has a method, getSlideToken(). This method obtains the principal from the web container using the normal request.getUserPrincipal() method, or, failing that, from a session attribute named org.apache.slide.webdav.method.principal. This is your magic bridge between third party authentication systems and Slide. :-) For this to work, you DON'T authenticate using standard web container services. So disable web.xml security-constraints etc. You'll need a filter that detects requests to the WebdavServlet from a user that hasn't got a HttpSession attribute with the above name. When the unauthenticated user is detected, you'll redirect them to the CAS server. After login, CAS will post back to another one of your filters which validates the CAS service ticket and sets up a valid Principal implementation in the HttpSession attribute named above. From that point forward, the WebdavUtils class will be able to extract the Principal. Slide only uses Principal.getName(), and then relies on its own authorization store to determine the ACLs that apply. The most work is in the filters/servlets that tie in the CAS login. Also, of course, you'll have a problem in that non-web-browser clients cannot obtain the CAS ticket as they use BASIC authentication which doesn't understand HTTP redirects (which is central to how CAS works). There are some ways you can approach it, though: - Forget about non-browser clients. Ouch... - Write a filter that detects the BASIC authentication request, then posts it through to CAS on behalf of the BASIC authentication client, and then processes the resulting opaque service ticket as described above. - Have dual authentication methods. For web browsers use native CAS. For BASIC authentication clients, directly validate against the backend database from your BASIC authentication processing filter. This is the cleanest model. Acegi Security might be worth a look for some code samples. It does BASIC authentication, CAS integration etc. You could also use it natively to perform most (if not all) of the above. Hope this helps. Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED]
Re: Slide and XP drive mapping
Paul Hussein wrote: As far as I am aware, the WebDAV Redirector is a IIS 6 thing. It exports IIS WebDAV folders as Windows Network shares. It is custom MS stuff. It's built into XP, not IIS. The WebDAV Redirector is a *client*, IIS is a *server*. WebDAV is built-in to IIS5 (5.1) which ships with XP Pro. However, as a server I am not sure the WebDAV Redirection works. I have seen no documentation for this feature in 5.x. PLease correct me if I am wrong. That's because it isn't an IIS feature at all. WebFolders are XP builtin WebDAV client functionality. Yes. In fact, they are shipping with Office, Windows 2000 and IE. But the WebFolder client is different from the WebDAV Redirector. Two separate clients, both with their own sets of bugs. WebFolders will connect to any WebDAV server, it then comes down to compatibility issues. Almost any :-) Using XP Clients you can connect to WebDAV Redirector redirected Shares using normal NET or Map Network Drive functionaility. Yes. So it's an XP feature. I have not seen anywhere in the documentation for microsoft any mention of the WebDAV redirector functionaility being interoperable with another implementation of a WebDAV server. The documentation says it's for WebDAV, so unless you specifically say for our own implementation of WebDAV, it's SHOULD be working with all compliant server. That's the whole point of open protocols. See yourself from the XP documentation: WebDAVWorking with Data on the Internet Windows XP enables you to publish documents on Internet servers and update them later. This is done using WebDAV (Web Digital Authoring and Versioning) technologya standard Internet file access protocol that travels through HTTP over existing Internet infrastructure (firewalls, routers, and so on.). Windows XP includes a WebDAV redirector which means you can access servers on the Internet just as you would a file share or server share at home or at work. While traditional file sharing protocols are limited in their ability to provide you with access to your data in every location, WebDAV uses Internet protocols that enable access to data repositories anywhere on the Internet. With WebDAV, you can get to your data from wherever you are while using standard software applications. For example, if you wanted to share a file with a colleague located at another location, you could use WebDAV over the Internet to collaborate on the same file. Or, if you're an ISP and you want to host storage for customers so that they can gain access directly using their own applications, WebDAV is your solution. In general, you can use the WebDAV redirector to publish your own Web data or to use Internet repositories for storing data and sharing information. No mention that this is limited to specific Microsoft servers... If anyone has managed to get a network drive from a slide WebDAV implementation other than using 3rd party software, please tell us. Best regards, Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Folders inside folders on Windows XP
Hi Guys I got a weird one here, for some reason when one of our clients looks into their webdav folder (using add a network place on Windows XP) They see the folder itself as a folder in its root listing!! For every folder the go into they see the folder they are in as well as its contents!! Its like facing mirrors going into the infinite. It only happens with their two XP systems, its ok with their Macs and regular browser views, and its ok when i look at it here from my test XP system!! Has anyone else experienced this issue before?? Anyone have any clues as to what might be going on or how to solve it? confused Al -- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JDOM problem with slide version 2.0 release
I have noticed a problem using newer versions of Jdom (1.0rc1, Feb 26th 2004 ) with the new slide final release, this did not occur with slide 2.0b1. If i use jdom beta 9 (as provided with slide 2.0) the problem disssapears. I just figured it would be nice to use the latest versions if possible. here is the exception when loading the domain (servlet startup): [snip] all the loading stuff 18 May 2004 11:56:20 - org.apache.slide.security.SecurityImpl - INFO - Action aggregations loaded successfully 18 May 2004 11:56:20 - org.apache.slide.common.Namespace - INFO - Import data into namespace slide 18 May 2004 11:56:20 - org.apache.slide.common.XMLUnmarshaller - INFO - Loading object / org.apache.slide.common.ServiceAccessException: Service TxFileStore at store/metadata working on work/metadata access error : org.jdom.Element.addContent(Lorg/jdom/Element;)Lorg/jdom/Element; at org.apache.slide.store.AbstractStore.storeRevisionDescriptor(AbstractStore.java:1107) at org.apache.slide.store.ExtendedStore.storeRevisionDescriptor(ExtendedStore.java:794) at org.apache.slide.content.ContentImpl.store(ContentImpl.java:1013) at org.apache.slide.common.XMLUnmarshaller.loadObjectRevision(XMLUnmarshaller.java:411) at org.apache.slide.common.XMLUnmarshaller.loadDefaultObjectRevision(XMLUnmarshaller.java:328) at org.apache.slide.common.XMLUnmarshaller.loadObjectNode(XMLUnmarshaller.java:261) at org.apache.slide.common.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:90) at org.apache.slide.common.NamespaceAccessTokenImpl.importData(NamespaceAccessTokenImpl.java:267) at org.apache.slide.common.Namespace.loadBaseData(Namespace.java:775) at org.apache.slide.common.Domain.initNamespace(Domain.java:814) at org.apache.slide.common.Domain.init(Domain.java:433) at org.apache.slide.common.Domain.init(Domain.java:367) at org.apache.slide.common.Domain.init(Domain.java:330) at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:256) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.slide.webdav.WebdavServlet.init(WebdavServlet.java:198) at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:220) at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445) at org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:150) at org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:458) at org.mortbay.http.HttpServer.start(HttpServer.java:663) at org.technolibre.interprise.WebDav.start(WebDav.java:154) at org.technolibre.interprise.ServiceKernel.startInternalServices(ServiceKernel.java:498) at org.technolibre.interprise.ServiceKernel.start(ServiceKernel.java:446) at org.technolibre.interprise.boot.main(boot.java:130) -- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Folders inside folders on Windows XP
Hi Alan, can this link help you? http://www.greenbytes.de/tech/webdav/webfolder-client-list.html Regards, Daniel Alan Wood wrote: Hi Guys I got a weird one here, for some reason when one of our clients looks into their webdav folder (using add a network place on Windows XP) They see the folder itself as a folder in its root listing!! For every folder the go into they see the folder they are in as well as its contents!! Its like facing mirrors going into the infinite. It only happens with their two XP systems, its ok with their Macs and regular browser views, and its ok when i look at it here from my test XP system!! Has anyone else experienced this issue before?? Anyone have any clues as to what might be going on or how to solve it? confused Al - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Folders inside folders on Windows XP
Hi Guys I got a weird one here, for some reason when one of our clients looks into their webdav folder (using add a network place on Windows XP) They see the folder itself as a folder in its root listing!! For every folder the go into they see the folder they are in as well as its contents!! Its like facing mirrors going into the infinite. It only happens with their two XP systems, its ok with their Macs and regular browser views, and its ok when i look at it here from my test XP system!! Has anyone else experienced this issue before?? Anyone have any clues as to what might be going on or how to solve it? confused Al -- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Folders inside folders on Windows XP
Hi Guys I got a weird one here, for some reason when one of our clients looks into their webdav folder (using add a network place on Windows XP) They see the folder itself as a folder in its root listing!! For every folder the go into they see the folder they are in as well as its contents!! Its like facing mirrors going into the infinite. It only happens with their two XP systems, its ok with their Macs and regular browser views, and its ok when i look at it here from my test XP system!! Has anyone else experienced this issue before?? Anyone have any clues as to what might be going on or how to solve it? confused Al -- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I stop Office caching files?
Luke Noel-Storr wrote: Hi, There seems to be a problem with Office caching files from slide. If I edit a file on one computer it seems to open it as it was the last time it was saved on that same computer even if it has been edited on another computer in the meantime. So, if I edit a Word file on computer A, save it, and close Word; then edit it on computer B, save it, and close word; then open it again on A: it is in the same state as when I saved it on A, and the changes from B are not seen. Any ideas as to how to prevent this? Is there a way to set the nocache header in the response for files returned by Slide? You don't want it to be not cacheable. What you want are working Etag and Last-Modified headers. Maybe there's something wrong with those. Trace it... Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide and XP drive mapping
Daniel Florey wrote: Hi, do you know if there are any document around describing the ms specific things of the Webdav redirector? It would be nice if slide could be mounted in this way. I think we don't have a choice other than hacking slide to work with ms clients. I don't see that ms cares much about interoperability issues. Regards, Daniel As a matter of fact, I just started a new document on it (but it probably still needs an introduction)...: http://greenbytes.de/tech/webdav/webdav-redirector-list.html Best regards, Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I stop Office caching files?
Julian Reschke wrote: You don't want it to be not cacheable. What you want are working Etag and Last-Modified headers. Maybe there's something wrong with those. Well, the Last-Modified header seem to be working (I have a JSP that displays details of the file and it is correctly displaying the last modified date - it uses the client API to get this date). What is the Etag header? how can and tell if it is working? why would it not be working? Cheers Luke. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSR 170 available for Public Review
hi davide there will be an implementation of the jcr api located in the slide cvs under /proposals/jcrri, available soon. this implementation will represent work in progress. fyi: i'am working on this proposal, on and off, since feb 2003. we had to remove the code from the slide cvs a while ago for legal reasons. but since the jsr 170 spec is now in public review these issues do not exist anymore. for a possible architecture, see remy's initial post: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05538.html cheers stefan -Original Message- From: Davide Savazzi [mailto:[EMAIL PROTECTED] Sent: Dienstag, 18. Mai 2004 10:07 To: 'Slide Users Mailing List' Subject: JSR 170 available for Public Review http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) -- Davide Savazzi - 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]
Re: JSR 170 available for Public Review
Hi Stefan, is the RI using slide as backend or is your implementation a replacement for the slide core? As we spent some time on improving the slide backend (tx filestore, improved db-stores) it would be nice to have this features available by using the jsr170 api. What about the webdav layer? Is your plan that it will be using the jsr170-RI in future. If so please remind that we are working hardly to make slide more MS exchange compatible by adding notification, search and transaction-support via webav. Best regards, Daniel Stefan Guggisberg wrote: hi davide there will be an implementation of the jcr api located in the slide cvs under /proposals/jcrri, available soon. this implementation will represent work in progress. fyi: i'am working on this proposal, on and off, since feb 2003. we had to remove the code from the slide cvs a while ago for legal reasons. but since the jsr 170 spec is now in public review these issues do not exist anymore. for a possible architecture, see remy's initial post: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05538.html cheers stefan -Original Message- From: Davide Savazzi [mailto:[EMAIL PROTECTED] Sent: Dienstag, 18. Mai 2004 10:07 To: 'Slide Users Mailing List' Subject: JSR 170 available for Public Review http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) -- Davide Savazzi - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 170 available for Public Review
Hi,
I've posted this to [EMAIL PROTECTED], but as there is no open discussion
(mailing list/newsgroup) I post my first impressions into this archive
as well:
I'm currently having a first look at the api and like to share my very
first impressions:
First of all, it looks very mature. Congratulations to all for this
great work!
Now I'll write down some comments while looking at the api.
I assume that the api can be used locally and remote, depending on the
implementation. The standard case for sure is to talk to a repository
that is located on a different machine, so I'll look at it as a remote api.
As Geoff Clemm worked on this api, I'd be interested in how it is
related to WVCM. JSR-147 also deals with remote content repository
access so I'm interested in figuring out all of this...
* Ticket Interface
- getNodeByAbsPath(String path)
This is an ugly method name. It would be much better (might be a matter
of taste, but I don't like shortcuts) to have a method like
getNode(Path path)
So the Path-class could deal with relative and absolute paths and have
some nice helper methods. Think of something like this
interface Path {
boolean isRelative();
boolean isAbsolute();
Path append(Path path);
boolean isDescendant(Path path);
boolean isAncestor(Path path);
boolean isChild(Path path);
...
}
The same for getNode(UURI uuri)...
- What about this revert/save methods?
In the java world I'd expect that a content repository is accessed using
JCA. Any datasource is configured in the J2EE-specific way.
Think of the following scenario:
An application is using different datasources (oracle rdbms, content
repository via jsr-170). So the user is starting a transaction and doing
some modifications to the data. The transaction manager cares if the
data should be rolled back or commited.
Depending on the transactions isolation level the user can query the
repository or database via it's query languages (sql, xpath or JCRQL)
and gets the result including the changes he made.
So why should the user care of any save/revert methods? Is search only
possible on the repository data after save()?
I'll have a closer look on the api soon and I can post some more if
comments are appreciated.
Regards,
Daniel Florey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide and XP drive mapping
Hi Julian, thanks again for your great work on the webdav stuff! Your site is a great help and a visual pleasure... What exactly do you mean by Network trace shows no outgoing request at all. Do you mean the redirector always sends the request on port 80? Best regards, Daniel Julian Reschke wrote: Daniel Florey wrote: Hi, do you know if there are any document around describing the ms specific things of the Webdav redirector? It would be nice if slide could be mounted in this way. I think we don't have a choice other than hacking slide to work with ms clients. I don't see that ms cares much about interoperability issues. Regards, Daniel As a matter of fact, I just started a new document on it (but it probably still needs an introduction)...: http://greenbytes.de/tech/webdav/webdav-redirector-list.html Best regards, Julian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New moderator needed for slide-dev and slide-user
Hi, I've been the moderator for these two lists for the past two years (I think, maybe longer ...) now, and would like to pass the tasks to someone else. Thanks, Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide and XP drive mapping
Daniel Florey wrote: Hi Julian, thanks again for your great work on the webdav stuff! Your site is a great help and a visual pleasure... What exactly do you mean by Network trace shows no outgoing request at all. Do you mean the redirector always sends the request on port 80? Best regards, Daniel It's not sending the request to the specified port. So either it doesn't send it all (URL parser failure), or it sends it always to port 80. Let me know if you find out more. Regards, Julian -- green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: JSR 170 available for Public Review
Hi Stefan, is the RI using slide as backend or is your implementation a replacement for the slide core? the current implementation of the ri has no dependencies on slide. it is a proposal only. what future direction the implementation will take is open. As we spent some time on improving the slide backend (tx filestore, improved db-stores) it would be nice to have this features available by using the jsr170 api. i totally agree. What about the webdav layer? Is your plan that it will be using the jsr170-RI in future. If so please remind that we are working hardly to make slide more MS exchange compatible by adding notification, search and transaction-support via webav. remy sketched a possible architecture in his initial proposal: quote - WebDAV powered JSR 170 client API - WebDAV server layer, using JSR 170 API - Slide core, providing a JSR 170 API /quote imo, such an architecture would make perfectly sense. but of course, the community has to come up with a strategy/decision regarding a future version of slide jsr 170. cheers stefan Best regards, Daniel Stefan Guggisberg wrote: hi davide there will be an implementation of the jcr api located in the slide cvs under /proposals/jcrri, available soon. this implementation will represent work in progress. fyi: i'am working on this proposal, on and off, since feb 2003. we had to remove the code from the slide cvs a while ago for legal reasons. but since the jsr 170 spec is now in public review these issues do not exist anymore. for a possible architecture, see remy's initial post: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05538.html cheers stefan -Original Message- From: Davide Savazzi [mailto:[EMAIL PROTECTED] Sent: Dienstag, 18. Mai 2004 10:07 To: 'Slide Users Mailing List' Subject: JSR 170 available for Public Review http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) -- Davide Savazzi - 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] - 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]
Re: [POLL] Do you still rely on JDK 1.3?
1.4.x is standard on Mac OSX 10.3. In the .Mac group here at Apple we have no requirement to run JDK 1.3. Chris Sharp On May 18, 2004, at 12:00 AM, Oliver Zeigermann wrote: We were having a discussion if we should switch to JDK 1.4 with the next Slide release. The question is how many of you still rely on JDK 1.3. Thanks for participating and cheers, 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]
Could not parse DAV:version-set:
Hi, I'm running a slide server using a MySQL database but with a file store to store the actual content. I've discovered I have a problem with slide losing the version history after a certain point. I've done a little investigating and it seems that the problem occurs after a file has gone through 10 changes or more (though it could be sooner) and I then restart Tomcat. Before restarting Tomcat it works fine, but after restating it I get the following exception in the logs: org.apache.slide.common.SlideException: Could not parse DAV:version-set: /history/9 at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:176) at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:159) at org.apache.slide.webdav.method.report.VersionTreeReport.execute(VersionTreeReport.java:131) at org.apache.slide.webdav.method.ReportMethod.executeRequest(ReportMethod.java:219) at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:343) at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:139) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:587) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:534) My diagnosis may not be exact, but it seems to be a consistent way of recreating the error. Any ideas? Cheers Luke. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSR 170 available for Public Review
Stefan Guggisberg wrote: Hi Stefan, is the RI using slide as backend or is your implementation a replacement for the slide core? the current implementation of the ri has no dependencies on slide. it is a proposal only. what future direction the implementation will take is open. As we spent some time on improving the slide backend (tx filestore, improved db-stores) it would be nice to have this features available by using the jsr170 api. i totally agree. What about the webdav layer? Is your plan that it will be using the jsr170-RI in future. If so please remind that we are working hardly to make slide more MS exchange compatible by adding notification, search and transaction-support via webav. remy sketched a possible architecture in his initial proposal: quote - WebDAV powered JSR 170 client API I like this aproach, but is this not more or less what WVCM is dealing with? To be honest: I still don't see, why there are two jsr's dealing with a repository api. The focus of jsr-147 seems to be more on the versioning (deltaV) stuff, but what we need is one java api for repository access including all features like acl, search, versioning, locking, versioning and all of this. To have the same api on client and server side is a big plus, so I'll vote for jsr-170 as this seems to include more of this features. The hard task is to handle all of the webdav specific requirements on api level so that content in the repository can be accessed and modified using the api layer or the webdav layer with same features and consistent data. At the moment you can't do the versioning stuff on slide api layer, because this changes don't get reflected properly on deltaV level. So I hope that jsr-170 fulfills all requirement that deltav and acl and the other protocols needs to get this running. Another big point is that it should be possible to access existing repositories with the java api. So if we take the most relevant ones as filesystem, cvs, subversion and other repositories it should be possible to access them with the jsr-170 api. So that if you checkin something in cvs, a new revision in jsr-170-based repository is also available. Regards, Daniel - WebDAV server layer, using JSR 170 API - Slide core, providing a JSR 170 API /quote imo, such an architecture would make perfectly sense. but of course, the community has to come up with a strategy/decision regarding a future version of slide jsr 170. cheers stefan Best regards, Daniel Stefan Guggisberg wrote: hi davide there will be an implementation of the jcr api located in the slide cvs under /proposals/jcrri, available soon. this implementation will represent work in progress. fyi: i'am working on this proposal, on and off, since feb 2003. we had to remove the code from the slide cvs a while ago for legal reasons. but since the jsr 170 spec is now in public review these issues do not exist anymore. for a possible architecture, see remy's initial post: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05538.html cheers stefan -Original Message- From: Davide Savazzi [mailto:[EMAIL PROTECTED] Sent: Dienstag, 18. Mai 2004 10:07 To: 'Slide Users Mailing List' Subject: JSR 170 available for Public Review http://www.jcp.org/en/jsr/detail?id=170 It could be interesting to write a store that uses jcr or implement jcr using slide :) -- Davide Savazzi - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Could not parse DAV:version-set:
OK, I've done a bit more investigation, and by adding some logging to the VersionTreeReport class where the error was happening and it seems the problem is that the XML is being cut off at 256 characters, as shown below: D:href xmlns:D=DAV:/history/9/1.0/D:hrefD:href xmlns:D=DAV:/history/9/1.1/D:hrefD:href xmlns:D=DAV:/history/9/1.2/D:hrefD:href xmlns:D=DAV:/history/9/1.3/D:hrefD:href xmlns:D=DAV:/history/9/1.4/D:hrefD:href xmlns:D=DAV:/h Anyone have any idea what may be causing this? Cheers Luke. - Luke Noel-Storr wrote: Hi, I'm running a slide server using a MySQL database but with a file store to store the actual content. I've discovered I have a problem with slide losing the version history after a certain point. I've done a little investigating and it seems that the problem occurs after a file has gone through 10 changes or more (though it could be sooner) and I then restart Tomcat. Before restarting Tomcat it works fine, but after restating it I get the following exception in the logs: org.apache.slide.common.SlideException: Could not parse DAV:version-set: /history/9 at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:176) at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:159) at org.apache.slide.webdav.method.report.VersionTreeReport.execute(VersionTreeReport.java:131) at org.apache.slide.webdav.method.ReportMethod.executeRequest(ReportMethod.java:219) at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:343) at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:139) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:587) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:534) My diagnosis may not be exact, but it seems to be a consistent way of recreating the error. Any ideas? Cheers Luke. - - 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]
Re: Could not parse DAV:version-set:
Hmm, OK, yet further investigation has shown the problem to be with the properties table, the column type for the property_value column is varchar(255), so when the history-set is getting longer than this it is truncated and becomes invalid. Can anyone suggest any solutions to this? one alternative is to increase the field length, however that doesn't really solve the problem, it just means it'll take longer for it to occur. Any other solutions? Cheers Luke. - Luke Noel-Storr wrote: OK, I've done a bit more investigation, and by adding some logging to the VersionTreeReport class where the error was happening and it seems the problem is that the XML is being cut off at 256 characters, as shown below: D:href xmlns:D=DAV:/history/9/1.0/D:hrefD:href xmlns:D=DAV:/history/9/1.1/D:hrefD:href xmlns:D=DAV:/history/9/1.2/D:hrefD:href xmlns:D=DAV:/history/9/1.3/D:hrefD:href xmlns:D=DAV:/history/9/1.4/D:hrefD:href xmlns:D=DAV:/h Anyone have any idea what may be causing this? Cheers Luke. - Luke Noel-Storr wrote: Hi, I'm running a slide server using a MySQL database but with a file store to store the actual content. I've discovered I have a problem with slide losing the version history after a certain point. I've done a little investigating and it seems that the problem occurs after a file has gone through 10 changes or more (though it could be sooner) and I then restart Tomcat. Before restarting Tomcat it works fine, but after restating it I get the following exception in the logs: org.apache.slide.common.SlideException: Could not parse DAV:version-set: /history/9 at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:176) at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:159) at org.apache.slide.webdav.method.report.VersionTreeReport.execute(VersionTreeReport.java:131) at org.apache.slide.webdav.method.ReportMethod.executeRequest(ReportMethod.java:219) at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:343) at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:139) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:587) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:534) My diagnosis may not be exact, but it seems to be a consistent way of recreating the error. Any ideas?
Re: Folders inside folders on Windows XP
Alan Wood wrote: Hi Guys I got a weird one here, for some reason when one of our clients looks into their webdav folder (using add a network place on Windows XP) They see the folder itself as a folder in its root listing!! For every folder the go into they see the folder they are in as well as its contents!! Its like facing mirrors going into the infinite. It only happens with their two XP systems, its ok with their Macs and regular browser views, and its ok when i look at it here from my test XP system!! Has anyone else experienced this issue before?? Maybe this one...: http://greenbytes.de/tech/webdav/webfolder-client-list.html#issue-folder-mismatch Excelent Julian, spot on thank you it was : 'folder-mismatch' 'When specifying port 80 explicitly in the URL (rather than letting the default apply), the webfolder fails to detect the entry for the parent collection from the PROPFIND/Depth:1 response body, displaying it as additional child collection.' from the link you gave. I changed the port from 80 to 8580 and bingo it works. The reason i use port 80 is because its a public service and port 80 gives me the least firewall issues with customers!! *Note* I also tell customers to enter the full URL including port into the address when they are adding a web folder (even though 80 is default of course) this prevents Microsoft's intefering user/login management automatically adding domain information to the user name!! Weird but true!! So now i really have a dilema if i wish to use port 80 (but dont specify port in the url) the user can't enter the username as windows interferes!! Has anyone found another way around this, forgive me I am not a Windows expert. How does one prevent windows (XP and 2000) from automatically converting login usernames to domain qualified ones? e.g. when adding a web folder using the wizard one enters the userName 'fred' and password 'fredspassword' then windows converts this into '[EMAIL PROTECTED]/files' for instance. -- [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Could not parse DAV:version-set:
Hi Luke! I am afraid you are right :( What about using a BLOB for the propterty values? This would mean certainly mean a slow down and would require changes to the DB adapter, but would work, right? Oliver Luke Noel-Storr wrote: Hmm, OK, yet further investigation has shown the problem to be with the properties table, the column type for the property_value column is varchar(255), so when the history-set is getting longer than this it is truncated and becomes invalid. Can anyone suggest any solutions to this? one alternative is to increase the field length, however that doesn't really solve the problem, it just means it'll take longer for it to occur. Any other solutions? Cheers Luke. - Luke Noel-Storr wrote: OK, I've done a bit more investigation, and by adding some logging to the VersionTreeReport class where the error was happening and it seems the problem is that the XML is being cut off at 256 characters, as shown below: D:href xmlns:D=DAV:/history/9/1.0/D:hrefD:href xmlns:D=DAV:/history/9/1.1/D:hrefD:href xmlns:D=DAV:/history/9/1.2/D:hrefD:href xmlns:D=DAV:/history/9/1.3/D:hrefD:href xmlns:D=DAV:/history/9/1.4/D:hrefD:href xmlns:D=DAV:/h Anyone have any idea what may be causing this? Cheers Luke. - Luke Noel-Storr wrote: Hi, I'm running a slide server using a MySQL database but with a file store to store the actual content. I've discovered I have a problem with slide losing the version history after a certain point. I've done a little investigating and it seems that the problem occurs after a file has gone through 10 changes or more (though it could be sooner) and I then restart Tomcat. Before restarting Tomcat it works fine, but after restating it I get the following exception in the logs: org.apache.slide.common.SlideException: Could not parse DAV:version-set: /history/9 at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:176) at org.apache.slide.webdav.method.report.VersionTreeReport.writeReport(VersionTreeReport.java:159) at org.apache.slide.webdav.method.report.VersionTreeReport.execute(VersionTreeReport.java:131) at org.apache.slide.webdav.method.ReportMethod.executeRequest(ReportMethod.java:219) at org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod.java:343) at org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:165) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:284) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.slide.webdav.filter.LogFilter.doFilter(LogFilter.java:139) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:257) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:245) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:199) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:587) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:149) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:156) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:567) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:732) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619) at
