October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Aslak Knutsen (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated AS7-2203: ------------------------------- Summary: Add Arquillian Container support for AS 7 domain controller (was: Add support for AS 7 domain controller) Component/s: Test Suite > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Critical > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3261) testing fluent api

by Mark Proctor (Created) (JIRA)

testing fluent api ------------------ Key: JBRULES-3261 URL: https://issues.jboss.org/browse/JBRULES-3261 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1989) Reading a server group resource in the CLI doesn't show the socket group

by Misty Stanley-Jones (JIRA)

Reading a server group resource in the CLI doesn't show the socket group ------------------------------------------------------------------------ Key: AS7-1989 URL: https://issues.jboss.org/browse/AS7-1989 Project: Application Server 7 Issue Type: Bug Components: CLI Environment: Fedora 15, Bash, very recent AS trunk. Reporter: Misty Stanley-Jones Assignee: Alexey Loubyansky Priority: Minor I added a server group using the following command: [domain@localhost:9999 /] /server-group=clustered-group:add(profile=ha,socket-group=ha-sockets) I then used the following command to read the resource: [domain@localhost:9999 /] /server-group=clustered-group:read-resource { "outcome" => "success", "result" => { "deployment" => undefined, "jvm" => undefined, "profile" => "ha", "system-property" => undefined } } It shows the profile but not the socket binding group. It seems like it should show both. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-2162) System properties propagated from command line using -D, -P or --properties aren't visible in CLI and console

by Rostislav Svoboda (Created) (JIRA)

System properties propagated from command line using -D, -P or --properties aren't visible in CLI and console ------------------------------------------------------------------------------------------------------------- Key: AS7-2162 URL: https://issues.jboss.org/browse/AS7-2162 Project: Application Server 7 Issue Type: Bug Components: CLI, Console, Domain Management Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 CLI and console shows only properties defined in .xml configuration files. System properties propagated from command line using -D, -P or --properties args should be visible too. It would be useful for administrators when searching for possible problems, the same applies to devels. For domain I'd like to see sysprops on each instance and separate overview for DC. Previous versions of AS/EAP provide such overview in /web-console/SysProperties.jsp. NOTE: JVM based properties like java.vendor etc. would be beneficial too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (JBMESSAGING-1903) autogenerate server peer ID when S3_PING is in use

by Aleksandar Kostadinov (Created) (JIRA)

autogenerate server peer ID when S3_PING is in use -------------------------------------------------- Key: JBMESSAGING-1903 URL: https://issues.jboss.org/browse/JBMESSAGING-1903 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: EAP/SOA-P Integration Environment: EC2 Reporter: Aleksandar Kostadinov Fix For: EAP/SOA-P Integration In EC2 one cannot easily generate unique server peer IDs for each server (see JBPAPP-7208). I thought it will not be too hard to use S3_PING to also generate unique server peer IDs. How feasible is implementation of such functionality? If not feasible, please provide your ideas about other possible approaches. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2202) The Service of the default-virtual-host should be bound to a well-known ServiceName

by Bob McWhirter (Created) (JIRA)

The Service of the default-virtual-host should be bound to a well-known ServiceName ----------------------------------------------------------------------------------- Key: AS7-2202 URL: https://issues.jboss.org/browse/AS7-2202 Project: Application Server 7 Issue Type: Feature Request Components: Web Reporter: Bob McWhirter Assignee: Remy Maucherat Priority: Minor The torquebox-web subsystem uses the WebVirtualHostService installed through the AS7 web subsystem. Which service actually is the default service is difficult to determine. Aliasing to a single well-known name, such as WebSubsystemServices.JBOSS_DEFAULT_WEB_HOST would make working with the default host easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1747) CLI commands are not consistent across

by Ramesh Reddy (JIRA)

CLI commands are not consistent across -------------------------------------- Key: AS7-1747 URL: https://issues.jboss.org/browse/AS7-1747 Project: Application Server 7 Issue Type: Enhancement Components: CLI Affects Versions: 7.0.1.Final Reporter: Ramesh Reddy Assignee: Alexey Loubyansky For creating a queue, CLI has "add-jms-queue", "remove-jms-queue" etc, where are "data-source" takes another approach for extensions to same command, which is not consistent across the commands in the CLI. Also, data-source command help and as well as error message when used say "--jndi-name: missing" instead of showing the correct usage. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (JBJCA-686) JBoss Logging Processor 1.0.0.CR3

by Jesper Pedersen (Created) (JIRA)

JBoss Logging Processor 1.0.0.CR3 --------------------------------- Key: JBJCA-686 URL: https://issues.jboss.org/browse/JBJCA-686 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-683) Track component updates

by Jesper Pedersen (Created) (JIRA)

Track component updates ----------------------- Key: JBJCA-683 URL: https://issues.jboss.org/browse/JBJCA-683 Project: IronJacamar Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-684) JBoss Logging 3.1.0.Beta2

by Jesper Pedersen (Created) (JIRA)

JBoss Logging 3.1.0.Beta2 ------------------------- Key: JBJCA-684 URL: https://issues.jboss.org/browse/JBJCA-684 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 October 2011