August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3589) Example incorrectly says JNDIView started (and disabled) using jboss-service.xml

by David Gecawich (JIRA)

Example incorrectly says JNDIView started (and disabled) using jboss-service.xml -------------------------------------------------------------------------------- Key: JBAS-3589 URL: http://jira.jboss.com/jira/browse/JBAS-3589 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming, System service Affects Versions: JBossAS-4.0.4.GA Environment: JBossAS-4.0.4 GA, Full J2EE server profile from installer Reporter: David Gecawich Assigned To: Scott M Stark Example incorrectly says JNDIView started from jboss-service.xml JBoss AS 4.0.4. Getting Started Guide, 2.2.1 Core Services, page 8, says "if you have a look at this file [conf/jndi-service.xml], you'ee MBeans for various sevrices including.... the JNDIView service service that we saw earlier. Try commenting out the entry for the JNDIView service..." PROBLEM: You cannot comment out the MBean entry for the JNDIView service in conf/jndi-service.xml because the MBean entry for the JNDIView service does not exist in the conf/jndi-service.xml file. The documentation appears to be incorrect. TO REPRODUCE: 1. Download the JBoss AS 4.0.4 Getting Started Guide. The links to the PDF and HTML files are below. PDF: http://labs.jboss.com/portal/jbossas/docs HTML: http://docs.jboss.org/jbossas/getting_started/v4/html/tour.html#d0e412 2. Install JBoss AS 4.0.4 as specified in the documentation (I installed the Full J2EE server profile) 3. Follow the instructions in Getting Started Guide, 2.2.1 Core Services, page 8 and open conf/jndi-service.xml in an editor. 4. Look for JNDIView in conf/jndi-service.xml Results: you cannot find JNDIView in conf/jndi-service.xml and cannot complete the example. Notes: 1. I searched jira.jboss.org on "JNDIView" and "naming-service.xml" and from the headers of items listed, did not see any apparent duplicate items. 2. We are upgrading from JBoss 3.2.5. In JBOss 3.2.5, JNDIView was present the in core jboss-service.xml configuration file. This service appears to have changed in JBoss 4.0.4, at least under some configurations, and the documentation may not have been updated to reflect this change. 3. I did some digging, and found that in JBoss 4.0.4, the MBean definition for "JNDIView" is included in the default configuration from the deploy file deploy/naming-service.xml (Iverify the JNDIView is loaded from the deploy/naming-service.xml file in the workaround). In JMX Console, JNDIView is loaded and can be invoked so the service is operational. 4. Since JNDIView is used as the example to describe how core services work in JBOss (a key concept) and how to disable a service, it is confusing to the reader why a core service is not in the jboss-service.xml and what the recommended procedure is to disable a core service in 4.0.4. Also, can one assume that JNDIView is no longer a core service? Possible Solution: Perhaps the JBoss AS 4.0.4 Getting Started doc can be updated to use another service that is loaded and disabled as an example, and a clarification can be made regarding JNDIView in section 2.2.1 to correct the example. Workaround: I found you can disable the JNDIView service as follows: 1. Goto JMX Console at http://localhost:8080/jmx-console/, find the JNDIView service to verify it is loaded. 2. Edit the /deploy/naming-service.xml file. 3. Comment out the MBean entry for JNDIView in this file, as follows:  3. Restart JBoss. 4. Goto JMX Console at http://localhost:8080/jmx-console/, try to find the JNDIView service. You should not be able to find it, thus verifying that you successfully did not start the JNDIView service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=comments#action_123... ] Adrian Brock commented on JBMICROCONT-35: ----------------------------------------- Rashid, if you want to state an opinion use the forums. > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0M1 > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=comments#action_123... ] Adrian Brock commented on JBMICROCONT-35: ----------------------------------------- I've also uncommented the equivalent tests for sets and list. We could also do with array and map tests. > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0M1 > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=all ] Adrian Brock updated JBMICROCONT-35: ------------------------------------ Comment: was deleted > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0M1 > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMICROCONT-35) Allow retrieval of the collection instance from the bean

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=all ] Adrian Brock reopened JBMICROCONT-35: ------------------------------------- Reopened since this isn't working. The only reason the test passed is because the default constructor was changed to set preinstantiated to true. If it uses the default constructor then it is not using preinstantiated object. > Allow retrieval of the collection instance from the bean > -------------------------------------------------------- > > Key: JBMICROCONT-35 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-35 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0M1 > > > See org.jboss.test.kernel.config.test.CollectionTestCase#TODOtestCustomCollectionPreInstantiated > Same issues apply to Lists, Sets, Maps, Arrays, etc. > i.e. If the bean already has a collection value for the property that can be > retrieved using the getter, we should be able to use that collection instance. > Need to think about the configuration options and rules. > Current rules are: > 1) Use class specified in metadata > 2) Use class specified on setter (if not an interface) > 3) Use ArrayList -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3345) Synch up with tomcat6 based jbossweb as the bundled web container

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3345?page=comments#action_12342464 ] Remy Maucherat commented on JBAS-3345: -------------------------------------- Last step: I have added a JBoss Web component in jboss/web in the thordparty repository, and HEAD could be switched to it. I propose making the following changes: - small update to the TC 6 integration (it uses commons-modeler, which is now packaged renamed, along with some other improvements) - remove the TC 5 integration code I can either do that in the current "tomcat" folder of the jbossas repository, or create a new top level "jbossweb" folder and leave the current Tomcat 6 code as is. Comments ? > Synch up with tomcat6 based jbossweb as the bundled web container > ----------------------------------------------------------------- > > Key: JBAS-3345 > URL: http://jira.jboss.com/jira/browse/JBAS-3345 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Scott M Stark > Assigned To: Remy Maucherat > Priority: Blocker > Fix For: JBossAS-5.0.0.Beta > > > We need a tomcat6 based version of jbosseb as the bundled web container for the jboss5 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-4) Remove (archive) un-used branches and tags

