November 2009 - weld-issues - Jboss List Archives

[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

16 years, 2 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

16 years, 2 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-251) Maven Archetype for Weld Projects

by Steven Boscarine (JIRA)

Maven Archetype for Weld Projects --------------------------------- Key: WELD-251 URL: https://jira.jboss.org/jira/browse/WELD-251 Project: Weld Issue Type: Feature Request Reporter: Steven Boscarine Getting started with Weld would be a lot easier if weld had maven archetypes that users could start their projects with. I can create a version very quickly I'll need a place to commit the code. Before it's ready for public consumption the code will need to be pushed to public maven repos. -- 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

16 years, 2 months

4
12
0 / 0

[JBoss JIRA] Created: (WELD-306) Errors thrown by lifecycle events or added to lifecycle events aren't being reported

by Pete Muir (JIRA)

Errors thrown by lifecycle events or added to lifecycle events aren't being reported ------------------------------------------------------------------------------------ Key: WELD-306 URL: https://jira.jboss.org/jira/browse/WELD-306 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir *.deployment.lifecycle.broken.addDefinitionError.AddDefinitionErrorTest.testObserverDefinitionErrorTreatedAsDefinitionError *.deployment.lifecycle.broken.addDeploymentProblem.AddDeploymentProblemTest.testObserverDeploymentProblemTreatedAsDeploymentError *.deployment.lifecycle.broken.exeptionInAfterBeanDiscoveryObserver.AfterBeanDiscoveryObserverExecutionFailureTest.testObserverFailureTreatedAsDefinitionError *.deployment.lifecycle.broken.exeptionInAfterBeanValidationObserver.AfterDeploymentValidationObserverExecutionFailureTest.testObserverFailureTreatedAsDeploymentError Weld is not rethrowing the exceptions due to incorrectly overridden fire method -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-262) Nuke ConcurrentCache

by Pete Muir (JIRA)

Nuke ConcurrentCache -------------------- Key: WELD-262 URL: https://jira.jboss.org/jira/browse/WELD-262 Project: Weld Issue Type: Task Reporter: Pete Muir Fix For: 1.0.1.CR1 Replace ComputeMap from Google Collections -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-282) Use maven-license-plugin

by Pete Muir (JIRA)

Use maven-license-plugin ------------------------ Key: WELD-282 URL: https://jira.jboss.org/jira/browse/WELD-282 Project: Weld Issue Type: Task Reporter: Pete Muir -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (WELD-295) Conversation are only for JSF: Please may then available for plain servlets and JSP

by Francisco Jose Peredo Noguez (JIRA)

Conversation are only for JSF: Please may then available for plain servlets and JSP ----------------------------------------------------------------------------------- Key: WELD-295 URL: https://jira.jboss.org/jira/browse/WELD-295 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.0.GA Reporter: Francisco Jose Peredo Noguez Aacording to Weld the docs: The conversation context is active during any JSF request. and at the code of org.jboss.weld.servlet.ConversationPropagationFilter One can read FIXME This filter is specifically for JSF and should be repackaged or split up to support non-JSF environments. All that indicates that conversations are only for JSF. Please make them available for plain servlets (and JSPs) -- 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

16 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-313) create() method of container Bean implementations should be reproducible with user Bean implementations

by Gavin King (JIRA)

create() method of container Bean implementations should be reproducible with user Bean implementations ------------------------------------------------------------------------------------------------------- Key: WELD-313 URL: https://jira.jboss.org/jira/browse/WELD-313 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Affects Versions: 1.0.0.GA Reporter: Gavin King Priority: Critical Fix For: 1.0.1.CR1 ManagedBean.create() looks like this: public T create(CreationalContext<T> creationalContext) { T instance = getInjectionTarget().produce(creationalContext); getInjectionTarget().inject(instance, creationalContext); if (isInterceptionCandidate() && (hasCdiBoundInterceptors() || hasDirectlyDefinedInterceptors())) { InterceptionUtils.executePostConstruct(instance); } else { getInjectionTarget().postConstruct(instance); } return instance; } The code that is aware of interceptors needs to be sucked into InjectionTarget.postConstruct(), since a portable extension can't easily reproduce that logic. create() should look like: public T create(CreationalContext<T> creationalContext) { T instance = getInjectionTarget().produce(creationalContext); getInjectionTarget().inject(instance, creationalContext); getInjectionTarget().postConstruct(instance); return instance; } Same goes for destroy(). The implementations of create() and destroy() in SessionBean are even worse. In this case, InjectionTarget.produce() seems to be doing something completely wrong and broken. It is supposed to return a non-container-managed object. EJB should be the thing calling it, not Weld directly. -- 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

16 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-255) Session bean injection tests fail when run incontainer

by Pete Muir (JIRA)

Session bean injection tests fail when run incontainer ------------------------------------------------------ Key: WELD-255 URL: https://jira.jboss.org/jira/browse/WELD-255 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Reporter: Pete Muir Fix For: 1.0.1.CR1 But bizarrely, pass when run on their own. org.jboss.jsr299.tck.tests.lookup.injection.enterprise.SessionBeanInjectionOrderingTest.testPostConstructCalledAfterInitializerOfSuperclass() org.jboss.jsr299.tck.tests.lookup.injection.enterprise.SessionBeanInjectionOrderingTest.testInitializerCalledAfterResourceInjection() -- 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

16 years, 2 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009