[JBoss Portal] - Re: CMS security not working
by DanielGallot
anonymous wrote : "/" - make readable to all roles including "myRole" except Users and Anonymous
| "/MyTopDirectory/TheUsableDirectory" - make readable and writable to "myRole"
|
| let me know what you get with this setup.
|
| note: this is essentially the same result you are trying to achieve except its a simpler way to approach it.
OK, I understand this is a simpler conf because I don't need to declare again the same rights than the rights already granted in the parent directories.
I try and I got the following :
- "Create a folder", in "/MyTopDirectory/TheUsableDirectory", for a user with "myRole"
==> exception "access denied"
- "Upload a file" : idem
But there is another effect I don't understand : "myRole" got read access to "/MyTopDirectory/TheUsableDirectory" and not to other directories where it has not been granted write access.
Do I miss something(s) ?
I see the second effect because actually I need to get the following : I have also "myRole2" that should have write access on "/MyTopDirectory/TheUsableDirectory2" but not read access to "/MyTopDirectory/TheUsableDirectory" - and vice versa for "myRole" - in fact I have 20 different roles and corresponding "TheUsableDirectoryN".
And also "mySupervisor" that has read/write access to all these directories, but not "/" !
I try to not give read access to all roles on "/", granting the read access on "/MyTopDirectory" - I get "access denied" (the exception) immediatly on the CMS administration. (N.B. : anonymous get "access denied" as a gentle message)
So what can I do ? I am a bit lost...
Thanks a lot for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115085#4115085
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115085
18 years, 4 months
[JBoss Seam] - SMPC transaction propagation and REQUIRES_NEW
by asookazian
SEAM2.0.0.GA
JBOSS4.2.1.GA
I'm currently using multiple SMPC's (for multiple DB's) that are configured in the components.xml. Also using flushMode=MANUAL for @Begin method to ensure that transactions are atomic (i.e. no premature updates before conversation ends). Seems to be working ok so far!
I'm trying to understand the impact of the below statement from the ref pdf. It sounds like Seam is violating the EJB3 spec in this regard. This part is what I'm concerned about:
anonymous wrote :
| However as the Seammanaged persistence context is propagated to any component within the conversation, it will be propagated to
| methods marked REQUIRES_NEW.
When a method is marked REQUIRES_NEW, afaik, the current transaction is suspended until the method marked REQUIRES_NEW is completed. REQUIRES_NEW indicates that the method should always be executed inside a new transaction context.
So I'm assuming in this case an exception would be thrown if you use SMPC and REQUIRES_NEW in case a transaction would be propagated. I tried it from a JSF getter method call to a method marked REQUIRES_NEW in a SFSB and there are no issues (but in that case apparently there is no transaction propagation)...
anonymous wrote : If you are using EJB3 and mark your class or method @TransactionAttribute(REQUIRES_NEW) then the transaction
| and persistence context shouldn't be propagated to method calls on this object. However as the Seammanaged
| persistence context is propagated to any component within the conversation, it will be propagated to
| methods marked REQUIRES_NEW. Therefore, if you mark a method REQUIRES_NEW then you should access the entity
| manager using @PersistenceContext.
--pg. 116 of JBoss Seam 2.0.0.GA ref pdf
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115073#4115073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115073
18 years, 4 months