1:16 a.m.
WeldApplication should not assume FacesContext is always active
---------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.Beta2
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 a.m.
New subject: [JBoss JIRA] Updated: (WELD-730) WeldApplication should not assume FacesContext is available during lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen updated WELD-730:
---------------------------
Summary: WeldApplication should not assume FacesContext is available during lazy
initialization (was: WeldApplication should not assume FacesContext is always active)
WeldApplication should not assume FacesContext is available during
lazy initialization
--------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.Beta2
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 a.m.
New subject: [JBoss JIRA] Updated: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen updated WELD-730:
---------------------------
Summary: WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization (was: WeldApplication should not assume FacesContext is
available during lazy initialization)
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.Beta2
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:24 p.m.
New subject: [JBoss JIRA] Updated: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-730:
---------------------------
Fix Version/s: 1.1.0.CR1
(was: 1.1.0.Beta2)
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 a.m.
New subject: [JBoss JIRA] Commented: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen commented on WELD-730:
--------------------------------
https://github.com/weld/core/pull/43
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 a.m.
New subject: [JBoss JIRA] Commented: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen commented on WELD-730:
--------------------------------
Adding a null check here is justifiable defense programming. The spec is not entirely
clear what this method should return in a filter.
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Resolved: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen resolved WELD-730.
----------------------------
Assignee: Dan Allen
Resolution: Done
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Updated: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Dan Allen updated WELD-730:
---------------------------
Priority: Minor (was: Major)
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 p.m.
New subject: [JBoss JIRA] Closed: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Pete Muir closed WELD-730.
--------------------------
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.1.0.CR1
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 p.m.
New subject: [JBoss JIRA] Reopened: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Pete Muir reopened WELD-730:
----------------------------
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.1.0.Beta3
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 p.m.
New subject: [JBoss JIRA] Closed: (WELD-730) WeldApplication shouldn't assume FacesContext is available when attempting lazy initialization
[
https://jira.jboss.org/browse/WELD-730?page=com.atlassian.jira.plugin.sys...
]
Pete Muir closed WELD-730.
--------------------------
Fix Version/s: 1.1.0.Beta3
(was: 1.1.0.CR1)
Resolution: Done
WeldApplication shouldn't assume FacesContext is available when
attempting lazy initialization
----------------------------------------------------------------------------------------------
Key: WELD-730
URL: https://jira.jboss.org/browse/WELD-730
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Affects Versions: 1.1.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Minor
Fix For: 1.1.0.Beta3
WeldApplication uses a forwarding wrapper around the delegate JSF Application object in
order to get around the fact that BeanManager may not have been initialized at the time
JSF is initializing. However, it assumes that the first use of Application will be during
a faces request, where FacesContext is available. However, the JSF Application object is
permitted to be accessed outside of the faces lifecycle (such as in a Servlet filter).
When this occurs, a NullPointerException in WeldApplication results.
WeldApplication should skip the BeanManager lookup if the FacesContext is null.
private BeanManager beanManager()
{
FacesContext facesContext;
if (beanManager != null && (facesContext = FacesContext.getCurrentInstance())
!= null) {
// lookup BeanManager
}
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4975
days inactive
5003
days old
10 comments
2 participants
participants (2)
-
Dan Allen (JIRA) -
Pete Muir (JIRA)