[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2523) Identity component should be scoped to the WAR module
by Reind D (JIRA)
Identity component should be scoped to the WAR module
-----------------------------------------------------
Key: JBSEAM-2523
URL: http://jira.jboss.com/jira/browse/JBSEAM-2523
Project: JBoss Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.0.1.CR1
Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA)
Reporter: Reind D
I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR.
The EAR is packaged as follows:
my-application.ear/
a.war/
WEB-INF/
components.xml
...
b.war/
WEB-INF/
components.xml
...
web.jar
Congure authentication as follows in both components.xml files:
a.war/WEB-INF/components.xml
<security:identity authenticate-method="#{authA.authenticate}" />
b.war/WEB-INF/components.xml
<security:identity authenticate-method="#{authB.authenticate}" />
--
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
15 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2854) Provide a way to nest pageflows
by Marcell Barbacena (JIRA)
Provide a way to nest pageflows
-------------------------------
Key: JBSEAM-2854
URL: http://jira.jboss.com/jira/browse/JBSEAM-2854
Project: JBoss Seam
Issue Type: Feature Request
Components: BPM, Core, JSF Controls
Affects Versions: 2.0.1.GA
Environment: All
Reporter: Marcell Barbacena
The current behaviour of pageflow subprocess tag is to include the pageflow definition in the the current flow, meaning that the parent pageflow is paused until the included pageflow ends.
However, sometimes it is desired that the parent pageflow do not "pause" and that the included gain its own flow.
The semantics of this nested pageflow is:
- when starts: provided a nested conversation from the parent pageflow.
- when ends: go back do the state before the nesting. If the parent pageflow is not associated in any way to the nested, its flow goes without interfering with the nested.
E.g.:
Parent directed graph: startpage1->page1; page1->page2; page1->nested; nested->page2; page2->page3; page3->endpage1;
Nested graph: startpage2->page5; page5->page6; page6->endpage2
Then we can have:
parent: startpage1->page1;
parent: page1->nested;
nested: startpage2->page5;
nested: page5->page6;
parent: page1->page2;
parent: page2>page3;
nested: page6->endpage2
nested:endpage2->page2;
parent: page3->endpage1;
nested: page2>page3;
nested: page3->endpage1;
See that the nested pageflow gains his own flow, i.e. independent of the parent.
--
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
15 years, 7 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam
by Florian Keusch (JIRA)
JPDL navigation and seam
------------------------
Key: JBSEAM-3056
URL: http://jira.jboss.com/jira/browse/JBSEAM-3056
Project: Seam
Issue Type: Task
Components: BPM
Reporter: Florian Keusch
hi
In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem:
if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown.
This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira.
It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown:
//now check that the restored view id matches what we expect
//from the pageflow node
//TODO: we need some way to disable this check, since users
// might want some adhoc nav in and out of a pageflow?
String viewId = Pages.getViewId(facesContext);
if ( !viewId.equals( getPage().getViewId() ) )
{
illegalNavigationError();
}
If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended.
fke
--
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
15 years, 7 months