Re: auto-version-values
Stefan, Stefan Burkard wrote on 07/12/04 11:00 AM: ---> ok, thanks for the advice. additionally i saw that the double-version only occurs when i first put in the document. when i put in a new version of an existing doc, it just creates ONE new version. Hmm, maybe this wasn't what I thought it was, but I guess that might depend on which client you used to create the document. I think I'd only ever seen 1 version created myself, but I honestly wasn't paying that much attention. just two other questions: - what are the consequences for dumb-client-documents that are checked out (automatically), but not checked in (manually) again? The consequence would be that a dumb client would never be able to actually create a new version of your document. You would have to perform the checking from a "smart client". This is normally not a problem if you have some sort of CMS/workflow interface to control the checkin features. You could leverage the "ease of use" of web folders or the KDE webdav:// protocol for day-to-day updates rather than a clunky web interface. I have had locking issues with dumb clients though, so if something gets locked by a smart client after an auto-checkout it will automatically get checked-in when the lock is removed again from the smart client. This is per the spec, but not always desired program behaviour. Long and the short of it, use a smart client for all checkout/checkin/uncheckout/locking. - what is the versioncontrol-method for? to activate and disactivate version-controlling on a document? If you don't use the "auto-version-control" parameter, yes, this is the method that would be called to place a resource under version control. We had an earlier discussion about how to take a resource out of version control and I think the consensus was you "couldn't". I think you would have to create a new resource that was specifically not under version and fill the contents/metadata from the last version. I have spent quite a bit of time investigating how all of these properties work with or against each other. The gist of everything is that dumb clients just mess everything up or make things more complicated. The only upside is easier use by the end user because you can have drag-drop, remote editing, remote saving, etc. I think you are wading your way through :) Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: auto-version-values
Stefan, If you leave the auto-version parameter blank, empty, no value then NOTHING will happen automatically. I will mention that you should be careful with understanding how these parameters work with "dumb" webdav clients such as Windows WebFolders. The dumb behaviour is to automatically overwrite whatever is "live" as there is no checkout/checking issued. I would recommend using the "checkout" option for that reason, as a safeguard. There is a duplicate of the file created in history to allow the uncheckout command to function. Uncheckout is like undo. You can checkout a file, do 20 changes on it, then decide "No, I really don't want to save those changes for this version", so you issue the uncheckout command to rollback to the last good copy from the history. Hope that helps. Tim Stefan Burkard wrote on 07/12/04 09:23 AM: hi slide-users ok, because my post about versioning ends up in a huge discussion about other things, i make a new one :-) i'm now a step ahead (thanks to warwick burrows). i set the following in domain.xml: checkout true when i put a new file in the repository i do a put, and right after that, i'm doing about 20 proppatches. finally, i do a manual checkin. result: 2 (equal) versions in "history" and a current one in "files". i guess that i always have the current version in history too, have i? question: why have i got two equal versions in history? are they created on (automatical) checkout and (manual) checkin? and second question: warwick burrows wrote "... disable auto-versioning altogether and do both checkout and checkin yourself..." how can i do this? set "auto-version-control" to false or "auto-version" to an empty string? thanks and greetings stefan - 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: example for versioning
Warwick, Thank you for the expanded explanation. I seem to vaguely recall that the behaviour you describe was not the one I was actually seeing when doing some testing last month. However, it is entirely possible that it was a combination of smart/dumb clients and not switching users. I was actually hoping it worked the way you describe. I will do some testing again to see what comes up. Maybe someone else can shed some light on the behaviour of a checkedout resource when being access by other users. Tim Warwick Burrows wrote on 03/12/04 12:33 PM: To my understanding other users shouldn't be able to see any of your changes to file content or properties until you actually checkin the file. Of course since you already have a WebdavResource constructed for the checkedout file you will see whatever changes you make to it immediately. But others shouldn't. If they access the same slide resource URI that you are modifying they will get the previous revision which, until you checkin, will still "point" to the most current revision. When you do checkin then your file revision becomes the latest at which time the slide resource URI is changed to point at your revision and it becomes visible to everyone. My original reason for saying this is that I wanted to make it clear that you can't keep the file checkedout and have others see the changes you have made. At some point you will have to checkin for the changes to be visible to others. Warwick -Original Message- From: Tim Frank [mailto:[EMAIL PROTECTED] Sent: Friday, December 03, 2004 11:07 AM To: Slide Users Mailing List Subject: Re: example for versioning Warwick, Would you be able to expand on the following statement for me? Warwick Burrows wrote on 03/12/04 11:32 AM: While the file is checked out any changes you make aren't visible to other users fetching the file or viewing its properties. In my limited testing, whenever I accessed the resource while it was checked out I always received the most recent version of the content and the properties. This was in a non-locking situation. I would assume that anyone with access to read the checkedout file would get all current information on that file. Is that not so? Tim - 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: example for versioning
Warwick, Would you be able to expand on the following statement for me? Warwick Burrows wrote on 03/12/04 11:32 AM: While the file is checked out any changes you make aren't visible to other users fetching the file or viewing its properties. In my limited testing, whenever I accessed the resource while it was checked out I always received the most recent version of the content and the properties. This was in a non-locking situation. I would assume that anyone with access to read the checkedout file would get all current information on that file. Is that not so? Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: example for versioning
Stefan, Not sure if you saw my previous post about the Domain.xml settings for the auto-version-control and auto-version properties. By default the auto-version property is set to checkout-checkin which means every modification makes a new version. You need to change this property if you don't want automatic control of resource versioning, or a different kind. Tim Stefan Burkard wrote on 03/12/04 04:29 AM: We discussed this recently on the list and I don't think that there is a Slide configuration that will let you do this. A file under version control cannot have its properties changed without checking it out/in again which will increment the version number. well, i never want to change individual properties of the file without putting a new version in the repository. all i want to avoid is that i get ONE version for EVERY property i patch on a new file. when i put a file in the repository and patch 20 properties on it (right after putting it in), i get an actual and 19 old versions, because every new property forces the creation of a new version. i'm sure there is a way to avoid this, isn't it? i guess my put-process is not the way it should... and i'm also guessing that the three methods checkin, checkout and versioncontrol can help me, but how? thanks and greetings stefan - 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: example for versioning
Stefan, Not sure if I'm fully understanding what you are trying to do, but see comments inline below Stefan Burkard wrote on 02/12/04 05:49 AM: i'd like to do something like this: - put a file in the repository (first time) You would want to have the auto-version-control on. - patch several properties on it You would need to checkout the resource first. This can be done by setting the auto-version to empty to force manual checkout/checkin. Or, you could use "checkout" so the resource is only checked out when a write is attempted but must be checked in manually. and then, when a document with the same name arrives: I don't quite understand what you mean by "document with the same name", you would always be working on the checkedout version of the document with a given name. - *** save the first version *** This would be the checkin command. - put the new version in the repository This would be another checkout as in the steps above to create another working copy. - patch several properties on it Same as above. my concrete questions: - has anybody a code-example how to do this? I'm not sure if there is any explicit code, but you would be using the checkout, checkin, possibly uncheckout methods in the Slide Client API. - and what values are needed in the auto-version-properties of domain.xml? I would recommend true and either or checkout to allow more manual control over the checkin process. and a general question: - has the property "auto-version" in domain.xml any function if the property "auto-version-control" is set to false? Good question, I haven't tested this. I would take a wild guess and say possibly. In that you could set auto-version-control to false so that a resource is NOT automatically put under version control. However, if the command was issued manually, then the auto-version property might be applied to control how that resource is handled. I hope that helps you a little bit or gives you some ideas to try. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting started
Chris, You will want to look at the PropFind/PropPatch methods for setting/retrieving properties. You can add in your own custom properties and namespace as well. Some of the functions in WebdavResource are a bit limiting, but you can always call the methods directly from the methods class if need be. Worst case you can write your own client library to do the HTTP calls. Tim Chris O'Connell wrote on 29/11/04 10:17 AM: I'm still trying to 'figure out' Slide, and I think I'm missing a few things. Or, at least I'm missing the one big thing that makes everything else fall into place. I want to use Slide as the back end for a content management application. We are going to store media files (.wav files, images etc.). The users will be able to go to the web site, look at (or hear) the current version of the media. If they want to make a change, they can upload a new version of the media file and we drop it into Slide. They also will be able to potentially see (hear) all old versions of the file. We also want to be able to group files together and then drop labels on those files and then get the labeled version of a file. So, maybe Hello.wav is currently on version 1.6, but 1.3 is labeled 'Production'. Without knowing the version number, we want the user to be able to get 'Production'. So, I have been playing with the WebdavResource, and it doesn't look like there is any way to use that class to do any of the labeling/getting that we want to do. I can call the 'reportMethod(...)' on the WebdavResource, and it will return the path to each version of a file and I can then get that version, but I can't figure out how do use the labeling. So, if anyone could fill in what I am missing, I would really appreciate it. Do people write their own client Socket to connect to the Servlet and push over HTTP/Webdav Headers to do what they want to do? Thanks, Chris - 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: the question about checkout and lock
Jacob, I have not found that any of these options actually LOCK the file automatically when checked out. They do dictate what happens IF a file is locked or after the file is unlocked. Maybe I have misunderstood the auto-version section numerous times. I believe Yong was looking for a "lock this file automatically when it is checked out" option. Tim Jacob Lund wrote on 25/11/04 09:45 AM: > Have a look at: > http://greenbytes.de/tech/webdav/rfc3253.html#PROPERTY_auto-version > > /jacob > > - Original Message - From: "Tim Frank" > <[EMAIL PROTECTED]> > To: "Slide Users Mailing List" <[EMAIL PROTECTED]> > Sent: Thursday, November 25, 2004 3:33 PM > Subject: Re: the question about checkout and lock > > >> Yong, >> >> I did some experimenting with this a while ago to get na understanding >> of how checkout/checkin and locking works. Checkout/checkin work >> independently of locks to some degree. Meaning you can checkout without >> locking so any user with access to the resource could modify it or >> perform checkin/uncheckout operations. >> >> If you decide to put a lock on a checkedout file, then there are various >> parts of the spec that dictate that when the lock is removed it is >> AUTOMATICALLY checked in. This is for interoperability with "dumb" >> webdav clients. >> >> I believe I tested the scenario when I could checkout a file, >> lock/unlock it as many times as I wanted, then checkin when I wanted. >> The specification does not enforce locking upon checkout. The use is up >> to the end-user application. >> >> Tim >> >> Yong Hu wrote on 25/11/04 03:57 AM: >> >>> All, >>> >>> Who could give me a clear explain the checkout and lock in Slide? >>> >>> I don't use lockMethod currently, but I use >>> checkoutMethod/checkinMethod to implement the versioncontrol. >>> >>> I find that if user1 checkout one file, another user can do >>> uncheckout or checkin on this file. I wonder why not the lock is >>> added to one file after it is checked out in order that other user >>> can't operate on it? >>> >>> Regards >>> Yong >>> >>> >>> >>> - >>> Do You Yahoo!? >>> 嫌邮箱太小？雅虎电邮自助扩容！ >> >> >> - >> 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: publishing workflow / best practices
I'm not sure, but I think these two ideas might be of slightly different magnitudes. I think the original request was how to migrate the minimal amount of information from a dev/staging instance to the live instance. Therefore one would not need/want to take all version/meta information across. It would be a simple "copy from stage to live" sort of function. I have been thinking about how to implement such a solution as well, but my solution was not going to store the "live" data in a webdav repository, just on a filesystem. (I'm not a fan of storing files in a database, so I use the filesystem store anyway) I think Daniel's idea was much broader about a full mirror/migration for ALL Webdav content and information. I definately agree that would be a great tool, but I think it might be overkill for the "stage to live" workflow. I guess that is assuming you are moving items piece by piece as they are approved. Tim Daniel Florey wrote on 25/11/04 03:03 AM: Yes, please!! This is what I had in mind for a longer time, but never managed to start working on it: A WebDAV-client-tool that determines the server capabilities by doing some OPTIONS request and retrieves the content by doing the appropriate WebDAV-requests afterwards. This would have the big advantage that it works with different WebDAV-based repositories and works if different Slide instances use different storage configurations. It might be a bit tricky to retrieve not only the content but also properties, locks, acl and versioning information, but it finally would be the most elegant solution. If we find a good XML representation for content/properties etc. we could use this for data import as well. The xml-format could consist of nested elements representing each resource. This would enable to "dump" the repository located under a given path and import it to a different location. Optional flags could be used to ignore locks/acl/versioning information. Just a dream... or is someone interested in implementing this? As stated before I had this on my personal roadmap for a while but am very busy at the moment and can hardly find the time to do it. Cheers, Daniel "Slide Users Mailing List" <[EMAIL PROTECTED]> schrieb am 24.11.04 23:04:34: It sounds like writing a client tool to migrate content from one Slide server to another one might be a good option. This should be fairly simple to write using the Webdav client library. Another option that I originally had in mind is to simply perform a database dump on the staging server and upload this to production. Of course, this would preserve the entire version history, which we most likely won't care about on our production server, so a separate tool might be more appropriate. -Mirko On Wed, 2004-11-24 at 13:58, Richard Emberson wrote: I must preface my remarks by stating that our Slide deployment will use a database for storage. Consider Slide namespaces. From what I've heard and based upon the mailing list traffic, multi Slide namespace installations do not occur very often. Lets say that such installations work just fine, - each namespace could use a different database - one would need some external Slide/webdav tool/script to promote (copy) directories from dev namespace to test namespace to production namespace. Since one has to create and use such a promotion tool, its not clear that having a single Slide with three namespaces buys one anything over having three distinct Slides each with their own DB. I am assuming that to promote a directory involves getting it (the whole directory hierarchy) into the (client) tool from one Slide server and then putting into a second Slide server. This is true even if one has the three Slide databases on the same database server; one must extract the directory from one db and insert it into another. Our dev Slide server will be version controlled while the test and production need only have non-versionable copies. Mirko Froehlich wrote: Our current staging environment really serves a different purpose. Our test, staging, and production servers correspond to phases in our software development cycle and are strictly separated. We definitely wouldn't want to use the production Slide server for development or test purposes, so those at the minimum would need to be separate servers. However, my example of publishing web content from staging to production uses a different concept of staging than we currently have, so it may not be an ideal example. I suppose for this scenario the content could very well live in two different folders on the production Slide server, with a simple publishing process that copies or moves content from the staging to the production server. I guess in the end this really depends on the workflows we need. For example, for content updates on the live site this approach would probably work well. But lets say we develop a new major version of the application with significant changes to our web content management framework
Re: the question about checkout and lock
Yong, I did some experimenting with this a while ago to get na understanding of how checkout/checkin and locking works. Checkout/checkin work independently of locks to some degree. Meaning you can checkout without locking so any user with access to the resource could modify it or perform checkin/uncheckout operations. If you decide to put a lock on a checkedout file, then there are various parts of the spec that dictate that when the lock is removed it is AUTOMATICALLY checked in. This is for interoperability with "dumb" webdav clients. I believe I tested the scenario when I could checkout a file, lock/unlock it as many times as I wanted, then checkin when I wanted. The specification does not enforce locking upon checkout. The use is up to the end-user application. Tim Yong Hu wrote on 25/11/04 03:57 AM: > All, > > Who could give me a clear explain the checkout and lock in Slide? > > I don't use lockMethod currently, but I use checkoutMethod/checkinMethod to > implement the versioncontrol. > > I find that if user1 checkout one file, another user can do uncheckout or > checkin on this file. I wonder why not the lock is added to one file after it > is checked out in order that other user can't operate on it? > > Regards > Yong > > > > - > Do You Yahoo!? > 嫌邮箱太小？雅虎电邮自助扩容！ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: annotating multi-version file
I think you are looking to make Slide do something that contradicts how the Version control specification operates. The only thing I could possibly suggest is this theoretical sequence of events. 1. Remove the resource from being under version control. 2. Make the modifications to the metadata. 3. Place the resource back under version control. I say that is theoretical, because I don't know if you can remove a resource from version control. I did successfully remove the D:auto-version property using PROPPATCH, but I didn't check whether or not I was then able to alter properties without a version being created. I'm also not sure how to tell that a resource is under version control. Tim Jussi Vaihia wrote on 24/11/04 09:54 AM: A quick follow-up; CHECKIN/CHECKOUT seems to always create a new version of the document. How can this be prevented, as the change is only to metadata (annotation) ? On Tue, 23 Nov 2004 09:34:19 -0800, Warwick Burrows <[EMAIL PROTECTED]> wrote: When a file is under version control you can't change the content or the metadata without having first checked the file out. You also need to check it back in after modifying its properties. Warwick - 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]
PropPatchMethod Hints
I thought this piece of information might be useful for others who are using/setting their own properties. I had some difficulty using the PropPatchMethod from the org.apache.webdav.lib.methods class for properties that had children/descendants. For example, the auto-version property that looks like this: I could remove the property by passing "auto-version" as the property name, but I could not create the property on first try. The trick I used was to pass the XML portion for the children/descendants as the String Value of the property. I noticed that internally all of the XML assembly for the request is a string, hence it just gets passed through nicely. So, if you want to create more complex properties, this is how you can create them with the webdav client API. Don't ask me how to retrieve those properties with the same API though, I don't think it can be done at present. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: auto-version checkout
For those who are interested, Slide DOES let you change the value of the
auto-version property. The RFC says the server can forbid this, but
luckly Slide does not. The following snippet of code accomplishes the
task: (Code is from Cocoon javascript, so the typing is not explicit)
var propPatch = new PropPatchMethod(filePath);
propPatch.addPropertyToSet("auto-version", "", null, "DAV:");
var state = client.executeMethod(propPatch);
Tim
James Mason wrote on 17/11/04 02:00 AM:
Tim,
I believe the behavior you're seeing is expected. There was a discussion
about this a few weeks back, you may be able to find it in the archive.
I don't know a lot about versions (maybe someone else can step in here),
but as far as I know the auto-version parameter only effects
newly-created resources. To change the behavior on existing resource you
need to set a property on them directly (I don't know which property
this is, but it sounds like you do ;) ). Try playing with propatch and
propget and see if you can change the behavior.
-James
On Mon, 2004-11-15 at 12:54 -0500, Tim Frank wrote:
I have been trying to experiment with the various settings for
auto-version specified in section 3.2.2 of the DeltaV RFC. I am either
not understanding one of these options, or it is not operating as it should.
I have set the auto-version parameter to "checkout" in Domain.xml like this:
checkout
I am using the KDE webadv:// protocol and Windows Web Folders as my dumb
clients, DAV Explorer as my smart client.
If I create a new file with DAV Explorer then the behaviour works as
expected, the dumb clients only put the file in the checkout state, then
I must use the smart client to check it in when complete.
However, if I try to use a file in the repository from before the
configuration change, the old auto-version behaviour persists. Is this
auto-version behaviour tied to every single file as it is created?? I
can't seem to get any information on the auto-version property using a
DASL search, it is always listed in the 404 response section. Is there a
way to change the auto-version behaviour on a previously created resource?
Tim
-
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: Added projector documentation link
James Mason wrote on 17/11/04 11:50 AM: On Wed, 2004-11-17 at 08:54 -0500, Tim Frank wrote: One thing I don't think JXTemplate can handle (not sure on this) is outputting non-marked-up content. This would be a problem with CSS files, for example. I love the way the CSS theme is handled with the example application (I've copied the idea into another system I'm working on), so it would be a shame to lose that. You can output non XML content from JX templates, just as long as your JX Template is a valid XML document. Same way you can output a comma-delimited data file from an XSLT transformation. So outputting CSS, Javascript, etc would not be a technical problem, but it might be ugly to do so. How would you do this? For the template to be valid xml there needs to be a root tag, and I haven't seen anyway to keep the tag out of the results. Is there a tag or something? Well, if we are sticking within the Cocoon framework where JX Templates work it is quite easy. This template: http://apache.org/cocoon/templates/jx/1.0";> This is my JX Template Combined with this sitemap entry: Will output nothing more than a simple text file. No root tag required. If you are serializing your JX to XML, of course you need at least a root tag. For CSS/Javascript they DO have a "root" tag of
Re: Added projector documentation link
See inline below, James Mason wrote on 17/11/04 01:52 AM: On Sun, 2004-11-14 at 02:34 +0100, Stephane Bailliez wrote: [snip...] [snip again...] I don't think JXTemplate can handle conditional attributes, but I would like to point out that in most cases there's a "false" value that can be used to keep the same behavior as leaving the parameter off. The most obvious example I can think of is the "selected" attribute for tags. Both selected="" and selected="false" should be valid for the unselected options. There are conditional constructs for IF and CHOOSE similar/mirrored from XSLT. There is also an enhanced version of forEach, macros for creating custom tags, lots of goodies overall. One thing I don't think JXTemplate can handle (not sure on this) is outputting non-marked-up content. This would be a problem with CSS files, for example. I love the way the CSS theme is handled with the example application (I've copied the idea into another system I'm working on), so it would be a shame to lose that. You can output non XML content from JX templates, just as long as your JX Template is a valid XML document. Same way you can output a comma-delimited data file from an XSLT transformation. So outputting CSS, Javascript, etc would not be a technical problem, but it might be ugly to do so. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Opinions for Exposing XML from Methods
Mirko, I have to agree with your feelings about the duality of the WebdavResource class. I think there does need to be a split somehow between access the properties from the result of a particular operation. For example, there is a getOwner() method in the class but it is only used for "locking purposes", therefore not useful for many other operations. The other problem I was having was trying to figure out what I would need to do if I wanted to get at properties that could be returned from a method that aren't stored in java. For example, the "lockMethod()" sets the owner and the lockToken which are accessible. However, the depth and timeout are returned in the XML, but don't seem to be accessible with java. Regardless, all of these properties are extracted with DOM operations/searches at a low level. This was the main reason why I wanted the actual DOM XML result available so that I could extract anything I wished. Tim Mirko Froehlich wrote on 15/11/04 02:41 PM: XML support sounds very useful for debugging. Speaking of the WebDAV client API: I have only recently started working with Slide and the WebDAV client API, and even though the client API is very powerful, I have to admit that I have mixed feelings about it. In particular, the WebdavResource does not have very clearly delineated responsibilities. It seems to act as a combination of a general facade into the API with many convenience methods, while also trying to act as an entity that represents a particular WebDAV resource. In my opinion, these responsibilities should be clearly split up, so that WebdavResource only acts as an entity and another class (maybe something like WebdavConnection, or maybe just the WebdavSession, which WebdavResource currently extends) could act as a more general facade into the API if necessary. Once created, a WebdavResource should only represent a particular folder or document, and all operations on it should use relative paths (based on the resource the instance represents), rather than allowing absolute paths. Anyway, just a side note. :) -Mirko On Mon, 2004-11-15 at 11:26, Tim Frank wrote: I have been working with the Webdav Client using the org.apache.webdav.lib.methods package directly to get the XML response from the slide server. I am using the XML results with XSLT to build web interfaces and reports. I noticed that the WebdavResource class seems to be the powerhouse of the client API, however, it does not seem to provide a way to extract the XML responses in any easy way. The best I have seen is a piece of code that walks through the nodelists to merely output the same XML that came from the server originally. This seems to be odd when the XML is available from most methods is available with getResponseDocument(). As a result, I was thinking of attempting to make the XML result available in the WebdavResource class for easy access to those needing the DOM representation of the result. My idea would be to store it as a w3c.dom variable in the class that would get set to something other than a default when a method was called that returns an XML response. This should also be useful for extracting error messages after methods are executed. I would appreciate ideas/opinions from others who may find this useful, or in some way problematic. Tim - 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]
Opinions for Exposing XML from Methods
I have been working with the Webdav Client using the org.apache.webdav.lib.methods package directly to get the XML response from the slide server. I am using the XML results with XSLT to build web interfaces and reports. I noticed that the WebdavResource class seems to be the powerhouse of the client API, however, it does not seem to provide a way to extract the XML responses in any easy way. The best I have seen is a piece of code that walks through the nodelists to merely output the same XML that came from the server originally. This seems to be odd when the XML is available from most methods is available with getResponseDocument(). As a result, I was thinking of attempting to make the XML result available in the WebdavResource class for easy access to those needing the DOM representation of the result. My idea would be to store it as a w3c.dom variable in the class that would get set to something other than a default when a method was called that returns an XML response. This should also be useful for extracting error messages after methods are executed. I would appreciate ideas/opinions from others who may find this useful, or in some way problematic. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Seeking java example querying slide
Phillip, Here is an example DASL query from the Wiki pages: http://wiki.apache.org/jakarta-slide/DASLSearch Someone else might know another way. Tim Phillip Rhodes wrote on 15/11/04 01:33 PM: I want to connect to slide using a Java API and find out for a given folder, the contents within it (other folders and files). I would like to use slide as an image repository and create some a database record for each image that is found in the dav server. I was hoping someone can point me to a good example. Thanks very much. - 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]
auto-version checkout
I have been trying to experiment with the various settings for auto-version specified in section 3.2.2 of the DeltaV RFC. I am either not understanding one of these options, or it is not operating as it should. I have set the auto-version parameter to "checkout" in Domain.xml like this: checkout I am using the KDE webadv:// protocol and Windows Web Folders as my dumb clients, DAV Explorer as my smart client. If I create a new file with DAV Explorer then the behaviour works as expected, the dumb clients only put the file in the checkout state, then I must use the smart client to check it in when complete. However, if I try to use a file in the repository from before the configuration change, the old auto-version behaviour persists. Is this auto-version behaviour tied to every single file as it is created?? I can't seem to get any information on the auto-version property using a DASL search, it is always listed in the 404 response section. Is there a way to change the auto-version behaviour on a previously created resource? Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Added projector documentation link
Stephane I clipped the message as I wanted to expand on the XSLT item. Stephane Bailliez wrote: I'm not too keen on xslt because I find it extremely difficult to find people that can jump into it. It takes a long time to learn tips and tricks even from people that are developpers. And it is a major pain to debug. Yes, XSLT can be very complicated. Yes it can be hard for somebody to jump right in and develop from scratch. I guess what I had in mind with mentioning it, is to use the technology to build some abstraction. Since XSLT can be applied to results of other XSLT transformations that create XML, I was thinking you could have a core template set that could act on a more simple "layout" template or something like that. So you could have a simple XML/XSLT template to layout a page or decide which functions go on a page. Then you could have the more complex core templates that actually do the meat of the work. For those adept at XSLT they can easily extend/override the core templates without any java knowledge to change the look of the application. I guess the idea is roughly along the lines of the Docbook XSL templates where you can choose to override any that you want, but if you don't, it just works "as-is". Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Added projector documentation link
Daniel,
I forgot to mention something on the issue of workflow and events. If
you have not done so I would suggest looking at the Cocoon
implementation of "Flows" and the use of flowscript and continuations.
Obviously I don't know what you had in mind specifically, but I do know
that there are a number of issues these do address quite well in
building web applications.
http://cocoon.apache.org/2.1/userdocs/flow/index.html
Not sure if that meshes with your ideas, but it may.
Tim
Daniel Florey wrote:
Finally I think that there are many different preferences regarding templating.
It depends on what people are used to use and what they personally like.
The primary goal of projector was not to introduce new templating mechanisms,
but mainly focusses on the event driven workflow engine. So other templating
engines can easily plugged in. For example Projector is already containing an
xslt processor that can be used for xml processing.
The Projector templates that we are currently dicussing about are targeted
towards html designers who want to have a really simple ability to fill dynamic
content into dynamic pages.
I think it is not easy to use standard jsp templating as I have no clue how to
call jsp's in background and cache the rendered result without making an
http-call. Is there a way to do so? Would be interesting...
Cheers,
Daniel
"Slide Users Mailing List" <[EMAIL PROTECTED]> schrieb am 15.11.04
08:39:13:
Tim Frank wrote:
Daniel,
Sorry to jump in the middle of this one, but I find it somewhat amusing
that you are having a huge discussion about separation of logic/layout
and then throw in an example from the HTML side of things that basically
goes back to mixing "logic/layout".
How do you handle HTML style attributes when outputting HTML from
programming code? You don't. You class the HTML elements, if necessary,
and use CSS to control style. That's it, done. Have your code output
Absolutely. Ultimately all is needed to modify is a class or id attribute.
Agreed.
On the topic of "Yet another template system", I would at least agree
theoretically that it would be better to adopt something standard. XSL
has always worked great for me and I am experimenting right now with
building a frontend for slide with XML/XSL using Cocoon. Cocoon also
offers JXTemplates which connect javascript/java code to a template
system. I am not familiar with the other ones mentioned, but you have to
remember, things start off simple, then somebody wants it to do X, Y,
and Z and before you know it, simple is lost.
Agreed. There are things introduced like the dateFormatter that makes it
already quite evident that there are dozen of things needed to be
introduced later.
I'm already wondering how to do something standard such as (that's
pseudo language):
if (messages){
${message}
} else {
AB
if (list.isEmpty()){
No elements in this list
} else {
foreach( item in list){
set (alternate = count%2 == 0 ? "even" : "odd"
${item.a}${item.b}
}
}
}
This can be done by using the TableRenderer that has many options how to format
lists/arrays. I hope I can add some example to the docs lateron.
Cheers,
Daniel
I'm not too keen on xslt because I find it extremely difficult to find
people that can jump into it. It takes a long time to learn tips and
tricks even from people that are developpers. And it is a major pain to
debug.
As for a web designer having to do logic code, no they shouldn't. They
should be in the CSS realm for layout. Let the programmer spit out the
tags, class them, let the designer style the hell out of it. You
inevitably will need display logic no matter what templating system you
use.
Well, in theory, your mockup design is done way before you start to make
them dynamic, so if you have in your team someone that is not a killer
developper but excellent designer, you can still use it to code things
above which he should be able to do without too much problem as he also
should know some javascript.
Sorry for the long message, but I really hate to see effort wasted on
things that already exist and can be adapted.
ditto.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
-
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: AW: Added projector documentation link
Daniel,
Sorry to jump in the middle of this one, but I find it somewhat amusing
that you are having a huge discussion about separation of logic/layout
and then throw in an example from the HTML side of things that basically
goes back to mixing "logic/layout".
How do you handle HTML style attributes when outputting HTML from
programming code? You don't. You class the HTML elements, if necessary,
and use CSS to control style. That's it, done. Have your code output
Then include a CSS file that does this
body {
background-color: yellow;
}
If you REALLY need it to be dynamic, have the CSS dynamically generated
for each page, but I often find that is not required once a
"theme/style" are set.
What happens when you want to change the colour? Change the style sheet.
Your WEB DESIGNER will know how to do this, no programming, no config
files, or tables of attributes. Gives you more control than you will
ever need. Once you have all elements classed the style possibilities
are unlimited.
For those unfamiliar with how far this can go, check out
http://www.csszengarden.com/ for the extreme.
On the topic of "Yet another template system", I would at least agree
theoretically that it would be better to adopt something standard. XSL
has always worked great for me and I am experimenting right now with
building a frontend for slide with XML/XSL using Cocoon. Cocoon also
offers JXTemplates which connect javascript/java code to a template
system. I am not familiar with the other ones mentioned, but you have to
remember, things start off simple, then somebody wants it to do X, Y,
and Z and before you know it, simple is lost.
As for a web designer having to do logic code, no they shouldn't. They
should be in the CSS realm for layout. Let the programmer spit out the
tags, class them, let the designer style the hell out of it. You
inevitably will need display logic no matter what templating system you use.
Sorry for the long message, but I really hate to see effort wasted on
things that already exist and can be adapted.
Tim
Daniel Florey wrote:
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im
Auftrag von Stephane Bailliez
Gesendet: Sonntag, 14. November 2004 02:34
An: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Betreff: Re: Added projector documentation link
Daniel Florey wrote:
Hi folks,
I've added a link to the Slide website that points to my (work in
progress)
documentation of Projector.
Congratulation Daniel, that's a cool documentation as an introduction to
the projector.
I have yet to digest everything and think more about it, but I have one
feeling to share:
why did you make your own template language ?
When I see this:
"?>>Hello
<%username;required;text/plain%>!?>
BTW: What do you think is the best way to handle optional attributes? In
Java we would write something like this:
String bgcolor = someDynamicBgColorValue;
StringBuffer output = new StringBuffer();
output.append("");
String renderedOutput = output.toString();
In Projector templating you write
>
Any ideas how to deal with it even more comfortable?
Daniel
I'm already screaming of pain ! It's not readable !
Why not using a standard jsp/jstl solution, should it means creating
taglibs ?
-
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: How to read components of a multi-status method return ?
Nick, I have been working with the XML/DOM being returned from various methods and have been using the getResponseDocument() method to get the w3c dom representation of the response. I don't know how to access these through the WebdavResource however as I have been using the various methods directly through HTTP. That might give you some ideas. Tim Nick Longinow wrote on 12/11/04 02:22 PM: Hi I'm getting a true result from a deleteMethod, but the resource is not being deleted. The WebdavResource.latestStatusCode is a 207 (multistatus). Does anyone know how to access the different components of this status ? Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Authentication not required after installation
Did you check to see that your jaas.conf file was correct? You can verify against the JAAS page on the Slide website. Tim johnw woo wrote on 11/11/04 12:05 PM: Thanks. But now it prompt us the exception of : javax.security.auth.login.LoginException: unable to find LoginModule class: org.apache.slide.jaas.spi.SlideLoginModule My files are in : %CATALINA_HOME%/conf/jaas.conf all libraries in %CATALINA_HOME%/webapps\slide\WEB-INF\lib Thanks. Perseus Tim Frank <[EMAIL PROTECTED]> wrote: There was an earlier thread related to a setup issue with environment variables and the JAAS configuration. The gist was that the $CATALINA_HOME was not set early enough in the startup.sh (not sure about startup.bat) and therefore the JAAS configuration file was not found. if you search the archives for "JAAS problem 2.1b2" you will find the thread, I sent some updated startup files. Hope that helps, Tim johnw woo wrote on 11/11/04 07:03 AM: Hi, Thanks. I tried to uncomment it. It gives me prompt but when I entered root/root, it doesn't let me in. What should be the right username / password ? Thanks. Perseus Roman Novak wrote: Hi, take a look at the web.xml in the slide.war looke for this section: - Moving house? Beach bar in Thailand? New Wardrobe? Win 10k with Yahoo! Mail to make your dream a reality. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - ALL-NEW Yahoo! Messenger - all new features - even more fun! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Authentication not required after installation
There was an earlier thread related to a setup issue with environment variables and the JAAS configuration. The gist was that the $CATALINA_HOME was not set early enough in the startup.sh (not sure about startup.bat) and therefore the JAAS configuration file was not found. if you search the archives for "JAAS problem 2.1b2" you will find the thread, I sent some updated startup files. Hope that helps, Tim johnw woo wrote on 11/11/04 07:03 AM: Hi, Thanks. I tried to uncomment it. It gives me prompt but when I entered root/root, it doesn't let me in. What should be the right username / password ? Thanks. Perseus Roman Novak <[EMAIL PROTECTED]> wrote: Hi, take a look at the web.xml in the slide.war looke for this section: - Moving house? Beach bar in Thailand? New Wardrobe? Win 10k with Yahoo! Mail to make your dream a reality. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Retrieving XML Output
I was poking around through the WebDAV RFC yesterday to piece together some ideas for building a frontend application. I was doing some manual requests via telnet to probe the various capabilities of slide yesterday and was happy with the various reports that I could retrieve with various queries. I have not done any programming with the WebDAV or Slide API's provided, and ideally am hoping I can skip that step if possible. I was wondering what the easiest way to send queries and receive the XML output result from slide? Obviously a properly formed request is required first of all, but after that, all I want is the XML result. I don't want to have to build it programatically with Java if I can avoid it. Any ideas or pointers would be appreciated. This is related to my research into using Cocoon to build a frontend. Thanks in advance, Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Projector features questions
Stephane Bailliez wrote on 04/11/04 12:17 PM: Tim Frank wrote: I was wondering about how to implement workflow on top of WebDAV as well... at a purely theoretical level. I had thought about using extended elements/attributes in the file information, as it seems you can arbitrarily add them. I do not know if a workflow standard RFC exists somewhere or not, as I have not looked. Considering the workflow mess and everybody rolling his own, if there is one standard, I doubt there is one which is not 100 times more complicated than it should be :) I would agree that a workflow standard would probably be incredibly complex... however, if one exists it would definately be a useful guide if nothing more :) I was also thinking about an interface for checking out, checking in, locking, reviewing, etc, etc. I know the cocoon slide block will let you upload via a web interface, but I couldn't download an arbitrary file type. It was the best start to an end user app that I have come across. I think such interface is just additional feature on top of a WebDAV server. It would be used because of clients that do not support WebDAV protocol so then you find yourself with a need to publish documents via the web interface if you want to glue people to the portal (this can also be convenient from a remote point of view), of course this is piece of cake when using the explorer in Windows when you just have to map it...you just copy files like if it was another folder. But for many customers, we are already reaching the far end of technical knowledge required to staff when ask to mess with file operations (I can see that already with people from my family that are not really used to computers as we do), therefore the interface is just a welcome helper and central point of operation, it is closer to the 'email habits' they are used to and stick to it. For me the issue was that there are not very many "smart" WebDAV clients out there right now that support the ability to checkout, lock, checkin. Aside from DAVExplorer, the OS based protocols are the "dumb" kind without DeltaV support. That makes using Web Folders a pain if you want to honour locks and such. I think having it integrated with the OS would be a great idea, but for now a web interface would be one way to have advanced features. Also, workflow would not likely be supported by OS clients, so you would need another interface for that portion. There is a sample in the Cocoon webdav block that uses DASL to query a slide repository. Is DASL completely dead? Reading http://www.webdav.org/dasl/ it does not seem like it is very lively. I was just wondering at which level such an application would need to be written... DASL, WebDAV API, Slide API, all of them? Ideally it would be nice if it wasn't 100% specific to Slide. Thanks for pointing that out. If you look at the current draft section, there is one dated from september 30: http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-07.html Thanks for the link, I hadn't looked around for a DASL reference yet. I was going to do some playing around with the DASL sample in cocoon to see how easy/difficult it was to use. I think it would at least be a step up in simplicity from having to code Java/JSP with the API's. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Projector features questions
Stephane, I was wondering about how to implement workflow on top of WebDAV as well... at a purely theoretical level. I had thought about using extended elements/attributes in the file information, as it seems you can arbitrarily add them. I do not know if a workflow standard RFC exists somewhere or not, as I have not looked. I was also thinking about an interface for checking out, checking in, locking, reviewing, etc, etc. I know the cocoon slide block will let you upload via a web interface, but I couldn't download an arbitrary file type. It was the best start to an end user app that I have come across. There is a sample in the Cocoon webdav block that uses DASL to query a slide repository. Is DASL completely dead? Reading http://www.webdav.org/dasl/ it does not seem like it is very lively. I was just wondering at which level such an application would need to be written... DASL, WebDAV API, Slide API, all of them? Ideally it would be nice if it wasn't 100% specific to Slide. More thoughts... Tim Stephane Bailliez wrote on 04/11/04 11:07 AM: Hello, Can someone shed some light about what is the goal (features) of the projector framework exactly ? I'm trying to find out (like others) if it could be a foundation for developping additional services regarding document management and hopefully contribute. What I have in mind at the moment (nothing spectacular) is to use Slide as the WebDAV server to store all kind of documents (Mostly PDF, Microsoft/Star/Open Office files) which would need to be indexed (according to the expected volume, it would probably mean an asynchronous remote lucene indexer, I have read that someone is also having a look at it). On top of that there might be a need for a workflow system in the document cycle (document permissions change according to workflow ? Looks like external annotations, comments.. are required too. Should they be stored in the files metadata def.xml ? this is food for thought I need to think more about this but any external eye is welcome) Of course, such a solution need also to be integrated in a portal (jsr-168). That's mainly the rough requirements...this is obviouslly something that is being done by many people following this list considering past emails. Reading the Projector features at http://jakarta.apache.org/slide/projector.html I can see that 'workflow' is being mentioned, but what exactly is meant behind this term ? Cheers, Stephane - 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: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ?
Oliver, It did technically work fine in the Engine element for slide, no problem at all. Sorry if I misunderstood. Tim Oliver Zeigermann wrote: Maybe you got me wrong. Of course the behavior you describe and want is the generally desired one. I was just asking why it did not work *technically* to have the slide realm in the engine section. It has the namespace attribute in it which used to work before. Anyway, I will try the setting you proposed... Oliver On Wed, 03 Nov 2004 21:35:38 -0500, Tim Frank <[EMAIL PROTECTED]> wrote: Oliver, It did "work" in the Engine element, however, that would require me to set up all the Tomcat admin/manager accounts as accounts within slide. Not exactly the default behaviour I was expecting. Also, the Tomcat docs indicate that adding entries to the tomcat-users.xml file will allow access to the admin/manager apps. This was no the case in the bundle. Putting the JAAS Realm inside the Context element inside the Host element allows slide to operate independently of other applications that require authentication. My assumption was this would be the default case as I would assume slide would not be the only webapp running on a server. I guess it is just my opinion that separating the Tomcat users from the slide users would be desired. If not, then putting it in the Engine element as it stands is fine, but if so, why not remove the other Realm entries in the Engine element (or comment them out since they don't work). Tim Oliver Zeigermann wrote: Hi Tim, any idea why this did not work for you in the engine element? Oliver On Wed, 03 Nov 2004 16:11:14 -0500, Tim Frank <[EMAIL PROTECTED]> wrote: It was my inexperience with Tomcat that caused the problem... and due to that a misunderstanding of the instructions on the following page: http://jakarta.apache.org/slide/howto-jaas.html ALSO, and more importantly, the server.xml bundled with the 2.1b2 binary including Tomcat 5 has the JAAS Realm set in the Engine element. This causes the Tomcat admin/manager apps to not work per the default setup instructions for Tomcat. I have modified my server.xml to place this block inside of the Host element defining localhost instead and then (finally) everything works! Thanks to Nick for pointing out the wiki page which made me realise I did not have this Realm inside of the correct element. I think it would be helpful to change the default bundle to handle this change as well, and maybe also point it out more explicitly on the JAAS instruction page for newcomers like myself. Thanks, Tim Nick Longinow wrote on 03/11/04 03:07 PM: Tim I was able to get this working using Slide 2.1B2. The wiki steps shown are almost completely sufficient (on Windows) Nick -Original Message- From: Tim Frank [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 3:03 PM To: Slide Users Mailing List Subject: Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ? I would just like to add that I am having the exact same problem with the 2.1b2 bundle that uses JAAS authentication. The only way I can login to the Tomcat admin/manager apps is to change the server.xml file to not use JAAS but the old MemoryRealm. Which of course then doesn't let me login to slide. I also apologise if this is a Tomcat issue, but it IS an issue with the 2.1b2 bundle you provide for download. Thanks, Tim Nick Longinow wrote on 03/11/04 01:26 PM: Hi, Again, apologies for what may be a Tomcat issue, but... Per Tomcat's documentation, I am trying to set the credentials for the admin and manager webapps that ship with Tomcat. I've added them to the tomcat-users.xml file (root/root), but when I try to login to http://localhost:8080/admin I get a stack dump like this: WARNING: Login exception authenticating username root javax.security.auth.login.LoginException: org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (The system cannot find the file specified) Any ideas ? Nick -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 12:58 PM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices John, Well, it looks like there are three cases we need to handle and we are only handling one of them. Right now the username/password/url are coming from the connection spec. They can also come from configuration properties. The case I need is when the credentials come from the JAAS Subject as a: javax.resource.spi.security.PasswordCredential. I don't think that the JCA specifications are clear on exactly which credentials should be used when they are supplied through more than one method. I'm using JBoss. I'm pretty sure the PasswordCredential should work the same under weblogic because I was using a lot of weblogic docs for info. I think weblogic also supports caller impersonation. I was really hoping somebody could shed some
Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ?
Oliver, It did "work" in the Engine element, however, that would require me to set up all the Tomcat admin/manager accounts as accounts within slide. Not exactly the default behaviour I was expecting. Also, the Tomcat docs indicate that adding entries to the tomcat-users.xml file will allow access to the admin/manager apps. This was no the case in the bundle. Putting the JAAS Realm inside the Context element inside the Host element allows slide to operate independently of other applications that require authentication. My assumption was this would be the default case as I would assume slide would not be the only webapp running on a server. I guess it is just my opinion that separating the Tomcat users from the slide users would be desired. If not, then putting it in the Engine element as it stands is fine, but if so, why not remove the other Realm entries in the Engine element (or comment them out since they don't work). Tim Oliver Zeigermann wrote: Hi Tim, any idea why this did not work for you in the engine element? Oliver On Wed, 03 Nov 2004 16:11:14 -0500, Tim Frank <[EMAIL PROTECTED]> wrote: It was my inexperience with Tomcat that caused the problem... and due to that a misunderstanding of the instructions on the following page: http://jakarta.apache.org/slide/howto-jaas.html ALSO, and more importantly, the server.xml bundled with the 2.1b2 binary including Tomcat 5 has the JAAS Realm set in the Engine element. This causes the Tomcat admin/manager apps to not work per the default setup instructions for Tomcat. I have modified my server.xml to place this block inside of the Host element defining localhost instead and then (finally) everything works! Thanks to Nick for pointing out the wiki page which made me realise I did not have this Realm inside of the correct element. I think it would be helpful to change the default bundle to handle this change as well, and maybe also point it out more explicitly on the JAAS instruction page for newcomers like myself. Thanks, Tim Nick Longinow wrote on 03/11/04 03:07 PM: Tim I was able to get this working using Slide 2.1B2. The wiki steps shown are almost completely sufficient (on Windows) Nick -Original Message- From: Tim Frank [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 3:03 PM To: Slide Users Mailing List Subject: Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ? I would just like to add that I am having the exact same problem with the 2.1b2 bundle that uses JAAS authentication. The only way I can login to the Tomcat admin/manager apps is to change the server.xml file to not use JAAS but the old MemoryRealm. Which of course then doesn't let me login to slide. I also apologise if this is a Tomcat issue, but it IS an issue with the 2.1b2 bundle you provide for download. Thanks, Tim Nick Longinow wrote on 03/11/04 01:26 PM: Hi, Again, apologies for what may be a Tomcat issue, but... Per Tomcat's documentation, I am trying to set the credentials for the admin and manager webapps that ship with Tomcat. I've added them to the tomcat-users.xml file (root/root), but when I try to login to http://localhost:8080/admin I get a stack dump like this: WARNING: Login exception authenticating username root javax.security.auth.login.LoginException: org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (The system cannot find the file specified) Any ideas ? Nick -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 12:58 PM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices John, Well, it looks like there are three cases we need to handle and we are only handling one of them. Right now the username/password/url are coming from the connection spec. They can also come from configuration properties. The case I need is when the credentials come from the JAAS Subject as a: javax.resource.spi.security.PasswordCredential. I don't think that the JCA specifications are clear on exactly which credentials should be used when they are supplied through more than one method. I'm using JBoss. I'm pretty sure the PasswordCredential should work the same under weblogic because I was using a lot of weblogic docs for info. I think weblogic also supports caller impersonation. I was really hoping somebody could shed some light on making the url configurable. I'm doing it from a config property right now like you said. That means I can only set the url to the slide root. I'm then using WebdavResource.getChildResources() to navigate down, but I feel like that might be doing a whole bunch of extra round trips, when I usually only want one resource at a time. Whats the best way to do this? Regards, -Ryan Rhodes From: "John Gilbert" <[EMAIL PROTECTED]> Reply-To: "Slide Users Mailing List" <
Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ?
It was my inexperience with Tomcat that caused the problem... and due to that a misunderstanding of the instructions on the following page: http://jakarta.apache.org/slide/howto-jaas.html ALSO, and more importantly, the server.xml bundled with the 2.1b2 binary including Tomcat 5 has the JAAS Realm set in the Engine element. This causes the Tomcat admin/manager apps to not work per the default setup instructions for Tomcat. I have modified my server.xml to place this block inside of the Host element defining localhost instead and then (finally) everything works! Thanks to Nick for pointing out the wiki page which made me realise I did not have this Realm inside of the correct element. I think it would be helpful to change the default bundle to handle this change as well, and maybe also point it out more explicitly on the JAAS instruction page for newcomers like myself. Thanks, Tim Nick Longinow wrote on 03/11/04 03:07 PM: Tim I was able to get this working using Slide 2.1B2. The wiki steps shown are almost completely sufficient (on Windows) Nick -Original Message- From: Tim Frank [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 3:03 PM To: Slide Users Mailing List Subject: Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ? I would just like to add that I am having the exact same problem with the 2.1b2 bundle that uses JAAS authentication. The only way I can login to the Tomcat admin/manager apps is to change the server.xml file to not use JAAS but the old MemoryRealm. Which of course then doesn't let me login to slide. I also apologise if this is a Tomcat issue, but it IS an issue with the 2.1b2 bundle you provide for download. Thanks, Tim Nick Longinow wrote on 03/11/04 01:26 PM: Hi, Again, apologies for what may be a Tomcat issue, but... Per Tomcat's documentation, I am trying to set the credentials for the admin and manager webapps that ship with Tomcat. I've added them to the tomcat-users.xml file (root/root), but when I try to login to http://localhost:8080/admin I get a stack dump like this: WARNING: Login exception authenticating username root javax.security.auth.login.LoginException: org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (The system cannot find the file specified) Any ideas ? Nick -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 12:58 PM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices John, Well, it looks like there are three cases we need to handle and we are only handling one of them. Right now the username/password/url are coming from the connection spec. They can also come from configuration properties. The case I need is when the credentials come from the JAAS Subject as a: javax.resource.spi.security.PasswordCredential. I don't think that the JCA specifications are clear on exactly which credentials should be used when they are supplied through more than one method. I'm using JBoss. I'm pretty sure the PasswordCredential should work the same under weblogic because I was using a lot of weblogic docs for info. I think weblogic also supports caller impersonation. I was really hoping somebody could shed some light on making the url configurable. I'm doing it from a config property right now like you said. That means I can only set the url to the slide root. I'm then using WebdavResource.getChildResources() to navigate down, but I feel like that might be doing a whole bunch of extra round trips, when I usually only want one resource at a time. Whats the best way to do this? Regards, -Ryan Rhodes From: "John Gilbert" <[EMAIL PROTECTED]> Reply-To: "Slide Users Mailing List" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Subject: RE: Custom authorization and authentication best practices Date: Wed, 3 Nov 2004 12:22:20 -0500 Ryan, What kind of changes are you looking to do for the jca connector? I was thinking of doing the same thing. For example, providing a property for the url and using container managed authentication. Also, are you using weblogic? - John -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices Hi Morten, I'm working on something similar to this right now. One way it "Could" be done is this. 1) Use a JAAS Login module to make slide the authentication realm for the web container. This way users and roles are pulled from Slide for web applications. 2) Use the JCA Connector to connect web applications to Slide. 3) Use a second JAAS login config for the JCA Connector. JCA supports 3 or 4 different types of authentication. The type called "Caller Im
Re: Accessing Tomcat Manager and Admin apps with Slide/Tomcat bundle ?
I would just like to add that I am having the exact same problem with the 2.1b2 bundle that uses JAAS authentication. The only way I can login to the Tomcat admin/manager apps is to change the server.xml file to not use JAAS but the old MemoryRealm. Which of course then doesn't let me login to slide. I also apologise if this is a Tomcat issue, but it IS an issue with the 2.1b2 bundle you provide for download. Thanks, Tim Nick Longinow wrote on 03/11/04 01:26 PM: Hi, Again, apologies for what may be a Tomcat issue, but... Per Tomcat's documentation, I am trying to set the credentials for the admin and manager webapps that ship with Tomcat. I've added them to the tomcat-users.xml file (root/root), but when I try to login to http://localhost:8080/admin I get a stack dump like this: WARNING: Login exception authenticating username root javax.security.auth.login.LoginException: org.apache.slide.common.DomainInitializationFailedError: Domain initialization error : Domain.xml (The system cannot find the file specified) Any ideas ? Nick -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 12:58 PM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices John, Well, it looks like there are three cases we need to handle and we are only handling one of them. Right now the username/password/url are coming from the connection spec. They can also come from configuration properties. The case I need is when the credentials come from the JAAS Subject as a: javax.resource.spi.security.PasswordCredential. I don't think that the JCA specifications are clear on exactly which credentials should be used when they are supplied through more than one method. I'm using JBoss. I'm pretty sure the PasswordCredential should work the same under weblogic because I was using a lot of weblogic docs for info. I think weblogic also supports caller impersonation. I was really hoping somebody could shed some light on making the url configurable. I'm doing it from a config property right now like you said. That means I can only set the url to the slide root. I'm then using WebdavResource.getChildResources() to navigate down, but I feel like that might be doing a whole bunch of extra round trips, when I usually only want one resource at a time. Whats the best way to do this? Regards, -Ryan Rhodes From: "John Gilbert" <[EMAIL PROTECTED]> Reply-To: "Slide Users Mailing List" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Subject: RE: Custom authorization and authentication best practices Date: Wed, 3 Nov 2004 12:22:20 -0500 Ryan, What kind of changes are you looking to do for the jca connector? I was thinking of doing the same thing. For example, providing a property for the url and using container managed authentication. Also, are you using weblogic? - John -Original Message- From: Ryan Rhodes [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 03, 2004 11:31 AM To: [EMAIL PROTECTED] Subject: RE: Custom authorization and authentication best practices Hi Morten, I'm working on something similar to this right now. One way it "Could" be done is this. 1) Use a JAAS Login module to make slide the authentication realm for the web container. This way users and roles are pulled from Slide for web applications. 2) Use the JCA Connector to connect web applications to Slide. 3) Use a second JAAS login config for the JCA Connector. JCA supports 3 or 4 different types of authentication. The type called "Caller Impersonation" allows you to pass on the user/roles from the calling web/ejb application to be used by the JCA connection. This way you don't have to keep around the username/password from the web login to re-use with Slide. The application server handles it for you, and the web user will automatically be limited to whatever document permisions they have in slide. Right now, the JCA Connector doesn't support any type of declarative configuration. The login/pass are passed programatically through the WebDavConnectionSpec when you create a connection. When I finish making it configurable I'll submit the changes, but I'll warn you that (#3) will always require configuration that is specific to the application server. Not every app server supports Caller Impersonation, and I think (#1), at least on Jboss, requires a JAAS Login Module that uses propriertary JBoss libraries and I heard those can't be mixed with Apache License, so... it probably won't be support by Slide. Hope that Helps, Ryan Rhodes From: Morten <[EMAIL PROTECTED]> Reply-To: "Slide Users Mailing List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Custom authorization and authentication best practices Date: Mon, 01 Nov 2004 19:15:34 +0100 Hi. I will be using Slide as a file system based content repository. It will be part of a web-application which contains a UI to add/remove users and set permissions at folder level. This m
Re: Slide/WebDAV Frontends
James, Thanks for the lead on jCMS, that is one we haven't yet looked at. I forgot to mention Lenya, but yes, that is looking like the most mature option for what we would need here. I did also read they were going to look at integrating slide at some point. I would hate to start from scratch if there was really no reason to. Lenya is based on Cocoon as well which got me thinking that Cocoon might be a good option. Oh, and if your "in progress" front end is purdy, then you have me sold... I mean it's all about eye candy right? :) Tim James Mason wrote on 01/11/04 12:07 PM: You might have a look (if you can find anything about it) at jCMS over at the Jetspeed project. Check their mailing list and Wiki. I've also done some work writing a Slide frontend using Cocoon. It's just a display app right now as I haven't had time to work on anything else but it looks all purdy ;). If you can't find anything better maybe it would serve as a good base to get you started (and since extending it is on my todo list that could workout well too). There's also Lenya incubating in the Cocoon project. There was talk about using Slide for Lenya's repository awhile back. This is the most mature option, but I don't think the Slide integration is there yet so you'd lose some of the nice advantages a WebDAV server brings. -James On Mon, 2004-11-01 at 10:09 -0500, Tim Frank wrote: Everyone, We have started looking at plausible content management options and I am very impressed with the options that Slide/WebDAV provide for file/revision managment and more. These can be at any stage of development as we are investigating at the moment. My question is, are there any current projects out there providing an END USER front end for managing content through Slide/WebDAV. I have looked at the slide block in Cocoon which is definately a good start. I have also looked at the WebDav block and Projector application. I have also looked at DAVExplorer (not too bad, but clunky), Windows WebFolders. All provide pieces, but there is no "glue" that I can find. We are looking for something that will provide end user functions for viewing/previewing content, rolling back revisions, workflow... you know, many of those CMS goodies. We are liking the combination of Slide with Cocoon for a possible development framework for our website. Something that fit into that model would be great. Thank you for any information you can provide to assist with our research. Tim - 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: Slide/WebDAV Frontends
Daniel, If we choose the Slide/Cocoon route then I would ideally love to contribute to something usable by the broader community. I work at a University and we are just making inroads into the areas of Portals and CMS's so I'd love to find solutions that build on open standards and open software. (Our campus portal will be based on uPortal). I liked the Slide Block of the Cocoon project as a very basic web interface for browsing a repository and viewing object properties. I'm not sure if you have looked at it or not, but it isn't bad. At this point I have not looked at any of the API's or have any understanding how difficult it is to work with WebDAV or Slide from a programming standpoint. I have also noticed that it seems to be recommended to write with the WebDAV API's rather than the native Slide API's. I have done some testing with Cocoon in the past and I like the way it separates the various layers of display, logic, etc. I find it much easier not having to worry about the exact HTML output when you are coding. I'd love to hear your thoughts and ideas. Tim Daniel Florey wrote on 01/11/04 10:39 AM: Hi Tim, are you planning to contribute your efforts to the Slide project? I started some time ago to build an administration application on top of Slide/Projector but I struggled as it looked so ugly as I'm no designer ;-( If you managed to start the admin app you know what I mean. I would help to build a CMS frontend on top of Slide/Projector as this is what I had in mind. Would be nice to have this as demo app for projector as well as you can use all the WebDAV notifications stuff to build pages in background and provide a fast app to the end users. Please let me know what you are planning! Cheers, Daniel "Slide Users Mailing List" <[EMAIL PROTECTED]> schrieb am 01.11.04 16:09:55: Everyone, We have started looking at plausible content management options and I am very impressed with the options that Slide/WebDAV provide for file/revision managment and more. These can be at any stage of development as we are investigating at the moment. My question is, are there any current projects out there providing an END USER front end for managing content through Slide/WebDAV. I have looked at the slide block in Cocoon which is definately a good start. I have also looked at the WebDav block and Projector application. I have also looked at DAVExplorer (not too bad, but clunky), Windows WebFolders. All provide pieces, but there is no "glue" that I can find. We are looking for something that will provide end user functions for viewing/previewing content, rolling back revisions, workflow... you know, many of those CMS goodies. We are liking the combination of Slide with Cocoon for a possible development framework for our website. Something that fit into that model would be great. Thank you for any information you can provide to assist with our research. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193 - 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]
Slide/WebDAV Frontends
Everyone, We have started looking at plausible content management options and I am very impressed with the options that Slide/WebDAV provide for file/revision managment and more. These can be at any stage of development as we are investigating at the moment. My question is, are there any current projects out there providing an END USER front end for managing content through Slide/WebDAV. I have looked at the slide block in Cocoon which is definately a good start. I have also looked at the WebDav block and Projector application. I have also looked at DAVExplorer (not too bad, but clunky), Windows WebFolders. All provide pieces, but there is no "glue" that I can find. We are looking for something that will provide end user functions for viewing/previewing content, rolling back revisions, workflow... you know, many of those CMS goodies. We are liking the combination of Slide with Cocoon for a possible development framework for our website. Something that fit into that model would be great. Thank you for any information you can provide to assist with our research. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: login config JAAS problem 2.1b2 mac osx / linux
Oliver,
Not a problem. I just had a look into the two files this morning and
made an adjustment that should make things work regardless if the
CATALINA_HOME is set prior to running the startup.sh or if it is set
during the execution of the catalina.sh script.
I basically moved the following line from startup.sh to catalina.sh for
the fix.
export CATALINA_OPTS="${CATALINA_OPTS}
-Djava.security.auth.login.config=${CATALINA_HOME}/conf/jaas.config"
It may be possible to integrate this with the options being set in the
"if -security" block in catalina.sh, but I don't know enough about what
those options are.
Files are attached.
Tim
Oliver Zeigermann wrote on 30/10/04 05:03 AM:
Hi Tim,
would you send the correct versions of catalina.sh and startup.sh to
the list so we all can benefit from it and take it over for the next
Slide release?
Thanks in advance,
Oliver
On Fri, 29 Oct 2004 15:15:14 -0400, Tim Frank
<[EMAIL PROTECTED]> wrote:
I just fought with this, among other things, today. After reading this
information:
http://jakarta.apache.org/slide/howto-jaas.html
I ended up putting the export portion in the catalina.sh file just under
the line where it checks/sets the CATALINA_HOME variable.
CATALINA_OPTS=-Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.config
export CATALINA_OPTS
I found that exporting the CATALINA_HOME was NOT enough to pick up the
path to the jaas.config file.
Hope that helps you. My other problem now is that once that is setup and
working I can't login to the Tomcat Admin/Manger consoles no matter what
I try :) Oh, and related to that, if you did change your server.xml to
use the old default MemoryRealm configuration it might also cause this
problem.
Tim
Brian Lee wrote on 29/10/04 03:03 PM:
How do you set the path correctly? it seems even if I set both
CATALINA_HOME and BASEDIR in my .profile -it doesn't work
Yes, but in startup.sh the path indeed isn't set correctly. So when
you launch it on non-Windows, it really does not work :(
Oliver
On Fri, 29 Oct 2004 12:06:17 +0200, Unico Hommes <[EMAIL PROTECTED]> wrote:
You should launch Tomcat using 'start' instead of 'catalina run' did
you do that? The location of the login configuration is set there.
--
Unico
On 29-okt-04, at 1:59, Brian Lee wrote:
I'm having a problem with Slide 2.1 b2 that I did not have for 2.0 for
both linux (fedora core 2) and mac osx. (This does not occur in
windows)
Once I start running Slide - I can't login with any of the default
users: root, guest, john, john2
I notice this error:
"Oct 28, 2004 4:07:33 PM org.apache.catalina.realm.JAASRealm
authenticate
SEVERE: Unexpected error
java.lang.SecurityException: Unable to locate a login configuration
at
com.sun.security.auth.login.ConfigFile.(ConfigFile.java:97)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructor
AccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCon
structorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at
javax.security.auth.login.Configuration$3.run(Configuration.java:221)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.Configuration.getConfiguration(Configuration.
java:215)
at
javax.security.auth.login.LoginContext$1.run(LoginContext.java:170)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.LoginContext.init(LoginContext.java:167)
at
javax.security.auth.login.LoginContext.(LoginContext.java:404)
at
org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:298)
at
org.apache.catalina.authenticator.BasicAuthenticator.authenticate(Basic
Authenticator.java:129)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticato
rBase.java:504)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
ontext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav
a:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
ontext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav
a:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
ontext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:
520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve
.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC
ontext.java:104)
Re: Projector Installation Help
Beautiful! The only part I was missing was pointing to the listUsers.html file specifically. I still get errors and exceptions in the logs relating to the user authentication, but things seem to work. Thanks, Tim James Mason wrote: Here's what I've done to get projector working: Prerequisites: the 2.1b2 Tomcat bundle unpacked somewhere and the 2.1b2 source distribution downloaded. 1) Build projector using the "webapp" target from the source distribution. 2) Extract projector/dist/webapp/projector.jar to TOMCAT_HOME/webapps/projector. 3) Edit WEB-INF/web.xml in the newly extracted so that the value for the "configuration" init-param is "../webapps/slide/projector.xml". 4) Copy projector/src/conf/projector.xml to TOMCAT_HOME/webapps/slide. 5) Unpack projector/src/content/store.zip to TOMCAT_HOME/bin. 6) Open a command prompt and navigate to TOMCAT_HOME/bin. 7) Set the CATALINE_HOME environment variable to ".." example (running bash on *nix): export CATALINA_HOME=.. 8) Run startup.(bat|sh). NOTE: If you're on a *nix system, make sure you set all of the .sh files to be executable. 9) Open a browser and navigate to http://localhost:8080/projector/listUsers.html -James On Fri, 2004-10-29 at 16:34 -0400, Tim Frank wrote: I have been working with the slide-2.1b2 distribution and have been trying to install the projector application to see what it has to offer for administration. I have completed the following steps with much pain: 1. Build projector.war and deploy on tomcat 5.0 2. Fixed "couldn't find projector.xml configuration file" by copying this file into the webapps directory and setting the full path to the file in the web.xml for the projector project. 3. Copied the projector applications directory from the content directory in the source to the projector directory in the slide repository. After all of that I can finally access the /projector/ application, but all I get are errors. Many of the errors are like: Oct 29, 2004 4:27:58 PM org.apache.catalina.realm.JAASRealm authenticate WARNING: Login exception authenticating username null javax.security.auth.login.LoginException: No user name entered I have updated the projector.xml file to use the root/root login for full privledges for testing, but it doesn't seem to be working. Has anybody else had success with getting this running? Thank you in advance, Tim - 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]
Projector Installation Help
I have been working with the slide-2.1b2 distribution and have been trying to install the projector application to see what it has to offer for administration. I have completed the following steps with much pain: 1. Build projector.war and deploy on tomcat 5.0 2. Fixed "couldn't find projector.xml configuration file" by copying this file into the webapps directory and setting the full path to the file in the web.xml for the projector project. 3. Copied the projector applications directory from the content directory in the source to the projector directory in the slide repository. After all of that I can finally access the /projector/ application, but all I get are errors. Many of the errors are like: Oct 29, 2004 4:27:58 PM org.apache.catalina.realm.JAASRealm authenticate WARNING: Login exception authenticating username null javax.security.auth.login.LoginException: No user name entered I have updated the projector.xml file to use the root/root login for full privledges for testing, but it doesn't seem to be working. Has anybody else had success with getting this running? Thank you in advance, Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: login config JAAS problem 2.1b2 mac osx / linux
I just fought with this, among other things, today. After reading this information: http://jakarta.apache.org/slide/howto-jaas.html I ended up putting the export portion in the catalina.sh file just under the line where it checks/sets the CATALINA_HOME variable. CATALINA_OPTS=-Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.config export CATALINA_OPTS I found that exporting the CATALINA_HOME was NOT enough to pick up the path to the jaas.config file. Hope that helps you. My other problem now is that once that is setup and working I can't login to the Tomcat Admin/Manger consoles no matter what I try :) Oh, and related to that, if you did change your server.xml to use the old default MemoryRealm configuration it might also cause this problem. Tim Brian Lee wrote on 29/10/04 03:03 PM: How do you set the path correctly? it seems even if I set both CATALINA_HOME and BASEDIR in my .profile -it doesn't work Yes, but in startup.sh the path indeed isn't set correctly. So when you launch it on non-Windows, it really does not work :( Oliver On Fri, 29 Oct 2004 12:06:17 +0200, Unico Hommes <[EMAIL PROTECTED]> wrote: You should launch Tomcat using 'start' instead of 'catalina run' did you do that? The location of the login configuration is set there. -- Unico On 29-okt-04, at 1:59, Brian Lee wrote: I'm having a problem with Slide 2.1 b2 that I did not have for 2.0 for both linux (fedora core 2) and mac osx. (This does not occur in windows) Once I start running Slide - I can't login with any of the default users: root, guest, john, john2 I notice this error: "Oct 28, 2004 4:07:33 PM org.apache.catalina.realm.JAASRealm authenticate SEVERE: Unexpected error java.lang.SecurityException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:97) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructor AccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCon structorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at java.lang.Class.newInstance0(Class.java:308) at java.lang.Class.newInstance(Class.java:261) at javax.security.auth.login.Configuration$3.run(Configuration.java:221) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.Configuration.getConfiguration(Configuration. java:215) at javax.security.auth.login.LoginContext$1.run(LoginContext.java:170) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.init(LoginContext.java:167) at javax.security.auth.login.LoginContext.(LoginContext.java:404) at org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:298) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(Basic Authenticator.java:129) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticato rBase.java:504) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC ontext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.jav a:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC ontext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.jav a:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC ontext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve .java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveC ontext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java: 520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java: 160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java: 799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process Connection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java: 577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.java:683) at java.lang.Thread.run(Thread.java:534) Caused by: java.io.IOException: Unable to locate a login configuration at com.sun.security.auth.login.ConfigFile.init(ConfigFile.java:206) at com.sun.security.auth.login.ConfigFile.(ConfigFile.java:95) ... 33 more" Does anyone have suggestions? Thanks in advance Brian - To unsubs
