February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4308) Proxies created via ContextService.createContextualProxy(...) are not Serializable

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-4308: ---------------------------------- Summary: Proxies created via ContextService.createContextualProxy(...) are not Serializable Key: WFLY-4308 URL: https://issues.jboss.org/browse/WFLY-4308 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 9.0.0.Alpha1 Reporter: Paul Ferraro Assignee: David Lloyd Priority: Critical Setting priority to critical since this is a matter of compliance with the concurrency utilities specification. Section 3.3.4 of the specification states that: "All invocation handlers for the contextual proxy implementation must implement java.io.Serializable." While the invocation handler does indeed implement Serializable, it contains a reference to org.jboss.as.server.moduleservice.ServiceModuleLoader, which is not serializable, thus the invocation handler cannot be serialized. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4307) Update to console 2.6.0.Final

by Heiko Braun (JIRA)

Heiko Braun created WFLY-4307: --------------------------------- Summary: Update to console 2.6.0.Final Key: WFLY-4307 URL: https://issues.jboss.org/browse/WFLY-4307 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4304) Servlet authentication kicked off when *not* a part of any security-constraint

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-4304?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-4304: ----------------------------------- Priority: Major (was: Critical) > Servlet authentication kicked off when *not* a part of any security-constraint > ------------------------------------------------------------------------------ > > Key: WFLY-4304 > URL: https://issues.jboss.org/browse/WFLY-4304 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Brett Meyer > Assignee: Darran Lofthouse > > Artificer runs on Wildfly 8.2 and uses Keycloak for auth. If our WAR contains a servlet that is *not* protected by a security-constraint in web.xml, Wildfly still attempts to authenticate the call (using Wireshark, I see the GET/POST get funneled through the Keycloak realm redirection) if basic auth credentials are in the header. In a keycloak-dev thread this past Dec., [~bill.burke] suggested this was most likely an issue within Wildfly auth itself. > A credentialed call on an un-protected servlet does sound like an edge case. However, this came up possibly due to a secondary symptom: > If I protect the servlet in web.xml, the call's Authorization header is stripped. I'm not currently able to figure out exactly where that's occurring... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4304) Servlet authentication kicked off when *not* a part of any security-constraint

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-4304?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-4304: -------------------------------------- Assignee: Darran Lofthouse (was: Jason Greene) > Servlet authentication kicked off when *not* a part of any security-constraint > ------------------------------------------------------------------------------ > > Key: WFLY-4304 > URL: https://issues.jboss.org/browse/WFLY-4304 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Reporter: Brett Meyer > Assignee: Darran Lofthouse > Priority: Critical > > Artificer runs on Wildfly 8.2 and uses Keycloak for auth. If our WAR contains a servlet that is *not* protected by a security-constraint in web.xml, Wildfly still attempts to authenticate the call (using Wireshark, I see the GET/POST get funneled through the Keycloak realm redirection) if basic auth credentials are in the header. In a keycloak-dev thread this past Dec., [~bill.burke] suggested this was most likely an issue within Wildfly auth itself. > A credentialed call on an un-protected servlet does sound like an edge case. However, this came up possibly due to a secondary symptom: > If I protect the servlet in web.xml, the call's Authorization header is stripped. I'm not currently able to figure out exactly where that's occurring... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4306) IIOP Subsystem: Attribute groups refactor

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFLY-4306: ------------------------------------ Summary: IIOP Subsystem: Attribute groups refactor Key: WFLY-4306 URL: https://issues.jboss.org/browse/WFLY-4306 Project: WildFly Issue Type: Enhancement Components: IIOP Reporter: Tomasz Adamski Assignee: Tomasz Adamski -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Yacine Jaber (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Yacine Jaber commented on DROOLS-702: ------------------------------------- I think the first one(from) is more secure. Cause "==" depends on hash & equals. It could change the behavior if these methods are extended. Thank you for your help. I close this issue. > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-702) Rule Inheritance fired the sub rule even the condition doen't match

by Yacine Jaber (JIRA)

[ https://issues.jboss.org/browse/DROOLS-702?page=com.atlassian.jira.plugin... ] Yacine Jaber closed DROOLS-702. ------------------------------- > Rule Inheritance fired the sub rule even the condition doen't match > ------------------------------------------------------------------- > > Key: DROOLS-702 > URL: https://issues.jboss.org/browse/DROOLS-702 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Environment: Windows, Java6.0.29 > Reporter: Yacine Jaber > Assignee: Davide Sottara > Priority: Critical > Attachments: wod-drools-test.7z > > > You can find the attached a simple maven project that shows this error. > You can run ExampleDrools class as main java application. > The sub rules are fired even if the condition is not matched. > There are a work arround by using <from $fact> into a sub rule to avoid firing this one. > This simple project shows the failed and work arround test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3880) Resource Adapters not visible in web console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3880?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3880: ----------------------------------------------- Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1144888|https://bugzilla.redhat.com/show_bug.cgi?id=1144888] from ON_QA to ASSIGNED > Resource Adapters not visible in web console > --------------------------------------------- > > Key: WFLY-3880 > URL: https://issues.jboss.org/browse/WFLY-3880 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.0.0.Final > Reporter: Van Halbert > Assignee: Heiko Braun > Attachments: Screenshot from 2014-08-26 17_20_50.png > > > In Web Console, in Configuration > Connectors > Resource Adapters, the names of the Resource Adapters (column Archive) are empty. Also, after clicking View> in any of the rows, always the same Connection Definitions are shown (most likely those belonging to the first resource adapter in the list). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4305) Script rumbles on after error

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-4305?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-4305: -------------------------------- Issue Type: Bug (was: Feature Request) > Script rumbles on after error > ----------------------------- > > Key: WFLY-4305 > URL: https://issues.jboss.org/browse/WFLY-4305 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > > After a failure in the script it rumbles on. > {noformat} > (master) carlo@devel01:~/work/wildfly$ ./build.sh clean > ./tools/download-maven.sh: 20: ./tools/download-maven.sh: curl: not found > Archive: maven.zip > End-of-central-directory signature not found. Either this file is not > a zipfile, or it constitutes one disk of a multi-part archive. In the > latter case the central directory and zipfile comment will be found on > the last disk(s) of this archive. > unzip: cannot find zipfile directory in one of maven.zip or > maven.zip.zip, and cannot find maven.zip.ZIP, period. > mv: cannot stat ‘apache-maven*’: No such file or directory > build.sh: Could not locate Maven; check $MVN or $MAVEN_HOME. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4229) Make http status return while deploying configurable

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4229?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4229: ------------------------------ Summary: Make http status return while deploying configurable (was: Make http status return whily deploying configurable) > Make http status return while deploying configurable > ---------------------------------------------------- > > Key: WFLY-4229 > URL: https://issues.jboss.org/browse/WFLY-4229 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Tomaz Cerar > Assignee: Bartosz Baranowski > > For deployment behind proxies it would be more than welcome to have server return 503 instead of 404 while application is deploying. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 2015