Can't lookup comp:java/Manager from JNDI in JBoss 5
---------------------------------------------------
Key: WBRI-93
URL: https://jira.jboss.org/jira/browse/WBRI-93
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA1
Reporter: Pete Muir
Assignee: Pete Muir
Fix For: 1.0.0.ALPHA2
--
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
Numberguess example reset doesn't reset biggest
-----------------------------------------------
Key: WBRI-94
URL: https://jira.jboss.org/jira/browse/WBRI-94
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA2
Environment: every environment
Reporter: Benjamin Graf
Priority: Minor
Fix For: 1.0.0.ALPHA2
Biggest is not reset when playing again. Since it is changed during a game it might become less than the next number to be guessed. Can look odd! :-)
--
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
Error with latest RI Integration
--------------------------------
Key: WBRI-89
URL: https://jira.jboss.org/jira/browse/WBRI-89
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA2
Environment: Linux+OpenJDK6
Reporter: Benjamin Graf
Fix For: 1.0.0.ALPHA2
While deploying WebBeans war project like Numberguess example an IllegalStateException is thrown at ServletBootstrap due to the fact that no WebBeansDiscoveryImpl is found. This might correspond to the fact that the current ri-int does not provide its own ResourceHandler and so the ServletResourceHandler is uses which might not even see the current impl-class in its classloader.
--
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
SessionBeanInterceptor doesn't proceed lifecycle callbacks
----------------------------------------------------------
Key: WBRI-91
URL: https://jira.jboss.org/jira/browse/WBRI-91
Project: Web Beans RI
Issue Type: Bug
Reporter: Tobias Koltsch
The SessionBeanInterceptor intercepts the lifecycle callbacks @PostConstruct and @PreDestroy. When the annotated methods in the interceptor class are triggered, javax.interceptor.InvocationContext.proceed() is never invoked. So it isn't possible that the callbacks proceed to the bean.
--
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
Refactor producer beans
-----------------------
Key: WBRI-90
URL: https://jira.jboss.org/jira/browse/WBRI-90
Project: Web Beans RI
Issue Type: Bug
Affects Versions: 1.0.0.ALPHA1
Reporter: Nicklas Karlsson
Assignee: Nicklas Karlsson
Fix For: 1.0.0.ALPHA2
The producer method/field beans have lots of overlapping. Move most stuff into AbstractProducerBean and add abstract methods for isAnnotatedMemberSerializable, produceInstance etc where field/method syntax differs
--
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
Refactor contexts hierachy as it's a little off
-----------------------------------------------
Key: WBRI-84
URL: https://jira.jboss.org/jira/browse/WBRI-84
Project: Web Beans RI
Issue Type: Task
Reporter: Pete Muir
Assignee: Pete Muir
Priority: Critical
Fix For: 1.0.0.ALPHA2
DependentContext shouldn't extend a context which has a map!
--
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