-
Notifications
You must be signed in to change notification settings - Fork 19
Make flows reusable #730
Comments
Reported by @edburns |
Issue-Links: |
@edburns said: |
@edburns said: |
@edburns said: |
@edburns said: |
rogerk said: |
1 similar comment
rogerk said: |
kito75 said: Support for modular, reusable, fragments of a web application http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-532 |
andy_bosch said: |
@edburns said: |
@edburns said: |
@edburns said: SECTION: API ChangesA jsf-api/src/main/java/javax/faces/application/FlowScoped.java
SECTION: Impl ChangesM jsf-ri/mojarra-jsf-impl.bnd
M jsf-ri/build.xml
http://docs.jboss.org/weld/reference/latest/en-US/html/extend.html#d0e4848 M common/ant/dependencies.xml
M test/agnostic/pom.xml
|
@edburns said: |
File: 20120330-1155-i_spec_730.patch |
@edburns said: Sending jsf-api/doc/web-facesconfig_2_2.xsd http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-730
SECTION: Spec changesA + jsf-api/src/main/java/javax/faces/flow/FlowScoped.java
M jsf-api/src/main/java/javax/faces/application/Application.java
M jsf-api/doc/web-facesconfig_2_2.xsd
A jsf-api/src/main/java/javax/faces/flow
M jsf-ri/src/main/java/com/sun/faces/config/WebConfiguration.java
// The flow feature is effectively disabled if no flows are detected Consider this line too: LOGGER.log(Level.WARNING, {0} was set to none, but Faces Flows requires {0} is enabled. Setting to ''url''.", new Object[] {featureName} ); This means that facesFlows will force WindowId to be enabled, if M jsf-ri/src/main/java/com/sun/faces/lifecycle/LifecycleImpl.java
M jsf-ri/src/main/java/com/sun/faces/lifecycle/LifecycleFactoryImpl.java
M jsf-ri/src/main/java/com/sun/faces/application/ApplicationAssociate.java
// PENDING(edburns): Make this come from a factory. M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java
// PENDING(edburns): Flows currently don't work with redirect. // Unconditionally tell the flow system we are transitioning M jsf-ri/src/main/java/com/sun/faces/config/ConfigureListener.java
M jsf-ri/src/main/java/com/sun/faces/flow/FlowCDIContext.java
A jsf-ri/src/main/java/com/sun/faces/flow/FlowHandlerImpl.java
M jsf-ri/src/main/java/com/sun/faces/util/FacesLogger.java
M test/agnostic/flow/basic/src/main/webapp/index.xhtml
D test/agnostic/flow/basic/src/main/java/com/sun/faces/test/agnostic/flow/basic/VersionBean.java
A test/agnostic/flow/basic/src/main/webapp/WEB-INF/faces-config.xml
D jsf-ri/conf/share/javax.enterprise.inject.spi.Extension
|
File: 20120406-1700-i_spec_730.patch |
@edburns said: Next flow checkpoint. Can define the existince of a flow within a page. 2256 old tests pass. 4 new tests pass. SECTION: Spec changesA jsf-ri/conf/share/faces-flow.taglib.xml
Consider these changes to the start.xhtml page.
|
@edburns said: Sending jsf-api/src/main/java/javax/faces/flow/Flow.java |
File: 20120412-1618-i_spec_730.patch |
@edburns said: |
@edburns said: |
File: 20120413-1638-i_spec_730.patch |
@edburns said: |
File: 20120417-1320-i_spec_730.patch |
File: 20120417-1331-i_spec_730-mods.zip |
@edburns said: <j:faces-flow-return> works. SECTION: Modified FilesM jsf-ri/conf/share/faces-flow.taglib.xml
M jsf-ri/src/main/java/com/sun/faces/facelets/flow/FacesFlowDefinitionTagHandler.java
M jsf-ri/src/main/java/com/sun/faces/facelets/compiler/SAXCompiler.java
M jsf-ri/src/main/java/com/sun/faces/application/NavigationHandlerImpl.java
M test/web-profile/flow/basic-multi-page/src/main/java/com/sun/faces/test/agnostic/flow/basic/FlowBean.java
M test/web-profile/flow/basic-multi-page/src/main/webapp/bounded-task-flow/bounded-task-flow.xhtml
M test/web-profile/flow/basic-multi-page/src/main/webapp/bounded-task-flow/next_a.xhtml
M jsf-api/src/main/java/javax/faces/flow/Flow.java
A + jsf-ri/src/main/java/com/sun/faces/facelets/flow/FacesFlowReturnTagHandler.java
A + test/web-profile/flow/basic-multi-page/src/main/webapp/bounded-task-flow/next_b.xhtml
Sending jsf-api/src/main/java/javax/faces/flow/Flow.java |
@edburns said: {facesFlowScope} . Analogous to ADF's # {pageFlowScope} . |
File: 20120419-2328-i_spec_730.patch |
@edburns said: |
File: 20121005-2221-i_spec_730.patch |
File: 20121009-2345-i_spec_730.patch |
File: 20121011-0039-i_spec_730.patch |
File: 20121013-0012-i_spec_730.patch |
@edburns said: |
@edburns said: |
File: 20121128-1054-GMT-5-task-flow-moderate.zip |
File: basic-explicit.zip |
Marked as fixed on Saturday, March 16th 2013, 9:39:14 am |
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-730 |
Although you can use several jsf-config files in a single application, essentially
breaking down your application into smaller flows, it's still too hard to create a flow
that's truly reusable across applications in JSF.
The idea here would be to define standalone flows that can be incorporated into
other flows. And to make things truly reusable, these flows should include a
standalone memory scope and a transaction scope. This will let developers
incorporate the flow into encapsulating flows without interfering with the
transaction and memory scope of the encapsulating flow.
Environment
Operating System: All
Platform: All
URL: http://java.sys-con.com/node/535314?page=0,2
Affected Versions
[2.0]
The text was updated successfully, but these errors were encountered: