November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-730) WeldApplication should not assume FacesContext is always active

by Dan Allen (JIRA)

WeldApplication should not assume FacesContext is always active --------------------------------------------------------------- Key: WELD-730 URL: https://jira.jboss.org/browse/WELD-730 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Fix For: 1.1.0.Beta2 WeldApplication uses a forwarding wrapper around the delegate JSF Application object in order to get around the fact that BeanManager may not have been initialized at the time JSF is initializing. However, it assumes that the first use of Application will be during a faces request, where FacesContext is available. However, the JSF Application object is permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter). When this occurs, a NullPointerException in WeldApplication results. WeldApplication should skip the BeanManager lookup if the FacesContext is null. private BeanManager beanManager() { FacesContext facesContext; if (beanManager != null && (facesContext = FacesContext.getCurrentInstance()) != null) { // lookup BeanManager } } -- 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

14 years

2
10
0 / 0

[JBoss JIRA] Created: (WELD-754) Fix weld parent pom repository list

by Sivakumar Thyagarajan (JIRA)

Fix weld parent pom repository list ----------------------------------- Key: WELD-754 URL: https://jira.jboss.org/browse/WELD-754 Project: Weld Issue Type: Bug Reporter: Sivakumar Thyagarajan The current weld parent pom (org.jboss.weld:weld-parent:pom:17) has a reference to the public repository http://repository.jboss.org/nexus/content/groups/public with the id "jboss-snapshots-repository". As per the documentation in http://community.jboss.org/wiki/MavenRepository, the public repository group has both snapshots and releases. - If a snapshots-only repository was only intended, could we use the /snapshots hosted repository available at https://repository.jboss.org/nexus/content/repositories/snapshots/. - On the other hand if the /public repository group was intended (ie both releases and snapshot), since the public repo group contains both releases and snapshots, could we fix line 41 and line 55 to enable releases? https://github.com/weld/parent/blob/17/pom.xml#L55 We had an issue recently because of the disabling of releases in line 55. Maven 2.0.10 is the minimum maven version for weld. When GlassFish added the JBoss public repository group to its nexus repo, if I used maven 2.0.10, when a maven artifact from the JBoss repo was obtained, all references from that maven artifact used the repository definition in weld-parent:pom. Since releases were disabled in this repo definition, the released artifact residing in JBoss repo could not be found. Maven 2.2.1 fixes this issue(and also consults the repo definition in GlassFish) and we use 2.2.1 now. However, it would be useful to fix this discrepancy in weld-parent POM. Thanks. -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-149) Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest

by Gurkan Erdogdu (JIRA)

Bug in org.jboss.jsr299.tck.tests.context.NormalContextTest ----------------------------------------------------------- Key: CDITCK-149 URL: https://jira.jboss.org/jira/browse/CDITCK-149 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu org.jboss.jsr299.tck.tests.context.MyContextual is a SessionScoped bean.As spec section 6.6.4 it must be passivation capable, but it is not. therefore it throws Definition exception -- 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

14 years

2
6
0 / 0

[JBoss JIRA] Created: (WELDX-186) We need a ForwardingInjection point

by Jason Porter (JIRA)

We need a ForwardingInjection point ------------------------------------ Key: WELDX-186 URL: https://jira.jboss.org/browse/WELDX-186 Project: Weld Extensions Issue Type: Feature Request Components: Generic Beans Affects Versions: 1.1.0.Beta1 Reporter: Jason Porter We have * ForwardingBean * ForwardingInjectionTarget * ForwardingObserverMethod a ForwardingInjectionPoint would be handy if you need to redefine one (i.e. using InjectableMethod and ParameterValueRedefiner) -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-190) When testing observer methods inheritance, the TCK must account for EJB subclassing rules

by Marius Bogoevici (JIRA)

When testing observer methods inheritance, the TCK must account for EJB subclassing rules ----------------------------------------------------------------------------------------- Key: CDITCK-190 URL: https://jira.jboss.org/browse/CDITCK-190 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Marius Bogoevici org.jboss.jsr299.tck.tests.event.observer.enterprise.EnterpriseEventInheritenceTest LazyFarmer and IndirectStockWatcher must implement the respective observer interfaces, otherwise the observer methods are not part of the EJBs business interface (see EJB 3.1 spec 4.9.2.1 and https://jira.jboss.org/browse/WELD-746) -- 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

14 years

1
4
0 / 0

