[ http://jira.codehaus.org/browse/JIBX-15?page=history ]
Dennis Sosnoski resolved JIBX-15:
---------------------------------
Fix Version: CVS
Resolution: Fixed
This is now the default behavior - an existing object value will be reused
rather than a new instance created. This *does* mean that collections need to
be cleared when reusing existing objects in unmarshalling, which at present
would need to be done using a pre-set method.
> Provide an option to no instanciate collections
> -----------------------------------------------
>
> Key: JIBX-15
> URL: http://jira.codehaus.org/browse/JIBX-15
> Project: JiBX
> Type: Improvement
> Components: core
> Versions: 1.0-beta3a
> Reporter: Guillaume Pothier
> Assignee: Dennis Sosnoski
> Priority: Minor
> Fix For: CVS
>
>
> It would be nice to add an attribute to the <collection> tag that permits to
> specify if the collection should be instanciated or not? For instance, I have
> this class:
> class A
> {
> private List itsList = new ArrayList ();
> public List getList () {return itsList;}
> }
> As instanciating this class automatically instanciates the list, I do not
> want to have a setList method (nor I want JiBX instanciating a list and
> setting my itsList field)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
