Hi all, As I'm not sure, if my previous post some days ago came through (I didn't subscribe to the list before), here is another try. I have added some new evaluation results I collected in the meantime. Basically my request is the same as that of James a year ago (http://www.mail-archive.com/[email protected]/msg05418.html).
In a project just started we're using a combination of open source products to build a secure document management system: - Tomcat with SSL client authentication - JSR168 portal (Liferay) - own DMS portlet for exploring and editing Slide content - Slide as the storage backend and for user management Our architect presented us a concept, in which Tomcat negotiates the secure ssl context with the client browser and this context is then shared by the portal and Slide (both as seperate webapps). Slide brings in a standard interface (webDAV) and the (required) version management. At the point to access the slide webapp from server side servlets (as part of our DMS portlet) we realized, that there seems to be no adequate method to access the Slide webapp on the server side (from a servlet) meeting our minimum requirements: - secure clean client certificate authentication in both Slide and the portal (sharing the ssl context managed by tomcat) - access via standard webDAV - versionmanagement in Slide This are the possibilities inside our servlet, all failing at one requirement at least: 1. Slide webdavclient lib (like in the connector/TestServlet example): Works only for username/passwd, can't share/forward the SSL-context 2. Slide serverside API: no standard webdav, our webapp has to "merge" with slide into one webapp by including its jars 3. Use the Slide servlet/the "webdav" layer underneath the servlet: Should we build ServletRequests on our own and parse the response objects? 4. WCK: no support for version management, beta 5. DAV4J: no further development 6. Slide Projector: Has probably too much impact on our overall architecture(?), maybe usable only as backend for our JSP? 7. Move the webdav stuff to a (thick) client: no thin client any more What to you think? Is it possible to meet the requirements with Slide? If yes, how could/should that be done? What could be a intermediate solution? - Does most of what we need now - Does all we need with the next release (2.2/3) - easy/best to migrate to the next release Any comparable project references or other hints? Thanks in advance, Kolja -- DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
