You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The observed behavior with CDI session beans is unusual: after modifying a property of the bean, then calling session.getAttributeNames() within the same method, the shared session cache is not updated. However, if session.getAttributeNames() is not called, everything works correctly and the cache is updated.
@SessionScoped
@Named ("test")
public class RoleManagementJspBean
{
private String test = "init";
public String process( HttpServletRequest request )
{
test= request.getParameter("test");
HttpSession session = request.getSession( true );
session.getAttributeNames();
}
}
Do you have any hypotheses about what could be causing this behavior?
The text was updated successfully, but these errors were encountered:
The observed behavior with CDI session beans is unusual: after modifying a property of the bean, then calling session.getAttributeNames() within the same method, the shared session cache is not updated. However, if session.getAttributeNames() is not called, everything works correctly and the cache is updated.
Do you have any hypotheses about what could be causing this behavior?
The text was updated successfully, but these errors were encountered: