[JBoss JIRA] Created: (JGRP-1231) create a Discovery protocol using a javax.sql.DataSource
by Sanne Grinovero (JIRA)
create a Discovery protocol using a javax.sql.DataSource
--------------------------------------------------------
Key: JGRP-1231
URL: https://jira.jboss.org/browse/JGRP-1231
Project: JGroups
Issue Type: Feature Request
Reporter: Sanne Grinovero
Assignee: Bela Ban
Fix For: 2.11, 3.0
It would be useful to have a JDBC/Datasource protocol do perform the autodiscovery of other nodes.
For example when used together to Infinispan which might use a database as cache store it would be practical to be able to reuse the same datasource for this purpose, so that setting up a service requires a single set of credentials.
In case of deployments on EC2 so it could be possible to use S3 for both discovery and cache store, or RDS for both discovery and cache store (or mixed in any form).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JGRP-1281) ProxyAddress and UUID don't compareTo()
by Bela Ban (JIRA)
ProxyAddress and UUID don't compareTo()
---------------------------------------
Key: JGRP-1281
URL: https://issues.jboss.org/browse/JGRP-1281
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.12
When we present global views in RELAY, we mix local (UUID) and global (ProxyAddress) addresses. This works fine as both classes implement Address.
However, when we sort them, there's a ClassCastException, because UUID.compareTo(ProxyAddress) fails. ProxyAddress.compareTo(UUID) works.
ProxyAddressTest is the unit test for this.
SOLUTION: add code in UUID.compare() that compares to a ProxyAddress
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBRULES-1644) Make drools imply null checks before trying to read a value
by Alex McCarrier (JIRA)
Make drools imply null checks before trying to read a value
-----------------------------------------------------------
Key: JBRULES-1644
URL: http://jira.jboss.com/jira/browse/JBRULES-1644
Project: JBoss Drools
Issue Type: Feature Request
Components: Drl Parser/Builder
Affects Versions: 4.0.6
Environment: all
Reporter: Alex McCarrier
Assigned To: Mark Proctor
Priority: Minor
Fix For: FUTURE
Not sure if this is MVEL or drools itself, but it would be nice if it would do null checks on fields for you rather than having the rule author do it. Example, when doing something like:
when
Object(value1.value2 == something)
before attempting to read value2 it makes sure value1 is not null, and if value1 is null than rather than throwing an error like it does currently, just consider the rule as not matching.
--
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
15 years, 1 month