Remoting Endpoint Connector Resource Adapter
--------------------------------------------
Key: JBREM-839
URL: http://jira.jboss.com/jira/browse/JBREM-839
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: Remoting 3 M3
--
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
Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier
------------------------------------------------------------
Key: JBREM-917
URL: http://jira.jboss.com/jira/browse/JBREM-917
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: David Lloyd
Fix For: 3.0.0.GA
Master bug to hold all issues that prevent inclusion of Remoting 3 - based transports for various services in JBossAS.
--
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
Make stream detectors pluggable
-------------------------------
Key: JBREM-908
URL: http://jira.jboss.com/jira/browse/JBREM-908
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: r3 api, r3 core
Reporter: David Lloyd
Fix For: Remoting 3 M3
Right now there's just a fixed singleton list with just the default detector. See org.jboss.cx.remoting.core.CoreSession.
--
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
The Eclipse IDE plugin should be split in a runtime and ui plugins
------------------------------------------------------------------
Key: JBRULES-766
URL: http://jira.jboss.com/jira/browse/JBRULES-766
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 3.0.5
Environment: Eclipse 3.2 + JBRULES 3.0.5
Reporter: Christophe Avare
Assigned To: Mark Proctor
Priority: Minor
This is a return of experience after working with Eclipse + JBRules on a medium-sized project.
It happens that the deployement of the org.drools.ide plugin on a end user workstation clutters the ui with unwanted features and we had to refactor it so that the libs are packaged on a plugin of their own, the UI stuff in another, not deployed, plugin.
--
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
Pair Matching in DRL editor
---------------------------
Key: JBRULES-581
URL: http://jira.jboss.com/jira/browse/JBRULES-581
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Kris Verlaenen
Assigned To: Kris Verlaenen
DRL editor should show matching bracket for '(', ')', '[', ']', '{' and '}'
It should support auto-adding of closing bracket when typing opening bracket as well.
--
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
IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository
----------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 3.1-m3
package layout will be something like:
/<RulePackageName>.package
- has imports in it etc...
/Rule Name 1.rule (vanilla DRL)
/Rule Name 2.brule (uses DSL)
/XXX.dsl (used by brule file)
None of the atomic rule files will have package name, or anything other then when/then/attributes, the IDE will have to look in to the .package file to find this out.
.drl files can work as they do now.
Let me know if this is a dupe ;)
--
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
Remember selected working memory for debug views
------------------------------------------------
Key: JBRULES-493
URL: http://jira.jboss.com/jira/browse/JBRULES-493
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Mark Proctor
Assigned To: Kris Verlaenen
Fix For: 3.1-m1
When you select working memory it should remember that instance, so when you are propagating through the network you shouldn't have to keep re-selecting it to view data. Better yet we should have another debug view that collects working memory instances as it "realises" them during debug runtime, the current one is highlighed and a different current can easily be selected.
--
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
tree views should remember open/close toggle
--------------------------------------------
Key: JBRULES-775
URL: http://jira.jboss.com/jira/browse/JBRULES-775
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Mark Proctor
Assigned To: Kris Verlaenen
Fix For: 3.1-m2
When using the views, such as agenda view, they keep expanding everything, when you have a large number of entries having to repeatedly re-adjust the layout of the tree view is annoying.
--
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
Working Memory View by Object Type
----------------------------------
Key: JBRULES-776
URL: http://jira.jboss.com/jira/browse/JBRULES-776
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Mark Proctor
Assigned To: Kris Verlaenen
Fix For: 3.1-m2
It would be nice in the Working Memory view if we could also view by object type.
--
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
Support drl files that contain only one rule
--------------------------------------------
Key: JBRULES-980
URL: http://jira.jboss.com/jira/browse/JBRULES-980
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Kris Verlaenen
Assigned To: Kris Verlaenen
Fix For: FUTURE
As possible in the BRMS, a drl file can possibly contain only one rule without rule name, in combination with a .package file.
Currently, the drl editor does not support this type of drl file.
--
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