February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-389) Improve support for @Traitable POJOs and @Trait interfaces

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-389?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-389. -------------------------------- Fix Version/s: 6.1.0.Beta1 Resolution: Done > Improve support for @Traitable POJOs and @Trait interfaces > ---------------------------------------------------------- > > Key: DROOLS-389 > URL: https://issues.jboss.org/browse/DROOLS-389 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > Fix For: 6.1.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2319) LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2319?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2319: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1061181|https://bugzilla.redhat.com/show_bug.cgi?id=1061181] from ON_QA to VERIFIED > LDAP Search containing URL - InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-2319 > URL: https://issues.jboss.org/browse/WFLY-2319 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Eduardo Martins > Fix For: 8.0.0.Final > > Attachments: LdapSearching.tgz > > > The following code: - > {code} > Hashtable env = new Hashtable(); > env.put("java.naming.factory.initial", "com.sun.jndi.ldap.LdapCtxFactory"); > env.put("java.naming.security.authentication", "simple"); > env.put("java.naming.provider.url", "ldap://localhost:10389"); > env.put(InitialDirContext.SECURITY_PRINCIPAL, "uid=admin,ou=system"); > env.put(InitialDirContext.SECURITY_CREDENTIALS, "secret"); > SearchControls ctl = null; > String attrArr[] = new String[1]; > attrArr[0] = "sn"; > ctl = new SearchControls(2, 0L, 0, attrArr, false, false); > String base = "ldap://localhost:10389/dc=simple,dc=wildfly,dc=org"; > String filter = "(uid=UserOne)"; > NamingEnumeration nenum = null; > DirContext ictx = null; > ictx = new InitialDirContext(env); > nenum = ictx.search(base, filter, ctl); > {code} > Results in the following exception: - > {noquote} > 13:03:45,598 ERROR [stderr] (default task-1) javax.naming.InvalidNameException: ldap:: [LDAP: error code 34 - Invalid root Dn given : ldap: (0x6C 0x64 0x61 0x70 0x3A ) is invalid]; remaining name 'ldap://localhost:10389/dc=simple,dc=wildfly,dc=org' > 13:03:45,599 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3025) > 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) > 13:03:45,600 ERROR [stderr] (default task-1) at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:1034) > {noquote} > Switching to a base that does not begin with a URL and the search works, executing this code outside of WildFly also works. > The underlying issue is that the default InitialContext implementation contains the following method: - > {code} > protected Context getURLOrDefaultInitCtx(String name) > throws NamingException { > if (NamingManager.hasInitialContextFactoryBuilder()) { > return getDefaultInitCtx(); > } > String scheme = getURLScheme(name); > if (scheme != null) { > Context ctx = NamingManager.getURLContext(scheme, myProps); > if (ctx != null) { > return ctx; > } > } > return getDefaultInitCtx(); > } > {code} > As the naming subsystem has registered a InitialContextFactoryBuilder this code will never fall down to the scheme specific section. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2901) mod_cluster hot standby worker can't be configured

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2901?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-2901: --------------------------------- Summary: mod_cluster hot standby worker can't be configured (was: mod_cluster hot standby worker can't be configured.) > mod_cluster hot standby worker can't be configured > -------------------------------------------------- > > Key: WFLY-2901 > URL: https://issues.jboss.org/browse/WFLY-2901 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 8.0.0.Final > > > <simple-load-provider factor="0"/> isn't accepted by the parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2901) mod_cluster hot standby worker can't be configured.

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2901?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-2901: --------------------------------- Summary: mod_cluster hot standby worker can't be configured. (was: modcluster hot standby worker can't be configured.) Fix Version/s: 8.0.0.Final Assignee: Radoslav Husar (was: Jean-Frederic Clere) So value 0 means standby. Is there anything else needed to support stand-by mode? https://community.jboss.org/wiki/Mod-ClusterManagementProtocol > mod_cluster hot standby worker can't be configured. > --------------------------------------------------- > > Key: WFLY-2901 > URL: https://issues.jboss.org/browse/WFLY-2901 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.CR1 > Reporter: Jean-Frederic Clere > Assignee: Radoslav Husar > Fix For: 8.0.0.Final > > > <simple-load-provider factor="0"/> isn't accepted by the parser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-421) EvaluatorWrapper does not resolve the right handle correctly

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-421?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-421. -------------------------------- Fix Version/s: 6.1.0.Beta1 Resolution: Done > EvaluatorWrapper does not resolve the right handle correctly > ------------------------------------------------------------ > > Key: DROOLS-421 > URL: https://issues.jboss.org/browse/DROOLS-421 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.Beta1 > > > The EvaluatorWrapper tries to look up the right handle from the WM, but there may be cases (e.g. when the right input comes from a FROM node) > where the handle is not in the WM, causing a NPE. This causes the right handle to be null, or to be resolved incorrectly. Evaluations are then inconsistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-421) EvaluatorWrapper does not resolve the right handle correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-421?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-421: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1063809|https://bugzilla.redhat.com/show_bug.cgi?id=1063809] from NEW to ASSIGNED > EvaluatorWrapper does not resolve the right handle correctly > ------------------------------------------------------------ > > Key: DROOLS-421 > URL: https://issues.jboss.org/browse/DROOLS-421 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > > The EvaluatorWrapper tries to look up the right handle from the WM, but there may be cases (e.g. when the right input comes from a FROM node) > where the handle is not in the WM, causing a NPE. This causes the right handle to be null, or to be resolved incorrectly. Evaluations are then inconsistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-421) EvaluatorWrapper does not resolve the right handle correctly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-421?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-421: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1063809 > EvaluatorWrapper does not resolve the right handle correctly > ------------------------------------------------------------ > > Key: DROOLS-421 > URL: https://issues.jboss.org/browse/DROOLS-421 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final, 6.0.1.Final, 6.1.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > > The EvaluatorWrapper tries to look up the right handle from the WM, but there may be cases (e.g. when the right input comes from a FROM node) > where the handle is not in the WM, causing a NPE. This causes the right handle to be null, or to be resolved incorrectly. Evaluations are then inconsistent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-416) Queries do not work with events

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-416?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-416. -------------------------------- Fix Version/s: 6.1.0.Beta1 Resolution: Done > Queries do not work with events > ------------------------------- > > Key: DROOLS-416 > URL: https://issues.jboss.org/browse/DROOLS-416 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > Fix For: 6.1.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-416) Queries do not work with events

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-416?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-416: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Queries do not work with events > ------------------------------- > > Key: DROOLS-416 > URL: https://issues.jboss.org/browse/DROOLS-416 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Critical > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-416) Queries do not work with events

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-416?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-416: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1063805|https://bugzilla.redhat.com/show_bug.cgi?id=1063805] from NEW to ASSIGNED > Queries do not work with events > ------------------------------- > > Key: DROOLS-416 > URL: https://issues.jboss.org/browse/DROOLS-416 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
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 February 2014