Oxygen XML Forum

Hi,
In our organisation we want to store the framework file and CSS files in a centralized repository and distribute to the end users when they want to update.
Now when the user update these by invoking a custom action we are downloading files from the server and we can able to load the CSS file using AuthorEditorAccess.refresh().

But the problem is with the framework file. We couldn't able to load the framework file at the run time. Is there any API available to load the framework file?
And the worst part is we cannot even ask the user to restart Oxygen. Because when the user closing the oxygen it will overwrite the framework file if there is any modification. Is there any way to avoid this overwriting?

Hello,

In the current version (11.0) you cannot reload the framework file at runtime. We will consider adding this feature in a future version of Oxygen Author.

We will consider also saving the framework file on closing only if the framework was modified in Author. You can avoid overwriting the framework file by setting the file as read-only. Oxygen Author writes the framework file on closing only if it is not read-only. That means after the framework file is modified by updating from repository you set the framework file as read-only and you can restart Author without overwriting the file on closing.


Regards,
Sorin

Hi,

mveerasamy wrote:Hi,
And the worst part is we cannot even ask the user to restart Oxygen. Because when the user closing the oxygen it will overwrite the framework file if there is any modification. Is there any way to avoid this overwriting?

We'll try to fix this issue (not overwriting externally modified framework files) in time for Oxygen 11.1 (available in a couple of weeks).

The other issue (API for reloading frameworks) will be discussed for a future version.

Regards,
Radu

You can avoid overwriting the framework file by setting the file as read-only. Oxygen Author writes the framework file on closing only if it is not read-only

Sorry this is not working. I tried with java
File.setReadOnly();
and File.setWritable(false, false);

Even i manually checked it before closing oxygen. The framework file set to read-only. And when i tried to modify with other editors like notepad and editplus those editors failed to save and warn me that the file was a read-only file.
But the same read-only file was modified by Oxygen while closing (which completely wipedout all my changes).

Please let me know if there is any other way to stop Oxygen to modify this. This is affecting our workflow a lot.

Thanks in advance,
Muthu

Dear Muthu,

Indeed the workaround does not work because Oxygen first saves the framework to a temporary file in the same directory and then renames the temporary file to the ".framework" final file.
You can try to create a file as a sibling of the "name.framework" file called "name.framework.tmp" and make it read-only. Oxygen will fail to write to it on exit so the framework will not get re-written.

As I said, you will no longer have this problem in Oxygen 11.1 (available in a couple of weeks). If you contact us on the support address we can try to provide you with a beta test link for Oxygen 11.1.
docbook4.framework.tmp

Regards,
Radu

Thanks for the quick help.
Hmm... i think its better to wait for 11.1.

-Muthu
EBSCO

Thanks for the update in 11.1. My requirement is working now.