May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4594) Move messaging subsystem to legacy/

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4594?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4594: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Move messaging subsystem to legacy/ > ----------------------------------- > > Key: WFLY-4594 > URL: https://issues.jboss.org/browse/WFLY-4594 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4593) Model-only representation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4593?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4593: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Model-only representation > ------------------------- > > Key: WFLY-4593 > URL: https://issues.jboss.org/browse/WFLY-4593 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha3 > > > Refactor the messaging subsystem to use ModelOnlyResource definition and remove all runtime code. > Remove also the org.hornetq and org.hornetq.ra) modules. > With WFLY-4584, a org.hornetq.client module is added to represent only the HornetQ client library (required for JMS forward compatibility) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4592) Deprecate messaging subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4592?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4592: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Deprecate messaging subsystem > ----------------------------- > > Key: WFLY-4592 > URL: https://issues.jboss.org/browse/WFLY-4592 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha3 > > > WildFly 10 will have a new messaging-activemq subsystem to provide its messaging capability. > The current messaging subsystem is deprecated. It will be moved to legacy directory and all its runtime will be removed. > Its management model will be preserved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4587) Provide a migration management operation for HornetQ to ActiveMQ Artemis

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4587?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4587: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Provide a migration management operation for HornetQ to ActiveMQ Artemis > ------------------------------------------------------------------------ > > Key: WFLY-4587 > URL: https://issues.jboss.org/browse/WFLY-4587 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha3 > > > WildFly 10 has a new messaging-activemq subsystem using ActiveMQ Artemis as its messaging broker. > WildFly 10 needs to provide a :migrate management operation so that user upgrading from WildFly 9 to 10 can start WildFly 10 with their old configuration (which used HornetQ) and migrate to the new subsystem (which used ActiveMQ Artemis). > This migrate operation deals only with the management resource and does *not* migrate data from HornetQ to Artemis. This will done in a separate step (using either a JMS bridge or data export tool) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4680) Fork and JChannel names need to be unique

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4680?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4680: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Fork and JChannel names need to be unique > ----------------------------------------- > > Key: WFLY-4680 > URL: https://issues.jboss.org/browse/WFLY-4680 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4674) Upgrade JGroups to 3.6.4.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4674?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4674: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Upgrade JGroups to 3.6.4.Final > ------------------------------ > > Key: WFLY-4674 > URL: https://issues.jboss.org/browse/WFLY-4674 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > Needed to pick up the fix for JGRP-1928 so that WildFly 9 clustering can work on OpenShift. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4658) merge Jipijapa source into WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4658?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4658: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > merge Jipijapa source into WildFly > ---------------------------------- > > Key: WFLY-4658 > URL: https://issues.jboss.org/browse/WFLY-4658 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.Alpha3 > > > Merging http://github.com/jipijapa/jipijapa sources back into WildFly to increase community involvement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4651) Change default locking isolation of infinispan caches to READ_COMMITTED

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4651?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4651: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Change default locking isolation of infinispan caches to READ_COMMITTED > ----------------------------------------------------------------------- > > Key: WFLY-4651 > URL: https://issues.jboss.org/browse/WFLY-4651 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Affects Versions: 9.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > This will allow concurrent read access to the session using our default configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4705) Enable interface declaration in subsystem template

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFLY-4705: ------------------------------------ Summary: Enable interface declaration in subsystem template Key: WFLY-4705 URL: https://issues.jboss.org/browse/WFLY-4705 Project: WildFly Issue Type: Feature Request Components: Build System, IIOP Affects Versions: 10.0.0.Alpha1 Reporter: Tomasz Adamski Assignee: Tomasz Adamski Priority: Optional Currently interfaces cannot be defined in subsystem templates. As a result of "unsecure" interface, which is used only by iiop subsystem, is defined in main template file and it's included in all subsystems configurations. Implement extension to feature pack plugin which enables specifying interfaces in subsystem configuration files and move "unsecure" interface configuration from main template to jacorb. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-91) Add ability to provide constant values for properties

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-91: ---------------------------------- Summary: Add ability to provide constant values for properties Key: LOGTOOL-91 URL: https://issues.jboss.org/browse/LOGTOOL-91 Project: Log Tool Issue Type: Feature Request Reporter: David Lloyd Assignee: James Perkins Right now I have to do this: {code} @Message(id = 28, value = "An unexpected protocol error occurred") XAException protocolErrorXA(@Property int errorCode); // ... then later ... throw Log.log.protocolErrorXA(XAException.XAER_RMFAIL); {code} I'd rather be able to do this: {code} @Message(id = 28, value = "An unexpected protocol error occurred") @Property(name = "errorCode", intValue = XAException.XAER_RMFAIL) XAException protocolErrorXA(); // ... then later ... throw Log.log.protocolErrorXA(); {code} The same annotation ({{@Property}}) could be reused by making it multi-valued (i.e. invisible wrapper annotation) and adding in defaulted {{xxxValue}} parameters (primitive types, {{Class<XX>}}, and {{String}}) which are rejected when applied directly to a method parameter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015