[rules-users] Drools 5.1.1 KnowledgeAgent and SecurityRules

[Robert Morse]

This is good to know.  I was just in the middle of converting to 5.1.1 but will not stop.  By the way the 5.1.1 version of Guvnor appears to be unstable under JBoss 5.1.
Verify operations just hang.  Error messages (with no message) get displayed, Inability to sign out, etc.   
Back to 5.0.1.

On Sep 9, 2010, at 7:53 AM, Tihomir Surdilovic wrote:

>  Inguyen, I assume you are using Seam2 in your client app. In Seam 
> 2.2.0.CR1 (http://relation.to/Bloggers/Seam220CR1Released ) we replaced 
> the Drools 4 jars with Drools 5.0 jars, however the internal integration 
> was not changed to use the Drools 5 API.
> Raise a JBSEAM (https://jira.jboss.org/browse/JBSEAM) Jira and we can 
> see what can be done, otherwise now your option is is to pull from 
> Guvnor 5.0.1 in your Seam applications until Seam3 becomes available as 
> this will be a non-issue in our Drools module for Seam3 
> (http://seamframework.org/Seam3).
> 
> Tihomir
> On 9/9/10 9:21 AM, lnguyen wrote:
>> I recently upgraded from drools guvnor 5.0.1 to 5.1.1 but I haven't seen any
>> examples on how to change securityRules now that RuleBase has been replaced
>> with KnowledgeBase.
>> 
>> Originally I had...
>> 
>> <drools:rule-agent
>>         name="securityRules"
>> 
>> url="https://127.0.0.1:7002/drools-guvnor-5.0.1/org.drools.guvnor.Guvnor/package/Security/LATEST"
>>         local-cache-dir="/tmp/"
>>         poll="60"
>>         auto-create="true"/>
>> 
>> <security:rule-based-permission-resolver security-rules="#{securityRules}"/>
>> 
>> I tried to leave this way but then i get an error but the 5.1.1 guvnor
>> secures the URL so I get the following: RuleAgent(default) EXCEPTION
>> Response: '401: Unauthorized' for url: ...
>> 
>> How do configure the application security to use the KnowledgeBase?
> 
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users

The human mind is an iterative processor, it never does anything right the first time.  What it does well is to make improvements on every iteration (deMarco)