[
https://issues.apache.org/jira/browse/DELTASPIKE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248647#comment-13248647
]
Gerhard Petracek edited comment on DELTASPIKE-151 at 4/6/12 8:19 PM:
---------------------------------------------------------------------
#1
that sounds like a feature which is very specific to camel
#2
there is no null check (not all beans have a name)
#3
most of the code is duplicated (see #getContextualReferences)
-> imo we need a discussion on the mailing list before we refactor and add it.
was (Author: gpetracek):
that sounds like a feature which is very specific to camel -> imo we need a
discussion on the mailing list before we add it.
> Provide lookup method with Map result
> -------------------------------------
>
> Key: DELTASPIKE-151
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-151
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.2-incubating
> Reporter: Łukasz Dywicki
> Assignee: Gerhard Petracek
> Attachments: DELTASPIKE-151.diff
>
>
> Currently BeanProvider do not support lookups with Map result. In my case I
> create a adapter from Camel registry object to CDI bean registry. Camel uses
> different kind of lookups when needed:
> - by name (when type is unknown)
> - by type (for one instance)
> - by name and type
> - by type, with names
> Second operation is used to collect for example all instances of given type
> (all Endpoint, Tracer implementations registered). Names are then used to get
> returned instances in correct places. Camel is container agnostic so we
> cannot rely on CDI features in all places.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
