October 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-173) Regenerate signature tests for CDI API 1.0-SP2

by Pete Muir (JIRA)

Regenerate signature tests for CDI API 1.0-SP2 ---------------------------------------------- Key: CDITCK-173 URL: https://jira.jboss.org/browse/CDITCK-173 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Signature Tests Reporter: Pete Muir Fix For: 1.0.2.CR3 -- 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

15 years, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (WELD-51) Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-51?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-51: -------------------------- Fix Version/s: 1.1.0.CR1 (was: 1.1.0.Beta2) > Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl > ----------------------------------------------------------------------------------------- > > Key: WELD-51 > URL: https://jira.jboss.org/browse/WELD-51 > Project: Weld > Issue Type: Feature Request > Components: Reflection layer > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1.0.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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (WELD-53) Full review of built in Reflection layer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-53?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated WELD-53: -------------------------- Fix Version/s: 1.1.0.CR1 (was: 1.1.0.Beta2) > Full review of built in Reflection layer > ---------------------------------------- > > Key: WELD-53 > URL: https://jira.jboss.org/browse/WELD-53 > Project: Weld > Issue Type: Feature Request > Components: Resolution (Typesafe and by Name) > Reporter: Pete Muir > Fix For: 1.1.0.CR1 > > > A few things: > * should we use javassist? > * need a full review of how we deal with Annotated* -- 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

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELDX-179) Introduce @Qualified to have package name prepended to @Named value

by Dan Allen (JIRA)

Introduce @Qualified to have package name prepended to @Named value ------------------------------------------------------------------- Key: WELDX-179 URL: https://jira.jboss.org/browse/WELDX-179 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Priority: Minor Fix For: TBC @Named gives the bean a name equal to the annotation value property or, if one is not specified, the decapitalized simple name of the type. This behavior is precisely what the majority of developers will appreciate. However, framework writers should avoid stomping on the root bean namespace, instead assigning qualified names to their built-in components. The motivation is the same as qualifying Java types. One way to accomplish this would be to include the package name in the name specified in the @Named annotation: @Named("org.jboss.seam.security.Identity") public class Identity ... { ... } However, this is not in the spirit of type-safety. As an alternative, Weld X can introduce an annotation which indicates that the bean name be qualified to the package in which the type resides. @Qualified @Named public class Identity ... { ... } This allows the bean name to be defaulted and keeps the package out of a string. -- 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

15 years, 5 months

2
8
0 / 0

[JBoss JIRA] Created: (CDI-17) Change name of the @Observes Reception attribute to "notified"

by Dan Allen (JIRA)

Change name of the @Observes Reception attribute to "notified" -------------------------------------------------------------- Key: CDI-17 URL: https://jira.jboss.org/browse/CDI-17 Project: CDI Specification Issues Issue Type: Feature Request Components: Javadoc and API Affects Versions: 1.0 Reporter: Dan Allen Priority: Minor Fix For: 1.1 As of the CDI 1.0 specification, the name of the Reception attribute on @Observes is "receive". The patch release of the API (SP1) changes the name to "notifyObserver", so a change is already being considered. Therefore, I'd like to suggest a better name that would read more fluently. That name is "notified". Let us compare the three cases: 1. @Observes(receive = IF_EXISTS) 2. @Observes(notifyObserver = IF_EXISTS) 3. @Observes(notified = IF_EXISTS) Of the three, notifyObserver breaks the flow of the sentence the most. On the other hand, notified reads nicely, including with the TransactionPhase attribute included: @Observes(notified = IF_EXISTS, during = TransactionPhase.AFTER_SUCCESS) -- 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

15 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-740) NCDFE in Introspection process should not cause deployment to fail

by Stuart Douglas (JIRA)

NCDFE in Introspection process should not cause deployment to fail ------------------------------------------------------------------ Key: WELD-740 URL: https://jira.jboss.org/browse/WELD-740 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta1 Reporter: Stuart Douglas Currently a NoClassDefFoundError in the introspection process causes the deployment to fail, I think that it should just log a warning and continue, so that we can support optional dependencies. Currently the exception is thrown is: Caused by: java.lang.NoClassDefFoundError: Lorg/jboss/seam/persistence/PersistenceContexts; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredFields(Class.java:1743) at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:115) at org.jboss.weld.util.reflection.SecureReflections$4.work(SecureReflections.java:111) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAndWrap(SecureReflectionAccess.java:67) at org.jboss.weld.util.reflection.SecureReflections.getDeclaredFields(SecureReflections.java:110) at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.java:177) at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:140) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:50) at org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:38) at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:592) -- 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

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (WELDX-184) Performance on startup of weldx is extremely slow

by Lincoln Baxter III (JIRA)

Performance on startup of weldx is extremely slow ------------------------------------------------- Key: WELDX-184 URL: https://jira.jboss.org/browse/WELDX-184 Project: Weld Extensions Issue Type: Quality Risk Reporter: Lincoln Baxter III 17:54:29,059 WARNING [ServiceLoader] Could not load service class org.jboss.weld.extensions.interceptor.InterceptorExtension 17:54:41,769 INFO [org.jboss.weld.extensions.core.CoreExtension] Preventing class com.ocpsoft.socialpm.domain.user.User from being installed as bean due to @Veto annotation A full 12, almost 13 seconds required during part of weldx bootup. Seems like something we could improve. -- 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

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-176) Weldx has a compile scoped dependency on jta, should be scope <test>

by Stuart Douglas (JIRA)

Weldx has a compile scoped dependency on jta, should be scope <test> -------------------------------------------------------------------- Key: WELDX-176 URL: https://jira.jboss.org/browse/WELDX-176 Project: Weld Extensions Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Stuart Douglas Fix For: 1.0.0.Beta2 -- 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

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (WELDX-177) add getSingleResult() to PropertyQuery

by Dan Allen (JIRA)

add getSingleResult() to PropertyQuery -------------------------------------- Key: WELDX-177 URL: https://jira.jboss.org/browse/WELDX-177 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Fix For: 1.0.0.Beta2 PropertyQuery should offer the method getSingleResult() for the same reason it exists in the JPA Query interface: to fetch a single result but also assert that there is only one result to be fetched. If more than one property is matched when getSingleResult() is called, an exception will result. Using getFirstResult() to return exactly one result is inappropriate (and could lead to bugs) because it could hide the fact that multiple properties are being inadvertently matched. As a workaround, the developer would currently have to run getResultList() to ensure only one property matches. Offering a getSingleResult() would resolve these issues. See http://download.oracle.com/javaee/6/api/javax/persistence/Query.html#getS... -- 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

15 years, 5 months

2
5
0 / 0

[JBoss JIRA] Commented: (WELD-17) Brazilian Portuguese translation of Web Beans Reference Documentation

by Bruno Leonardo Gonçalves (JIRA)

[ https://jira.jboss.org/browse/WELD-17?page=com.atlassian.jira.plugin.syst... ] Bruno Leonardo Gonçalves commented on WELD-17: ---------------------------------------------- I suggest changing the summary of this issue for "Brazilian Portuguese Translation of Weld Reference Guide". Thanks. > Brazilian Portuguese translation of Web Beans Reference Documentation > --------------------------------------------------------------------- > > Key: WELD-17 > URL: https://jira.jboss.org/browse/WELD-17 > Project: Weld > Issue Type: Task > Components: Documentation > Reporter: Joao Viragine > Fix For: TBC > > > I would like to translate Web Beans Reference Documentation to Brazilian Portuguese. (pt-BR) -- 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

15 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2010