[JBoss JIRA] Created: (JBRULES-931) Have defect with JavaBeans as fact.
by Anthony Tran (JIRA)
Have defect with JavaBeans as fact.
-----------------------------------
Key: JBRULES-931
URL: http://jira.jboss.com/jira/browse/JBRULES-931
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 3.0.6
Environment: W-XP SP2
Reporter: Anthony Tran
Assigned To: Mark Proctor
Fix For: 3.0.6
I use XMLBeans to generate and compile Java classes at runtime, then parse XML files to be objects of classess which has been compiled. Those objects are added into working memory as facts in my application. JBOSS Rule engine can recognize those facts, but can't bound.
Ex:
rule
when
p:ProductService(type == "monitor")
u:User(product == p)
then
.....
end
The LHS is never fired.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months
[JBoss JIRA] Created: (JBAS-3720) Change structure of ClusteredSSO data in tree cache to avoid lock issues
by Brian Stansberry (JIRA)
Change structure of ClusteredSSO data in tree cache to avoid lock issues
------------------------------------------------------------------------
Key: JBAS-3720
URL: http://jira.jboss.com/jira/browse/JBAS-3720
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
For each SSO entry, their should be child node per server where the SSO has been used. This is different from the current where all the session data for an SSO is in one node. The data map in each child node would hold the session ids of the sessions active on that server.
This kind of structure avoids most lock contention between different servers.
Can't do this in 4.0.x as it prevents interoperation with earlier releases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 10 months