November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-867) Can't load classes from expanded class dir on windows

by Dan Lipofsky (JIRA)

Can't load classes from expanded class dir on windows ----------------------------------------------------- Key: JBRULES-867 URL: http://jira.jboss.com/jira/browse/JBRULES-867 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.6 Environment: Windows XP SP2 (problem not reproducable on Linux), JDK 1.5.0_11-b03, Ant 1.7.0, Eclipse 3.2.2 Reporter: Dan Lipofsky Assigned To: Mark Proctor Priority: Minor When running some JUnit tests of our rules from an Ant task or from Eclipse, we got the following rule compile errors: org.drools.rule.InvalidRulePackage: Rule Compilation error The import com.bricsnet.core.util.constants cannot be resolved UserGroup cannot be resolved The same rules compile perfectly on the server. On the server the class is question is only available from a JAR file. In Eclipse it in an expanded class dir. In the Ant task both the expanded class dir and the JAR file were in the classpath, but the expanded class dir was first. Putting the JAR first on the classpath solved the problem for the ant task (but this is not possible for eclipse since the JAR is not available). Therefore we believe the problem is specifically related to loading from an expanded class dir. The problem seems to occur on Windows but not Linux. Finally the problem only seems to occur for some classes. All 3 of the classes in the sample rule file below are in the same boat, but for some reason only UserGroup is a problem (it might be the Example 1 (fails): package com.foobar.rules; import com.foobar.core.util.constants.UserGroup; import com.foobar.core.util.security.principal.UserPrincipal; import com.foobar.core.util.security.auth.RuleAuthorization; rule "test_rule" when r: RuleAuthorization() u: UserPrincipal() eval(u.hasGroup(123)) then r.setLevel(RuleAuthorization.READ); end Example 2 (works): package com.foobar.rules; import com.foobar.core.util.security.principal.UserPrincipal; import com.foobar.core.util.security.auth.RuleAuthorization; rule "test_rule" when r: RuleAuthorization() u: UserPrincipal() eval(u.hasGroup(123)) then r.setLevel(RuleAuthorization.READ); end -- 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, 2 months

5
6
0 / 0

[JBoss JIRA] Created: (JBAOP-395) Release/Packaging holder task

by Kabir Khan (JIRA)

Release/Packaging holder task ------------------------------ Key: JBAOP-395 URL: http://jira.jboss.com/jira/browse/JBAOP-395 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 -- 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, 2 months

1
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1781) enable optimistic locking when using jboss cache as second level cache

by Prabhat Jha (JIRA)

enable optimistic locking when using jboss cache as second level cache ---------------------------------------------------------------------- Key: JBPORTAL-1781 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1781 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.2 Final Reporter: Prabhat Jha Assigned To: Sohil Shah Just creating this jira so that we can track what we discussed. Corresponding forum entry at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101418#4101418. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1222) POC - Refactor of MethodCall class

by Mircea Markus (JIRA)

POC - Refactor of MethodCall class ---------------------------------- Key: JBCACHE-1222 URL: http://jira.jboss.com/jira/browse/JBCACHE-1222 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Mircea Markus Priority: Minor Fix For: 2.2.0.GA prototype: Instead of using reflection for calling methods on cache, all those called methods(the CacheImpl._xyz methods) might be moved to their own classes. Benefits: - no more reflection calls (small as reflection optimized) - the rollback and do methods would be in same place - easier to read code - code would be easy to test -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1143) ClassTypeResolver throws an Error

by Michael Neale (JIRA)

ClassTypeResolver throws an Error --------------------------------- Key: JBRULES-1143 URL: http://jira.jboss.com/jira/browse/JBRULES-1143 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 4.0.0.GA Reporter: Michael Neale Assigned To: Mark Proctor Priority: Minor Fix For: FUTURE would be nicer if it was a better exception (or reported it a bit better) - perhaps. Its pretty buried. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1111) Final methods of POJO's aer never evaluated

by Arjun Dhar (JIRA)

Final methods of POJO's aer never evaluated ------------------------------------------- Key: JBRULES-1111 URL: http://jira.jboss.com/jira/browse/JBRULES-1111 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA Reporter: Arjun Dhar Assigned To: Mark Proctor Priority: Minor If a POJO defines certain getters as final and they are used in a condition in the Rules, then they do not evaluate properly -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1118) Abstract base classes of remote proxies are not declaring serialVersionUIDs

by Carlo de Wolf (JIRA)

Abstract base classes of remote proxies are not declaring serialVersionUIDs --------------------------------------------------------------------------- Key: EJBTHREE-1118 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1118 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA Reporter: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.Beta3, AS 4.2.3.GA javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3 .remoting.BaseRemoteProxy; local class incompatible: stream classdesc serialVersionUID = -2711693270411201590, local class serialVersionUID = 1126421850898582900] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:724) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589) at javax.naming.InitialContext.lookup(InitialContext.java:351) ...... -- 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, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1289) BRMS gives unusable error messages when validating DSL based rules

by Phil Verghese (JIRA)

BRMS gives unusable error messages when validating DSL based rules ------------------------------------------------------------------ Key: JBRULES-1289 URL: http://jira.jboss.com/jira/browse/JBRULES-1289 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.2 Reporter: Phil Verghese Assigned To: Mark Proctor The error messages that are shown when you click "Validate" when editing a business rule that uses a DSL in the BRMS are not user-friendly at all. If I make a small typo and misspell the name of an attribute (a very likely thing for a BRMS user to do), and click the Validate button, the error I get back is a big stack trace starting with "java.lang.RuntimeException: SNO: Conversion failed at org.codehaus.janino.UnitCompiler.numericPromotion(UnitCompiler.java) at ..." Nowhere in that stack trace is anything that gives a hint that the error is just a typo of an attribute name. Contrast this with the rather helpful error message I get if I make the same typo when editing a DRL rule: "Unable to create Field Extractor for 'overtimHours'". (The error is that I misspelled overtimeHours). The BRMS needs to give the same type of helpful error message on validation errors when editing a DSL rule. -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1133) Janino and eclipse compiler might need to be optional for 4.1

by Geoffrey De Smet (JIRA)

Janino and eclipse compiler might need to be optional for 4.1 ------------------------------------------------------------- Key: JBRULES-1133 URL: http://jira.jboss.com/jira/browse/JBRULES-1133 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Fix For: FUTURE I didn't want to make this change for 4.0.x as it would require our users to put a direct dependency on either janino or eclipse-compiler. Drools-compiler needs one of both. Currently users get bloated with a transitive dependency on both. Making them optional would force them to make a dependency on one of the themselves... which makes the "hello world" program harder. As it would also force jbrms's etc tests to choose one. Why shouldn't do this before 4.1, if we even want to do this. What do you think? -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1335) Add Welcome Screen , Tooltips (or 1 para of descriptive text) to BRMS to help new users and links to Help Docs

by Paul Browne (JIRA)

Add Welcome Screen ,Tooltips (or 1 para of descriptive text) to BRMS to help new users and links to Help Docs ------------------------------------------------------------------------------------------------------------- Key: JBRULES-1335 URL: http://jira.jboss.com/jira/browse/JBRULES-1335 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Environment: Drools BRMS Reporter: Paul Browne BRMS is very powerful, but can be intimidating for first time users. Suggest adding 1) Welcome screen (e.g. Like Eclipse after 1st install) giving 3/4 pointers to users as to where they might begin 2) Within the various BRMS screens, add Tooltips / descriptive text to explain what each command does . Give advanced users options to close / hide this 3) Link to HTML Help doc (even current drools manual) from every screen. -- 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, 3 months

3
2
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 November 2007