Re: WebFacing - Client JavaScript load sequence

I'm having to exit the WDSc IDE entirely though - even restarting the
application server instance doesn't work.

Stu





Mike Hockings <hockings@xxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
17/10/2007 13:24
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] WebFacing - Client JavaScript load sequence






That is correct. The directory contents are read once when the webapp
starts and the files included on each application page thereafter. If you

add or remove files you would need to stop then start the webapp in order
for the change to make a difference.

Mike

Mike Hockings, P.Eng.
System i Application Development Tools - CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 905 413 3199




sbramley@xxxxxxxxx
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
10/17/2007 04:12 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] WebFacing - Client JavaScript load sequence






It is not the JavaScript itself that is being cached, it is the
enumeration of the files in the usr directory. i.e. If I delete a file
from the directory (using the IDE), there will still be <script> tags
generated for it.

Stu




Mike Hockings <hockings@xxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
16/10/2007 17:16
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] WebFacing - Client JavaScript load sequence






There has not been any changes to the way the user defined JavaScript is
loaded. There is no specific order that the files are loaded, the files
in the usr directory are enumerated when the webapp starts and then an
include is generated for each file when the page is emitted. I _think_
that the order is actually set by the order they are in the file system
but I have not done any research to confirm that. As far as I know the
actual name of the file has no bearing on the order in which they are
loaded (unless the OS that WAS is running on uses that to order things).

The JavaScript is likely cached by the browser so you may wish to test
with a new instance of IE started outside of WDSC just to be sure that
the browser is not caching the files.

Mike

Mike Hockings, P.Eng.
System i Application Development Tools - CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 905 413 3199




sbramley@xxxxxxxxx
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
10/16/2007 11:13 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
WDSCI-L@xxxxxxxxxxxx
cc

Subject
[WDSCI-L] WebFacing - Client JavaScript load sequence






Has the load sequence for JavaScript files in the ClientScript/usr folder
changed at all at version 7 of WDSc?

We have a DHTML calendar, added as per the instructions in one of the
Webfacing Redbooks. The JavaScript files need to be loaded in a certain
sequence, and the Redbook recommends naming the *.js files so that they
are added in the desired order.

This worked in previous versions of WDSc, however since upgrading to
version 7, the sequence does not seem to be guaranteed. For example if we
place the files 1.js, 2.js and 3.js in the ClientScript/usr folder, the
<script> tags are being sequenced 2.js, 3.js and then 1.js. (This is not
consistent across different projects/workspaces though). I can get around




this issue by moving the files into another folder and hard-coding the
tags in PageBuilder.jsp - but this is not ideal.

There also seems to be some horrific caching going on - I have to shut
down WAS and close/reopen WDSc every time I make changes to the contents
of this folder in order for the changes to be picked up.. sometimes more
than once.

Regards,
Stu