[
http://jira.andromda.org/browse/BPM-306?page=comments#action_15410 ]
Jan Ciriack commented on BPM-306:
---------------------------------
The attached patch solves the problem by separating the generation of the security elements for use-cases and manageables. Note that it generates security-role elements for all actors of the model at the end of the file no matter if the actors are linked to a use-case or a entity. I am still not happy with logic of this fix to access the actors of the model (temp variables $aManageable + $aApplicationUseCase and if/else before security-roles).
> Security elements are not generated for manageable entities without usecase
> ---------------------------------------------------------------------------
>
> Key: BPM-306
> URL:
http://jira.andromda.org/browse/BPM-306> Project: Bpm4Struts Cartridge
> Type: Bug
> Components: CRUD
> Versions: 3.2, 3.3
> Reporter: Jan Ciriack
> Assignee: Wouter Zoons
> Attachments: web.xml.vsl
>
> Within the web.xml template security elements like <security-constraint>, <security-role> etc are beeing generated if you have no use-cases at all. This is because the part that generates these elements is inside the usecase loop. For more details see:
http://galaxy.andromda.org/forum/viewtopic.php?t=5675--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
