[
http://team.ops4j.org/browse/QI-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091#comment-18091
]
Niclas Hedhman commented on QI-329:
-----------------------------------
I think you have a good point, but I think we should have a single method for
type lookup, which always returns "all matches", and the 'creational lookup'
usages will check the non-ambiguity requirement
(Specification<Iterable<Class<?>>> ??). Possibly a parallel method that does
this.
> ValueBuilderFactory doesn't perform correct type-to-composite lookup
> --------------------------------------------------------------------
>
> Key: QI-329
> URL: http://team.ops4j.org/browse/QI-329
> Project: Qi4j
> Issue Type: Bug
> Components: Core Runtime
> Reporter: Niclas Hedhman
> Fix For: 2.0 - Reductionism
>
> Attachments: entities-ambiguous-check-tests-reports.tar.gz
>
>
> When doing
> {code}
> ValueBuilder<DomainEvent> builder = vbf.newValueBuilder(DomainEvent.class)
> {code}
> Type-to-Composite lookup/search is not happening.
--
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