[JBoss JIRA] Created: (WELD-743) Serialization failure for Events injected into non-contextual instances

by Clint Popetz (JIRA)

Serialization failure for Events injected into non-contextual instances ----------------------------------------------------------------------- Key: WELD-743 URL: https://jira.jboss.org/browse/WELD-743 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta1 Reporter: Clint Popetz If a class has an @Inject Event, and a non-contextual instance of that class is injected programmatically via the BeanManager API, the resulting proxies will fail with a NPE when serialized. {noformat} java.lang.NullPointerException at org.jboss.weld.serialization.ContextualStoreImpl.putIfAbsent(ContextualStoreImpl.java:109) at org.jboss.weld.injection.WeldInjectionPoint$WeldInjectionPointSerializationProxy.<init>(WeldInjectionPoint.java:43) at org.jboss.weld.injection.FieldInjectionPoint$SerializationProxy.<init>(FieldInjectionPoint.java:197) at org.jboss.weld.injection.FieldInjectionPoint.writeReplace(FieldInjectionPoint.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1032) {noformat} -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (WELDX-185) Implement an interpolator for strings containing expressions

by Dan Allen (JIRA)

Implement an interpolator for strings containing expressions ------------------------------------------------------------ Key: WELDX-185 URL: https://jira.jboss.org/browse/WELDX-185 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Fix For: 1.0.0.Beta2 Since Weld Extensions has adopted the EL expression resolver, it's fitting that it also provides an interpolator for strings containing EL expression. Provide an interpolator that resolves EL expressions and position parameters in strings. This feature was available in Seam 2 [1]. Since it's not provided yet in Seam 3, we see it showing up as a utility in various modules, including the International [2] and REST [3] modules. We should consolidate this to a single, authoritative source. It should probably be made an interface with implementations that process specific expression languages, such as EL. For instance, one implementation might interpret MVEL. Just an idea. [1] http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2/src/main/... [2] https://github.com/seam/international/raw/master/impl/src/main/java/org/j... [3] https://github.com/seam/rest/raw/master/impl/src/main/java/org/jboss/seam... -- 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

14 years

2
12
0 / 0

[JBoss JIRA] Created: (WELDX-188) Provide utility to check if Type is assignable to another Type

by Dan Allen (JIRA)

Provide utility to check if Type is assignable to another Type -------------------------------------------------------------- Key: WELDX-188 URL: https://jira.jboss.org/browse/WELDX-188 Project: Weld Extensions Issue Type: Feature Request Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.Beta2 Often times when writing an extension, you need to know if one Type is assignable from another Type. This is a more sophisticated version of Class#isAssignableFrom(Class) which takes into account paramaterized types. given parameterized type Bean<N extends Number> then type Bean<Number> is assignable from type Bean<Integer> One area where this is useful is when checking if a bean type is more specific than another bean type. It's not sufficient to assume the bean type is a simple class. Something similar to what is provided by: http://google-gson.googlecode.com/svn-history/r442/trunk/gson/src/main/ja... -- 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

14 years

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-191) NarrowingBeanBuilder should support reading from Annotated

by Dan Allen (JIRA)

NarrowingBeanBuilder should support reading from Annotated ---------------------------------------------------------- Key: WELDX-191 URL: https://jira.jboss.org/browse/WELDX-191 Project: Weld Extensions Issue Type: Feature Request Reporter: Dan Allen Currently, NarrowingBeanBuilder supports reading only from AnnotatedType. However, if you are trying to create a specialized producer method based on information at an injection point, you need to be able to read from the more general Annotated type. In fact, the NarrowingBeanBuilder is currently not using any information from AnnotatedType that isn't provide by Annotated, so it's definition worth making more general. -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-187) Rename (or deprecate) @Veto in favor of @Vetoed

by Dan Allen (JIRA)

Rename (or deprecate) @Veto in favor of @Vetoed ----------------------------------------------- Key: WELDX-187 URL: https://jira.jboss.org/browse/WELDX-187 Project: Weld Extensions Issue Type: Feature Request Affects Versions: 1.0.0.Beta1 Reporter: Dan Allen Fix For: 1.0.0.Beta2 All the major type annotations in CDI are adjectives or nouns. For example: @Named @Decorator @Typed @Model @*Scoped @Alternative However, @Veto is an action (verb). Thus, to be consistent with the CDI naming convention, the @Veto annotation should be renamed to @Vetoed. -- 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

14 years

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