May 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-504) Lifecycle event exception logging lacks info

by David Allen (JIRA)

Lifecycle event exception logging lacks info -------------------------------------------- Key: WELD-504 URL: https://jira.jboss.org/jira/browse/WELD-504 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: David Allen Assignee: David Allen Priority: Blocker Fix For: 1.0.2.CR1 The logging of exceptions accumulated during lifecycle events is only listing the exception messages. The stack traces are also needed along with original causes. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-535) Injection does not occur into a scoped (proxied) bean the observer method is final

by Dan Allen (JIRA)

Injection does not occur into a scoped (proxied) bean the observer method is final ---------------------------------------------------------------------------------- Key: WELD-535 URL: https://jira.jboss.org/browse/WELD-535 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.0.1.Final Reporter: Dan Allen If the observer method of a bean is private, and the bean which contains it has a scope (it's proxied), then injection into the bean does not occur. For example, the injection points are null when the following observer is invoked: @SessionScoped public class SampleObserver implements Serializable { @Inject SampleHelper helper; private void observes(@Observes final SampleBean bean) { System.out.println("Did injection occur? " + (helper = null ? "no" : "yes")); } } Prints: Did injection occur? no -- 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, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (WELD-525) weld-core-bom specifies invalid groupId for ch.qos.cal10n:cal10n-api

by Asgeir Frimannsson (JIRA)

weld-core-bom specifies invalid groupId for ch.qos.cal10n:cal10n-api -------------------------------------------------------------------- Key: WELD-525 URL: https://jira.jboss.org/jira/browse/WELD-525 Project: Weld Issue Type: Bug Components: Infrastructure Affects Versions: 1.0.1.Final Reporter: Asgeir Frimannsson In the dependencyManagement section of weld-core-bom, the groupId for cal10n-api is specified as 'ch.qos'. The correct groupId should be 'ch.qos.cal10n'. http://repo2.maven.org/maven2/ch/qos/cal10n/cal10n-api/ http://oss.sonatype.org/index.html#nexus-search;quick~cal10n-api (no matches in jboss nexus instance) This is also the case for weld trunk. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDINT-62) Add throws clause to Deployment.loadBeanDeploymentArchive javadoc

by Flavia Rainone (JIRA)

Add throws clause to Deployment.loadBeanDeploymentArchive javadoc ----------------------------------------------------------------- Key: WELDINT-62 URL: https://jira.jboss.org/browse/WELDINT-62 Project: Weld Integration Issue Type: Task Reporter: Flavia Rainone The Deployment.loadBeanDeploymentArchive Javadoc does not specify what behaviour is expected in case no BDA is found. (i.e, in case beanClass is not visible to current Deployment). The method should throw an exception, to be defined in the Javadoc. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-534) Update Maven plugins

by Pete Muir (JIRA)

Update Maven plugins -------------------- Key: WELD-534 URL: https://jira.jboss.org/browse/WELD-534 Project: Weld Issue Type: Task Components: Infrastructure 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-509) weld-parent POM should specify maven standard directory for docbook folder

by Lincoln Baxter III (JIRA)

weld-parent POM should specify maven standard directory for docbook folder -------------------------------------------------------------------------- Key: WELD-509 URL: https://jira.jboss.org/jira/browse/WELD-509 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Lincoln Baxter III To follow the Maven way, we want to put the docbook source in src/main/docbook. However, Weld is configured to put the sources right at the root. current Weld way: docs/reference/en-US/*.xml the way it should be: docs/reference/src/main/docbook/en-US/*.xml The <sourceDirectory> element needs to be added: <plugin> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jdocbook-plugin</artifactId> ... <configuration> <sourceDirectory>${project.basedir}/src/main/docbook</sourceDirectory> <sourceDocumentName>master.xml</sourceDocumentName> <masterTranslation>en-US</masterTranslation> ... </configuration> ... </plugin> -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-536) SFSB proxies not serializable in JBoss AS

by David Allen (JIRA)

SFSB proxies not serializable in JBoss AS ----------------------------------------- Key: WELD-536 URL: https://jira.jboss.org/browse/WELD-536 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Reporter: David Allen The deserialization of a client proxy for a stateful session bean fails in JBoss AS. It appears to be serializing Microkernel classes in the object graph which are naturally not available to the classloader of the test application during deserialization. This is demonstrated by test org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testSerializeSFSB(). -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-527) Include emma plugin in weld-parent

by Jordan Ganoff (JIRA)

Include emma plugin in weld-parent ---------------------------------- Key: WELD-527 URL: https://jira.jboss.org/browse/WELD-527 Project: Weld Issue Type: Feature Request Components: Testing Infrastructure (Mocks and Harness Integration) Environment: maven 2.0.10 Reporter: Jordan Ganoff Priority: Minor As per Pete Muir's request, please add the necessary emma-maven-plugin configuration to weld-parent. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-530) NPE possible in AnnotationLiteral hashCode()

by Nicklas Karlsson (JIRA)

NPE possible in AnnotationLiteral hashCode() -------------------------------------------- Key: WELD-530 URL: https://jira.jboss.org/browse/WELD-530 Project: Weld Issue Type: Bug Components: CDI API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson the implementation of hashCode() doesn't take into account the possibility of Object value = invoke(member, this); returning null, causing failure in else { memberValueHashCode = value.hashCode(); } -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-495) readme.txt needs to be updated

by asookazian (JIRA)

readme.txt needs to be updated ------------------------------ Key: WELD-495 URL: https://jira.jboss.org/jira/browse/WELD-495 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Environment: Windows XP, Weld 1.0.1-final, Maven 2.2.1, JBoss AS 6.0.0.M2 Reporter: asookazian Priority: Trivial The readme.txt for weld-1.0.1-final states "Currently, you must use JBoss AS 5.2.0.Beta1 (use nightly builds until released) or above deploy the provided examples out of the box." The current recommended version of JBoss AS is 6.0.0.M2. Also "Other application servers may be supported by the examples in the 1.0.0 release" needs to be fixed as well as this readme.txt is for 1.0.1-final. So perhaps the app servers need to be stated now. -- 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, 7 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2010