March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3098) Complete Undertow to JAAS Digest Integration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3098?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3098: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Complete Undertow to JAAS Digest Integration > -------------------------------------------- > > Key: WFLY-3098 > URL: https://issues.jboss.org/browse/WFLY-3098 > Project: WildFly > Issue Type: Enhancement > Components: Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3075) add supplement to socket-bindings in template assembly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3075?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3075: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > add supplement to socket-bindings in template assembly > ------------------------------------------------------ > > Key: WFLY-3075 > URL: https://issues.jboss.org/browse/WFLY-3075 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > The messaging.xml subsystem configuration defines a "ha" supplement used to build the standalone-full-ha.xml. > This supplement requires to have a socket-binding for multicast: > {noformat} > <socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/> > {noformat} > However, this socket-binding is *always* added even when the "ha" supplement is not used. > We end up with a standalone-full.xml configuration with the regular messaging subsystem (no ha parts) *and* the messaging-group socket binding. > Ideally, this socket-binding should only be added when the ha supplement is used. > One way to achieve this would be to allow <socket-binding> definitions inside the <supplement>/<replacement> elements. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3064) Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3064?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3064: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-3064 > URL: https://issues.jboss.org/browse/WFLY-3064 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > A new test case was added under WFLY-3063 that demonstrates the correct way to do this so now remove the original way that depended on internal APIs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3167) Allow the SASL protocol to be specified for Remoting

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3167?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3167: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Allow the SASL protocol to be specified for Remoting > ---------------------------------------------------- > > Key: WFLY-3167 > URL: https://issues.jboss.org/browse/WFLY-3167 > Project: WildFly > Issue Type: Task > Components: Domain Management, Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > The SASL protocol can now be overridden within Remoting, this is very useful for cases such as GSSAPI where the Kerberos ticket request takes this into account. > There is a slight drawback in that mechanisms like Digest require both sides of the connection to be in synch but the mechanism has also been enhanced to allow a comma separated list of acceptable protocols to be supplied to alleviate this, -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3188) Optimize use of Infinispan listeners

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3188?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3188: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Optimize use of Infinispan listeners > ------------------------------------ > > Key: WFLY-3188 > URL: https://issues.jboss.org/browse/WFLY-3188 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > Typically, when we use an Infinispan cache listener, we only need it to be invoked on one node in the cluster. Infinispan 6/7 have added several mechanisms to filter when listeners are invoked. For example, we can leverage @Listener(primaryOnly = true) in many places. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3224) SSL The Last Round

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3224?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3224: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > SSL The Last Round > ------------------ > > Key: WFLY-3224 > URL: https://issues.jboss.org/browse/WFLY-3224 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > I could probably list most components in the components box, anyway this is a top level task to contain all of the SSL enhancements required so that they can be addressed once and for all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3248: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 9.0.0.CR1 > > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3291) Pass Jandex CompositeIndex into Hibernate 5.x

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3291?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3291: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Pass Jandex CompositeIndex into Hibernate 5.x > ---------------------------------------------- > > Key: WFLY-3291 > URL: https://issues.jboss.org/browse/WFLY-3291 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.CR1 > > > 1. When creating the persistence unit for Hibernate 5.x, pass a Jandex composite index via: > integrationMap.put( "hibernate.jandex_index", CompositeIndex.create( pu.getAnnotationIndex().values() ). > 2. Also change from: > integerationMap.put( "hibernate.ejb.resource_scanner", HibernateArchiveScanner.class ) > To: > integrationMap.put( "hibernate.jpa.scanner_archive_delegate", VirtualFileSystemArchiveDescriptorFactory.INSTANCE ) > This may turn out to be a Jipajapa only change. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3334) Event with qualifier @Initialized not raised if no webapp is deployed

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3334?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3334: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Event with qualifier @Initialized not raised if no webapp is deployed > --------------------------------------------------------------------- > > Key: WFLY-3334 > URL: https://issues.jboss.org/browse/WFLY-3334 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.1.0.CR1 > Environment: Wildfly 8.0.0.Final, OpenJDK 1.7.0_45 > Reporter: Daniel Lechner > Assignee: Jozef Hartinger > Fix For: 9.0.0.CR1 > > > As stated in the CDI-specification (section 6.7.3. Application context lifecycle) > {quote} > An event with qualifier @Initialized(ApplicationScoped.class) is fired when the application context is initialized and an event with qualifier @Destroyed(ApplicationScoped.class) is fired when the application is destroyed. > {quote} > But in my environment this is only true, if the deployed application (packaged in an EAR) contains a webapplication (as WAR inside the EAR). If there is no webapplication, the event is not raised and observer-methods are not called at all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3434) Add xsd schemas on wildlfy.org

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3434?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3434: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 9.0.0.Beta1) > Add xsd schemas on wildlfy.org > ------------------------------ > > Key: WFLY-3434 > URL: https://issues.jboss.org/browse/WFLY-3434 > Project: WildFly > Issue Type: Feature Request > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR1 > > > we should have all wildfly releated schemas to wildfly.org/schema. > As part of this task, we need to update all docs to point to new URL. > have as much automated as possible process for uploading new schemas when new releases is done. > consolidate this over various (sub)projects that provide schemas that should be here. > What is not expected to be done is to host all old schemas that have nothing do do with WildFly on new location. > Example are most of pre AS7 jboss specific descriptors that WildFly no longer honors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015