September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1803) Improve command line help text

by Brian Stansberry (JIRA)

Improve command line help text ------------------------------ Key: AS7-1803 URL: https://issues.jboss.org/browse/AS7-1803 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.1.0.Alpha1 As discussed on the linked dev list thread. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1378) Make module directory configurable using .sh/.bat run scripts

by Rostislav Svoboda (JIRA)

Make module directory configurable using .sh/.bat run scripts ------------------------------------------------------------- Key: AS7-1378 URL: https://issues.jboss.org/browse/AS7-1378 Project: Application Server 7 Issue Type: Feature Request Reporter: Rostislav Svoboda Fix For: 7.1.0.Alpha1 Make module directory configurable using .sh/.bat run scripts, currently you can specify configuration location using '--server-config' or '--domain-config' + '--host-config' , location of modules directory should be configurable too. It's necessary to make changes on .bat/.sh files level to make module directory configurable. Currently it's hard-coded to use module directory under JBOSS_HOME directory {code} -mp \"$JBOSS_HOME/modules\" \ {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1668) Usability: Lack of -b binding support in AS7 leads to confusion

by Michael Dobozy (JIRA)

Usability: Lack of -b binding support in AS7 leads to confusion --------------------------------------------------------------- Key: AS7-1668 URL: https://issues.jboss.org/browse/AS7-1668 Project: Application Server 7 Issue Type: Bug Reporter: Michael Dobozy The replacement for -b in AS7, from what I understand, is to edit standalone.xml and, under the public interface section, specify <any-address /> as the binding interface. "<any-address />" doesn't seem like an obvious value for specifying the wildcard interface - I'd think that the standard "0.0.0.0" would lead to less problems. If it's impossible to support 0.0.0.0 specifically, or to add support for -b again, then some additional information on the error message that comes back from when a user attempts the -b argument would be more helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Resolved: (AS7-1819) CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-1819?page=com.atlassian.jira.plugin.s... ] Paul Gier resolved AS7-1819. ---------------------------- Fix Version/s: 7.0.2.Final (was: 7.1.0.CR1) Resolution: Done > CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-1819 > URL: https://issues.jboss.org/browse/AS7-1819 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Paul Gier > Fix For: 7.0.2.Final > > > When creating new jms queue using add-jms-queue command and not specifying durable attribute then by default is durable=false - should be durable=true according description of add-jms-queue command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1819) CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-1819?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky updated AS7-1819: ----------------------------------- Assignee: Paul Gier (was: Alexey Loubyansky) Git Pull Request: https://github.com/jbossas/jboss-as/pull/291 (was: https://github.com/jbossas/jboss-as/pull/291) Component/s: JMS (was: CLI) > CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-1819 > URL: https://issues.jboss.org/browse/AS7-1819 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Paul Gier > Fix For: 7.1.0.CR1 > > > When creating new jms queue using add-jms-queue command and not specifying durable attribute then by default is durable=false - should be durable=true according description of add-jms-queue command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1819) CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-1819?page=com.atlassian.jira.plugin.s... ] Paul Gier updated AS7-1819: --------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/291 > CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-1819 > URL: https://issues.jboss.org/browse/AS7-1819 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.0.CR1 > > > When creating new jms queue using add-jms-queue command and not specifying durable attribute then by default is durable=false - should be durable=true according description of add-jms-queue command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1793) Upgrade Infinispan to 5.0.1.FINAL

by Paul Ferraro (JIRA)

Upgrade Infinispan to 5.0.1.FINAL --------------------------------- Key: AS7-1793 URL: https://issues.jboss.org/browse/AS7-1793 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Affects Versions: 7.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-673) Arquillian 1.0.0.CR5

by Jesper Pedersen (JIRA)

Arquillian 1.0.0.CR5 -------------------- Key: JBJCA-673 URL: https://issues.jboss.org/browse/JBJCA-673 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-674) ShrinkWrap Descriptors 1.2.0.Alpha1

by Jesper Pedersen (JIRA)

ShrinkWrap Descriptors 1.2.0.Alpha1 ----------------------------------- Key: JBJCA-674 URL: https://issues.jboss.org/browse/JBJCA-674 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1583) Plugging in Hibernate 3.3.x in AS 7+ should be possible for user migrating from EAP 5

by Jim Tyrrell (JIRA)

Plugging in Hibernate 3.3.x in AS 7+ should be possible for user migrating from EAP 5 ------------------------------------------------------------------------------------- Key: AS7-1583 URL: https://issues.jboss.org/browse/AS7-1583 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell Thinking about the amount of hibernate that is out in the wild, and not knowing the scope/effort of having everyone switch to Hibernate 4.X, it would be nice if we can document what it takes to plug in the version of Hiberante/s that are in EAP 5. I also wonder aloud about EAP 4, but I think EAP 5 would be enough. Thoughts on extending this to EAP 4 version of hibernate. For reference version numbers are here: http://www.jboss.com/products/platforms/application/components/ Looks like 3.3.x for EAP 5 Looks like 3.2.x for EAP 4.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011