Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Q:Converting Forms to J2EE

Re: Q:Converting Forms to J2EE

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Wed, 10 Aug 2005 19:51:45 +0200
Message-ID: <dddeem$dlr$1@news1.zwoll1.ov.home.nl>


Mark C. Stock wrote:
> "Frank van Bortel" <frank.van.bortel_at_gmail.com> wrote in message
> news:ddarr1$nu1$3_at_news5.zwoll1.ov.home.nl...
>

>>Oliver Gehlert wrote:
>>
>>
>>>Forms user a very "soiled" user, so moving them from forms to html db 
>>>will
>>>be difficult. And i doubt that migrating full featured forms to html db
>>>will be simple.
>>>
>>
>>Soiled?
>>
>>But moving from forms to htmldb is simple. Unless the users
>>fail to accept the changes due to HTML handling the front end.
>>
>>-- 
>>Regards,
>>Frank van Bortel

>
>
> Simple?
>
> If the forms application has any validation logic at all, or any triggers at
> all, or any transaction logic, it would all have to be rewritten -- major
> work, based on the forms apps I've seen over the last 20 years.
>
> HTML DB is a great tool, but it's a different paradigm than Forms -- even if
> you're using really, really, simple Forms.
>
> ++ mcs
>
>

Yes - HTMLDB is simple, and straighforward. Validation can only be basic, as one would expect from HTML. Triggers in a form - to do what? Same comment on HTML applies. Transaction logic should not be in a form alone - it is allowed as duplicate of the db transactional code, nothing more. Thus - HTMLDB will cope (with the db-centric code).

And did I not say "Unless .... changes due to HTML..."? As I replies to Oliver: stick to Java, then.

-- 
Regards,
Frank van Bortel
Received on Wed Aug 10 2005 - 12:51:45 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US