Webdav refreshInProject not working

[Lilia]

Hello,

We are using Oxygen Developer 17.1 Our project consists of webdav folders. We cannot add/delete files via api in the project tree: .xpr file is not updated via StandalonePluginWorkspace.refreshInProject or StandalonePluginWorkspace.delete (on delete actual file is deleted, but this is not reflected in the project tree).

Front end action in editor tab menu "Add to project" works great. But seems there is no api access to that component.

Could you please help us to troubleshoot this. Thanks.

[Radu]

Hi,

Indeed you can use the "Add to project" to add remove files to the Oxygen Project, but the view is static, it does not refresh to reflect added/removed files from the remote server.

The "StandalonePluginWorkspace.refreshInProject" API works only for local files and folders referenced in the project. Also, as you saw the "StandalonePluginWorkspace.delete" API can be used to delete a resource but it does not refresh the project.

So you should avoid using the Project to map remote webdav resources. Ideally you would use the ""Data Source Explorer" view (Window menu->Show View), it is a live representation of the webdav remote folder and it can thus replace the Project view which is useful more for local files.

Regards,
Radu

[Lilia]

Hi Radu,

In "Data Source Explorer" view file, that added on the file system level, appears in the "Data Source Explorer" tree view only after manual refresh of the root folder. Is there a setting that can force refresh any time webdav file structure changes or api that can be used to force refresh / add / delete from the plugin?

Thank you.

[Radu]

Hi Lilia,

I'm afraid we do not have API for this but I will add an issue on our side. Maybe we can make the existing API refreshInProject(URL) to also refresh the Data Source Explorer if it contains that URL.
Just to better understand your situation, you already have a plugin for Oxygen, right?
Do you have some kind of CMS implementation? Another possible solution for you would be to create your custom CMS browser view and take control over the way in which the CMS is browsed without using our Project or Data Source Explorer view.

Regards,
Radu

[Lilia]

Yes, we recently added various plugins for Oxygen, integrated with our CMS implementation, but we can not go live until this issue resolved.

Do you have an example of custom CMS browser view the takes control over Project or Data Source Explorer view? It would be great to keep the look and feel similar to original view.

Thank you!

[Radu]

Hi,

Most CMS vendors opted to create their own CMS browser views. They also usually opt to have their own custom URL protocol implementation:

https://www.oxygenxml.com/doc/versions/ ... lugin.html

This custom view would need to be implemented using Java Swing. We do not have an example for this.

Regards,
Radu