July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1144) Document how to change the default user name and password for the Felix Web Console

by David Bosschaert (JIRA)

Document how to change the default user name and password for the Felix Web Console ----------------------------------------------------------------------------------- Key: AS7-1144 URL: https://issues.jboss.org/browse/AS7-1144 Project: Application Server 7 Issue Type: Task Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Optional Currently the Felix Web Console operates under the default username and password (admin/admin). We need to document how to change this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1143) Should pre-populated modules a high start level be loaded in lower start levels?

by David Bosschaert (JIRA)

Should pre-populated modules a high start level be loaded in lower start levels? -------------------------------------------------------------------------------- Key: AS7-1143 URL: https://issues.jboss.org/browse/AS7-1143 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Optional A number of modules are specified to be pre-loaded in the OSGi framework in the <modules> section of the osgi subsystem configuration. {code}<modules> <module identifier="javaee.api"/> <module identifier="org.jboss.logging"/> <module identifier="org.apache.aries.util"/> <module identifier="org.jboss.osgi.webconsole"/> <module identifier="org.osgi.compendium"/> <module identifier="org.apache.felix.log" startlevel="1"/> <module identifier="org.jboss.osgi.logging" startlevel="1"/> <module identifier="org.apache.felix.configadmin" startlevel="1"/> <module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/> <module identifier="org.apache.aries.jmx" startlevel="2"/> <module identifier="org.apache.felix.eventadmin" startlevel="2"/> <module identifier="org.apache.felix.metatype" startlevel="2"/> <module identifier="org.apache.felix.webconsole" startlevel="2"/> <module identifier="org.jboss.osgi.jmx" startlevel="2"/> <module identifier="org.jboss.osgi.http" startlevel="2"/> <module identifier="org.jboss.osgi.blueprint" startlevel="3"/> <module identifier="org.jboss.osgi.webapp" startlevel="3"/> <module identifier="org.jboss.osgi.xerces" startlevel="3"/> </modules>{code} Currently all modules are loaded, regardless of start level and only those that have a start level <= the current one are actually started. I wonder whether this is desirable. When a module has a startlevel specified, it clearly needs to be started and is likely not useful when not started. It would therefore make sense to me to not pre-load modules with a higher start level, but only load these once their start level is being reached. This would improve subsystem start times too... I.e. even when start level 1 is specified, the following output appears when the framework is started: {code}13:52:28,008 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: system.bundle:0.0.0 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: javaee.api:0.0.0 13:52:28,119 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-10) Install bundle: org.jboss.logging:3.0.0 13:52:28,133 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: jboss-as-osgi-configadmin:7.0.0.CR1 13:52:28,137 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jbosgi-webconsole:1.0.6 13:52:28,140 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-12) Install bundle: jboss-osgi-logging:1.0.0 13:52:28,176 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-7) Install bundle: jboss-osgi-jmx:1.0.10 13:52:28,204 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-5) Install bundle: org.apache.felix.metatype:1.0.4 13:52:28,219 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8 13:52:28,228 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: org.apache.aries.util:0.3.0 13:52:28,229 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-14) Install bundle: org.apache.aries.jmx:0.3.0 13:52:28,237 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: org.apache.felix.log:1.0.0 13:52:28,240 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-16) Install bundle: jbosgi-blueprint:1.0.2 13:52:28,313 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-webapp:1.0.2 13:52:28,325 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.apache.felix.eventadmin:1.2.6 13:52:28,333 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-9) Install bundle: jboss-osgi-xerces:2.9.1.SP7 13:52:28,368 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-13) Install bundle: org.apache.felix.webconsole:3.1.6.SP1 13:52:28,394 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-15) Install bundle: jboss-osgi-http:1.0.3 13:52:28,460 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.cmpn:4.2.0.200908310645 {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1222) Subsystem developers guide

by Brian Stansberry (JIRA)

Subsystem developers guide -------------------------- Key: AS7-1222 URL: https://issues.jboss.org/browse/AS7-1222 Project: Application Server 7 Issue Type: Task Reporter: Brian Stansberry Assignee: Kabir Khan Fix For: 7.0.1.Final A guide on how to develop an AS7 extension/subsystem and a maven archetype for same. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1172) JNDI

