Data Services 1.1 release includes important new features, bug fixes and documentation additions that makes this product the foundation for a seamless client-server architecture.
Here are a few of the highlights:
We've just published 4 updated examples for the JSF Edition. The first example illustrates how to implement Internationalization (i18n) with the JSF Edition and covers configuration, localization of widgets and localization of validation. The second example shows how to create custom JSF components, illustrated with a custom balloon widget. The third example describes how the JSF Edition and DWR can be used together for pushing messages from the server to the client. The fourth example shows how to set up a listGrid with paging, sorting and row selection.
Integrating Spring into your application adds a lot of advantages like better modularity, great flexibility for developers, perfect testability of your code etc. Integrating Spring into JSF also adds cool possibilities for developers like usage of Spring AOP in backing beans or security checks for backing bean methods with usage of "spring-security".
Recently a feature request was reported on our bug tracking system with the following description;
The bjsf:menubarItem enables the user to load new views in an application. Currently when a new view is loaded we cannot go back to the previous view using the browser back button. It would be great if of could have this feature.
Is this not something we can all ready do, without even tough the current bjsf:menubarItem implementation? The answer is yes! Within this article you find code snippets showing how to achieve this request.
After reading this article you should be able to make your own custom client-side error handler that would allow you to send client-side errors to your backend when running a JSF Edition application.
Late 2007 we released version 4.1.2 of Backbase Enterprise Ajax for JSF, which includes several new features. This article describes the new features that are unique to the JSF Edition, while the new features that are shared with the Client Edition are described in a separate article.
Courtesy of Kees Broenink, here is some step-by-step advice on how to locate the source of slow performance in a JSF page.
When experiencing a bad performance you must first see if it is client, network or server.
I will explain how to measure the server. If you are working on a LAN the network is most of the time not the bottleneck. This leaves you with a way to have an idea about the client: total - server = client.
|
