[JBoss JIRA] Closed: (JBRULES-261) Mismatched types in field constraints
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-261?page=all ]
Edson Tirelli closed JBRULES-261.
---------------------------------
Resolution: Done
Fixed. Test case added.
> Mismatched types in field constraints
> -------------------------------------
>
> Key: JBRULES-261
> URL: http://jira.jboss.com/jira/browse/JBRULES-261
> Project: JBoss Rules
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rule Assemply/SPI
> Affects Versions: 3.0.1
> Reporter: Michael Neale
> Assigned To: Edson Tirelli
> Priority: Minor
> Fix For: 4.0.0.MR4
>
>
> Problem: If a rule compares two fields and one of them is a char and the
> other one is a String, the match is always negative. No type-mismatch error
> or warning is displayed. This can be quite confusing. The attached Eclipse
> project illustrates this problem.
> Suggested Solution: If all information is available at compile-time an error
> should be generated on type mismatches. Otherwise there should be a warning
> during run-time and maybe a type conversion attempt.
--
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
17 years
[JBoss JIRA] Updated: (JBRULES-261) Mismatched types in field constraints
by Edson Tirelli (JIRA)
[ http://jira.jboss.com/jira/browse/JBRULES-261?page=all ]
Edson Tirelli updated JBRULES-261:
----------------------------------
Issue Type: Bug (was: Task)
> Mismatched types in field constraints
> -------------------------------------
>
> Key: JBRULES-261
> URL: http://jira.jboss.com/jira/browse/JBRULES-261
> Project: JBoss Rules
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Rule Assemply/SPI
> Affects Versions: 3.0.1
> Reporter: Michael Neale
> Assigned To: Edson Tirelli
> Priority: Minor
> Fix For: 4.0.0.MR4
>
>
> Problem: If a rule compares two fields and one of them is a char and the
> other one is a String, the match is always negative. No type-mismatch error
> or warning is displayed. This can be quite confusing. The attached Eclipse
> project illustrates this problem.
> Suggested Solution: If all information is available at compile-time an error
> should be generated on type mismatches. Otherwise there should be a warning
> during run-time and maybe a type conversion attempt.
--
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
17 years
[JBoss JIRA] Created: (JBMESSAGING-761) Consider clean ways of taking a node out of the cluster for maintenance
by Tim Fox (JIRA)
Consider clean ways of taking a node out of the cluster for maintenance
-----------------------------------------------------------------------
Key: JBMESSAGING-761
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-761
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Fix For: 1.2.1
We should consider how the system administrator can take a node out of the cluster for maintenance without clients losing messages.
If a node is just shut down then any clients connected to that node will failover to another node, potentially losing any non persistent messages - this may not be acceptable.
We should also consider functionality on the jmx console where a server cen block the creation of any new connections, and the information such as client machine name, client id, ip address can be displayed for existing connetions. This would allow the sysadmin to contact the clients and shut them down cleanly before bringing the server down.
--
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
17 years
[JBoss JIRA] Created: (JBPORTAL-1538) Permissions Caching When Session Abandoned
by Mike Millson (JIRA)
Permissions Caching When Session Abandoned
------------------------------------------
Key: JBPORTAL-1538
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1538
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Security
Affects Versions: 2.4.1 SP1
Environment: RHEL 5 Workstation
FireFox 1.5.0.1.2
Reporter: Mike Millson
Assigned To: Julien Viet
Starting with an out-of-box portal deployment:
1) Log in as admin
2) Create a role TestRole
3) Create a user TestUser
4) Assign TestRole to TestUser
5) Create a page TestPage and secure it with TestRole
6) Log out
7) Log in as TestUser. You will see the TestPage tab
8) Abandon the TestUser session by closing the browser or deleting the TestUser session cookie
9) Log in as admin
10) Remove TestRole from TestUser
11) Log out
12) Type in the url to the portal (don't use login screen presented after #11 logout)
13) Log in as TestUser
14) The TestPage tab is displayed, even though TestUser no longer has permission to access it.
The TestPage tab does not disappear until I log out and re-login as TestUser.
I don't think this is a 2nd level cache or query cache issue, as I disabled both and could still reproduce this.
--
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
17 years
[JBoss JIRA] Created: (JBRULES-976) ShadowProxyUtils.cloneObject() spews noise to stdout
by Dirk Bergstrom (JIRA)
ShadowProxyUtils.cloneObject() spews noise to stdout
----------------------------------------------------
Key: JBRULES-976
URL: http://jira.jboss.com/jira/browse/JBRULES-976
Project: JBoss Rules
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 4.0.0.MR4
Reporter: Dirk Bergstrom
Assigned To: Mark Proctor
Attachments: diff.txt
With this new code, I get about 75 megs worth of the following errors
when I initialize my application (stacktraces abbreviated):
java.lang.IllegalAccessException: Class org.drools.util.ShadowProxyUtils can not access a member of class java.util.Collections$EmptySet with modifiers "private"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
at java.lang.Class.newInstance0(Class.java:344)
at java.lang.Class.newInstance(Class.java:303)
at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
java.lang.InstantiationException: java.util.Collections$UnmodifiableSet
at java.lang.Class.newInstance0(Class.java:335)
at java.lang.Class.newInstance(Class.java:303)
at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
The attached patch takes care of these two errors, and removes the
printStackTrace() call from the catch block, since it's noise to
everyone except the Drools developers. If there's a debug or
developer flag of some kind in the codebase, it would be reasonable to
use that to control the output.
--
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
17 years