July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments

by David Lloyd (JIRA)

Detect, filter, and act upon system APIs found in deployments ------------------------------------------------------------- Key: JBAS-8983 URL: https://issues.jboss.org/browse/JBAS-8983 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Implement a fixed set of package paths which are automatically filtered out of deployments. In addition, certain paths should be interpreted as an implicit dependency request. For example if "org/slf4j" is found in a deployment, it should be filtered, and an implicit import dependency upon the org.slf4j module (which provides the org.slf4j package) should be added to the deployment. Use sub-tasks for each API to filter or detect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
14
0 / 0

[JBoss JIRA] Created: (AS7-1128) Allow the server to ignore files or groups of files at deployment time

by Marius Bogoevici (JIRA)

Allow the server to ignore files or groups of files at deployment time ---------------------------------------------------------------------- Key: AS7-1128 URL: https://issues.jboss.org/browse/AS7-1128 Project: Application Server 7 Issue Type: Feature Request Components: Server Affects Versions: 7.0.0.CR1 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 7.1.0.Alpha1 Legacy and migrated applications may occasionally contain files which are incompatible with the Java EE specification and can cause the application to fail the deployment. The difference between those cases and really faulty Java EE applications lies in the intent of the developer - whether they wish for those files to be picked up by the server and processed, or not. In such cases, it may be useful to expand the deployment specification and to be able to instruct the server to ignore particular files at deployment time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-814) Fix or remove ignored smoke tests

by Thomas Diesler (JIRA)

Fix or remove ignored smoke tests --------------------------------- Key: AS7-814 URL: https://issues.jboss.org/browse/AS7-814 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts

by Brian Stansberry (JIRA)

Simple start and stop scripts ----------------------------- Key: JBAS-8137 URL: https://jira.jboss.org/browse/JBAS-8137 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> I would like to see all the configurations that normally get set on the >> command line (JBoss opts and system props) moved to a config file so all >> that is ever required to start a Jboss instance is simply "run.sh >> /<configuration>/". The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-9176) List servers in a servergroup below /server-group/<groupname>

by Heiko Rupp (JIRA)

List servers in a servergroup below /server-group/<groupname> ------------------------------------------------------------- Key: JBAS-9176 URL: https://issues.jboss.org/browse/JBAS-9176 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp It would be nice from a consistency standpoint to list the servers of a servergroup in its api below /server-group/groupname/ - just the names would be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9306) Expose address of DC as runtime attributes on the HC

by Heiko Rupp (JIRA)

Expose address of DC as runtime attributes on the HC ---------------------------------------------------- Key: JBAS-9306 URL: https://issues.jboss.org/browse/JBAS-9306 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Rupp Currently there is no way to learn about the http management port of the DC from a slave's host.xml or runtime. 17:02:31] <pilhuhn> I am reading host.xml to find the DC, so that I can contact its http port for e.g. querying the /socket-binding-group if the one on the host is undefined [17:02:41] <+bstansberry> I don't want it in the config, but I'm ok with adding it as a runtime attribute [17:04:13] <pilhuhn> bstansberry fine with me when I can query the HC for the http port of the DC [17:04:46] <+bstansberry> pilhuhn: the native API port should be a runtime attribute as well [17:04:51] <+bstansberry> yes please [17:05:04] <+bstansberry> what i mean by that is we should expose it as a runtime attribute 17:05:49] <+bstansberry> the config bit is an instruction to the HC, but we are going to add alternatives, e.g. a multicast address [17:06:55] <+bstansberry> so using the config will not be a reliable source; runtime can be -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8952) Fix the testsuite/integration testcase failures

by jaikiran pai (JIRA)

Fix the testsuite/integration testcase failures ----------------------------------------------- Key: JBAS-8952 URL: https://issues.jboss.org/browse/JBAS-8952 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Environment: JBoss AS7 master Reporter: jaikiran pai Assignee: Shelly McGowan Fix For: 7.0.0.CR1 As reported in the mailing list http://lists.jboss.org/pipermail/jboss-as7-dev/2011-March/000759.html thread, the "testsuite/integration" tests are failing with a CCE in JSFUnitApplicationArchiveProcessor: {code} Caused by: java.lang.ClassCastException: org.jboss.shrinkwrap.impl.base.spec.ResourceAdapterArchiveImpl cannot be cast to org.jboss.shrinkwrap.api.spec.WebArchive at org.jboss.jsfunit.arquillian.JSFUnitApplicationArchiveProcessor.process(JSFUnitApplicationArchiveProcessor.java:41) at org.jboss.arquillian.impl.ClientDeploymentGenerator.applyApplicationProcessors(ClientDeploymentGenerator.java:91) at org.jboss.arquillian.impl.ClientDeploymentGenerator.generate(ClientDeploymentGenerator.java:64) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:52) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:42) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) {code} The tests are currently disabled and need to be fixed and enabled in some upcoming release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8744) Failure to start the JVM should trigger a management update plan to rollback

by Andrig Miller (JIRA)

Failure to start the JVM should trigger a management update plan to rollback ---------------------------------------------------------------------------- Key: JBAS-8744 URL: https://issues.jboss.org/browse/JBAS-8744 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Andrig Miller Assignee: Brian Stansberry Fix For: 7.0.0.Beta1 I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility. So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9204) On component stop, destroy all instances

by David Lloyd (JIRA)

On component stop, destroy all instances ---------------------------------------- Key: JBAS-9204 URL: https://issues.jboss.org/browse/JBAS-9204 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE Reporter: David Lloyd Fix For: 7.0.0.Beta3 This will cause all outstanding component destroy lifecycle methods to be invoked when the component is stopped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBAS-9224) Automatic JNDI implementation

by David Lloyd (JIRA)

Automatic JNDI implementation ----------------------------- Key: JBAS-9224 URL: https://issues.jboss.org/browse/JBAS-9224 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE, Naming Reporter: David Lloyd Assignee: John Bailey Priority: Critical The JNDI subsystem should become fully service-oriented, meaning: 1) Contexts are always read-only 2) The NamingStore is populated solely by services 3) When the last binding in a context is removed, the context is automatically removed For pesky legacy subsystems which still expect to be able to bind into Context, we could possibly make up a "fake" Context from which the bound ObjectFactory (or whatever) is extracted to create the "real" service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011