[ http://jira.jboss.com/jira/browse/JBRULES-352?page=all ]
Mark Proctor updated JBRULES-352:
---------------------------------
Fix Version/s: 4.0.0.MR3
(was: 4.0.0.MR2)
> DRLEditor to have seperate tab for DSL style DRL editing, and vanilla DRL editing
> ---------------------------------------------------------------------------------
>
> Key: JBRULES-352
> URL: http://jira.jboss.com/jira/browse/JBRULES-352
> Project: JBoss Rules
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Eclipse IDE
> Affects Versions: 3.0.1
> Reporter: Michael Neale
> Assigned To: Kris Verlaenen
> Fix For: 4.0.0.MR3
>
>
> Editor is a bit complex mixing in DSL and DRL features. Best to seperate it out. There will also be an API for expanding a DSL style DRL into vanilla DRL for debugging.
--
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
[ http://jira.jboss.com/jira/browse/JBRULES-347?page=all ]
Mark Proctor updated JBRULES-347:
---------------------------------
Fix Version/s: 4.0.0.MR3
(was: 4.0.0.MR2)
> context assist help with f1
> ---------------------------
>
> Key: JBRULES-347
> URL: http://jira.jboss.com/jira/browse/JBRULES-347
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Mark Proctor
> Assigned To: Kris Verlaenen
> Fix For: 4.0.0.MR3
>
>
> f1 should show appropriate help.
--
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
[ http://jira.jboss.com/jira/browse/JBRULES-300?page=all ]
Mark Proctor updated JBRULES-300:
---------------------------------
Fix Version/s: 4.0.0.MR3
(was: 4.0.0.MR2)
> Keyboard shortcuts support for DRL editor
> -----------------------------------------
>
> Key: JBRULES-300
> URL: http://jira.jboss.com/jira/browse/JBRULES-300
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Eclipse IDE
> Affects Versions: 3.0.1
> Reporter: Kris Verlaenen
> Assigned To: Kris Verlaenen
> Priority: Minor
> Fix For: 4.0.0.MR3
>
>
> Keyboard shortcuts ? like F3 to navigate to the class or getter would be nice
--
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
Bean proxy in JNDI not properly refreshed when cluster topology changes
-----------------------------------------------------------------------
Key: EJBTHREE-949
URL: http://jira.jboss.com/jira/browse/EJBTHREE-949
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: AS 4.2.0 CR2, EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 4.2.0 GA
When a change to the cluster topology occurs, the proxies in JNDI for the affected beans are not being updated. Effect is the target list in the proxy always contains the members that were present when the bean was deployed and the proxy created.
EJB2 has a process to rebind the proxy when a topology change occurs; EJB3 probably needs something similar.
--
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
Move conways game of life to a stateful example
-----------------------------------------------
Key: JBRULES-800
URL: http://jira.jboss.com/jira/browse/JBRULES-800
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Mark Proctor
Assigned To: Mark Proctor
Fix For: 3.1-m2
Conways game of life still has a lot of logic in java and works statefully, so a lot of repopulating of data. Should re-work the example to be stafeful, initially using agenda-groups and then move it to rule-flow, so that we have a good rule-flow example.
--
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
[ http://jira.jboss.com/jira/browse/JBRULES-229?page=all ]
Mark Proctor closed JBRULES-229.
--------------------------------
Resolution: Done
> Use static imports for functions instead of functionfixer
> ---------------------------------------------------------
>
> Key: JBRULES-229
> URL: http://jira.jboss.com/jira/browse/JBRULES-229
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Reporter: Michael Neale
> Assigned To: Mark Proctor
> Fix For: 3.1-m2
>
>
> Would be much neater to be able to do away with function fixer.
--
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
Add missing serialVersionUIDs
-----------------------------
Key: EJBTHREE-951
URL: http://jira.jboss.com/jira/browse/EJBTHREE-951
Project: EJB 3.0
Issue Type: Task
Affects Versions: AS 4.2.0 CR2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 4.2.0 GA, EJB 3.0 RC11 - FD
Eclipse reports the following classes in src/main are missing serialVersionUID in Branch_4_2:
CacheMap
ExtendedEntityManager
ExtendedSessionInvocationHandler
ActivationSpec
Will update trunk as well including any other classes that eclipse warns about.
--
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
in an enterprise appln where thousands of rules are there, how can we load the drls and for specified request how to load specified drl
----------------------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-827
URL: http://jira.jboss.com/jira/browse/JBRULES-827
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rule Assemply/SPI
Affects Versions: 3.0.4
Reporter: dibyananda senapati
Assigned To: Mark Proctor
how can we implement drools in enterprise appln.
Should we load all the entire drl files before the appln starts or we should dynamically load the drl.
please suggest and provide me the code
--
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
can anybody please let me know how to access the complex object structure in the rules file
-------------------------------------------------------------------------------------------
Key: JBRULES-835
URL: http://jira.jboss.com/jira/browse/JBRULES-835
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.6
Reporter: Venkat Garlapati
Assigned To: Mark Proctor
I have object like this
Entity{
Application getApplication()
Award getAward()
}
I cannot assert objects before firing the rules all I can assert is Entity object and I will get the appropriate nested objects in the .drl file and compare them against the rules that I have written.
my problem is as these objects are nested objects how to access the properties of these objects in the LHS
ex. application.getName().getAge() and comparing them against some value.
please help me.
--
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
Large integer values in decision tables are converted to scientific notation in DRL which cannot be parsed
----------------------------------------------------------------------------------------------------------
Key: JBRULES-435
URL: http://jira.jboss.com/jira/browse/JBRULES-435
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Decision tables, Drl Parser/Builder
Reporter: Volker Augustin
Assigned To: Mark Proctor
When a condition column in a decision table contains values like 25000000, this is compiled using the SpreadsheetCompiler into 2.5E7 in the DRL. However, the DRL parser/compiler cannot cope with this notation and exists with a unexpected token "E7" error message.
--
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