June 2009 - weld-issues - Jboss List Archives

[webbeans-issues] [JBoss JIRA] Created: (WBRI-26) Implement JMS components

by Pete Muir (JIRA)

Implement JMS components ------------------------ Key: WBRI-26 URL: http://jira.jboss.com/jira/browse/WBRI-26 Project: Web Beans RI Issue Type: Task Reporter: Pete Muir Fix For: 1.0.0.EDR2 Via xml only -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
6
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-236) Use a standalone resolver for disposal beans

by Pete Muir (JIRA)

Use a standalone resolver for disposal beans -------------------------------------------- Key: WBRI-236 URL: https://jira.jboss.org/jira/browse/WBRI-236 Project: Web Beans Issue Type: Feature Request Components: Producer beans Reporter: Pete Muir Assignee: Daniel Roth Fix For: 1.0.0.PREVIEW -- 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, 9 months

1
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-278) Expose Scheduler via SPI so container can manage if it wants to

by Pete Muir (JIRA)

Expose Scheduler via SPI so container can manage if it wants to --------------------------------------------------------------- Key: WBRI-278 URL: https://jira.jboss.org/jira/browse/WBRI-278 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir Priority: Minor Fix For: 1.1.0.BETA1 -- 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, 10 months

1
0
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-246) Invalid tomcat.undeploy target

by Jozef Hartinger (JIRA)

Invalid tomcat.undeploy target ------------------------------ Key: WBRI-246 URL: https://jira.jboss.org/jira/browse/WBRI-246 Project: Web Beans Issue Type: Bug Components: Examples Affects Versions: 1.0.0.PREVIEW1 Reporter: Jozef Hartinger Fix For: 1.0.0.PREVIEW2 Currently, tomcat.undeploy target does not work properly. When called, it tries to delete both file and folder identified by "${tomcat.home}/webapps/${example.name}". Instead of that, it should only remove a file at "${tomcat.home}/webapps/${example.name}.war". Note the ".war" suffix. -- 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, 10 months

2
1
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-276) NullPointer using @Produces

by Diego Coronel (JIRA)

NullPointer using @Produces --------------------------- Key: WBRI-276 URL: https://jira.jboss.org/jira/browse/WBRI-276 Project: Web Beans Issue Type: Bug Components: Producer beans Affects Versions: 1.0.0.PREVIEW1 Environment: Windows Vista, Tomcat 6.0.20, Java 6, jstl-api-1.2, JSF@ Reporter: Diego Coronel I added all jars (WB, JSTL, JSF2) to tomcat/lib Steps to reproduce: 1 - http://127.0.0.1:8080/HelloWebBeans/login/login.jsf 2 - Login = a password = a 3 - Click in "Teste" button 4 - http://127.0.0.1:8080/HelloWebBeans/login/login.jsf -- 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, 10 months

2
4
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-275) Enterprise WebBeans w/ PersistenceContext throw incorrect exception when failing

by John Ament (JIRA)

Enterprise WebBeans w/ PersistenceContext throw incorrect exception when failing -------------------------------------------------------------------------------- Key: WBRI-275 URL: https://jira.jboss.org/jira/browse/WBRI-275 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Environment: Suse 11.1 and SLES 10.2 Java 6 64 Bit JDK JBoss AS 5.1 Reporter: John Ament Priority: Minor If you create an enterprise web bean with a logical error, i.e. attempting to play with the transaction from within a method or attempt to access a table that does not exist, you get a stack trace that only mentions: java.lang.IllegalArgumentException: enterpriseBeanInstance.setDestroyed() called with non-boolean argument This is incorrect, or at least undesirable, because there's no clear indication where the error actually lies. Examples of the poor programming: Referencing an entity bean that has @Table("some_non_existent_table") Starting a transaction: entityManager.getTransaction().begin(); Query q = entityManager.createQuery("select i from Image i where i.skuAssociated = :sku").setParameter("sku", sku); List<Image> results = q.getResultList(); entityManager.getTransaction().commit(); return results; Essentially, anything that can cause a RuntimeException (or child of) to be thrown from within the methods of a Stateful EJB. To test: Create a standard EJB w/ a similar programming problem and see that it does not throw this exception. Create an enterprise web bean w/out this programming problem and see that it does not throw this exception. -- 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, 10 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-253) provide informative exception when attempt is made to invoke EJB from test in standalone mode

