[jboss-jira] [JBoss JIRA] Commented: (JBRULES-2733) Groupassignment doesn't work in the gwt console

[Kris Verlaenen (JIRA)]

    [ https://jira.jboss.org/browse/JBRULES-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560932#action_12560932 ] 

Kris Verlaenen commented on JBRULES-2733:
-----------------------------------------

Thank you for the patch.  Do you know if there is another way to get the roles of users that is less dependent on the exact path (so it can work with multiple versions / configs of the AS or even on another AS), as 
    FileInputStream fstream = new FileInputStream("jboss-4.2.3.GA/server/default/conf/roles.properties");
seems pretty hardcoded, maybe there's like an identity manager service you could contact?

It would also be useful if you could provide me the changes to the eclipse plugin in a patch format, as it's difficult to figure out what changed exactly based on the class files only ;)

Kris

> Groupassignment doesn't work in the gwt console
> -----------------------------------------------
>
>                 Key: JBRULES-2733
>                 URL: https://jira.jboss.org/browse/JBRULES-2733
>             Project: Drools
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: drools-process
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Csaba Vizsnyai
>            Assignee: Mark Proctor
>         Attachments: drools_gwt_console.patch, org.drools.eclipse_5.1.0.jar, org.drools.eclipse_5.1.1.jar
>
>
> Groupassignment doesn't work in the GWT-console, because handle of the groupassignment is missing from source. I visited this problem and I found that GWT-console always call the getTasksAssignedAsPotentialOwner(idRef, "en-UK", responseHandler) function without groupIds (in DroolsFlowTaskManagement.java). 
> So I never get task list of the groups.
> I fixed this problem. If I start the jboss server with ant (drools installer created the install directory, where I can use ant for starting system) under install directory, then my solution will read the roles.properties file and store the user's role in hashmap.
> The modified function call is look like:
> getTasksAssignedAsPotentialOwner(idRef, Arrays.asList(groupListMap.get(idRef).split(",")), "en-UK", responseHandler)
> This solution only work with roles.properties file, which contains all user's roles.
> I've attached the patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira