Weblog for the AMIS Technology corner
Posts tagged customization
OOW 2009: Castle in the Clouds: SaaS-Enabling Oracle ADF Faces Applications
Oct 12th
It will be my last presentation at Oracle Open World 2009 – how to turn any ADF application into a SaaS application – an application suitable for deployment ‘on the cloud – available to users from different organizations’. One of my statements is that most if not all applications benefit from applying those same SaaS concepts. It makes applications running within the walls of an enterprise more agile, more manageable, better suited to the specific needs of individual users and user groups and easier to integrate in the IT landscape of the enterprise, both at the services level (SOA, ESB) and at the user interface level (Portlet). The presentation will discuss a number of facilities and characteristics that are desirable in SaaS applications as well as other Web Applications.
If you are interested in attending and watching the live demos, please come to the session: S307483 Castle in the Clouds: SaaS-Enabling Oracle ADF Faces Applications (Wednesday 14th October, Time: 11:45 – 12:45, Marriott Hotel, Salon 3).
ADF 11g – persisted run time user UI personalization or: Impatient man’s MDS
Jan 9th
One of the rather cool pieces of functionality that did not make it into the JDeveloper 11g Boxer release of early October 2008 is the Meta Data Service or MDS and especially its capability to store and reapply user created personalizations of the User Interface across sessions. Some simple examples of what this means: ADF 11g Rich Client Components allow users to manipulate the state of components – such as the position of the separator in the PanelSplitter, the ordering and width of Table Columns, the initially visible tab or accordion child etc.. Through MDS, these changes are captured and stored for th duration of the session (if so desired), which means that when the user returns to a page thus ‘personalized’, the component will not assume their default state as specified in the JSF page at design time by the developer, but rather the state that user specified. Eventually MDS will persist these component personalizations across sessions – but not right now. That means that at the present when a user starts a new session, all components are presented in their default state.
In this article I will describe two things: Change Persistency for all attributes – not just the built-in settings that can be manipulated through the components and Persisting the changes across sessions, even with the current release of JDeveloper, ADF and MDS.
