September 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1099) Cannot invoke web service resource declared with @WebServiceRef

by Martin Kouba (JIRA)

Martin Kouba created WELD-1099: ---------------------------------- Summary: Cannot invoke web service resource declared with @WebServiceRef Key: WELD-1099 URL: https://issues.jboss.org/browse/WELD-1099 Project: Weld Issue Type: Bug Affects Versions: 1.1.6.Final Reporter: Martin Kouba ... results in following error: {noformat} org.jboss.weld.exceptions.NullInstanceException: WELD-000044 Unable to obtain instance from null {noformat} -- 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

11 years, 5 months

2
1
0 / 0

[JBoss JIRA] (WELD-1177) Built-in InjectionPoint bean not injected for stateless session bean

by Martin Kouba (JIRA)

11 years, 5 months

3
4
0 / 0

[JBoss JIRA] (WELD-1200) Implement CDI-43

by Jozef Hartinger (JIRA)

11 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (WELD-862) Interceptors not threadsafe

by Sebastian Schaffert (JIRA)

Interceptors not threadsafe --------------------------- Key: WELD-862 URL: https://issues.jboss.org/browse/WELD-862 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.0.Final Environment: Jetty, Weld Filter Reporter: Sebastian Schaffert I am trying to implement an "@Asynchronous" interceptor that runs methods annotated with the @Asynchronous annotation in a separate thread. The implementation of the interceptor currently looks as follows: private static final ThreadGroup asyncMethods = new ThreadGroup("asynchronous method invocations"); @AroundInvoke public Object manageAsynchronous(final InvocationContext ctx) throws Exception { final UUID threadID = UUID.randomUUID(); Runnable r = new Runnable() { @Override public void run() { try { log.debug("asynchronous method invocation of {}.{} (Thread ID {})",new Object[] {ctx.getTarget().getClass().getName(),ctx.getMethod().getName(), threadID}); Object val = ctx.proceed(); if(val != null) { log.debug("asynchronous method invocation of {}.{} (Thread ID {}) returned value {}",new Object[] {ctx.getClass().getName(),ctx.getMethod().getName(), threadID, val}); } } catch(Exception ex) { log.error("exception during asynchronous method invocation",ex); } } }; Thread t = new Thread(asyncMethods,r); t.setName("asynchronous method invocation of "+ctx.getTarget().getClass().getName()+ctx.getMethod().getName() + " (Threaad ID " + threadID+")"); t.start(); return null; } Now the problem is that the interceptor is called infinitely often. The reason is that the annotated method forks a new thread and then returns instantly, setting the variable "currentPosition" in SimpleInterceptorChain back to the value 0 (in a "finally" block). So when the proceed() method is called inside the thread, the interceptor chain again points to the first interceptor in the chain and it all repeats infinitely. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

6
8
0 / 0

[JBoss JIRA] (WELD-1204) Implement CDI-227

by Jozef Hartinger (JIRA)

11 years, 6 months

2
4
0 / 0

[JBoss JIRA] (WELD-1008) Weld should as for container resources at boot time rather than runtime

by Stuart Douglas (Created) (JIRA)

Weld should as for container resources at boot time rather than runtime ----------------------------------------------------------------------- Key: WELD-1008 URL: https://issues.jboss.org/browse/WELD-1008 Project: Weld Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Jozef Hartinger This will break SPI compatibility, but if weld need to inject a persistence unit or other resource, it should also the container for it at boot time rather than runtime. This should result in bother better performance, as better reporting of deployment errors. -- 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

11 years, 6 months

5
7
0 / 0

[JBoss JIRA] (WELD-1035) ProcessInjectionTarget not fired for message driven bean

by Martin Kouba (Created) (JIRA)

ProcessInjectionTarget not fired for message driven bean -------------------------------------------------------- Key: WELD-1035 URL: https://issues.jboss.org/browse/WELD-1035 Project: Weld Issue Type: Bug Reporter: Martin Kouba *11.5.8. ProcessInjectionTarget event* states: "The container must fire an event for every Java EE component class supporting injection that may be instantiated by the container at runtime, including every managed bean declared using @ManagedBean, EJB session or message-driven bean, enabled bean, enabled interceptor or enabled decorator." However it is not fired for message driven bean. TCK 1.1 test: *org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.jms.ContainerEventTest.testProcessInjectionTargetEventFiredForMessageDrivenBean()* -- 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

11 years, 6 months

3
4
0 / 0

[JBoss JIRA] (WELD-1089) Resource type is not checked against matching object in the Java EE component environment

by Martin Kouba (JIRA)

Martin Kouba created WELD-1089: ---------------------------------- Summary: Resource type is not checked against matching object in the Java EE component environment Key: WELD-1089 URL: https://issues.jboss.org/browse/WELD-1089 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha1, 1.1.5.Final Reporter: Martin Kouba *3.6.1. Declaring a resource* states: "If the matching object in the Java EE component environment is not of the same type as the producer field declaration, the container automatically detects the problem and treats it as a definition error." See TCK test *org.jboss.cdi.tck.tests.implementation.simple.resource.broken.type.ResourceDefinitionWithDifferentTypeTest*. -- 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

11 years, 6 months

2
4
0 / 0

[JBoss JIRA] (WELD-1050) Separate Bean implementations from Producers

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1050: ------------------------------------- Summary: Separate Bean implementations from Producers Key: WELD-1050 URL: https://issues.jboss.org/browse/WELD-1050 Project: Weld Issue Type: Task Reporter: Jozef Hartinger Fix For: 2.0.0.Alpha2 Currently producer implementations are tightly coupled with the corresponding Bean implementations (e.g. ManagedBean or ProducerField) and thus they are not reusable. This is crucial in order to implement CDI-95 properly. This requires major refactoring. -- 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

11 years, 6 months

1
4
0 / 0

[JBoss JIRA] (WELD-1185) Cache methods within DefaultBytecodeMethodResolver

by Jozef Hartinger (JIRA)

11 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues September 2012