Adding a user without updating the group-member-set
This is perhaps more of a Tomcat question than a Slide question, but here goes anyway: For my application, I don't need to use Slide roles. Given the way ACEs work in Slide, I can assign a privilege to any user on an individual basis, which is exactly what I need. If, however, I create a user without adding the user to a group-member-set, and then try to log in as that user, I can't even get to the point of testing the resulting ACL. Tomcat (5.0.28) throws a 403 error before even trying to run any Slide code. I put a breakpoint on the first line of the service method of WebdavServlet, and never reached it. In a nutshell, I created a user, /users/john3, but did not add him to any role's group-member-set. Logging in to Slide as john3 fails inside Tomcat, before any Slide-specific code runs. Presumably, this has to do with the realm and auth-constraints configured in Tomcat, which somehow check user IDs and roles against Slide's idea of user roles. I'm using a completely stock Tomcat configuration (except for adding the slide realm). Is it at all possible to use Slide without updating the group-member-set? I'll never use ACEs which rely on group memberships. I understand that I can just add all new users to /roles/user when I create them, and remove them from /roles/user when I delete them, but it seems like an unnecessary hassle. Are Tomcat and Slide so married to the idea of roles that it cannot be removed? Many thanks, CV __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Slide, Tomcat, JBoss, and the JCA test servlet
After doing a little work, I succeeded in firing up Slide 2.1 with the following configuration: Tomcat 5.0.28: - Slide servlet JBoss 4.0.1sp1: - Slide JCA connector - another Tomcat instance, running the connector-example.war distributed with the Slide client Whenever I try to access the connector-example servlet, however, I run into trouble at the line where the TestServlet code tries to retrieve a non-existent file using a second WebdavResource handle. (That's the line of code that declares and initializes the thisIsWhatTx2Sees variable.) I expect that line to result in a 404. In reality, that line causes the Tomcat instance hosting Slide to hang. When I try to shut down the Tomcat, I see the following: Jun 28, 2005 4:20:33 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-80 28 Jun 2005 16:20:36 - org.apache.slide.common.Namespace - INFO - Shutting down service tx(org.apache.slide.store.ExtendedStore) 28 Jun 2005 16:20:36 - org.apache.commons.transaction.file.FileResourceManager - INFO - Stopping RM at 'store/metadata' / 'work/metadata' 28 Jun 2005 16:20:36 - org.apache.commons.transaction.file.FileResourceManager - INFO - Waiting for tx [EMAIL PROTECTED] to finish for 24 milli seconds 28 Jun 2005 16:20:46 - file-content-store - INFO - DEADLOCK VICTIM: Thread Thread[http-80-Processor24,5,main] marked transaction branch [EMAIL PROTECTED] for rollback http-80-Processor24, 28-Jun-2005 16:18:46, unauthenticated, GET, 409 Conflict, 120171 ms, /files/file1 When I comment out the parts of the TestServlet code that use a second WebdavResource, everything works fine. I don't understand why there might be deadlock here. Is anyone successfully using a configuration similar to mine? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
