[JBoss JIRA] (CDI-607) Register a bean from a producer
by John Ament (JIRA)
John Ament created CDI-607:
------------------------------
Summary: Register a bean from a producer
Key: CDI-607
URL: https://issues.jboss.org/browse/CDI-607
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: John Ament
Assuming I've defined a custom implementation of Producer<T>, register it as a bean via addBean().
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (CDI-606) Add missing read methods
by John Ament (JIRA)
John Ament created CDI-606:
------------------------------
Summary: Add missing read methods
Key: CDI-606
URL: https://issues.jboss.org/browse/CDI-606
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Javadoc and API
Reporter: John Ament
Add missing read() methods to Annotated*Configurator to read attributes from an existing source.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (CDI-605) Add some built in predicates
by John Ament (JIRA)
John Ament created CDI-605:
------------------------------
Summary: Add some built in predicates
Key: CDI-605
URL: https://issues.jboss.org/browse/CDI-605
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Javadoc and API
Reporter: John Ament
During review, Antonin pointed out some useful predicates that should be reusable in the context of CDI.
https://github.com/astefanutti/camel-cdi/blob/0c9ae969c5721e655da3d396d17...
{code}
static Predicate<Bean> hasType(Type type) {
requireNonNull(type);
return bean -> bean.getTypes().contains(type);
}
static Predicate<Annotation> isAnnotationType(Class<? extends Annotation> clazz) {
requireNonNull(clazz);
return annotation -> clazz.equals(annotation.annotationType());
}
{code}
We should consider adding them.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
CDI SE and synthetic bean archives
by Martin Kouba
Hi all,
few notes WRT discussion about CDI SE and synthetic bean archives (EG
mtg, 2016-05-24):
* Weld SE does not scan JDK classes
** by default, only jars/dirs with beans.xml are considered
** if org.jboss.weld.se.scan.classpath.entries set to true, Weld SE
scans the class path entries and implicit bean archives which don't
contain a beans.xml file are also supported; but rt.jar and friends are
not listed in the "java.class.path" system property
** AFAIK there is no other way how to implement this in a better way
Synthetic bean archive was originally intended as a feature for power
users who either know all the beans beforehand (possibly with discovery
disabled) or want to add some extra beans (if discovery is enabled).
That's the reason why it behaves as it has bean discorey mode "all". If
I understand John's concerns, it's all about the case of adding packages
(which itself is problematic because of java limitations).
If so, we could introduce something like
org.jboss.shrinkwrap.api.container.ClassContainer.addPackages(boolean,
Filter<ArchivePath>, Package...). And provide some default "Filter"
implementations.
Martin
8 years, 7 months
[JBoss JIRA] (CDI-603) Create separate doc section for each Annotated*Configurator
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-603?page=com.atlassian.jira.plugin.sy... ]
Work on CDI-603 started by Antoine Sabot-Durand.
------------------------------------------------
> Create separate doc section for each Annotated*Configurator
> -----------------------------------------------------------
>
> Key: CDI-603
> URL: https://issues.jboss.org/browse/CDI-603
> Project: CDI Specification Issues
> Issue Type: Clarification
> Affects Versions: 2.0-EDR1
> Reporter: Matej Novotny
> Assignee: Antoine Sabot-Durand
>
> Currently, doc section 11.4.1 "AnnotatedTypeConfigurator SPI" covers all types of Annotated configurators (see below). That is:
> * {{AnnotatedTypeConfigurator}}
> * {{AnnotatedFieldConfigurator}}
> * {{AnnotatedMethodConfigurator}}
> * {{AnnotatedConstructorConfigurator}}
> * {{AnnotatedParameterConfigurator}}
> While {{AnnotatedTypeConfigurator}} is the entry point for all the others, I think it would be better to have a separate doc section for each configurator. It would make it much more readable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (CDI-603) Create separate doc section for each Annotated*Configurator
by Antoine Sabot-Durand (JIRA)
[ https://issues.jboss.org/browse/CDI-603?page=com.atlassian.jira.plugin.sy... ]
Antoine Sabot-Durand reassigned CDI-603:
----------------------------------------
Assignee: Antoine Sabot-Durand
> Create separate doc section for each Annotated*Configurator
> -----------------------------------------------------------
>
> Key: CDI-603
> URL: https://issues.jboss.org/browse/CDI-603
> Project: CDI Specification Issues
> Issue Type: Clarification
> Affects Versions: 2.0-EDR1
> Reporter: Matej Novotny
> Assignee: Antoine Sabot-Durand
>
> Currently, doc section 11.4.1 "AnnotatedTypeConfigurator SPI" covers all types of Annotated configurators (see below). That is:
> * {{AnnotatedTypeConfigurator}}
> * {{AnnotatedFieldConfigurator}}
> * {{AnnotatedMethodConfigurator}}
> * {{AnnotatedConstructorConfigurator}}
> * {{AnnotatedParameterConfigurator}}
> While {{AnnotatedTypeConfigurator}} is the entry point for all the others, I think it would be better to have a separate doc section for each configurator. It would make it much more readable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (CDI-603) Create separate doc section for each Annotated*Configurator
by Matej Novotny (JIRA)
Matej Novotny created CDI-603:
---------------------------------
Summary: Create separate doc section for each Annotated*Configurator
Key: CDI-603
URL: https://issues.jboss.org/browse/CDI-603
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 2.0-EDR1
Reporter: Matej Novotny
Currently, doc section 11.4.1 "AnnotatedTypeConfigurator SPI" covers all types of Annotated configurators (see below). That is:
* {{AnnotatedTypeConfigurator}}
* {{AnnotatedFieldConfigurator}}
* {{AnnotatedMethodConfigurator}}
* {{AnnotatedConstructorConfigurator}}
* {{AnnotatedParameterConfigurator}}
While {{AnnotatedTypeConfigurator}} is the entry point for all the others, I think it would be better to have a separate doc section for each configurator. It would make it much more readable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
Builder API merged
by Antoine Sabot-Durand
Hi all,
As decided yesterday, I merged the Builder/configurator code.It's certainly
not complete and some of the feedback (from John, Antonin and others)
should be considered, but it appeared easier to accept this PR to work from
a known and validated code.
I rebased PR 290 (Enhanced SE API) on it to make it clearer.
Antoine
8 years, 7 months
