[
https://issues.apache.org/jira/browse/DELTASPIKE-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354816#comment-14354816
]
Gerhard Petracek commented on DELTASPIKE-853:
---------------------------------------------
for @View/@Folder it doesn't make sense, because they are optional and we have
a workaround which is ~ok.
however, we could use that trick for @ViewConfigRoot which allows the support
of implicit bean archives in combination with @ApplicationScoped (= the current
workaround).
since users have to know that part of the documentation, it's imo no big diff.
if they use @ViewConfigRoot or @ViewConfigRoot+@ApplicationScoped.
defining @ViewConfigRoot as a stereotype is imo confusing for users, if their
ide lists it as a stereotype.
however, we could "hide" that by adding it via
BeforeBeanDiscovery#addStereotype.
> Use @Stereotype for interface/enum discovery
> --------------------------------------------
>
> Key: DELTASPIKE-853
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-853
> Project: DeltaSpike
> Issue Type: Task
> Reporter: Jozef Hartinger
>
> In several places DeltaSpike uses ProcessAnnotatedType to discover
> interfaces/enum provided by the application. These interfaces/enums are
> usually annotated with a marker annotation, e.g.:
> * @MessageBundle
> * @View/@Folder
> * @Repository
> * most likely others
> This works fine in explicit bean archives, where PAT is fired for each and
> every interface/enum within the archive.
> In CDI 1.1+ implicit bean archives, this won't work however as PAT is only
> fired for classes with a "bean defining annotation".
> One option to make these extensions work in CDI 1.2 environment is to add
> @Stereotype to the marker annotations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
