January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-353) MDBs throw DeploymentException

by Nicklas Karlsson (JIRA)

MDBs throw DeploymentException ------------------------------ Key: WELD-353 URL: https://jira.jboss.org/jira/browse/WELD-353 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Class Beans (Managed and Session) Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Fix For: 1.0.1.CR1 -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-359) EJBs without local interfaces throws NPEs

by Nicklas Karlsson (JIRA)

EJBs without local interfaces throws NPEs ----------------------------------------- Key: WELD-359 URL: https://jira.jboss.org/jira/browse/WELD-359 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson EJBs without local interfaces appear to throw NPE: java.lang.NullPointerException at org.jboss.weld.ejb.InternalEjbDescriptor.<init>(InternalEjbDescriptor.java:48) at org.jboss.weld.ejb.EjbDescriptors.add(EjbDescriptors.java:111) at org.jboss.weld.ejb.EjbDescriptors.addAll(EjbDescriptors.java:166) at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:78) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:197) at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:174) at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:295) at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.initialize(BootstrapBean.java:136) -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-351) Provide relevant failure message when using old maven

by Ondrej Skutka (JIRA)

Provide relevant failure message when using old maven ----------------------------------------------------- Key: WELD-351 URL: https://jira.jboss.org/jira/browse/WELD-351 Project: Weld Issue Type: Feature Request Components: Infrastructure Affects Versions: 1.0.0.GA Environment: Maven version: 2.0.8 Reporter: Ondrej Skutka Fix For: 1.0.1.CR1 When building (core) with maven <2.0.10, a fatal error is thrown with message "Failed to validate POM for project org.jboss.weld:weld-core" before the maven-enforcer-plugin comes into use. So the message doesn't indicate that the problem is in fact in maven's version. I suggest using maven's <prerequisite> tag to enforce maven >=2.0.10. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-283) Documentation issues

by Jozef Hartinger (JIRA)

Documentation issues -------------------- Key: WELD-283 URL: https://jira.jboss.org/jira/browse/WELD-283 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.0.GA Reporter: Jozef Hartinger Fix For: 1.0.0.GA Global problems - a significant number of links is missing the value of href attribute (these links point nowhere) - the JBoss AS 5.2.x have become obsolete recently (changed to 6.0.0.M1) - the documentation references this obsolete version. i.e. Chapters 6, section 18.1 - there is a number of unnecessary blank pages in the PDF version - Section 2.1.2. Scope - there is a missing *want* in the Note in the sentence: "If you don't the bean to live in the session indefinitely..." - Section 6.2 Deploying to JBoss AS - there is a missing space in the sentence "Create a new file namedlocal.build.properties ..." - Section 6.2 Deploying to JBoss AS - is not finished - there is a TODO at the very end of the section - Secion 7.1. The numberguess example in depth - the numbers which mark an important line of a code sample (1), (2), etc... are broken in the second sample of the section (web.xml). They are placed on wrong places (wrong line, beggining of the line instead of end) and they are followed by "ml_plain">" in the HTML version. Besides, I would emphasize more the benefit of the typesafe resolution i.e. in section 1.2 - (that all the unsatisfied and ambiguous dependencies are discovered at the deployment time - you do not need to click anything to find out that the you set some dependencies wrong - more formal verification) - I don't say it is not there already. I just had a feeling that it is not stated explicitly enough. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-320) JBoss links & version invalid in getting started guide

by Steven Boscarine (JIRA)

JBoss links & version invalid in getting started guide ------------------------------------------------------ Key: WELD-320 URL: https://jira.jboss.org/jira/browse/WELD-320 Project: Weld Issue Type: Bug Components: Documentation Reporter: Steven Boscarine The download link is wrong. Also, isn't it supposed to be JBoss 6? <p> <a id="jbossas"> To deploy the examples to JBoss AS, you'll need </a><a class="ulink" href="">JBoss AS 5.2.0.Beta1</a> or above. If a release of the JBoss AS 5.2 line isn't yet available, you can download a <a class="ulink" href="">nightly snapshot</a>. The reason JBoss AS 5.2.0.Beta1 or above is required is because it's the first release that has both CDI and Bean Validation support built-in, making it close enough to Java EE 6 to run the examples. The good news is that there are no additional modifications you have to make to the server. It's ready to go! </p> -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-278) Fix distribution management so that release plugin transforms properly

by Pete Muir (JIRA)

Fix distribution management so that release plugin transforms properly ---------------------------------------------------------------------- Key: WELD-278 URL: https://jira.jboss.org/jira/browse/WELD-278 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.1.CR1 -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (WELD-91) Document a strategy for writing a unit test which guards against performance blackspots reoccurring

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-91?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-91: -------------------------- Fix Version/s: 1.0.2.CR1 (was: 1.0.1.CR1) > Document a strategy for writing a unit test which guards against performance blackspots reoccurring > --------------------------------------------------------------------------------------------------- > > Key: WELD-91 > URL: https://jira.jboss.org/jira/browse/WELD-91 > Project: Weld > Issue Type: Task > Components: Testing Infrastructure (Mocks and Harness Integration) > Reporter: Pete Muir > Fix For: 1.0.2.CR1 > > > When someone reports/isolates a performance issue, we need to write a unit test to stop it reoccurring (a regression occurring). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-61) Test errors creating client proxy

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-61?page=com.atlassian.jira.plugin... ] Pete Muir commented on WELD-61: ------------------------------- Possibly I was looking at the coverage report, or more possibly the fact that the exception above is wrong according to the spec, but we weren't testing this. > Test errors creating client proxy > --------------------------------- > > Key: WELD-61 > URL: https://jira.jboss.org/jira/browse/WELD-61 > Project: Weld > Issue Type: Task > Components: Scopes & Contexts > Reporter: Pete Muir > Assignee: Nicklas Karlsson > Priority: Minor > Fix For: 1.0.1.CR1 > > > This block > catch (InstantiationException e) > { > throw new RuntimeException("Could not instantiate client proxy for " + bean, e); > } > catch (IllegalAccessException e) > { > throw new RuntimeException("Could not access bean correctly when creating client proxy for " + bean, e); > } > isn't tested -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-375) Set Up Weld functional tests to run against JBoss AS 6

by Martin Gencur (JIRA)

Set Up Weld functional tests to run against JBoss AS 6 ------------------------------------------------------ Key: WELD-375 URL: https://jira.jboss.org/jira/browse/WELD-375 Project: Weld Issue Type: Task Components: Examples Reporter: Martin Gencur Assignee: Martin Gencur This task was created to track creating of Hudson job that will be periodically executing functional test from Weld. This job will be triggered by nightly build of Weld. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (WELD-61) Test errors creating client proxy

by Nicklas Karlsson (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-61?page=com.atlassian.jira.plugin... ] Nicklas Karlsson commented on WELD-61: -------------------------------------- Probably just you discovering the EMMA plugin and ignoring the fast that if we opened JIRAs for all segments that are not covered we would now be on 4-digit issue numbers? ;-) > Test errors creating client proxy > --------------------------------- > > Key: WELD-61 > URL: https://jira.jboss.org/jira/browse/WELD-61 > Project: Weld > Issue Type: Task > Components: Scopes & Contexts > Reporter: Pete Muir > Assignee: Nicklas Karlsson > Priority: Minor > Fix For: 1.0.1.CR1 > > > This block > catch (InstantiationException e) > { > throw new RuntimeException("Could not instantiate client proxy for " + bean, e); > } > catch (IllegalAccessException e) > { > throw new RuntimeException("Could not access bean correctly when creating client proxy for " + bean, e); > } > isn't tested -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010