March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-596) When a rule project is set to use jdk5 in properties -> java compiler, it can cause "unsupportered major.minor version" error

by peter lin (JIRA)

When a rule project is set to use jdk5 in properties -> java compiler, it can cause "unsupportered major.minor version" error ----------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-596 URL: http://jira.jboss.com/jira/browse/JBRULES-596 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.5 Environment: windows XP, eclipse 3.2.1, jdk 1.5.0 Reporter: peter lin Assigned To: Mark Proctor Priority: Minor If a person's Eclipse is set to use jdk5 as the default, it can cause the plugin to not work. The error in the problems summary in eclipse says "unsupported major.minor version". The solution is to set the rule project to use jdk1.4. right click on the project select properties select java compiler change setting to jdk1.4 another potential workaround is to set eclipse to use jdk1.4 as the default. -- 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, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBRULES-618) Rule Flow

by Mark Proctor (JIRA)

Rule Flow --------- Key: JBRULES-618 URL: http://jira.jboss.com/jira/browse/JBRULES-618 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-366) Show whether a member left gracefully or ungracefully (crash)

by Bela Ban (JIRA)

Show whether a member left gracefully or ungracefully (crash) ------------------------------------------------------------- Key: JGRP-366 URL: http://jira.jboss.com/jira/browse/JGRP-366 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Optional Fix For: 2.6 Could be a simple tag in the View for each crashed member (default is graceful leave). Possibly API change, tbd -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-429) Optionally disable message bundling for unicast messages

by Bela Ban (JIRA)

Optionally disable message bundling for unicast messages -------------------------------------------------------- Key: JGRP-429 URL: http://jira.jboss.com/jira/browse/JGRP-429 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Unicast messages are often used for responses (e.g. Rpc/MessageDispatcher). While requests arrive as multicast messages, responses are sent back as unicast messages. When sending many requests, bundling may be preferred because we never have to wait for the bundle to fill up: as we're sending many messages, bundles fill up quickly. However, for responses, that may not be the case, so we may want to disable bundling for unicasts. This should be configurable. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-590) Update the manual with the GEF installation instructions

by Michael Neale (JIRA)

Update the manual with the GEF installation instructions -------------------------------------------------------- Key: JBRULES-590 URL: http://jira.jboss.com/jira/browse/JBRULES-590 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.5 Reporter: Michael Neale Assigned To: Michael Neale not sure if this should be in 3.0.x or only trunk. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-602) Missing note on GEF requirement in documentation.

by Philipp Rechberger (JIRA)

Missing note on GEF requirement in documentation. ------------------------------------------------- Key: JBRULES-602 URL: http://jira.jboss.com/jira/browse/JBRULES-602 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.5 Reporter: Philipp Rechberger Assigned To: Mark Proctor I'm evaluating JBRules for our project and so far everything went fine... until I had to reinstall my Eclipse due to several reasons. After doing so I mentioned the new JBRules 3.0.5 version. I setup the update site in Eclipse according to the documentation and installed it. But after restarting Eclipse there was no JBRules icon in the menu bar at all! What went wrong? My colleague was able to reproduce the same problem with a brand new Eclipse installation on his machine. It took us some hours of reinstallations and googling - then we found the problem: it was the missing Graphical Editing Framework (GEF)! After installation of GEF via Calisto Discovery Site the JBRules icon appeared, and so did the JBoss Rules Project entry in the New Project dialog. We found a hint on this site: http://www.zymose.com/faq.html. => "I've installed the plug-in under Eclipse 3.0 but the plug-in is not accessible. What can I do? ... Now drill down in the Eclipse Platform tree view. Both the Graphical Editing Framework 3.0.0 (GEF) and DRLAssistant need to be present (if not, they are not installed) and enabled.". But there is neither a word in the JBRules documentation about dependencies in general, nor GEF in particular. I don't know whether Eclipse's Update Manager should take care on dependencies. Please provide at least a note in your next documentation in order to avoid people getting frustrated to much on that issue (as I almost did) AND maintain the documentation in order it does not say the following: "The Rete View is an advanced feature which is still in experimental state. It uses Swing inside Eclipse. In future it will maybe improved using SWT or GEF." <= It looks like this is outdated information? Cheers Phil -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-764) Example 3.13 should be Predicate expression

by Steve Miner (JIRA)

Example 3.13 should be Predicate expression ------------------------------------------- Key: JBRULES-764 URL: http://jira.jboss.com/jira/browse/JBRULES-764 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 3.0.6 Environment: Mac OS X 10.4.9 JBoss Rules 3.0.6 Reporter: Steve Miner Assigned To: Mark Proctor The docs for 3.0.6 has a mislabled example. Example 3.13 looks like a Predicate expression, not a Return Value operator. Example 3.13. Return Value operator Person( girlAge : age, sex = "F" ) Person( boyAge : age -> ( girlAge.intValue() == boyAge.intValue() + 2 ), sex = 'M' ) -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-569) Typographical error in the documentation.

by Ramakrishnan Subramanian (JIRA)

Typographical error in the documentation. ----------------------------------------- Key: JBRULES-569 URL: http://jira.jboss.com/jira/browse/JBRULES-569 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Ramakrishnan Subramanian Assigned To: Mark Proctor Priority: Trivial Typographical error in this URL: http://labs.jboss.com/file-access/default/members/jbossrules/freezone/doc... Under section 1.6.4. WorkingMemory ..."however this is a weak reference, so it should eventually me garbage collected anyway. ". It should be "however this is a weak reference, so it should eventually be garbage collected anyway. " Under section 1.6.4.2. Assertion. ..."however, no rules are executedl you call "fireAllRules()" should be "however, no rules are executed until you call "fireAllRules()" -- 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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-525) better documentation for globals

by Mark Proctor (JIRA)

better documentation for globals -------------------------------- Key: JBRULES-525 URL: http://jira.jboss.com/jira/browse/JBRULES-525 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 documentations for globals needs padding out some more, maybe with a few use case examples. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-488) Create documentation for "collect" conditional element

by Edson Tirelli (JIRA)

Create documentation for "collect" conditional element ------------------------------------------------------ Key: JBRULES-488 URL: http://jira.jboss.com/jira/browse/JBRULES-488 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 3.1-m1 Add documentation for "collect" conditional element. -- 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, 11 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007