November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5621) Cleanup HornetQ xsd files in "docs/schema" directory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5621?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5621: ---------------------------------------- -jboss-as-messaging_x_y.xsd (server configuration files, replaced by "wildfly-messaging-activemq_1_0.xsd"). This schema is still usable, both in a domain where some slaves can be running earlier releases, and to launch a standalone server in --admin-only mode and then use the migrate op. If the a - jmx.xml using jboss-as-messaging-deployment_1_0.xsd doesn't work any more, I agree it should be dropped. > Cleanup HornetQ xsd files in "docs/schema" directory > ---------------------------------------------------- > > Key: WFLY-5621 > URL: https://issues.jboss.org/browse/WFLY-5621 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR4 > Reporter: Wolfgang Knauf > Assignee: Jason Greene > Priority: Minor > > The download zip for WildFly 10.0CR4 contains the xsd files for HornetQ messaging configurations in "docs/schema". Those are obsoleted by ActiveMQ and should be removed. > -jboss-as-messaging-deployment_1_0.xsd (deployment of a "-jms.xml" file according to this old schema will fail with an error anyway), replaced by "wildfly-messaging-activemq-deployment_1_0.xsd") > -jboss-as-messaging_x_y.xsd (server configuration files, replaced by "wildfly-messaging-activemq_1_0.xsd"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5621) Cleanup HornetQ xsd files in "docs/schema" directory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5621?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5621: ----------------------------------- Component/s: JMS (was: Server) > Cleanup HornetQ xsd files in "docs/schema" directory > ---------------------------------------------------- > > Key: WFLY-5621 > URL: https://issues.jboss.org/browse/WFLY-5621 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Wolfgang Knauf > Assignee: Jason Greene > Priority: Minor > > The download zip for WildFly 10.0CR4 contains the xsd files for HornetQ messaging configurations in "docs/schema". Those are obsoleted by ActiveMQ and should be removed. > -jboss-as-messaging-deployment_1_0.xsd (deployment of a "-jms.xml" file according to this old schema will fail with an error anyway), replaced by "wildfly-messaging-activemq-deployment_1_0.xsd") > -jboss-as-messaging_x_y.xsd (server configuration files, replaced by "wildfly-messaging-activemq_1_0.xsd"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5621) Cleanup HornetQ xsd files in "docs/schema" directory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5621?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5621: -------------------------------------- Assignee: Jeff Mesnil (was: Jason Greene) > Cleanup HornetQ xsd files in "docs/schema" directory > ---------------------------------------------------- > > Key: WFLY-5621 > URL: https://issues.jboss.org/browse/WFLY-5621 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Wolfgang Knauf > Assignee: Jeff Mesnil > Priority: Minor > > The download zip for WildFly 10.0CR4 contains the xsd files for HornetQ messaging configurations in "docs/schema". Those are obsoleted by ActiveMQ and should be removed. > -jboss-as-messaging-deployment_1_0.xsd (deployment of a "-jms.xml" file according to this old schema will fail with an error anyway), replaced by "wildfly-messaging-activemq-deployment_1_0.xsd") > -jboss-as-messaging_x_y.xsd (server configuration files, replaced by "wildfly-messaging-activemq_1_0.xsd"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5651) Validation errors in "jboss-web_10_0.xsd"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5651?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5651: ----------------------------------- Component/s: Web (JBoss Web) (was: Server) > Validation errors in "jboss-web_10_0.xsd" > ----------------------------------------- > > Key: WFLY-5651 > URL: https://issues.jboss.org/browse/WFLY-5651 > Project: WildFly > Issue Type: Bug > Components: Web (JBoss Web) > Affects Versions: 10.0.0.CR4 > Reporter: Wolfgang Knauf > Assignee: Jason Greene > Attachments: jboss-common_10_0.xsd, jboss-web_10_0.xsd, validationerrors.png > > > When creating an instance of this XSD file, Eclipse cannot validate the XSD file. > Attached is a screenshot of all errors. Sorry for the screenshot, but Eclipse does not allow copying of error messages from the "validation errors in included xsd file" window. > I assume the errors are caused mainly by this problem: > a) "jboss-web_10_0.xsd" declares the namespace "xmlns:jboss="http://www.jboss.com/xml/ns/javaee" ", but it does not include/import any file where those common things are declared. I assume it references "jboss-common_6_0.xsd"? See "jboss-web_7_0.xsd", where the common file is included. > b) if this is true, the next problem is that there is a namespace mismatch: jboss-common_6_0.xsd declares this: xmlns:javaee="http://java.sun.com/xml/ns/javaee" > But "jboss-web_10_0.xsd" declares xmlns:javaee="http://xmlns.jcp.org/xml/ns/javaee" > Probably it should be the same namespace in both files? > So a new "jboss-common_10_0.xsd" would be needed, which also imports "javaee_7.xsd" instead of "javaee_6.xsd". > Attached are "jboss-web_10_0.xsd" and "jboss-common_10_0.xsd" files which don't contain the namespace mismatch errors any more. But I don't know whether they are correct and would work when wildfly validates a xml file with this schema. > My files still contain one last error (don't know how to fix it): > src-ct.2.1: Complex Type Definition Representation Error for type 'symbolic-linked-allowedType'. When <simpleContent> is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'boolean' satisfies none of these conditions. > in jboss-web_10_0.xsd, line 313 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5650) Cancel button in JConsole do nothing

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5650?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5650: ---------------------------------------- Please open issue in the correct project. > Cancel button in JConsole do nothing > ------------------------------------ > > Key: WFLY-5650 > URL: https://issues.jboss.org/browse/WFLY-5650 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Cancel button in JConsole do nothing. It should be removed from JConsole > *How reproducible:* > Always > *Steps to Reproduce:* > # cd EAP_HOME > # ./bin/standalone.sh & > # ./bin/jconsole.sh > # Click to CLI tab > # Click to "Cancel" button -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5650) Cancel button in JConsole do nothing

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5650?page=com.atlassian.jira.plugin.... ] Brian Stansberry edited comment on WFLY-5650 at 11/19/15 9:03 PM: ------------------------------------------------------------------ Please open issues in the correct project. was (Author: brian.stansberry): Please open issue in the correct project. > Cancel button in JConsole do nothing > ------------------------------------ > > Key: WFLY-5650 > URL: https://issues.jboss.org/browse/WFLY-5650 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Cancel button in JConsole do nothing. It should be removed from JConsole > *How reproducible:* > Always > *Steps to Reproduce:* > # cd EAP_HOME > # ./bin/standalone.sh & > # ./bin/jconsole.sh > # Click to CLI tab > # Click to "Cancel" button -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1143) Cancel button in JConsole do nothing

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1143?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-5650 to WFCORE-1143: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1143 (was: WFLY-5650) Component/s: CLI (was: CLI) Affects Version/s: 2.0.0.Final (was: 10.0.0.CR4) > Cancel button in JConsole do nothing > ------------------------------------ > > Key: WFCORE-1143 > URL: https://issues.jboss.org/browse/WFCORE-1143 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Final > Reporter: Marek Kopecký > Assignee: Tomaz Cerar > > *Description of problem:* > Cancel button in JConsole do nothing. It should be removed from JConsole > *How reproducible:* > Always > *Steps to Reproduce:* > # cd EAP_HOME > # ./bin/standalone.sh & > # ./bin/jconsole.sh > # Click to CLI tab > # Click to "Cancel" button -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5673) Equals signs in cookies configuration is not working in Domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5673?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5673: ----------------------------------- Component/s: Domain Management Web (Undertow) > Equals signs in cookies configuration is not working in Domain mode > ------------------------------------------------------------------- > > Key: WFLY-5673 > URL: https://issues.jboss.org/browse/WFLY-5673 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Web (Undertow) > Reporter: Boominathan Shanmugam > Assignee: Jason Greene > > The property that allows WILDFLY 8.1 in standalone mode to have = in cookie values > <subsystem xmlns="urn:jboss:domain:undertow:1.1"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http" allow-equals-in-cookie-value="true"/> > The issue we are seeing is that setting that to true, via CLI, in domain mode does not make the code behave the same way as it does in standalone. Could be that there are more changes required in domain mode than just setting this setting, but I could not find anything. Could also be that caching is somehow not letting the new value in, tho I did restart the entire system, including the DC (even deleted the /tmp folder on both nodes and on DC). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5673) Equals signs in cookies configuration is not working in Domain mode

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5673?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5673: -------------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > Equals signs in cookies configuration is not working in Domain mode > ------------------------------------------------------------------- > > Key: WFLY-5673 > URL: https://issues.jboss.org/browse/WFLY-5673 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Web (Undertow) > Reporter: Boominathan Shanmugam > Assignee: Tomaz Cerar > > The property that allows WILDFLY 8.1 in standalone mode to have = in cookie values > <subsystem xmlns="urn:jboss:domain:undertow:1.1"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http" allow-equals-in-cookie-value="true"/> > The issue we are seeing is that setting that to true, via CLI, in domain mode does not make the code behave the same way as it does in standalone. Could be that there are more changes required in domain mode than just setting this setting, but I could not find anything. Could also be that caching is somehow not letting the new value in, tho I did restart the entire system, including the DC (even deleted the /tmp folder on both nodes and on DC). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-889) Kerberos authentication for Management CLI should fallback when server principal is set incorrectly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-889?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-889: ------------------------------------ Fix Version/s: (was: 3.0.0.Alpha1) > Kerberos authentication for Management CLI should fallback when server principal is set incorrectly > --------------------------------------------------------------------------------------------------- > > Key: WFCORE-889 > URL: https://issues.jboss.org/browse/WFCORE-889 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 2.0.3.Final > > > In case when kerberos authentication is configured in security realm but principal attribute in keytab element is set incorrectly (e.g. remote/wrong_localhost(a)JBOSS.ORG, remote/localhost(a)WRONG_JBOSS.ORG or wrong_remote/localhost(a)JBOSS.ORG instead of remote/localhost(a)JBOSS.ORG) then authentication does not fallback into another authentication mechanism for user with valid kerberos ticket. In case when user does not have kerberos ticket then fallback is taken into account correctly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015