December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDRAD-19) Weld Archetype uses deprecated expressions

by Ken Gullaksen (JIRA)

Weld Archetype uses deprecated expressions ------------------------------------------ Key: WELDRAD-19 URL: https://jira.jboss.org/jira/browse/WELDRAD-19 Project: Weld Archetypes Issue Type: Patch Reporter: Ken Gullaksen Priority: Minor When building projects generated with weld-jsf-jee-minimal archetype in apache-maven-3.0-alpha-7. The following warnings are encountered. [WARNING] The expression ${artifactId} is deprecated. Please use ${project.artifactId} instead. @ net.glxn:arquillian-playground:1.0.0-SNAPSHOT, /home/ken/dev/git/arquillian-playground/pom.xml [WARNING] The expression ${build.finalName} is deprecated. Please use ${project.build.finalName} instead. @ net.glxn:arquillian-playground:1.0.0-SNAPSHOT, /home/ken/dev/git/arquillian-playground/pom.xml [WARNING] The expression ${build.finalName} is deprecated. Please use ${project.build.finalName} instead. @ net.glxn:arquillian-playground:1.0.0-SNAPSHOT, /home/ken/dev/git/arquillian-playground/pom.xml -- 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

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-65) JEE Archetypes need to support JBoss AS 6.0 when it is released.

by Steven Boscarine (JIRA)

JEE Archetypes need to support JBoss AS 6.0 when it is released. ---------------------------------------------------------------- Key: WELDX-65 URL: https://jira.jboss.org/jira/browse/WELDX-65 Project: Weld Extensions Issue Type: Feature Request Reporter: Steven Boscarine Whenever a new milestone or the final version of JBoss AS 6.0 is released, we need to confirm that our archetypes work with it. -- 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

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDX-66) Update web.xml to servlet 3.0

by Steven Boscarine (JIRA)

Update web.xml to servlet 3.0 ----------------------------- Key: WELDX-66 URL: https://jira.jboss.org/jira/browse/WELDX-66 Project: Weld Extensions Issue Type: Sub-task Components: Archetypes Affects Versions: Archetypes 1.0.0-BETA1 Reporter: Steven Boscarine Assignee: Steven Boscarine JBoss AS 6.0.M1 only supported Servlet 2.5. We need to update the web.xml to support Servlet 3.0 in the JEE archetypes. -- 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

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-94) Archetype BOM needs to be updated to reflect Weld 1.0.1

by Steven Boscarine (JIRA)

Archetype BOM needs to be updated to reflect Weld 1.0.1 ------------------------------------------------------- Key: WELDX-94 URL: https://jira.jboss.org/jira/browse/WELDX-94 Project: Weld Extensions Issue Type: Task Components: Archetypes Reporter: Steven Boscarine Assignee: Steven Boscarine -- 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

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-739) maven archetype using outdated arquillian

by Gregory Gerard (JIRA)

maven archetype using outdated arquillian ----------------------------------------- Key: WELD-739 URL: https://jira.jboss.org/browse/WELD-739 Project: Weld Issue Type: Bug Components: Examples Reporter: Gregory Gerard Following the JEE6 instructions: http://seamframework.org/Documentation/WeldQuickstartForMavenUsers At the end, I got a project using Alpha3. Alpha4 is the current. -- 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

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDRAD-25) The project created from the weld-jsf-jee archetype contains a qualifier type with @Target({FIELD, METHOD, PARAMETER})

by Alexey Kazakov (JIRA)

The project created from the weld-jsf-jee archetype contains a qualifier type with @Target({FIELD, METHOD, PARAMETER}) ---------------------------------------------------------------------------------------------------------------------- Key: WELDRAD-25 URL: https://jira.jboss.org/browse/WELDRAD-25 Project: Weld Archetypes Issue Type: Bug Affects Versions: 1.0.0.Beta1 Reporter: Alexey Kazakov There is @Qualifier @Target({ElementType.FIELD, ElementType.METHOD, ElementType.PARAMETER}) @Retention(RetentionPolicy.RUNTIME) public @interface WidgetRepository {} But JSR-299 describes a qualifier type as: 2.3.2. Defining new qualifier types A qualifier type is a Java annotation defined as @Target({METHOD, FIELD, PARAMETER, TYPE}) and @Retention(RUNTIME). ... 10.1. Event types and qualifier types ... An event qualifier type is just an ordinary qualifier type as specified in Section 2.3.2, "Defining new qualifier types" with the exception that it may be declared @Target({FIELD, PARAMETER}). ... Though the spec doesn't require to treat such annotations (like @Target({FIELD, METHOD, PARAMETER})) as definition errors JBoss Tools mark them as errors. Please see https://jira.jboss.org/browse/JBIDE-7710 for details. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-10) Add ability to access a bean instance from a proxy

by Stuart Douglas (JIRA)

Add ability to access a bean instance from a proxy -------------------------------------------------- Key: CDI-10 URL: https://jira.jboss.org/browse/CDI-10 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Stuart Douglas There are occasions when it would be useful to access a bean instance directly from a proxy. This could be achieved by making all proxies assignable to an interface (say BeanProxy) that provides a getBeanInstance() method. Client code that needs access to the actual instance can check if the object is assignable to the BeanProxy interface and then call getBeanInstance() to get the actual instance if required. This is something that is probably more useful to extension writers than the end user, but there have already been a few requests on the weld forum about this so it is probably worth considering. -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-18) cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives

by Mark Struberg (JIRA)

cleanup Bean Archive behaviour (BDA) of interceptors, decorators and alternatives --------------------------------------------------------------------------------- Key: CDI-18 URL: https://jira.jboss.org/browse/CDI-18 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.0 Reporter: Mark Struberg Fix For: 1.0 Currently the spec defines that <interceptors>, <decorators> and <alternatives> affect only the Bean Archives where they are configured in (via beans.xml). Thus if you e.g. enable an Alternative in a WEB-INF/beans.xml, it does NOT count for the jars in it's WEB-INF/lib folder! This is pretty unhandy because you would need to repackage all your jars in your WEB-INF/lib folder and add/expand the <alternatives> sections in their beans.xml. Needless to say that this is not only hard to do in a company build but is also impossibly to handle at deploy time in an OSGi environment! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-323) XSD missing enable element

by Jason Porter (JIRA)

XSD missing enable element -------------------------- Key: WELD-323 URL: https://jira.jboss.org/jira/browse/WELD-323 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Jason Porter Section 12.3 says there's an enable element, it's not there in the XSD. -- 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

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (CDI-23) Allow BeanManager to be resolved as though you were in another bean archive

by Pete Muir (JIRA)

Allow BeanManager to be resolved as though you were in another bean archive --------------------------------------------------------------------------- Key: CDI-23 URL: https://issues.jboss.org/browse/CDI-23 Project: CDI Specification Issues Issue Type: Bug Reporter: Pete Muir Currently it's not possible to access beans as though you were in another bean manager, something that is useful for extensions to be able to do. For example, if I want to create a facade over the ELResolver, or access a particular configuration bean. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010