RE: Webfacing source changes ?

["Richard Casey" <casey_r@xxxxxxxxxxxxxxxx>]

Joe and Fergal,

At runtime, you DO need the display files in your library list. I'm using
WebSphere Express 5.0 and WDSC 5.0.1. If the display file can't be found,
you get a MCH3601 error. Keep in mind that the application itself still
thinks it is talking to a display file.

Richard

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Pluta
Sent: Tuesday, June 17, 2003 12:09 PM
To: Midrange Systems Technical Discussion
Subject: RE: Webfacing source changes ?


> From: fergal.o'flynn
>
> Dear All,
>             1.  If I webface my application will I still need to have the
> DSPF objects in my library list ?
>
>             2. Are there changes webfacing will require me to do
> to my DSPF
> DDS code that will require me to recompile my RPG code ?

Fergal, at least some of the developers of WebFacing hang out on WDSCI-L, so
you might get a better response there.

At the same time, let me take a stab at your question.

During conversion, you need to have access to the display file and its
source.  Webfacing converts that to WebFacing objects such as JSPs and
record definition objects (these used to be JavaBeans, but are now XML
files, similar to my product).

At runtime, you will need the display file in your library list, at least
you did in the beta release.  I will retest that assumption this week.

There are several keywords that are not supported or only partially
supported.  If these affect how your application works, you will need to
change your application.  Once you have eliminated any unsupported keywords,
then you won't need to make any further changes.

Joe