March 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1055) Exception when deploying EJB with duplicated Interceptors-annontation is not informative enough

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WELD-1055?page=com.atlassian.jira.plugin.... ] Jozef Hartinger updated WELD-1055: ---------------------------------- Fix Version/s: 2.0.0.Alpha2 > Exception when deploying EJB with duplicated Interceptors-annontation is not informative enough > ----------------------------------------------------------------------------------------------- > > Key: WELD-1055 > URL: https://issues.jboss.org/browse/WELD-1055 > Project: Weld > Issue Type: Enhancement > Affects Versions: 1.1.5.Final > Reporter: Simon Walter > Assignee: Marko Lukša > Priority: Minor > Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 > > > {noformat} > 13:11:12,017 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: > Failed to start service jboss.deployment.unit."xxx.ear".WeldService: > org.jboss.msc.service.StartException in service jboss.deployment.unit."xxx.ear".WeldService: > org.jboss.interceptor.proxy.InterceptorException: > Duplicate interceptor class definition when bindingorg.jboss.interceptor.reader.SimpleInterceptorMetadata@1db7445 on AROUND_INVOKE > {noformat} > The exception should contains information regarding the interceptor or the annotated class: > org.jboss.interceptor.builder.InterceptionModelImpl Line 162: {code}throw new InterceptorException("Duplicate interceptor class definition when binding" + interceptor + " on " + interceptionType.name());{code} should at least be > {code}throw new InterceptorException("Duplicate interceptor class definition when binding" + interceptor.getInterceptorClass().getClassName() + " on " + interceptionType.name());{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WELD-989) #{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide

by Marek Schmidt (Created) (JIRA)

#{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide ---------------------------------------------------------------------------------------------------------- Key: WELD-989 URL: https://issues.jboss.org/browse/WELD-989 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.2.Final Reporter: Marek Schmidt http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.htm... on the line "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>" and in the sentence "The unique identifier of the conversation may be obtained from the Conversation object, which has the EL bean name conversation. " -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (WELD-926) Weld Servlet still uses old Google Collections instead of Guava

by Sebastian Schaffert (JIRA)

Weld Servlet still uses old Google Collections instead of Guava --------------------------------------------------------------- Key: WELD-926 URL: https://issues.jboss.org/browse/WELD-926 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Sebastian Schaffert Even though WELD-564 is fixed, the latest version of Weld Servlet still includes the old Google Collections code. I think it should not contain the code at all and instead use a dependency on the library. Or at least update to the latest version of Guava. The problem is that it makes it impossible to use Guava in the same classpath as Weld. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (WELD-894) Around-Invoke interceptors should not wrap RuntimeException into WeldException

by Vlastimil Menčík (JIRA)

Around-Invoke interceptors should not wrap RuntimeException into WeldException ------------------------------------------------------------------------------ Key: WELD-894 URL: https://issues.jboss.org/browse/WELD-894 Project: Weld Issue Type: Feature Request Components: Interceptors and Decorators Affects Versions: 1.1.1.Final Reporter: Vlastimil Menčík Currently, org.jboss.weld.bean.InterceptorImpl always throws a WeldException when the invoked method throws an exception. This causes all exceptions in intercepted session bean methods to be treated as system exceptions by the EJB subsystem as WeldException is a system exception. If RuntimeExceptions were simply rethrown, such exceptions (annotated with javax.ejb.ApplicationException) could pass through the interceptor unwrapped and be recognized as application exception in the EJB sense. Of course, checked application exceptions are a bigger problem that would probably require a more sofisticated solution, that could be resolved later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
4
0 / 0

[JBoss JIRA] (WELD-1056) Weld-servlet brings transitive dependency on weld-build-config

by Lukáš Fryč (JIRA)

Lukáš Fryč created WELD-1056: -------------------------------- Summary: Weld-servlet brings transitive dependency on weld-build-config Key: WELD-1056 URL: https://issues.jboss.org/browse/WELD-1056 Project: Weld Issue Type: Bug Affects Versions: 1.1.4.Final Reporter: Lukáš Fryč This transitive dependency comes from {{weld-core-parent}}: https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b4... Since this config currently contains only checkstyle definitions, I suggest to remove this project dependency and use only {{maven-checkstyle-plugin}} dependency (which is currently configured too): https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b4... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (WELD-1062) Superclass of a modified AnnotatedType is ignored

by Gert Palok (JIRA)

Gert Palok created WELD-1062: -------------------------------- Summary: Superclass of a modified AnnotatedType is ignored Key: WELD-1062 URL: https://issues.jboss.org/browse/WELD-1062 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final, 2.0.0.Alpha1 Reporter: Gert Palok When modifying an AnnotatedType in ProcessAnnotatedType event, the resulting Bean instance will have Object as its superclass instead of the real superclass, causing inherited injection points to be ignored -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
10
0 / 0

[JBoss JIRA] (WELD-1000) Pass extension instances to bootstrap

by Pete Muir (Created) (JIRA)

Pass extension instances to bootstrap ------------------------------------- Key: WELD-1000 URL: https://issues.jboss.org/browse/WELD-1000 Project: Weld Issue Type: Feature Request Components: Java SE Support Affects Versions: 1.1.2.Final Reporter: Pete Muir If you are bootstrapping Weld yourself using new Weld() it would be nice to be able to pass in an already created Extension instance, rather than have the container instantiate it from META-INF/services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (WELD-954) URIs escaped twice in URLScanner

by Emond Papegaaij (JIRA)

URIs escaped twice in URLScanner -------------------------------- Key: WELD-954 URL: https://issues.jboss.org/browse/WELD-954 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.2.Final Reporter: Emond Papegaaij The fix for WELD-834 can cause spaces to be escaped twice in an URL. This leads to errors like: Error handling file /var/lib/jenkins/jobs/Wicket%2520Weld/workspace/wicket-cdi-examples/target/classes Notice how 'Wicket%20Weld' is escaped to 'Wicket%2520Weld'. https://github.com/papegaaij/wicket-cdi demonstrates the problem, clone the project in a directory with a space in the name, and run 'mvn install -Dwicket.version=1.5-RC5.1'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
9
0 / 0

[JBoss JIRA] Created: (WELD-910) Wrong example code - refering non-existent Weld#shutdown()

by Ondrej Zizka (JIRA)

Wrong example code - refering non-existent Weld#shutdown() ---------------------------------------------------------- Key: WELD-910 URL: https://issues.jboss.org/browse/WELD-910 Project: Weld Issue Type: Bug Components: Documentation Reporter: Ondrej Zizka http://docs.jboss.org/weld/reference/latest/en-US/html_single/#weld-se public static void main(String[] args) { WeldContainer weld = new Weld().initialize(); weld.instance().select(MyApplicationBean.class).get(); weld.shutdown(); } versus http://www.jarvana.com/jarvana/view/org/jboss/weld/weld-se/1.0.1-Final/we... >From which I conclude that the example's call to shutdown() is wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (WELD-937) Documentation issue - Instantiating abstract class

by Sebastian Wramba (JIRA)

Documentation issue - Instantiating abstract class -------------------------------------------------- Key: WELD-937 URL: https://issues.jboss.org/browse/WELD-937 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Final Reporter: Sebastian Wramba In chapter 4.10 the abstract class AsynchronousQualifier is defined. The next code sample instantiates this AsynchronousQualifier. However, instantiating an abstract class is not allowed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2012