Posts tagged resource bundle
Kom kennismaken met AMIS en doe mee met uitdagende projecten
0Ben jij een (junior) Oracle consultant die een stap verder wil maken? Wil je verder groeien en ontwikkelen tot principal consultant? AMIS geeft je de kans om die stap te zetten. Bij ons krijg je de ruimte om te experimenteren én te leren samen met de experts op je vakgebied.
Laat ons in een vrijblijvend gesprek vertellen welke mogelijkheden we je kunnen bieden. Neem voor een afspraak met een van onze consultants contact op met Eva.van.der.kleij@amis.nl of bel haar op 030-6016000. Je bent van harte welkom.
AMIS merkt dat haar concept van hoogwaardige en kennisintensieve dienstverlening erg succesvol is. Onze toekomst ziet er erg aantrekkelijk uit met interessante opdrachten bij toonaangevende klanten. Vandaar dat we op zoek zijn naar uitbreiding van ons team.
Denk niet direct dat je hiervoor te weinig kennis of ervaring hebt: jouw toekomstige ervaren collega’s doen niets liever dan jou verder helpen. Ons trainingsprogramma voorziet in een grote diversiteit aan opleidingen en tijdens onze interne kennissessies kun je op veel terreinen iets van je collega’s opsteken. Concreet hebben we de volgende vacatures:
Creating reusable ADF Library with generic live resource bundle editing functionality and reusing it in any ADF application
1In previous articles, I have introduced functionality to centralize management of boilerplate text elements such as prompt, title, hint text and messages in resource bundles. This also allows for language or user group and other context sensitive values for these boilerplate text elements. The resource bundles, as was demonstrated, can be backed by database tables, refreshed at run time and even be edited from within the JSF application itself. The last installment in the series before this one introduced an approach that allows for live page editing with minimal impact on the page itself – through run time UI component tree manipulation. However, the code for handling the live editing and dealing with the resource bundles was still part of the application making use of that functionality. This article demonstrates how this generic functionality can be isolated in a separate ADF application, deployed to an ADF Library and reused in one or many different ADF applications.
Live resource bundle entry editing in a generic way through declarative component and UI component tree manipulation
0In a series of five articles I have discussed how boilerplate text elements such as prompts and labels could and should be taken out of pages and centralized in resource bundles. I have explained how resource bundles can be implemented in database tables, how the bundles can be refreshed at run time and how different user groups can be served with different resource bundles. The previous article demonstrated how text properties can be edited at run time, in the context of the application.
The approach discussed for live text editing works fine. However, its current implementation requires specific manipulation – of every individual page. Each page contains a popup component and each component to be edited needs to have an associated showPopupBehavior or even a commandImageLink.
This article outlines a more generic approach that requires virtually no page or component specific preparation. The popup is takes out of the page into a page fragment. This page fragment is included in every page using a single declarative component tag. Via a phaseListener on the f:view tag, the UIComponent tree of every page is programmatically manipulated before being rendered. The manipulation More >
Live update of Resource Bundle from within running ADF application
0In a number of prior articles I have discussed how resource bundles are used in ADF applications to centralize boilerplate text elements – and how such resource bundles can be implemented in the database. I have shown how various groups of users can be served with different sets of resource bundle entries (context sensitive) and how resource bundles can be refreshed at run time, without redeployment or even restart of the application. Building on top of these earlier steps, I will now add functionality to the demo application to edit the resource bundle entries live and in context of the application. That means: a user (with the proper authorization) can bring up a boilerplate text editor in the context of a specific UI component and edit the resource bundle entries associated with that component – for each of the supported languages and each of the supported context values.
Any changes made while editing are recorded in the database table under the resource bundle and can be applied to the running application through the refresh resource bundle functionality introduced earlier on.
Refresh resource bundle from within the ADF application – to absorb changes in database backed bundles
2Any web application contains boilerplate text: text that is not part of the enterprise data from web services or databases that is manipulated by the end users using the application but that is part of the application definition itself. Text that is shown as prompt, title, message, hint text and in other ways. Developers can sprinkle the boilerplate text all throughout the application, in pages, JavaScript and other code sections. But they should not do that. Changing boiler plate text is a frequent requirement from the business. Having all boilerplate text in a central location makes such changes a lot easier. Additionally, many organizations require applications to be multi-lingual: different groups of users speak different languages and want to have the application support them in their own language. That means boiler plate text is not just defined once in that central location, but once for every language the application needs to support.
In previous articles I discussed how resource bundles can be used for centralizing the boilerplate text items and how a resource bundle can be implemented in a database table. I also demonstrated I how to support not just different More >
Adding customization (or context sensitivity) to boilerplate text from database backed resource bundles in ADF applications
0Any web application contains boilerplate text: text that is not part of the enterprise data from web services or databases that is manipulated by the end users using the application but that is part of the application definition itself. Text that is shown as prompt, title, message, hint text and in other ways. Developers can sprinkle the boilerplate text all throughout the application, in pages, JavaScript and other code sections. But they should not do that. Changing boiler plate text is a frequent requirement from the business. Having all boilerplate text in a central location makes such changes a lot easier. Additionally, many organizations require applications to be multi-lingual: different groups of users speak different languages and want to have the application support them in their own language. That means boiler plate text is not just defined once in that central location, but once for every language the application needs to support.
In previous articles I discussed how resource bundles can be used for centralizing the boilerplate text items and how a resource bundle can be implemented in a database table. In this article I will describe how to support not just different More >
Recent Comments