ORACLE 11G: Embedding an ORACLE Form within an ADF JSF page

Question

We are currently reviewing the options available to allow us to embed an ORACLE 11G form within an ADF application (11.1.1.4), we are aware of the 'oraformsfaces' functionality but wanted to ask whether there were any other options available to us within ORACLE 11G?
The reason for the question is that we were informed by ORACLE prior to upgrading to ORACLE 11G that the facility to embed an ORACLE form was 'standard' within ADF 11G hence the reason for upgrading.
Thanks in Advance!
Neil

Answer 1

As I noted before, when you seamless, if you mean the user will be unaware that he has switched from a Forms app to an ADF app then I think he will notice - some clever integration of things like JS maps and Graphs might be seamless but a complete ADF app would be obvious to a user. Physically the Forms widgets are a different technology to ADF Faces - you can get the colors the same, you can event get the widgets the same size but it will pretty much be impossible to get the same because you are not comparing apples and apples.
Regarding your questions
1) Do you mean the time it takes to start up the applet? Possible longer than ADF but not necessarily
2) Each form runtime process will have its own database connection and each user has his own applet.
3) "Considerable" is subjective - it will involve some work but we specifically built the JS api to help
Your last point - are you refering to "evolve core business logic into a common layer" what I mean here is that if you have a business process (e.g. hire_employee) which involves creating a new record,ordering a laptop and getting a security pass - then you could take that code out of Forms and put it somewhere else. You could then call that code from Forms (your old apps that you still need) and also call it from your new apps (so calll that code rather than calling the Forms application to do the job). - Of course, there is effort involved there...
One final point to make ADF is NOT Forms - its not the "new" Forms and it doesn't replace Forms - so any change between Forms and ADF is by no means "go to the next version" - they are different technologies with different sweet spots - moving one to the other will be a considerable effort, and I would say one which should also accompany business process changes (if possible) as well..
Hope this helps
Grant