Hello
I think the portability has to do with that the file is read from the WEB-INF
directory and that it is not always possible to store thing there. So probably
a struts-config-config application would not have the same problem, depending
on how it wanted to handle the file.
A way to handle it, without having to store anything persistent on the server
would be that the user starts with selecting a struts-config.xml to upload
(or selects to work with a completely new configuration). Then do all
the wanted changes and finally request the web-app to generate a struts-config
with the current configuration, the file could then be delivered to the
browser and saved/viewed just as any other file.
Mikael
"Gogineni, Pratima" wrote:
> Hi,
>
> This could be done similar to the way they serialize the user database xml
> file in the struts example but this is what I saw under the changes and bug
> fixes section of the struts example application:
>
> "Removed any attempt to save the pseudo-database at application shutdown,
> because there is no portable mechanism to accomplish this task. "
>
> a. does anyone know why the mechanism is not portable?
> b. if above is true we will face the same problem when you try to serialize
> the struts-config.xml file?
>
> pratima
