Use NonContextualInjection in testcore
--------------------------------------
Key: WELDX-63
URL: https://jira.jboss.org/jira/browse/WELDX-63
Project: Weld Extensions
Issue Type: Bug
Components: CDI Test
Reporter: Aslak Knutsen
Test core should be changed to use non contextual injection
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
AnnotationInvokationHandler has no support for annotation default values
------------------------------------------------------------------------
Key: WELDX-56
URL: https://jira.jboss.org/jira/browse/WELDX-56
Project: Weld Extensions
Issue Type: Bug
Reporter: Stuart Douglas
Attachments: an-inv-hand-patch.diff
Attached patch supplies 'sensible' defaults for annotation values to prevent null pointer exceptions. It would be nice if it was possible to get the default values that were defined on the annotation type, but I am not sure how to do that (or even if it is possible).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
BeanImpl shoud be a public class
--------------------------------
Key: WELDX-107
URL: https://jira.jboss.org/browse/WELDX-107
Project: Weld Extensions
Issue Type: Bug
Affects Versions: 1.0.0.Alpha2
Reporter: alberto Gori
This code can't compile because BeanImpl is not a public class:
BeanBuilder<X> beanBuilder = new BeanBuilder<X>(at, bm);
beanBuilder.setBeanLifecycle(new BeanLifecycleImpl() {
@Override
public Object create(BeanImpl bean, CreationalContext creationalContext) {
...
}
});
This mean that BeanLifecycle interface is useless.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide an annotation scanner that can locate a particular annotation on a bean property
----------------------------------------------------------------------------------------
Key: WELDX-104
URL: https://jira.jboss.org/browse/WELDX-104
Project: Weld Extensions
Issue Type: Feature Request
Reporter: Shane Bryzak
The scanner needs to be able to locate a bean property (either a field, or getter method) that is annotated with a certain annotation type, and containing certain annotation attribute values. There is an implementation of this in Seam Security (see http://svn.jboss.org/repos/seam/modules/security/trunk/impl/src/main/java...), however it may be better to perform the attribute matching as a callback via an abstract method (and get rid of the AttributeValue stuff), e.g: public abstract boolean isMatch(T annotation);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Using AnnotatedTypeBuilder for ProcessAnnotatedType<T> event.setAnnotatedType() causes injection to fail globally.
------------------------------------------------------------------------------------------------------------------
Key: WELDX-100
URL: https://jira.jboss.org/jira/browse/WELDX-100
Project: Weld Extensions
Issue Type: Bug
Reporter: Lincoln Baxter III
Priority: Blocker
http://www.seamframework.org/Community/HowDoIRegisterAProducerForSubtypes...
Caused by: org.jboss.weld.DeploymentException: Injection point has unstatisfied dependencies. Injection point: field org.jboss.seam.faces.component.FormFieldProducer.log; Qualifiers: @javax.enterprise.inject.Default()
public class FormFieldTypingExtension implements Extension
{
public <T> void processAnnotatedType(@Observes final ProcessAnnotatedType<T> event)
{
AnnotatedTypeBuilder<T> builder = AnnotatedTypeBuilder.newInstance(event.getAnnotatedType());
for (AnnotatedField<?> f : event.getAnnotatedType().getFields())
{
if (f.isAnnotationPresent(InputField.class))
{
builder.overrideFieldType(f.getJavaMember(), Object.class);
}
}
event.setAnnotatedType(builder.create());
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Weld docs have incorrect details for setting up Weld Logger
-----------------------------------------------------------
Key: WELD-540
URL: https://jira.jboss.org/browse/WELD-540
Project: Weld
Issue Type: Task
Components: Documentation
Reporter: Pete Muir
Fix For: 1.0.2.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Port Weld slf4j extensions to Weld Extensions
---------------------------------------------
Key: WELDX-92
URL: https://jira.jboss.org/jira/browse/WELDX-92
Project: Weld Extensions
Issue Type: Feature Request
Reporter: Pete Muir
Fix For: Weld Extensions 1.0.0.Beta1
This will be made redundent by JBoss Logging 3 when available
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Global qualifier for signifying User
------------------------------------
Key: WELDX-108
URL: https://jira.jboss.org/browse/WELDX-108
Project: Weld Extensions
Issue Type: Feature Request
Reporter: Ken Finnigan
In the Seam I18N module we have a need to define Locale and TimeZone objects that are specific to a User Session. Would also be of benefit to other Seam modules to have a way to identify a User.
Options include @User and @Client, though @Client received support from within the developer mailing list and I would agree with using @Client
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira