Bug 339983

Comment 1 Angel Vera 2011-03-17 14:29:18 EDT

If I understand the problem correctly,....

As long as the xml file is updated in the file system, the javascript running from the server should be able to pick up the change as the file has been updated in the filesystem. 

I believe that once the IDE has open the xml file in an editor, it keeps a in memory state of the file, and if the file changes outside of IDE, the IDE would not know.

I am not entirely sure of the properties of the WASCE in terms of how it handles the publishing of the files from your dynamic web project (ie, if it copies the resources to a temporary location or just run them from the project location). But I wouldn't think it matters, can you try with Tomcat? 

Providing a testcase would also help with the faster resolution.

Comment 2 dmachop 2011-03-20 04:01:05 EDT

(In reply to comment #1)
> If I understand the problem correctly,....
> 
> As long as the xml file is updated in the file system, the javascript running
> from the server should be able to pick up the change as the file has been
> updated in the filesystem. 
> 
> I believe that once the IDE has open the xml file in an editor, it keeps a in
> memory state of the file, and if the file changes outside of IDE, the IDE would
> not know.
> 
> I am not entirely sure of the properties of the WASCE in terms of how it
> handles the publishing of the files from your dynamic web project (ie, if it
> copies the resources to a temporary location or just run them from the project
> location). But I wouldn't think it matters, can you try with Tomcat? 
> 
> Providing a testcase would also help with the faster resolution.

Well, in that case what I observed was the same set of code worked in a different IDE [Netbeans with Glassfish 3].
Clarification in terms of the working of the WASCE server -- the server copies into the directory C:\Program Files\IBM\WebSphere\AppServerCommunityEdition\var\project name\files.xml where the file is not updated when compared with the project directory.
But no success there running glassfish too.

I think that the problem with Eclipse is the auto-refresh which takes too much time to update the project view in the IDE.

Comment 3 Angel Vera 2011-03-31 13:21:06 EDT

I think you are running into a problem particular problem that might be hard to fix. The actual problem is not eclipse but rather the server adapters code, it is even arguable to say that this is a server adapter problem. 

Allow me to give you the convoluted answer first...

The Eclipse IDE is very flexible interms of how a project can be structured by a user (it allows link resources, multiple source folder, multiple output folders, ...) In some cases (not all) some server adapter can't interpret the layout of an EAR Project, Dynamic Web project or similars, as it is configured by the user, or as it is  layout in the file system. It is in this cases were server adapter will require to make a read your project files, and copy them into a format that the server adapter can interpret them. Since the files are actually copied to a different temp location (sometimes this temp location is the actual server deployed application path) the server doesn't use the files from the project directly. 

It is because of this copy effect that you experiencing this problem. So far I haven't seen any server adapter that refreshes the file that are copied into this temp location back to the location of the project. Meaning that this copy process is a one way street.

I would suggest talking to the server adapter directly and see how if they would be willing to provide an option where the files are always kept in sync in both side, no matter where the update came from. 

I am closing this bug as NOT_ECLIPSE