Damian wrote: ... > > A couple options: > > > > 1. Simply ensure that 0000000000.cfg is read-only. This currently > > causes a PermissionDenied exception that is displayed in > the GUI, but > > this would be trivial to suppress. > > > > 2. Allow a list of "exclude" zip file entries to be > specified for in > > upload.xml, and use this from the "entries" loops in Upload.java > > deployZipFile() and undeployZipFile(). But I see that the > upload.xml > > data is accessed though intermediate FileSettings.java > objects, which > > are not specific to zip files... > > > > I prefer 2 to 1.
I also prefer 2. But what's an acceptable way to jam the "exclude" list through FileSettings.java? My first instinct is to enhance the upload.xml schema, and then have Upload.java read the upload.xml files directly. But, surely there is some reason for FileSettings.java to be sitting between the two? -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
