JHeadstart Forms2ADF Generator Demos

On the JHeadstart Product Center, we posted a series of viewlets that demonstrate how you can transform Oracle Forms into ADF applications using the JHeadstart Forms2ADF Generator.
In addition to the automated transformation, the viewlets show how easy it is to customize the migration result to produce a different user interface, more suited for web applications.
The viewlets are using JHeadstart 10.1.3.3. If you want to see how the migrated forms will look when using JHeadstart release 11, then you can view the screen shots here.

Comments:

This really rocks! Is there allready some documentation available? Question about the slides 19 and 20. The presenters (detail block) are post-query ;-) populated in the form. I suppose in the ADF version this behaviour is generated into the ADF BC View objects. What about the PLSQL code that was generated to populate the lookup presenters. Is this generated as comment or is it left out because there is an ADF replacement? Are you able to make a difference between generated forms and hand build forms? In that case you could leave out all generated code (CG$%)

Posted by Erik on October 01, 2008 at 09:44 PM PDT #

Erik, 1. In the JHeadstart developers guide, downloadable from the JHeadstart Product Center, there is a chapter on the JHeadstart Forms2ADF generator. 2. We do not parse the POST-QUERY trigger. Instead we look for an LOV defined on the item, if present, we use the LOV query as embedded query expression within the View Object query to populate the lookup items. If no LOV is present, the lookup items will be empty, and you need to modify the ViewObject manually after the conversion. 3. Well, we could add a switch to not copy over PL/SQL code starting with CG$. But even CG$ program units can have custom code as you are able in Designer to add custom code before or after generated code. Steven Davelaar, JHeadstart Team.

Posted by Steven Davelaar on October 01, 2008 at 09:56 PM PDT #

Steven, Thx for the response. Designer Generated Forms: I think in a (big) form there is a lot of code generated that you are not interested in in case of the Forms2ADF migration. The only code you are extremely interested in is the custom code. This custom code are all program units that are not starting with cg$ (unless you are naming your custom program units in this way which certainly is not good practice) and custom code added to trigger logic. Problem are the triggers that are generated where you've added your own custom code. It would be very powerful if the Forms2ADF migration would only migrate the custom hooks and I think that can be possible. All pieces of code in a trigger like this have comment labels starting with /* CG* followed by an anonymous block. Regards Erik

Posted by Erik on October 02, 2008 at 03:30 PM PDT #

Erik, Fair enough. I have added your request to our list of enhancements for release 11. Steven.

Posted by Steven Davelaar on October 02, 2008 at 04:07 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Java EE Consultants - JHeadstart, ADF, JSF

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today