November 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Commented: (WELD-18) Documentation issues

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-18?page=com.atlassian.jira.plugin... ] Dan Allen commented on WELD-18: ------------------------------- 1) The sentence style lists is Gavin's preferred style. Since he uses this approach in the spec, we use it in the ref guide too. 2) The Game source is going to be reviewed by Peter shortly. 3) JavaServer Faces is the correct name for JSF. 4) I'm clarifying the situation with remove methods. > Documentation issues > -------------------- > > Key: WELD-18 > URL: https://jira.jboss.org/jira/browse/WELD-18 > Project: Weld > Issue Type: Bug > Components: Documentation > Affects Versions: 1.0.0.PREVIEW1 > Reporter: Jozef Hartinger > Assignee: Dan Allen > Fix For: 1.0.0.GA > > > Here are some documentation issues: > 1.) Unordered lists: > In many places in documentation, I can see list items containing commas and periods at the end of line as well as "and" at the last but one item. These should not be there. Some occurences: 1.2.1, , 1.3.1, 1.3.2, etc > 2.) Outdated source code for Game.java in section 3.4 > 3.) Java ServerFaces instead of JavaServer Faces in 3.4.2 > 4.) Section 1.3.2 unclear > Third paragraph talks about a "remove" method or "remove method annotated with @Destructor". However, the source code excerpt that follows this paragraph shows "destroy" method annotated with "@Remove". -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (WELD-20) Document editing examples/build.properties file.

by Dan Allen (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-20?page=com.atlassian.jira.plugin... ] Dan Allen resolved WELD-20. --------------------------- Fix Version/s: 1.0.0.CR2 (was: 1.0.0.GA) Resolution: Done > Document editing examples/build.properties file. > ------------------------------------------------ > > Key: WELD-20 > URL: https://jira.jboss.org/jira/browse/WELD-20 > Project: Weld > Issue Type: Bug > Components: Documentation > Affects Versions: 1.0.0.PREVIEW1 > Reporter: Ondrej Skutka > Assignee: Dan Allen > Priority: Minor > Fix For: 1.0.0.CR2 > > > * In Chapter 3.1 (Getting stated with Web Beans..../Using JBoss AS 5) before "Now, you're ready to deploy your first example!" should be mentioned the need for editing the jboss.home property in examples/build.properties, just like it's mentioned for the jboss-as/build.properties file. > * Similar problem is in chapter 3.2 (Using Apache Tomcat 6.0). > * Is there a reason to edit tomcat.home in jboss-as/build.properties file? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-245) BeanManager.getInterceptorBindingTypeDefinition()

by Gavin King (JIRA)

BeanManager.getInterceptorBindingTypeDefinition() ------------------------------------------------- Key: WELD-245 URL: https://jira.jboss.org/jira/browse/WELD-245 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.0.CR1 Reporter: Gavin King Assignee: Pete Muir Fix For: 1.0.0.CR2 should be getInterceptorBindingDefinition() according to spec -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Updated: (WELD-92) Unify asynchronous execution interfaces

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WELD-92?page=com.atlassian.jira.plugin... ] Pete Muir updated WELD-92: -------------------------- Fix Version/s: 1.0.0.CR2 (was: 1.1.0.BETA1) Assignee: Pete Muir (was: David Allen) > Unify asynchronous execution interfaces > --------------------------------------- > > Key: WELD-92 > URL: https://jira.jboss.org/jira/browse/WELD-92 > Project: Weld > Issue Type: Feature Request > Components: Events, Infrastructure > Affects Versions: 1.0.0.BETA1 > Reporter: David Allen > Assignee: Pete Muir > Priority: Minor > Fix For: 1.0.0.CR2 > > > Since the spec identifies several cases of asynchronous tasks which must be performed, the RI should have a single, consistent set of interfaces to provide the executor services needed and the tasks to be performed. In Java SE 5 and 6, java.util.concurrent does provide useful interfaces for dealing with tasks which are executed by a separate service. It is recommended that the Executor interface be used as-is for those not requiring a timer (just execution in a separate thread of control), and perhaps the Delayed mix-in style interface for tasks requiring a timer or delay of execution. Alternatively, another executor interface can be chosen from SE to provide methods which take both the task to perform and the time delay. > In general, use of the java.util.concurrent interfaces, and even the implementations where possible, will reduce the amount of code in the RI and make better use of existing Java resources. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (WELD-212) Reread Deployment structure after reading classes, and also after discovering beans

by Pete Muir (JIRA)

Reread Deployment structure after reading classes, and also after discovering beans ----------------------------------------------------------------------------------- Key: WELD-212 URL: https://jira.jboss.org/jira/browse/WELD-212 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Critical Fix For: 1.0.0.CR2 Currently, we don't rescan, so if beans are found outside an existing BDA, they won't be registered -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-213) Check deployment for new bean, rather than assuming it comes from the current BDA

by Pete Muir (JIRA)

Check deployment for new bean, rather than assuming it comes from the current BDA --------------------------------------------------------------------------------- Key: WELD-213 URL: https://jira.jboss.org/jira/browse/WELD-213 Project: Weld Issue Type: Feature Request Components: Class Beans (Managed and Session) Reporter: Pete Muir Fix For: 1.0.0.CR2 Also, we need to check to see if it's a session bean in another module -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-241) BeanManager#resolveObserverMethods must return Set<ObserverMethod<? super T>> according to the latest spec

by Mark Struberg (JIRA)

BeanManager#resolveObserverMethods must return Set<ObserverMethod<? super T>> according to the latest spec ---------------------------------------------------------------------------------------------------------- Key: WELD-241 URL: https://jira.jboss.org/jira/browse/WELD-241 Project: Weld Issue Type: Feature Request Components: Resolution (Typesafe and by Name) Reporter: Mark Struberg but instead returns Set<ObserverMethod<T>> failure in the spec or the weld-api (used in the current TCK) ? -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-242) Interceptor interface must be updated to the lastest spec

by Mark Struberg (JIRA)

Interceptor interface must be updated to the lastest spec --------------------------------------------------------- Key: WELD-242 URL: https://jira.jboss.org/jira/browse/WELD-242 Project: Weld Issue Type: Bug Reporter: Mark Struberg e.g. getInterceptorBindingTypes() -> getInterceptorBindings() -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-203) Hard dependency on jsr250-api exists in Beans.getPostConstruct() and possibly elsewhere

by Pete Muir (JIRA)

Hard dependency on jsr250-api exists in Beans.getPostConstruct() and possibly elsewhere --------------------------------------------------------------------------------------- Key: WELD-203 URL: https://jira.jboss.org/jira/browse/WELD-203 Project: Weld Issue Type: Feature Request Components: Reflection layer Reporter: Pete Muir Fix For: 1.0.0.CR2 Run SE tests without jsr250-api in pom -- 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, 5 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2009