by Dan Allen (JIRA)

provide informative exception when attempt is made to invoke EJB from test in standalone mode --------------------------------------------------------------------------------------------- Key: WBRI-253 URL: https://jira.jboss.org/jira/browse/WBRI-253 Project: Web Beans Issue Type: Feature Request Components: Enterprise Beans Affects Versions: 1.0.0.PREVIEW1 Environment: test-harness in standalone mode Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.CR1 My understanding is that I cannot invoke a method on an EJB session bean unless I am using incontainer mode (@IntegrationTest). Otherwise I get the following exception, assuming a method signature of HotelSearch#isPreviousPageAvailable(). java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.webbeans.bean.proxy.ClientProxyMethodHandler.invoke(ClientProxyMethodHandler.java:97) at org.jboss.seam.examples.booking.action.HotelSearch_$$_javassist_1.isPreviousPageAvailable(HotelSearch_$$_javassist_1.java) at org.jboss.seam.examples.booking.action.FooTest.testCallMethodOnSessionBean(FooTest.java:20) Caused by: java.lang.NullPointerException at org.jboss.webbeans.util.Reflections.lookupMethod(Reflections.java:514) at org.jboss.webbeans.util.Reflections.lookupMethod(Reflections.java:496) at org.jboss.webbeans.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:136) at org.jboss.seam.examples.booking.action.HotelSearch_$$_javassist_0.isPreviousPageAvailable(HotelSearch_$$_javassist_0.java) ... 43 more It might helpful to turn this NullPointerException into an IllegalStateException to make it clear that it's not possible to do such a call in standalone mode. -- 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, 10 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-256) can't inject a instance which has ParameterizedType super class.

by Takeshi Kondo (JIRA)

can't inject a instance which has ParameterizedType super class. ---------------------------------------------------------------- Key: WBRI-256 URL: https://jira.jboss.org/jira/browse/WBRI-256 Project: Web Beans Issue Type: Bug Components: Simple Beans Affects Versions: 1.0.0.PREVIEW1 Reporter: Takeshi Kondo Assignee: Nicklas Karlsson for instnce -- public class LookupSingiletonMap { @Current SingletonMap map; } @ApplicationScoped public class SingletonMap extends ConcurrentHashMap<String, Object> { } --- Manager can't inject SingletonMap to LookupSingiletonMap. because if injected instance has ParameterizedType super class, org.jboss.webbeans.introspector.jlr.AbstractAnnotatedItem#isAssignableFrom(Class<?> type, Type[] actualTypeArguments) method always returns false. -- 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, 10 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-265) Remove methods can be called on non-dependent scoped stateful beans

by David Allen (JIRA)

Remove methods can be called on non-dependent scoped stateful beans ------------------------------------------------------------------- Key: WBRI-265 URL: https://jira.jboss.org/jira/browse/WBRI-265 Project: Web Beans Issue Type: Bug Components: Enterprise Beans Affects Versions: 1.0.0.PREVIEW1 Reporter: David Allen TCK assertion 3.3.1 (c) states that an UnsupportedOperationException is to be thrown if a remove method is called on a stateful session bean that is not dependent scoped. Corresponding TCK test is: EnterpriseBeanRemoveMethodTest.applicationCannotCallRemoveMethodOnNonDependentScopedSessionEnterpriseBean() -- 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, 10 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-266) A specializing bean inheriting from a non-simple bean is not throwing correct exception

by David Allen (JIRA)

A specializing bean inheriting from a non-simple bean is not throwing correct exception --------------------------------------------------------------------------------------- Key: WBRI-266 URL: https://jira.jboss.org/jira/browse/WBRI-266 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.PREVIEW1 Reporter: David Allen TCK assertion 3.2.7 (d) specifies that an DefinitionException is to be thrown if a specializing bean class does not directly extend a simple bean class. Currently it produces a different exception. Affected test is: SpecializingClassExtendsNonSimpleBean.testSpecializingClassExtendsNonSimpleBean() -- 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, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2009