by Dimitris Andreadis (JIRA)

Remove (archive) un-used branches and tags ------------------------------------------ Key: JBCOMMON-4 URL: http://jira.jboss.com/jira/browse/JBCOMMON-4 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Ruel Loehr Priority: Minor The standalone commons project carries over from JBossAS all of its branches & tags. I believe those are of no use to the commons project and they should be archived. If a bug needs to be fixed in older jboss versions that include the commons module it will be fixed there. Only Branch_1_0 is currently in use (producing the common jdk1.4 based versions targeting jboss 4.0.5+) They following tags where added by Thomas D., so leave them there for now. https://svn.jboss.org/repos/common/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-291) PullPushAdapter starts thread in constructor before listeners are registered

by Steve Nicolai (JIRA)

PullPushAdapter starts thread in constructor before listeners are registered ---------------------------------------------------------------------------- Key: JGRP-291 URL: http://jira.jboss.com/jira/browse/JGRP-291 Project: JGroups Issue Type: Feature Request Affects Versions: 2.3 Environment: All Reporter: Steve Nicolai Assigned To: Bela Ban The PullPushAdapter has the ability to multiplex based on a Serializable identifier. Unfortunately, all the constructors start the adaptor. This makes it very difficult to register listeners via registerListener(Serializable identifier, MessageListener l) before the adaptor is started. When a new node is joining an existing cluster that is actively sending messages, there is a race between getting the listeners registered and a message arriving. Suggested fix: Remove the call to start() from the constructors, allowing the PullPushAdaptor to be constructed, the listeners to be registered, then start() the adaptor. For example: a = new PullPushAdaptor(.....) a.registerListener("id1", ....) a.registerListener("id2", ....) a.start(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-290) Variables are not substituted with the Multiplexer

by Bela Ban (JIRA)

Variables are not substituted with the Multiplexer -------------------------------------------------- Key: JGRP-290 URL: http://jira.jboss.com/jira/browse/JGRP-290 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 Variables defined in stacks.xml are not substituted, because variable substitution only occurs in JChannel.init(). However, in JChannelFactory.createMulitplexerChannel(), we don;t call the substitution method ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBMICROCONT-28) BeanMetaData should implement ValueMetaData

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-28?page=all ] Ales Justin updated JBMICROCONT-28: ----------------------------------- JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=89581 > BeanMetaData should implement ValueMetaData > ------------------------------------------- > > Key: JBMICROCONT-28 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-28 > Project: JBoss MicroContainer > Issue Type: Task > Components: MetaData > Reporter: Adrian Brock > Assigned To: Ales Justin > Fix For: JBossMC_2_0_0RC1 > > > BeanMetaData should implement ValueMetaData > where the value is the bean constructed. > This allows direct configuration like: > <bean bean="xxx"> > <attribute name="blah"> > <bean bean="yyy"> > etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 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 August 2006