[
https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-558:
------------------------------------------
I have 3 concerns by having these accessible only in lifecycle event:
* Consistency: why having some accessible in events and others elsewhere
* It doesn't solve the problem of having a place to put AnnotatedTypeBuilder
* It prevents creation of these meta data from outside CDI. The use could be to create a
bean and use it in launching the container in SE or if we decide later to allow addition
of some meta data at runtime.
Standardize the Meta-Data builders API (BeanBuilder, etc...)
------------------------------------------------------------
Key: CDI-558
URL:
https://issues.jboss.org/browse/CDI-558
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Martin Kouba
Fix For: 2.0 (discussion)
The RI includes an experimental BeanBuilder API (see also
http://weld.cdi-spec.org/news/2015/02/25/weld-300Alpha5/#_bean_builder_api for more
information). The API is similar to the [API provided by
DeltaSpike|http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspi...]
but also includes some improvements (e.g. Java 8 lambdas may be used to simplify the
process of registration).
* BeanBuilder Javadoc:
http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment...
* ExperimentalAfterBeanDiscovery Javadoc:
http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment...
* See also [the test extension for more examples of using this
API|https://github.com/weld/core/blob/master/tests-arquillian/src/test/ja...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)