December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1502) Installing the HAL console as a layer doesn't work

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1502?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1502: ----------------------------- Fix Version/s: 9.0.0.Final > Installing the HAL console as a layer doesn't work > -------------------------------------------------- > > Key: WFLY-1502 > URL: https://issues.jboss.org/browse/WFLY-1502 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Fix For: 9.0.0.Final > > > The installation procedure for layered products [1] doesn't work. The updated console ins't pulled in. > [1] https://github.com/hal/release-stream/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3747) build.bat can not run without the administrator on the windows

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3747?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3747: ----------------------------- Fix Version/s: 9.0.0.Final > build.bat can not run without the administrator on the windows > -------------------------------------------------------------- > > Key: WFLY-3747 > URL: https://issues.jboss.org/browse/WFLY-3747 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 9.0.0.Final > > Attachments: 0001-Update-to-bypass-the-execution-policy-on-the-windows.patch > > > we are building the widlfy on the windows and meet the following failure. It looks like the powershell needs the Administrator to run the script. > {noformat} > C:\hudson\workspace\btny-pulls-narayana-windows2008\jboss-as\tools\download-maven.ps1 > cannot be loaded because the execution of scripts is disabled on this > system. Please see "get-help about_signing" for more details. > At line:1 char:2 > + & <<<< tools\download-maven.ps1 > + CategoryInfo : NotSpecified: (:) [], > PSSecurityException > + FullyQualifiedErrorId : RuntimeException > {noformat} > It could be set the execution policy or bypass it. see http://stackoverflow.com/questions/4037939/powershell-execution-of-script... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4293) deprecate :enable :disable operation for (xa)DataSource

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4293?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4293: ----------------------------- Fix Version/s: 9.0.0.Final > deprecate :enable :disable operation for (xa)DataSource > ------------------------------------------------------- > > Key: WFLY-4293 > URL: https://issues.jboss.org/browse/WFLY-4293 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Final > > > Those operations will no more supported in next version of WF. They will stau in MODEL stage to permit domain administration on older version server, but RUNTIME stage will be removed and operation will fail. > Also enabled attribute will be updated to maintain consistent behavior -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3763) move as many as possible of the cli tests from wildfly to wildfly-core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3763?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3763: ----------------------------- Fix Version/s: 9.0.0.Final > move as many as possible of the cli tests from wildfly to wildfly-core > ---------------------------------------------------------------------- > > Key: WFLY-3763 > URL: https://issues.jboss.org/browse/WFLY-3763 > Project: WildFly > Issue Type: Task > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 9.0.0.Final > > > The CLI testsuite really belongs next to the CLI sourcecode. Except those tests that require functionality not available in the core, e.g. data-source related commands, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4208) Migrate Quickstarts to JDK 7

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4208?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4208: ----------------------------- Fix Version/s: 9.0.0.Final > Migrate Quickstarts to JDK 7 > ---------------------------- > > Key: WFLY-4208 > URL: https://issues.jboss.org/browse/WFLY-4208 > Project: WildFly > Issue Type: Sub-task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > WildFly Quickstarts are compatible with JDK 7, but still not fully taking advantage of its new language features. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4728) Undertow no confidential port is available

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4728?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4728: ----------------------------- Fix Version/s: 9.0.0.Final > Undertow no confidential port is available > ------------------------------------------ > > Key: WFLY-4728 > URL: https://issues.jboss.org/browse/WFLY-4728 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR1 > Environment: Java application server: wildfly-9.0.0.CR1 > Java Development Kit (JDK): 1.7.0_04 > OS: Windows 7 (x64) > Reporter: David Zukerman > Assignee: Stuart Douglas > Labels: security, security-constraint, undertow > Fix For: 9.0.0.Final > > > I configured my application's web.xml file to handle all calls through https: > <security-constraint> > <web-resource-collection> > <web-resource-name>All resources</web-resource-name> > <url-pattern>/*</url-pattern> > </web-resource-collection> > <user-data-constraint> > <description>SSL</description> > <transport-guarantee>CONFIDENTIAL</transport-guarantee> > </user-data-constraint> > </security-constraint> > I configured WildFly 9.0.0 CR1 to handle https request on the 443 port: > <socket-binding name="https" port="${jboss.https.port:443}"/> > <security-realm name="UndertowRealm"> > <server-identities> > <ssl> > <keystore path="keystore.jks" relative-to="jboss.server.config.dir" keystore-password="mypassword" alias="server" key-password="mypassword"/> > </ssl> > </server-identities> > </security-realm> > <https-listener name="default-https" socket-binding="https" security-realm="UndertowRealm"/> > If I type on the browser https://localhost/ca/user/1 everything is just fine, but if I type http://localhost/ca/user/1, instead of redirecting to http://localhost/ca/user/1 I get the following error: > 2015-06-03 01:49:28,228 ERROR [io.undertow.request] (default task-1) UT005001: An exception occurred processing the request: java.lang.IllegalStateException: UT010053: No confidential port is available to redirect the current request. > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.getRedirectURI(ServletConfidentialityConstraintHandler.java:80) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:49) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:72) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:274) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:253) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > Please note that this issue doesn't happen over WildFly 8.2 Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4206) jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4206?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4206: ----------------------------- Fix Version/s: 9.0.0.Final > jboss-javaee-7.0-with-resteasy bom exposes JUnit as dependency > -------------------------------------------------------------- > > Key: WFLY-4206 > URL: https://issues.jboss.org/browse/WFLY-4206 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 8.2.0.Final > Reporter: James Bodkin > Assignee: Tomaz Cerar > Priority: Minor > Fix For: 9.0.0.Final > > > The jboss-javaee-7.0-with-resteasy bom includes the JUnit dependency, I believe this should be included with the jboss-javaee-7.0-with-tools bom instead. (It seems to already be included in tools as well) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4134) Java EE 7 Quickstarts

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4134?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4134: ----------------------------- Fix Version/s: 9.0.0.Final > Java EE 7 Quickstarts > --------------------- > > Key: WFLY-4134 > URL: https://issues.jboss.org/browse/WFLY-4134 > Project: WildFly > Issue Type: Task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > WildFly Quickstarts should demo the technologies introduced/updated by Java EE 7. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3651) permissions.xml is not used

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3651?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3651: ----------------------------- Fix Version/s: 9.0.0.Final > permissions.xml is not used > --------------------------- > > Key: WFLY-3651 > URL: https://issues.jboss.org/browse/WFLY-3651 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 8.1.0.Final > Environment: Fedora 20, jdk1.7.0_60 > Reporter: Ondrej Kotek > Assignee: David Lloyd > Priority: Blocker > Fix For: 9.0.0.Final > > Attachments: wfly3651.war > > > With security manager turned on, an application cannot use permissions allowed by permissions.xml configuration -- against EE 7 specification. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2839) Remote Naming communication exception should be thrown on ConnectException

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2839?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2839: ----------------------------- Fix Version/s: 9.0.0.Final > Remote Naming communication exception should be thrown on ConnectException > -------------------------------------------------------------------------- > > Key: WFLY-2839 > URL: https://issues.jboss.org/browse/WFLY-2839 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 8.0.0.CR1 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 9.0.0.Final > > > Remote Naming communication exception should be thrown on ConnectException, a remoting bug fix showed that a ConnectException can be thrown to remoting and we should throw this as a CommunicationException instead of generic NamingException. This is related to WFLY-2198 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017