JavaScript Package Problems in WSG Generation (Des 6.0)
Date: Tue, 11 Jan 2000 00:52:40 GMT
Message-ID: <01bf5bce$25118900$1ac056a5_at_mb_ws400>
I'm using Designer 6.0 to generate WS apps. I have all my library/toolkit routines installed on OAS_PUBLIC, and they are the correct versions (wsgl.sql from '\cgenw60\cvwetc' etc.). The toolkit/libs are not causing any problems as all my public synonyms/grants are OK. I've looked at these packages and they are all as they should be.
When generating the WS packages from Des 6.0.3.6, the JavaScript routines,
such as CreateQueryJavaScript, CreateListJavaScript etc. are being placed
into separate packages (such as mod1$js$main where mod1$main would be the
package containing the bulk of the WSG code; in Des 2.1 you would only get
the one package). The problem is, the generated code does not seem to be
correct
and is causing repeated PLS-0201 and 306 errors. For example, the package
mod1$main makes a call to CreateQueryJavaScript but doesn't reference it as
mod1$js$main.CreateQueryJavaScript so you get a compilation error. Also the
actual mod1$js$main.CreateQueryJavaScript references things like
VF_BODY_ATTRIBUTES and LOV_FRAME which are defined only in mod1$main, so
you get identifier errors.
I don't think the WSGL packages have anything to do with this problem. Rather, the generated code packages themselves contain the errors, and it is only because the JavaScript routines are hived off to a separate WSG package in Des 6.0. Has anyone else ever had this problem, or know which templates Des 6 is using to generate this stuff? TIA.
-- Mike Ball B.Sc. Information Services Manager Qld Health Scientific Services 39 Kessels Road, Coopers Plains, 4108 AUSTRALIAReceived on Tue Jan 11 2000 - 01:52:40 CET