[
http://jira.jboss.com/jira/browse/JBMICROCONT-35?page=comments#action_123... ]
Rashid Kamran commented on JBMICROCONT-35:
------------------------------------------
Whatever you are saying is correct but conventionally a <property> tag is supposed
to call a setXXX method and setter methods are supposed to overwrite the properties
completely. Because the way its now a constructor could add three elements as default and
one can add two more from the configuration file and this is inconsistency because as a
programmer my intention would be to give defaults in the code and overwrite defaults using
properties. while you are merging both.. It's not conventional
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