by Alexandre Gattiker (JIRA)

JNDI ----- Key: AS7-1172 URL: https://issues.jboss.org/browse/AS7-1172 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.CR1 Reporter: Alexandre Gattiker If a JMS destination is created with a JNDI name starting with "/jms/", the JNDI View issues an error message. The destination appears to be up and running fine though. <h1>java: Namespace</h1> <pre> +- topic (class: javax.naming.Context) | +- test (class: org.jboss.as.naming.context.ModularReference) +- app (class: javax.naming.Reference) +- module (class: javax.naming.Reference) +- comp (class: javax.naming.Reference) +- queue (class: javax.naming.Context) | +- test (class: org.jboss.as.naming.context.ModularReference) +- jms (class: javax.naming.Context) Failed to lookup: jms, errmsg=Name 'jms' not found in context '' +- global (class: javax.naming.Reference) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1360) Incorrect soap:address connector port generated in WSDL for JAX-WS service

by Abhijit Sarkar (JIRA)

Incorrect soap:address connector port generated in WSDL for JAX-WS service -------------------------------------------------------------------------- Key: AS7-1360 URL: https://issues.jboss.org/browse/AS7-1360 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.0.0.Final Environment: Ubuntu 11.04, JBoss AS 7.0.0.Final, RESTEasy 2.2.1.GA Reporter: Abhijit Sarkar Assignee: Alessio Soldano Default soap:address connector port generated in WSDL even though server is running on a different HTTP port. Please see forum reference for detail. ?? jaikiran pai wrote: Please open a JIRA for this. The way the connector port is being inferred from the configured connectors, from the JBoss WS code, will not work in AS7. ?? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (AS7-1286) IronJacamar 1.0.0.Final

by Jesper Pedersen (JIRA)

IronJacamar 1.0.0.Final ----------------------- Key: AS7-1286 URL: https://issues.jboss.org/browse/AS7-1286 Project: Application Server 7 Issue Type: Component Upgrade Components: Build System Reporter: Jesper Pedersen Assignee: Paul Gier Fix For: 7.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1890) Recovery configuration in a cluster is too burdensome

by Justin Bertram (JIRA)

Recovery configuration in a cluster is too burdensome ----------------------------------------------------- Key: JBMESSAGING-1890 URL: https://issues.jboss.org/browse/JBMESSAGING-1890 Project: JBoss Messaging Issue Type: Task Components: JMS Clustering Affects Versions: 1.4.8.SP1 Reporter: Justin Bertram The recovery configuration describe on http://community.jboss.org/wiki/Non-serializableXAResourceErrorFromJBossM... is too burdensome, especially for large clusters. When a new node is added to the cluster then *every* node in the cluster needs a configuration change. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (JBRULES-3126) NPE when retracting an object with a collection field which has been accumulated on

by Davide Sottara (JIRA)

NPE when retracting an object with a collection field which has been accumulated on ----------------------------------------------------------------------------------- Key: JBRULES-3126 URL: https://issues.jboss.org/browse/JBRULES-3126 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical the engine throws a NPE in ReteooWorkingMemory.execute as the "accctx" variable there is null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1137) Add support to specify a username and password for all demos to allow running against secured servers.

by Darran Lofthouse (JIRA)

Add support to specify a username and password for all demos to allow running against secured servers. ------------------------------------------------------------------------------------------------------ Key: AS7-1137 URL: https://issues.jboss.org/browse/AS7-1137 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8548) Integrate SwitchBoard into AS

by jaikiran pai (JIRA)

Integrate SwitchBoard into AS ----------------------------- Key: JBAS-8548 URL: https://jira.jboss.org/browse/JBAS-8548 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 6.0.0.CR1 This JIRA will track the integration of the SwitchBoard component http://community.jboss.org/wiki/Switchboard into AS. Initially, the integration is being done on a separate branch https://svn.jboss.org/repos/jbossas/branches/switchboard-integration/ and finally will be merged to AS trunk. -- 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

14 years, 8 months

2
6
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 July 2011