Re: Import Designer 2000 Web PLSQLs into Designer 9i

[Quoted] Jeez, this indeed is a mess!

[Quoted] There is no trace of the earlier repository anywhere :( Also we are planning to move this application onto entirely new machines and will be creating the database afresh in which case i guess we have only the folliwng options. 1. Create a new repository and create the application from scratch using Designer 9i. This will take a considerable amount of work assuming we have sufficient knowledge of the screens and database. Thankfully the application as such is not humongous. 2. Compile all designer built in packages (WSGL,WSGLM,WSGFL,WSGJSL and associated objects) and designer application packages onto the Oracle 9i database, directly edit the packages using standard PL/SQL editors (changes are not minor but manageable) and compile the same. This as pointed out will be regular PL/SQLs with no designer fucntionality.

the second option is a crude way of doing things but will reduce effort (&costs), provided it works and there are no incomptibilies inbetween. In the end again, we will not have a repository and the same problems will continue if future enhancements are made.

But then will such a thing work, as we will not be using the Designer toolset to code/install any of the objects, also would additional configurations be required on the Web Server apart from setting up the mod_plsql to listen to SQL requests?

Have heard of a something of a Web PL/SQL toolkit.Can that help me in any way here?

Thank Raz

Frank van Bortel <fvanbortel_at_netscape.net> wrote in message news:<cb9s6a$2pb$1_at_news3.tilbu1.nb.home.nl>...
> jhking wrote:
>
> > Frank van Bortel wrote:
> >
> >> Jason King wrote:
> >>
>
> >>
> >>
> >> Nonsense, you can reverse engineer any PL/SQL in designer....
> >>
> >> It's just a pity you will not have any relations, code reusability,
> >> etc, what could have been inside the previous repository.
> >> Don't you have a backup, or application export lying around
> >> somewhere?
> >> Would be a tremendous help.
> >>
> >> If not - you're faced with the problem of distinguishing
> >> Designer added (transactional/referential) code from the actual
> >> application code.
> >> Not a nice task, as one of the long standing
> >> bugs has been the size of Designer generated packages and procedures
> >> being too large for SQLplus to execute...
> >
> >
> > Assuming we have mod$ mod$comp and mod$js$comp for a simple
> > one-component web pl/sql module you can indeed reverse engineer the 3
> > packages back, but they're just pl/sql code. There is no automated way
> > to turn them back into a designer module and module component and use
> > Designer to change, say, query criteria and regenerate. I believe that
> > was the OPs question.
> > For Developer modules I gather there is some ability to reverse engineer
> > them back into modules, but as I've never worked on Developer modules I
> > don't know how well that works.
>
> As I said.
> And there is no mention of developer modules
> in the OP's post, just revere engineering.
> Which indeed cannot be done, and engineering from the
> 'raw' pl/sql code is a pita.
> As I tried to make clear
Received on Wed Jun 23 2004 - 11:04:30 CEST