January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5484) Calling HttpServletRequest.logout() with single sign-on enabled only works every second time

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5484?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-5484: ------------------------------------ [~rjanik] I've looked at the reproducer, but I fail to see where ?logout=true is handled anywhere in the requested servlet. (I'm assuming this uses this application: https://github.com/clusterbench/clusterbench/blob/master/clusterbench-com...) As far as I can tell, the only request parameters being handled are: * readonly (for read-only requests) * invalidate (for session invalidation) I see no code that performs a HttpServletRequest.logout(). If I am mistaken, please post the source. > Calling HttpServletRequest.logout() with single sign-on enabled only works every second time > -------------------------------------------------------------------------------------------- > > Key: WFLY-5484 > URL: https://issues.jboss.org/browse/WFLY-5484 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 10.0.0.CR5 > > Attachments: reproducer-jbeap-1282.zip > > > See "Steps to Reproduce". Logging out from an application only works every second time, e.g. HttpRequestServlet.logout() has to be called twice in order to have any effect > This doesn't occur without <single-sign-on/> enabled - logout() has the expected effect. The issue is security related, thus I'm adding our security team members as watchers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5935) Upgrade Netty to 4.0.32.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-5935: --------------------------------- Summary: Upgrade Netty to 4.0.32.Final Key: WFLY-5935 URL: https://issues.jboss.org/browse/WFLY-5935 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1019: ------------------------------------- Description: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility when changed) -- The current proposal is to rename the target namespace to http://drools.org/xsd/kmodule (so it's clear where the xsd's can be found) - The release procedure will include copying the xsd file during a community .0.Final release. was: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility when changed) - The release procedure will include copying the xsd file during a community .0.Final release. > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility when changed) > -- The current proposal is to rename the target namespace to http://drools.org/xsd/kmodule (so it's clear where the xsd's can be found) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1019: ------------------------------------------ The xsd's are online now, for example here: http://www.drools.org/xsd/kmodule_6_3.xsd Mario found out that the examples already used the 6.0.0 namespace, so it can't be made versionless in the 6 series. > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet edited comment on DROOLS-1019 at 1/5/16 11:16 AM: ------------------------------------------------------------------- The xsd's are online now, for example here: http://www.drools.org/xsd/kmodule_6_3.xsd Mario found out that the examples already used the 6.0.0 target namespace, so it can't be made versionless in the 6 series :( was (Author: ge0ffrey): The xsd's are online now, for example here: http://www.drools.org/xsd/kmodule_6_3.xsd Mario found out that the examples already used the 6.0.0 namespace, so it can't be made versionless in the 6 series. > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1019: ------------------------------------- Description: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility when changed) - The release procedure will include copying the xsd file during a community .0.Final release. was: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) - The release procedure will include copying the xsd file during a community .0.Final release. > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility when changed) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1019: ----------------------------------- Assignee: Geoffrey De Smet (was: Mario Fusco) > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1019: ------------------------------------------ PR on release procedure: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/122 > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1017) NPE deleting an expired event in equality mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1017?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1017: ------------------------------------------------- Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1295786|https://bugzilla.redhat.com/show_bug.cgi?id=1295786] from ASSIGNED to MODIFIED > NPE deleting an expired event in equality mode > ---------------------------------------------- > > Key: DROOLS-1017 > URL: https://issues.jboss.org/browse/DROOLS-1017 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.4.x > > > Trying to delete an already expired event in equality mode causes the following NPE in the TMS: > {code} > java.lang.NullPointerException > at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:506) > at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:442) > at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1120) > at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:121) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1003) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1346) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1284) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1303) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1274) > at org.drools.compiler.integrationtests.CepEspTest.testDeleteExpiredEventWithTimestampAndEqualityKey(CepEspTest.java:5682) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2000) Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2000?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2000: -------------------------------- Although, if you submit a pull request (e.g. write the fully qualified classname)?... :-) > Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications > ---------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2000 > URL: https://issues.jboss.org/browse/JGRP-2000 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Reporter: Jim Thomas > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.7 > > > The output of printProtocolSpecAsXML does not contain the pbcast package prefix for NACKACK2, GMS, STATE, etc. so the load fails due to class load failure. > Suggest either add org.jgroups.protocols.pbcast to the protocol loading search or write protocol names with full classpath when printing the spec. > Might it also make sense to skip writing out deprecated parameters? > Reason: I'm generating my protocol stack programmatically because some of the parameter values are determined at run time. In order to facilitate some experimentation with timeouts/retries/etc. I decided to temporarily use an xml file which I first generate by writing out the stack to an xml file which we can tweak the settings for subsequent runs. Since every member has a unique protocol stack keeping the edits to a minimum is helpful. (Maybe using property variables would be a better approach for me?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 January 2016