On this week I was visiting Sofia, Bulgarian capital. City is a mix of western and eastern culture, this makes it unique and beautiful. Definitely you should find time to visit it, you will have a chance to meet very warm and friendly people ;).
St. Alexander Nevsky Cathedral, it was built in honour to the Russian soldiers who died during the Russo-Turkish War of 1877-1878. It looks really impressive.
Sunday, September 30, 2007
Friday, September 14, 2007
Automatic Java class invocation after deployment of Oracle ADF application
Recently I was implementing requirement of automatic Java class invocation right after application is deployed on Oracle Application Server. Automatic class loading possibly is required when for example job scheduling system like Quartz is used by application. This means that job scheduling should be started right after application is deployed, so main question is how to to invoke Java class automatically.
In developed sample application - DeploymentRegistration.zip, I have decided not to use any job scheduling invocation, but to implement deployment registration functionality. Implemented logic - when application is deployed, record with history data is stored in the database table. Application itself is based on standard HR schema, however some additional elements are used. You can find SQL script with statements for database table, sequence and trigger in sample application package.
Data is inserted into database table using application module that is looked up and created using a Command-Line Java Test Client for ADF BC. So, this means that ADF BC functionality is accessed from external Java class. Java class code, which is invoked automatically after deployment:
DeploymentHistory class acquires application module, creates new row and commits it into database. You are probably interested, how this code is invoked automatically, after deployment. Automatic invocation is implemented using simple servlet - AutoLoader, this servlet is loaded automatically after deployment and invokes main method in DeploymentHistory class. Servlet code:
AutoLoader servlet is declared in web.xml with load-on-startup setting equal to 1, this means that servlet will be loaded after deployment automatically and init method code will be executed. Declaration in web.xml:
Now we can test developed application. To test it we can use OC4J that comes with JDeveloper, just right-click on main.jspx and choose Run - application will be deployed on embedded OC4J and started. Developed application shows a table with information about countries and provides a button - Deployments History, which opens pop-up window with information about deployments history stored in the database.
Let's say there were several deployments, it is reflected in deployments history:
When running sample application, don't forget to add adf-faces-impl.jar and jsf-impl.jar to application's WEB-INF\lib directory.
In developed sample application - DeploymentRegistration.zip, I have decided not to use any job scheduling invocation, but to implement deployment registration functionality. Implemented logic - when application is deployed, record with history data is stored in the database table. Application itself is based on standard HR schema, however some additional elements are used. You can find SQL script with statements for database table, sequence and trigger in sample application package.
Data is inserted into database table using application module that is looked up and created using a Command-Line Java Test Client for ADF BC. So, this means that ADF BC functionality is accessed from external Java class. Java class code, which is invoked automatically after deployment:
DeploymentHistory class acquires application module, creates new row and commits it into database. You are probably interested, how this code is invoked automatically, after deployment. Automatic invocation is implemented using simple servlet - AutoLoader, this servlet is loaded automatically after deployment and invokes main method in DeploymentHistory class. Servlet code:
AutoLoader servlet is declared in web.xml with load-on-startup setting equal to 1, this means that servlet will be loaded after deployment automatically and init method code will be executed. Declaration in web.xml:
Now we can test developed application. To test it we can use OC4J that comes with JDeveloper, just right-click on main.jspx and choose Run - application will be deployed on embedded OC4J and started. Developed application shows a table with information about countries and provides a button - Deployments History, which opens pop-up window with information about deployments history stored in the database.
Let's say there were several deployments, it is reflected in deployments history:
When running sample application, don't forget to add adf-faces-impl.jar and jsf-impl.jar to application's WEB-INF\lib directory.
Wednesday, September 5, 2007
Oracle Fusion User Group and JDev/ADF Labs
We (Frans Thamura and me) have decided to open Oracle Fusion User Group (OFUG). User Group homepage - ofug-global.
OFUG is created in order to bring together technical people who are working with Oracle Fusion. This group will be focused on educational aspect, everyone could share knowledge and get benefit from acquiring available knowledge.
OFUG was created by Frans and is based on labs material that I have prepared recently. Everyone who will join OFUG, can use this material for his/her education. In October I will deliver 1 day workshop based on those labs in Vilnius for local technical community.
Currently in OFUG are available those labs:
OFUG is created in order to bring together technical people who are working with Oracle Fusion. This group will be focused on educational aspect, everyone could share knowledge and get benefit from acquiring available knowledge.
OFUG was created by Frans and is based on labs material that I have prepared recently. Everyone who will join OFUG, can use this material for his/her education. In October I will deliver 1 day workshop based on those labs in Vilnius for local technical community.
Currently in OFUG are available those labs:
- Labs environment description
- Data model layer development using ADF Business Components
- Page flow definition
- Search functionality development. Search page contains a form for search parameters and a table for search results
- Create functionality development. This page contains several select-one-choice components and allows to insert new data into Departments entity
- Edit functionality development
- Complex table component development. This component will allow to perform create, update, and delete operations
Multi-selection and Row Data Editing in ADF Faces
In this post I have decided to dive into multi-selection feature offered by ADF Faces little bit more deeper and to show how it could be used in practice. Developed application use case is based on two pages, in first page user can select multiple rows in search results table and press edit button. Second page will be opened only with selected rows. So, this post is focused on how to open in second page only rows selected in first page.
Sample application - TableSelection.zip is based on standard HR schema. Two pages are implemented - search.jspx and edit.jspx. In search.jspx you can find two components - a search form and and a table for search results. In search form is implemented af:selectOneChoice component and table contains read-only af:selectOneChoice for region names. In edit.jspx there is editable table with af:selectOneChoice component for region name.
So, what happens when in search.jspx Edit button is pressed? Edit button is binded with editButton_action() method, available in backing_search backing bean. This means, when Edit button is pressed - editButton_action() is invoked:
This method finds needed iterator and acquires keys for selected rows. And main functionality - method sets where clause for View object that is used in edit.jspx page. Where clause is generated according to primary keys data of selected rows, this allows to open in edit.jspx only needed rows.
Just imagine, that we want to move several countries to other continent - no problem, select those countries and press Edit button:
Edit form is opened, here you can change region name for selected countries, save your changes and return to search form:
And..., you can continue a process... :-)
When running sample application, don't forget to add adf-faces-impl.jar and jsf-impl.jar to application's WEB-INF\lib directory.
Sample application - TableSelection.zip is based on standard HR schema. Two pages are implemented - search.jspx and edit.jspx. In search.jspx you can find two components - a search form and and a table for search results. In search form is implemented af:selectOneChoice component and table contains read-only af:selectOneChoice for region names. In edit.jspx there is editable table with af:selectOneChoice component for region name.
So, what happens when in search.jspx Edit button is pressed? Edit button is binded with editButton_action() method, available in backing_search backing bean. This means, when Edit button is pressed - editButton_action() is invoked:
This method finds needed iterator and acquires keys for selected rows. And main functionality - method sets where clause for View object that is used in edit.jspx page. Where clause is generated according to primary keys data of selected rows, this allows to open in edit.jspx only needed rows.
Just imagine, that we want to move several countries to other continent - no problem, select those countries and press Edit button:
Edit form is opened, here you can change region name for selected countries, save your changes and return to search form:
And..., you can continue a process... :-)
When running sample application, don't forget to add adf-faces-impl.jar and jsf-impl.jar to application's WEB-INF\lib directory.