December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2097) Upgrade to WildFly Elytron 1.1.0.Beta17

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2097?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2097: ------------------------------------- Fix Version/s: 3.0.0.Alpha16 (was: 3.0.0.Alpha15) > Upgrade to WildFly Elytron 1.1.0.Beta17 > --------------------------------------- > > Key: WFCORE-2097 > URL: https://issues.jboss.org/browse/WFCORE-2097 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha16 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-828) Make PeerIdentityContext#setPeerIdentity protected

by Farah Juma (JIRA)

Farah Juma created ELY-828: ------------------------------ Summary: Make PeerIdentityContext#setPeerIdentity protected Key: ELY-828 URL: https://issues.jboss.org/browse/ELY-828 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Farah Juma Assignee: Farah Juma This will allow subclasses of PeerIdentityContext to be able to initialize the currently set peer identity. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4539) logging statement to trace remoting heartbeat

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFLY-4539?page=com.atlassian.jira.plugin.... ] Peter Palaga commented on WFLY-4539: ------------------------------------ I cloned to REM3-255 and sent a PR https://github.com/jboss-remoting/jboss-remoting/pull/91 > logging statement to trace remoting heartbeat > --------------------------------------------- > > Key: WFLY-4539 > URL: https://issues.jboss.org/browse/WFLY-4539 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: Carsten Lichy-Bittendorf > Assignee: Peter Palaga > Priority: Minor > > you can set the heartbeat on a remoting connection by setting: > remote.connection.default.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL > What is missing is the option to log on the client when the heartbeat message is fired. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7777) logging statement to trace remoting heartbeat

by Peter Palaga (JIRA)

Peter Palaga created WFLY-7777: ---------------------------------- Summary: logging statement to trace remoting heartbeat Key: WFLY-7777 URL: https://issues.jboss.org/browse/WFLY-7777 Project: WildFly Issue Type: Enhancement Components: EJB Affects Versions: JBoss AS7 7.2.0.Final Reporter: Peter Palaga Assignee: Peter Palaga Priority: Minor you can set the heartbeat on a remoting connection by setting: remote.connection.default.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL What is missing is the option to log on the client when the heartbeat message is fired. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2102) HC is unaware when managed server's MSC is unstable

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2102: ---------------------------------------- Summary: HC is unaware when managed server's MSC is unstable Key: WFCORE-2102 URL: https://issues.jboss.org/browse/WFCORE-2102 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.0.Alpha15 The HC should be aware if a managed server has a service container that cannot stabilize. What it will do with this information can evolve over time, but it should at least log it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2102) HC is unaware when managed server's MSC is unstable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2102?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2102: ------------------------------------- Fix Version/s: (was: 3.0.0.Alpha15) > HC is unaware when managed server's MSC is unstable > --------------------------------------------------- > > Key: WFCORE-2102 > URL: https://issues.jboss.org/browse/WFCORE-2102 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The HC should be aware if a managed server has a service container that cannot stabilize. > What it will do with this information can evolve over time, but it should at least log it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-398?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBMETA-398: ------------------------------------------- Bugzilla Update: Perform > The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse > ------------------------------------------------------------------------- > > Key: JBMETA-398 > URL: https://issues.jboss.org/browse/JBMETA-398 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.2.0.Final > Reporter: Radovan Netuka > Assignee: Radovan Netuka > > The jboss-web_7_2.xsd file cause validation errors in eclipse. > The following error from line 261: > 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 > This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-398?page=com.atlassian.jira.plugin... ] Radovan Netuka updated JBMETA-398: ---------------------------------- Description: The jboss-web_7_2.xsd file cause validation errors in eclipse. The following error from line 261: 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 This also happens in jboss-web_7_1.xsd was: The jboss-web_7_2.xsd file cause validation errors in eclipse. The following error from line 261: 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 This also happens in jboss-web_7_1.xsd > The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse > ------------------------------------------------------------------------- > > Key: JBMETA-398 > URL: https://issues.jboss.org/browse/JBMETA-398 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.2.0.Final > Reporter: Radovan Netuka > Assignee: Radovan Netuka > > The jboss-web_7_2.xsd file cause validation errors in eclipse. > The following error from line 261: > 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 > This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-398?page=com.atlassian.jira.plugin... ] Radovan Netuka updated JBMETA-398: ---------------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/108 > The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse > ------------------------------------------------------------------------- > > Key: JBMETA-398 > URL: https://issues.jboss.org/browse/JBMETA-398 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.2.0.Final > Reporter: Radovan Netuka > Assignee: Radovan Netuka > > The jboss-web_7_2.xsd file cause validation errors in eclipse. > The following error from line 261: > 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 > This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-398) The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-398?page=com.atlassian.jira.plugin... ] Radovan Netuka commented on JBMETA-398: --------------------------------------- PR: https://github.com/jboss/metadata/pull/108 > The jboss-web_7_1.xsd and 7.2.xsd file cause validation errors in Eclipse > ------------------------------------------------------------------------- > > Key: JBMETA-398 > URL: https://issues.jboss.org/browse/JBMETA-398 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 7.2.0.Final > Reporter: Radovan Netuka > Assignee: Radovan Netuka > > The jboss-web_7_2.xsd file cause validation errors in eclipse. > The following error from line 261: > 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 > This also happens in jboss-web_7_1.xsd -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016