June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1608) Add back support for maxEmptyLife in clustered SSO.

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-1608: ---------------------------------- Summary: Add back support for maxEmptyLife in clustered SSO. Key: WFLY-1608 URL: https://issues.jboss.org/browse/WFLY-1608 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.0.0.Alpha2 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha3 The new clustered SSO implementation removes empty SSOs automatically. Instead, the SSO credentials should remain valid for the period specified by maxEmptyLife. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1607) Upgrade JGroups to 3.3.2.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-1607: ---------------------------------- Summary: Upgrade JGroups to 3.3.2.Final Key: WFLY-1607 URL: https://issues.jboss.org/browse/WFLY-1607 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 8.0.0.Alpha2 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1606) Publicly export wildfly-clustering-api

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-1606?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-1606: ------------------------------- Description: The goal is to create a single publicly exported clustering module, with a refined, stable public API. The current wildfly-clustering-api module is too cluttered. Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate. As part of this, we will also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. The distributed lock manager components are obsolete. was: The goal is to create a single publicly exported clustering module, with a refined, stable public API. The current wildfly-clustering-api module is too cluttered. Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate. We should also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. > Publicly export wildfly-clustering-api > -------------------------------------- > > Key: WFLY-1606 > URL: https://issues.jboss.org/browse/WFLY-1606 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Alpha2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha3 > > > The goal is to create a single publicly exported clustering module, with a refined, stable public API. > The current wildfly-clustering-api module is too cluttered. > Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate. > As part of this, we will also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. The distributed lock manager components are obsolete. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1606) Publicly export wildfly-clustering-api

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-1606?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-1606: ------------------------------- Summary: Publicly export wildfly-clustering-api (was: Refactor wildfly-clustering-api/wildfly-clustering-impl modules) > Publicly export wildfly-clustering-api > -------------------------------------- > > Key: WFLY-1606 > URL: https://issues.jboss.org/browse/WFLY-1606 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 8.0.0.Alpha2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha3 > > > The goal is to create a single publicly exported clustering module, with a refined, stable public API. > The current wildfly-clustering-api module is too cluttered. > Once the api module is cleaned up, we can merge it with the current wildfly-clustering-annotations module - which does not need to be separate. > We should also clean up the wildfly-clustering-impl module. CoreGroupCommunicationService needs to be overhauled, and split into smaller, light-weight components. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-366) Update Java EE 7 schemas to the final releases

by Eduardo Martins (JIRA)

Eduardo Martins created JBMETA-366: -------------------------------------- Summary: Update Java EE 7 schemas to the final releases Key: JBMETA-366 URL: https://issues.jboss.org/browse/JBMETA-366 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: client, common, ear, ejb, rar, web Reporter: Eduardo Martins Assignee: Eduardo Martins The final release of the Java EE 7 schemas have changes with respect the ones currently in the Metadata project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1381) OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-1381?page=com.atlassian.jira.plugin.... ] Igor Shulika commented on WFLY-1381: ------------------------------------ The future WildFly (8.0.0) and JBoss EAP (7.0) releases will not support OSGi - is this correct? > OSGi: "Web-ContextPath" header is not supported to install/start WAB bundle from repository > ------------------------------------------------------------------------------------------- > > Key: WFLY-1381 > URL: https://issues.jboss.org/browse/WFLY-1381 > Project: WildFly > Issue Type: Bug > Components: OSGi > Affects Versions: 8.0.0.Alpha2 > Reporter: Igor Shulika > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The WAB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.sample.webapp:my-sample-webapp:1.0" startlevel="4"/> > > Note: When I just simply drop my WAB file inside "deployments" directory the web application starting successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1382) OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-1382?page=com.atlassian.jira.plugin.... ] Igor Shulika commented on WFLY-1382: ------------------------------------ The future WildFly (8.0.0) and JBoss EAP (7.0) releases will not support OSGi - is this correct? > OSGi: "Export-EJB" header is not supported to install/start EJB3 bundle from repository > --------------------------------------------------------------------------------------- > > Key: WFLY-1382 > URL: https://issues.jboss.org/browse/WFLY-1382 > Project: WildFly > Issue Type: Bug > Components: OSGi > Affects Versions: 8.0.0.Alpha2 > Reporter: Igor Shulika > > I am using the latest WildFly 8.0.0.Alpha2-SNAPSHOT server to install/start all of my OSGi bundles from Maven repository. The EJB 3 MDB is not starting if I am just declare capability in the standalone-osgi.xml file. > > Here is my capability configuration. > <capability name="org.test.ejb3.mdb:ejb-high-velocity-queue-mdb:1.0" startlevel="4"/> > > Note: When I just simply drop my EJB 3 MDB JAR file inside "deployments" directory the message driven bean starting successfully (see below). > INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'HighVelocityQueueMessageBean' with 'hornetq-ra' resource adapter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by Jess Sightler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1594?page=com.atlassian.jira.plugin.... ] Jess Sightler reassigned WFLY-1594: ----------------------------------- Assignee: Jess Sightler (was: Darran Lofthouse) > Domain Management logout 'feature' not working for HTTP BASIC authentication. > ----------------------------------------------------------------------------- > > Key: WFLY-1594 > URL: https://issues.jboss.org/browse/WFLY-1594 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Jess Sightler > Fix For: 8.0.0.Alpha3 > > > The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1594?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1594: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> made a comment on [bug 976917|https://bugzilla.redhat.com/show_bug.cgi?id=976917] Sure, feel free to take both issues and I can review what you have. > Domain Management logout 'feature' not working for HTTP BASIC authentication. > ----------------------------------------------------------------------------- > > Key: WFLY-1594 > URL: https://issues.jboss.org/browse/WFLY-1594 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha3 > > > The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-182) Timed rules can disrupt other activations as they are being fired

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-182: ------------------------------------- Summary: Timed rules can disrupt other activations as they are being fired Key: DROOLS-182 URL: https://issues.jboss.org/browse/DROOLS-182 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Beta3, 5.5.1.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Blocker Timer-driven rules are executed by separated thread. One such thread may retract a fact which is being used by the (main) thread in a rule being fired. This preemption will lead to a NPE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 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 June 2013