[JAVASERVERFACES_SPEC_PUBLIC-970] Plugin System Created: 14/Apr/11 Updated: 06/Jan/12 Resolved: 20/Nov/11
|Resolution:||Works as designed||Votes:||0|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
core system to build a multi-templating system and more...
|Comment by lamine_ba [ 15/Apr/11 ]|
Broadly speaking, this feature is a starting point to set the building blocks that will help us move towards a standard application framework.What would you say if a plugin was a book? that it has an id, a name, a description, an author...?
Without reading its metadata, How one could know that 'Secrets of the Rockstar Programmers' is written by Ed burns? And if that metadata wasn't loaded at first to create a view of that book, how one could read it?
And who can manage my books? PluginManager! Did you hear my call? My plugins are stored in a folder and they are waiting to be loaded...
And from this little thing, a multi-templating system is born.
you can read more about this feature there http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-971
|Comment by kito75 [ 20/Apr/11 ]|
Make flows reusable http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-730
|Comment by smsajid [ 05/Jan/12 ]|
Is this issue fixed?
|Comment by lamine_ba [ 06/Jan/12 ]|
First of all, Thank you very much for your comment and let me reassure you that this issue has not been fixed. Now to clarify something : Modularity in the language does not mean that JSF will become automatically a modular framework. Using the module system of Java 8, How one can package his css, his images, his js, his composite components, his views, the navigation logic into a reusable unit and plug it into any JSF application? Yes with Java 8, we will be able to plug reusable units of business logic but nothing more. So it means that JSF needs to have its own "Virtual" module system to manage and discover its own artifacts.
The real reason why I have closed this issue is that : The JSF plugin and module system we need is just an aggregation of the two issues below....
1) Make flows reusable
2) Support for modular, reusable, fragments of a web application