This array of modules makes my head go wwwwwwwrrrr..
Why can't we go back to the original suggestion, and separate in a
public API and an internal API, but in the same jar-file.
org.apache.myfaces.commons.public.*
org.apache.myfaces.commons.internal.*
And what's the reason again not to have a very small set of very
common components which don't render markup, but every component
library needs in there? Components can be public API, just like in
Trinidad?
regards,
Martin
On 5/4/07, Glauco Pimentel Gomes <[EMAIL PROTECTED]> wrote:
What do you think about a sub project called "Myfaces Modules" like
"Spring Modules" [1], and modules like:
- Myfaces Converters and Validators (all, including client side);
- Myfaces Dojo Support [2];
- Myfaces Common Components;
- DataList;
- SaveState;
- SubForm;
- AliasBean;
- HtmlTag;
- SelectItens (Tomahawk version);
- JavaScript Listener;
- LoadBundle (Sandbox version);
- Focus;
- IfMessage;
- Submit on Event;
...
- Myfaces Ajax Support;
- Partial Page Rendering;
...
- Myfaces Common API;
- Myfaces Shared API;
- Myfaces Skins (future?)
...
[1] https://springmodules.dev.java.net/
[2]
http://www.nabble.com/-Proposal--Apache-MyFaces-JAR-for-dojo-tf3687496.html
Glauco P. Gomes
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
