November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-94) Archetype BOM needs to be updated to reflect Weld 1.0.1

by Steven Boscarine (JIRA)

Archetype BOM needs to be updated to reflect Weld 1.0.1 ------------------------------------------------------- Key: WELDX-94 URL: https://jira.jboss.org/jira/browse/WELDX-94 Project: Weld Extensions Issue Type: Task Components: Archetypes Reporter: Steven Boscarine Assignee: Steven Boscarine -- 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

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-739) maven archetype using outdated arquillian

by Gregory Gerard (JIRA)

maven archetype using outdated arquillian ----------------------------------------- Key: WELD-739 URL: https://jira.jboss.org/browse/WELD-739 Project: Weld Issue Type: Bug Components: Examples Reporter: Gregory Gerard Following the JEE6 instructions: http://seamframework.org/Documentation/WeldQuickstartForMavenUsers At the end, I got a project using Alpha3. Alpha4 is the current. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDRAD-25) The project created from the weld-jsf-jee archetype contains a qualifier type with @Target({FIELD, METHOD, PARAMETER})

by Alexey Kazakov (JIRA)

The project created from the weld-jsf-jee archetype contains a qualifier type with @Target({FIELD, METHOD, PARAMETER}) ---------------------------------------------------------------------------------------------------------------------- Key: WELDRAD-25 URL: https://jira.jboss.org/browse/WELDRAD-25 Project: Weld Archetypes Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Alexey Kazakov There is @Qualifier @Target({ElementType.FIELD, ElementType.METHOD, ElementType.PARAMETER}) @Retention(RetentionPolicy.RUNTIME) public @interface WidgetRepository {} But JSR-299 describes a qualifier type as: 2.3.2. Defining new qualifier types A qualifier type is a Java annotation defined as @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME). ... 10.1. Event types and qualifier types ... An event qualifier type is just an ordinary qualifier type as specified in Section 2.3.2, "Defining new qualifier types" with the exception that it may be declared @Target({FIELD, PARAMETER}). ... Though the spec doesn't require to treat such annotations (like @Target({FIELD, METHOD, PARAMETER})) as definition errors JBoss Tools mark them as errors. Please see https://jira.jboss.org/browse/JBIDE-7710 for details. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-10) Add ability to access a bean instance from a proxy

by Stuart Douglas (JIRA)

Add ability to access a bean instance from a proxy -------------------------------------------------- Key: CDI-10 URL: https://jira.jboss.org/browse/CDI-10 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Stuart Douglas There are occasions when it would be useful to access a bean instance directly from a proxy. This could be achieved by making all proxies assignable to an interface (say BeanProxy) that provides a getBeanInstance() method. Client code that needs access to the actual instance can check if the object is assignable to the BeanProxy interface and then call getBeanInstance() to get the actual instance if required. This is something that is probably more useful to extension writers than the end user, but there have already been a few requests on the weld forum about this so it is probably worth considering. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-18) cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives

by Mark Struberg (JIRA)

cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives --------------------------------------------------------------------------------- Key: CDI-18 URL: https://jira.jboss.org/browse/CDI-18 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Mark Struberg Fix For: 1.0 Currently the spec defines that <interceptors>, <decorators> and <alternatives> affect only the Bean Archives where they are configured in (via beans.xml). Thus if you e.g. enable an Alternative in a WEB-INF/beans.xml, it does NOT count for the jars in it's WEB-INF/lib folder! This is pretty unhandy because you would need to repackage all your jars in your WEB-INF/lib folder and add/expand the <alternatives> sections in their beans.xml. Needless to say that this is not only hard to do in a company build but is also impossibly to handle at deploy time in an OSGi environment! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-323) XSD missing enable element

by Jason Porter (JIRA)

XSD missing enable element -------------------------- Key: WELD-323 URL: https://jira.jboss.org/jira/browse/WELD-323 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Jason Porter Section 12.3 says there's an enable element, it's not there in the XSD. -- 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

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-717) @Observes(propagate = false) - stop event propagation after being handled by an observer

by Walter White (JIRA)

@Observes(propagate = false) - stop event propagation after being handled by an observer ---------------------------------------------------------------------------------------- Key: WELD-717 URL: https://jira.jboss.org/browse/WELD-717 Project: Weld Issue Type: Feature Request Components: Events Affects Versions: 1.0.1.Final Environment: any Reporter: Walter White I would like to have the ability to stop event propagation after it is handled by any observer only for certain situations. Is it possible to add a property to the annotation indicating whether the propagation should continue after being handled by the observer? Alternatively, would it be more concise to add a qualifier annotation which specifies the propagation. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-19) Ordering execution on Extensions

by Robson Saraiva Ximenes (JIRA)

Ordering execution on Extensions -------------------------------- Key: CDI-19 URL: https://jira.jboss.org/browse/CDI-19 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.1 Reporter: Robson Saraiva Ximenes Priority: Minor I believe the cdi portable extension could have the load order of extensions the same as it is registered; It is possible that one extension expect some previous preparation of beans from another extension -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-16) Improve EE 6 Managed Bean integration

by Pete Muir (JIRA)

Improve EE 6 Managed Bean integration ------------------------------------- Key: CDI-16 URL: https://jira.jboss.org/browse/CDI-16 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Reporter: Pete Muir Fix For: 1.1 Try to work out if we can improve on this. At least, we should clarify what happens if a CDI managed bean is annotated with @ManagedBean -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-15) Relax @Target annotation for CDI Scopes and Qualifiers

by Stuart Douglas (JIRA)

Relax @Target annotation for CDI Scopes and Qualifiers ------------------------------------------------------ Key: CDI-15 URL: https://jira.jboss.org/browse/CDI-15 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Stuart Douglas In some cases it may make sense to apply a scope or qualifier in a place that was not envisaged by the spec but that would be useful for a portable extension. For example, the @Constructs extension described at http://www.seamframework.org/Weld/PortableExtensionsPackage#H-BeanDeclara... is not possible because scopes and qualifiers can not be placed on constructors -- 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

13 years, 10 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010