[JAVASERVERFACES_SPEC_PUBLIC-532] Support for modular, reusable, fragments of a web application Created: 27/Feb/09  Updated: 01/Aug/14  Resolved: 04/Feb/12

Status: Closed
Project: javaserverfaces-spec-public
Component/s: Facelets/VDL
Affects Version/s: 2.2 Sprint 8
Fix Version/s: 2.2

Type: Improvement Priority: Major
Reporter: daschneider Assignee: Ed Burns
Resolution: Duplicate Votes: 16
Labels: None
Remaining Estimate: 1 week, 3 days
Time Spent: Not Specified
Original Estimate: 1 week, 3 days
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
blocks JAVASERVERFACES_SPEC_PUBLIC-971 Multi-templating System Closed
Duplicate
duplicates JAVASERVERFACES_SPEC_PUBLIC-730 Make flows reusable Closed
Issuezilla Id: 532
Status Whiteboard:

size_large importance_medium


 Description   

Currently JSF does not support decomposition of a web application into smaller
reusable fragments. For example, you can't build a collection of pages, managed
beans, and navigation rules to perform a common task like completing a consumer
transaction (enter shipping info, billing info, etc.) and package it as a
reusable component. Instead, JSF treats a web application as one monolithic
entity, which becomes problematic in large application. It would be useful to
able to package a portion of a web application into a reusable library.



 Comments   
Comment by Ed Burns [ 24/Sep/09 ]

Move to unscheduled target milestone

Comment by Ed Burns [ 24/Nov/09 ]

Prepare to delete "spec" subcomponent.

Comment by Ed Burns [ 04/Mar/10 ]

I think the Servlet 3.0 spec addresses this. If you feel it does not, please re-open.

Comment by daschneider [ 16/Mar/10 ]

What I had in mind was more along the lines of a Spring WebFlow or an Oracle ADF
Task flow. I don't believe there's anything like this currently covered by any
of the JavaEE specifications.

Comment by Ed Burns [ 22/Jun/10 ]

edburns

Comment by Ed Burns [ 22/Jun/10 ]

This would be great to have, but it's not on the radar at the moment. Feel free to contribute it!

Comment by rogerk [ 27/Oct/10 ]

triage

Comment by kellerapps [ 18/Apr/11 ]

Should programmers use facelet includes to factor out modal dialogs, tab content, & the like?

Comment by daschneider [ 18/Apr/11 ]

The intent of this feature is not to handle page fragment use cases as the above comment suggests. It's intended to allow creation of application fragments that consist of multiple pages, managed bean definitions, navigation rules, etc. that can be packaged up into reusable units. For example, say you have a shopping site checkout flow that consists of several pages to collect billing informaiton, shipping information, confirm the order, etc. How can you build this as a reusable unit that can be used by multiple faces web applications? That's the type of use case this feature intendes to address.

Comment by lamine_ba [ 18/Apr/11 ]

daschneider, I have voted for your issue.

Comment by kito75 [ 20/Apr/11 ]

Related issues:

Make flows reusable http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-730
Simplify external view loading requirements http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-809
Plugin System: http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-970

Comment by lamine_ba [ 11/Dec/11 ]

As you can read it above in a comment left by daschneider

daschneider>What I had in mind was more along the lines of a Spring WebFlow or an Oracle ADF
daschneider> Task flow. I don't believe there's anything like this currently covered by any
daschneider> of the JavaEE specifications.

This issue is a duplicate to http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-730.
they are sharing the same goal : modularization of a JSF application and it wouldn't make sense to achieve it in two different ways. So I think it is better to close this one in favor of the Tasksflow feature which is already meaningful.

Comment by Ed Burns [ 04/Feb/12 ]

This really is a subset of the requirements of task flows.

Comment by Manfred Riem [ 01/Aug/14 ]

Closing resolved issue out

Generated at Wed Dec 07 08:55:58 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.