Redesign communication between SessionBeanInterceptor and the Web Beans Manager to not rely on thread-local/timing trickery
---------------------------------------------------------------------------------------------------------------------------
Key: WBRI-191
URL: https://jira.jboss.org/jira/browse/WBRI-191
Project: Web Beans
Issue Type: Feature Request
Components: Enterprise Beans
Reporter: Pete Muir
Priority: Blocker
Fix For: 1.1.0.BETA1
Currently the SessionBeanInterceptor (an EJB interceptor responsible for doing all interception work on session objects) is using a ThreadLocal to obtain info on which Bean it is for. Redesign this to be less brittle.
--
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
Verify Web Beans on EJB 3.1 container
-------------------------------------
Key: WBRI-231
URL: https://jira.jboss.org/jira/browse/WBRI-231
Project: Web Beans
Issue Type: Task
Components: Enterprise Beans
Affects Versions: 1.0.0.CR1
Reporter: Pete Muir
org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testEnterpriseBeanWithLocalViewAndNotParameterizedTypeHasClassAndSuperclassesAsBeanTypes()
--
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
Request scope is not active/destroyed during call to Ejb timeout method
-----------------------------------------------------------------------
Key: WBRI-228
URL: https://jira.jboss.org/jira/browse/WBRI-228
Project: Web Beans
Issue Type: Bug
Components: Enterprise Beans
Reporter: Pete Muir
Priority: Minor
Fix For: 1.0.0.PREVIEW
org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeActiveDuringCallToEjbTimeoutMethod()
org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest.testRequestScopeDestroyedAfterCallToEjbTimeoutMethod()
--
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
Should gracefully disable EJB and TX services if TX SPIs and EJB SPIs aren't present
------------------------------------------------------------------------------------
Key: WBRI-168
URL: https://jira.jboss.org/jira/browse/WBRI-168
Project: Web Beans
Issue Type: Feature Request
Components: Bootstrap
Reporter: Pete Muir
Fix For: 1.0.0.CR1
--
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
Conversation scoped data not switched in conversations example
--------------------------------------------------------------
Key: WBRI-163
URL: https://jira.jboss.org/jira/browse/WBRI-163
Project: Web Beans
Issue Type: Bug
Components: Examples
Affects Versions: 1.0.0.ALPHA2
Reporter: Nicklas Karlsson
Assignee: Pete Muir
Fix For: 1.0.0.BETA1
The data input box bound to the conversation scoped data component doesn't switch when conversations are switched. Perhaps the bean store is set at a point where the old value is restored in the new conversation incorrectly?
--
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
Separate Logging into a separate module
---------------------------------------
Key: WBRI-171
URL: https://jira.jboss.org/jira/browse/WBRI-171
Project: Web Beans
Issue Type: Task
Reporter: David Allen
Fix For: 1.0.0.CR1
The JSR-299 RI logging in package org.jboss.webbeans.log should be moved to its own module so that it is re-usable across projects.
--
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
Separate log message and log level from module.
-----------------------------------------------
Key: WBRI-214
URL: https://jira.jboss.org/jira/browse/WBRI-214
Project: Web Beans
Issue Type: Feature Request
Reporter: Takeshi Kondo
Under development , log message is used to dubug the program
So log message internationalization will be broaden the webbeans user base.
And it make easy to document log message.
Under operation, maybe only in Japan, Log message is used to trigger alert.
so I frequently change log level to prevent alert at the last minute operation.
--
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
Scope @PersistenceContext for simple beans to module
----------------------------------------------------
Key: WBRI-95
URL: https://jira.jboss.org/jira/browse/WBRI-95
Project: Web Beans RI
Issue Type: Bug
Reporter: Pete Muir
Priority: Minor
Fix For: 1.0.0.BETA1
EJB spec says the PUs are scoped to the module in which they defined, but currently WB just scans whole of the EAR.
--
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