December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-279) Upgrade to JBoss Remoting after 4.0.5.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-279?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-279: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Upgrade to JBoss Remoting after 4.0.5.Final > ------------------------------------------- > > Key: WFCORE-279 > URL: https://issues.jboss.org/browse/WFCORE-279 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Remoting > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-278) Revisit error message for an authentication failure.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-278?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-278: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Revisit error message for an authentication failure. > ---------------------------------------------------- > > Key: WFCORE-278 > URL: https://issues.jboss.org/browse/WFCORE-278 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha16 > > > After authentication fails in the CLI the following error message is output: - > {code} > Unable to authenticate against controller at localhost:9990: Authentication failed: the server presented no authentication mechanisms > {code} > This text is a bit misleading, what it actually means is all mechanisms presented have either been excluded or attempted and now no further mechanisms are available to try. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-240) We need something similar to StandardConfigsXMLValidationUnitTestCase in Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-240?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-240: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > We need something similar to StandardConfigsXMLValidationUnitTestCase in Core > ----------------------------------------------------------------------------- > > Key: WFCORE-240 > URL: https://issues.jboss.org/browse/WFCORE-240 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Fix For: 1.0.0.Alpha16 > > > One feature of this test is that it validates that schemas are correct according to the schema schema, presently we only find out about errors in schemas when the wildfly testsuite is executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-137: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-129: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha16 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-107) Update whoami operation to return authentication mechanism where verbose=true

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-107?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-107: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > Update whoami operation to return authentication mechanism where verbose=true > ----------------------------------------------------------------------------- > > Key: WFCORE-107 > URL: https://issues.jboss.org/browse/WFCORE-107 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha16 > > > The admin console currently contains a "logout" handler that follows a round of HTTP message exchanges to trick the web browser into forgetting the credentials it has cached. > This only makes sense where the browser has cached a credential - if we return the authentication mechanism then the console can make a better decision regarding displaying the logout link or could change the implementation so display a message to the user explaining why logout does not make sense. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-461) TestSuiteEnvironment should use privileged access to properties

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-461?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-461: ------------------------------------ Fix Version/s: 1.0.0.Alpha16 (was: 1.0.0.Alpha15) > TestSuiteEnvironment should use privileged access to properties > --------------------------------------------------------------- > > Key: WFCORE-461 > URL: https://issues.jboss.org/browse/WFCORE-461 > Project: WildFly Core > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha16 > > > The current TestSuiteEnvironment uses lots of {{System.getProperty()}} which fail under a security manager. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4196) HTTP protocol violation

by Nicolas Cazottes (JIRA)

[ https://issues.jboss.org/browse/WFLY-4196?page=com.atlassian.jira.plugin.... ] Nicolas Cazottes commented on WFLY-4196: ---------------------------------------- Hi, I confirm after adding this configuration that the default gzip filter in undertow works correctly without any problem. Neverless, my need is to handle it in the application and not globally in the server. For the different ideas, as it works correctly in previous versions of Jboss (EAP 6, EAP 5 and EAP 4) with the same WAR, I think, you should perhaps look at how it is managed in these versions (I suppose in tomcat) to set a similar strategy. I think for example, a strategy could be to detect that under a defined content size (for example 64kb), undertow bufferize and set the content-length after the filter processing. If more than 64kb content is detected, switch to chunked encoding which is justified. To complete my case, my application serves small files like in the given sample war but also big text files of 25Mb which compress in a few Mb transparently through this gzip filter. This problem seems not to be specific to gzip compression. Imagine a filter that does pre or post processing of files (js or css server side includes for example), the problem would be the same. From what I have seen with my application, for jquery.js file, if the browser does not have the correct Content-Length size, the file is not correctly interpreted. > HTTP protocol violation > ----------------------- > > Key: WFLY-4196 > URL: https://issues.jboss.org/browse/WFLY-4196 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final, 8.2.0.Final > Reporter: Nicolas Cazottes > Assignee: Stuart Douglas > Priority: Blocker > Attachments: bug-wildfly-gzip-war-1.0.0-SNAPSHOT.war, fiddler_protocol_violation.jpg > > > If you deploy the given war in wildfly and open this url http://localhost:8080/bug/images/download.png : it seems to work correctly but if you run it with fiddler2 active, fiddler reports a protocol violation on the Content-Length header value. > Actually, If the content is some js or css, the browser does not correctly reads it and the web page is corrupted. > The explanation is that the web application uses a filter to compress the content in gzip format. > For information, this application works correctly with jboss as 7 or before (that embed tomcat). I discovered the problem while trying to upgrade my application. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3488) Add the implementation version to the manifest file of the JSF impl jar

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-3488?page=com.atlassian.jira.plugin.... ] Farah Juma resolved WFLY-3488. ------------------------------ Fix Version/s: 9.0.0.Beta1 Resolution: Done > Add the implementation version to the manifest file of the JSF impl jar > ----------------------------------------------------------------------- > > Key: WFLY-3488 > URL: https://issues.jboss.org/browse/WFLY-3488 > Project: WildFly > Issue Type: Feature Request > Components: JSF > Reporter: Brian Leathem > Assignee: Farah Juma > Fix For: 9.0.0.Beta1 > > > Currently it is not possible to retrieve the JSF implementation version in wildfly using the {{java.lang.Package}} API. To enable this, the build of the JSF implementation needs to include the implementation version in the manifest file of the jar, as per: > http://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-486?page=com.atlassian.jira.plugin... ] Alexey Loubyansky commented on WFCORE-486: ------------------------------------------ Just a note, the commit in the PR is using CLIExpressionResolver class introduced by the changes in WFCORE-453. > cli echo command should not output the result in columns > -------------------------------------------------------- > > Key: WFCORE-486 > URL: https://issues.jboss.org/browse/WFCORE-486 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Alpha15 > > > Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 6 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 December 2014