The PF is a way to decouple the portal from its presentation layer so you can have the
implementation of your choice:
- HTML (Classic)
- Ajax
- Flex
- Swing
the need really comes from the fact that the portal *must* not rely on a specific kind of
presentation technology. For instance your portal should not behave differently if you use
HTML or Ajax, what I mean by behave here is the portal logic, like if I click on page XYZ,
it shows page page XYZ).
The PF does other things, I wrote a document that outlines it, you can see read it
http://docs.google.com/Doc?id=dhfvtj95_1fnrk2f
We can discuss about it in that forum.
"thomas.heute(a)jboss.com" wrote : No the presentation framework sure doesn't
rely on an ajax framework. It's decoupled from the view actually.
|
| If you want to base your view on YUI the good thing is that you can. But if your
neighbor want it based on GWT (Which is quite popular, like it or not) he can, and if
someone else want plain old HTML he can too.
|
| The presentation framework gives you the necessary abstraction ! We won't rely on
a technology, it changes too quickly, and that's why the presentation framework is
born :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130909#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...