Issue Details (XML | Word | Printable)

Key: JAVASERVERFACES_SPEC_PUBLIC-1054
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Works as designed
Priority: Major Major
Assignee: Ed Burns
Reporter: lamine_ba
Votes: 2
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
javaserverfaces-spec-public

Define a standard structure for a JSF application

Created: 29/Nov/11 12:49 PM   Updated: 29/Nov/11 07:06 PM   Resolved: 29/Nov/11 07:06 PM
Component/s: None
Affects Version/s: 2.2
Fix Version/s: 2.2

Time Tracking:
Not Specified

Tags:
Participants: Ed Burns, lamine_ba, lu4242 and Neil Griffin


 Description  « Hide

The goal of this feature is to define a standard structure for a JSF 2.2 application. And here is the proposal :

Resources


The css, js, images files must be stored in the resources folder like for JSF 2.0

  • resources
Views


The views must be stored in a folder named views

  • views


The protected views must be stored in a sub folder named protected

  • views
    • protected
Templates


The templates must be stored in a folder named templates

  • templates
    • mytemplate
      • css
      • js
      • images
      • template.xhtml
      • template.png
      • template.xml
Tasks Flows (modules)


The modules must be stored in a folder named modules. Note that the structure of a Task flow has not yet been set.

  • modules

And we end up finally with this standard and cohesive structure :

  • app
    • resources
    • views
    • templates
    • modules
    • web-inf
Externalization of the JSF artifacts


The folders must be externalized and stored out of the WAR file to enlarge the possibilities for new ideas and systems.



Sort Order: Ascending order - Click to sort in descending order
lamine_ba made changes - 29/Nov/11 12:49 PM
Field Original Value New Value
Summary Define an standard structure for a JSF application Define a standard structure for a JSF application
lamine_ba made changes - 29/Nov/11 12:52 PM
Description The goal of this feature is to define a standard structure for a JSF 2.2 application. And here is the proposal :

h5. Resources
\\
The css, js, images files must be stored in the resources folder like for JSF 2.0

- resources

h5. Views
\\
The views must be stored in a folder named views

- views

h5. Templates
\\
The templates must be stored in a folder named templates

- templates
 -- mytemplate
   --- css
   --- js
   --- images
   --- template.xhtml
   --- template.png
   --- template.xml

h5. Tasks Flows (modules)
\\
The modules must be stored in a folder named modules. Note that the structure of a Task flow has not yet been set.

- modules

And we end finally with this standard and cohesive structure :

- app
    -- resources
    -- views
    -- templates
    -- modules
    -- web-inf
 
h5. Externalization of the JSF artifacts
\\
The folders must be externalized and stored out of the WAR file to enlarge the possibilities for new ideas and systems.


The goal of this feature is to define a standard structure for a JSF 2.2 application. And here is the proposal :

h5. Resources
\\
The css, js, images files must be stored in the resources folder like for JSF 2.0

- resources

h5. Views
\\
The views must be stored in a folder named views

- views

\\
The protected views must be stored in a sub folder named protected

- views
  -- protected

h5. Templates
\\
The templates must be stored in a folder named templates

- templates
 -- mytemplate
   --- css
   --- js
   --- images
   --- template.xhtml
   --- template.png
   --- template.xml

h5. Tasks Flows (modules)
\\
The modules must be stored in a folder named modules. Note that the structure of a Task flow has not yet been set.

- modules

And we end up finally with this standard and cohesive structure :

- app
    -- resources
    -- views
    -- templates
    -- modules
    -- web-inf
 
h5. Externalization of the JSF artifacts
\\
The folders must be externalized and stored out of the WAR file to enlarge the possibilities for new ideas and systems.


lamine_ba made changes - 29/Nov/11 07:06 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Works as designed [ 7 ]