[
http://team.ops4j.org/browse/QI-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504#comment-17504
]
Niclas Hedhman commented on QI-361:
-----------------------------------
Once you attempt to persist "any fields", you are quickly in a nightmare of
problems. we know roughly what those problems are, since all the complexity of
Hibernate is all about handling that. it is a bad place to be, and I don't
intend to go there.
I can't look at the test easily now, but in general; Values are not only about
storage of state, but often to ensure an easier concurrency model. perhaps
HashMap is not the best example. and perhaps pojos will seldom be used this
way. I don't know that right now. But once it is solved, the method applies to
objects and transients as well.
> "ValueBuilder instances can not be reused."
> -------------------------------------------
>
> Key: QI-361
> URL: http://team.ops4j.org/browse/QI-361
> Project: Qi4j
> Issue Type: Bug
> Components: Core Runtime
> Reporter: Niclas Hedhman
> Fix For: 2.0 - Reductionism
>
>
> If you try to use the same ValueBuilder as a cookie-cutter for similar
> values, you will receive the error;
> java.lang.IllegalStateException: ValueBuilder instances cannot be reused
> This defeats the purpose of having the methods prototype() and prototypeFor().
> So, either the names need to change (I don't like that), or the previous
> behavior of prototype instantiation should be supported.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://team.ops4j.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
