[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2121) Support for an SMPC per nested conversation
by Jacob Orshalick (JIRA)
Support for an SMPC per nested conversation
-------------------------------------------
Key: JBSEAM-2121
URL: http://jira.jboss.com/jira/browse/JBSEAM-2121
Project: JBoss Seam
Issue Type: Feature Request
Affects Versions: 2.0.0.CR2
Reporter: Jacob Orshalick
Currently an open issue and ongoing discussion with respect to the existing nested conversation implementation is master-details editing. If a Seam-managed Persistence Context (SMPC) is shared between the outer and nested conversation, any changes made in the nested conversation will be flushed by the SMPC in the outer conversation and vice versa if a flush is initiated. Support for initialization of a new SMPC within a nested conversation would allow state changes in the nested conversation to be confined to that conversation, thus resolving this issue. Perhaps something like the following could be supported:
<persistence:managed-persistence-context name="bookingDatabase"
auto-create="true"
per-nested-conversation-"true"
persistence-unit-jndi-name="java:/EntityManagerFactories/bookingData"/>
It would also be nice to be able to use annotations (i.e. something similar to @PerNestedConversation).
For further information on this approach please see the forum posting. Thanks.
--
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
16 years, 2 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1009) optionally login-require in a more specific page should be able to override a wildcard login-require
by Leo Baschy (JIRA)
optionally login-require in a more specific page should be able to override a wildcard login-require
----------------------------------------------------------------------------------------------------
Key: JBSEAM-1009
URL: http://jira.jboss.com/jira/browse/JBSEAM-1009
Project: JBoss Seam
Issue Type: Patch
Components: Security
Affects Versions: 1.2.0.GA
Environment: all
Reporter: Leo Baschy
This should be optional to switch on, so no one's existing expectations of security get broken.
The point is about having a generic wildcard <page view-id="*" scheme="http" login-required="true"> to secure the whole site, and then allowing specific pages or specific wildcards to have login-required="false". E.g. for a registration (with preview) section as one cannot be logged in if one isn't registered yet.
Some may suggest instead forcing pages into dedicated secure and not-secure directories, but in reality if there are multiple reasons to force pages into directories different ways (security, hyperlink management, publishability of URLs, etc.), one cannot serve all of them.
--
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
16 years, 2 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2133) inline EL in component property value not properly detected
by Dan Allen (JIRA)
inline EL in component property value not properly detected
-----------------------------------------------------------
Key: JBSEAM-2133
URL: http://jira.jboss.com/jira/browse/JBSEAM-2133
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.CR2
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Critical
Fix For: 2.0.1.GA
Currently, the EL notation in a property is only being evaluated if the property starts with "#{". There are two problems with this assumption.
1. Inline EL can only be used if the property starts with an expression (i.e. <property name="message">#{applicationName} is a cool application</property>)
2. There is no way to escape EL so that is is evaluated by the property accepting the string (rather than when the value is assigned).
The correct behavior would be to treat the property value as a value expression if it CONTAINS "#{". The benefits are two fold:
1. A property value can use inline EL that is evaluated when the property value is set (see above)
2. The resolved value of the property can be EL (delayed EL) that is to be interpreted by the component as needed. This is done by escaping the EL per the unified EL spec (i.e. <property name="created-message">The user \#{user.name} has been created!</property)
Surprisingly, everything is already in place. All that needs to happen is the check for EL needs to change from "startsWith" to "contains".
--
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
16 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1277) ServerConversationContext does not process removals / additions when an exception propagates up
by Chris Rudd (JIRA)
ServerConversationContext does not process removals / additions when an exception propagates up
-----------------------------------------------------------------------------------------------
Key: JBSEAM-1277
URL: http://jira.jboss.com/jira/browse/JBSEAM-1277
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.0.GA
Reporter: Chris Rudd
I have an Stateful EJB Component that throws an exception (this is expected, im testing that the system can recover from that error). This causes the component to be removed from the seam contexts (via the RemoveInterceptor). Then the exception floats up and is caught by the ExceptionFilter, and is redirected to a new view. All that works correctly. BUT when I return to the conversation that contained the EJB component, the component is still in it (even though the RemoveInterceptor removed it).
Ive traced it down to this :
ServerConversationContext.remove -- this adds the removal to the removals list, but does not update the session.attributes (the real storage for the context).
ServerConversationContext.flush -- this applies the removals / additions to the session attributes map.
The problem is that flush is never called when an exception propagates out. Thus the changes to that context are never flushed to the session attributes.
--
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
16 years, 3 months