jGallery: supposedly being able to include directories from elsewhere in the file system by evaluating the docBase of a different context. However, this doesn't work with anything newer than Tomcat 3.X. The workaround with the properties file does not seem to work as well. It doesn't follow symlinks from the unpacked servlet to the real location, either. Unfortunately, Tomcat does follow the symlink when undeploying the servlet, subsequently removing all my pictures.
ginp: well, it seems to be in a much better state. Apart from storing passwords in clear text, crappy thumbnail quality and resizing the pictures according to some arbitrary values. And apparently it re-creates the thumbnails on every request. At least the servlet itself can be re-deployed without losing any configuration data.
Anyway, the thing about Java programmers ignoring best practices of system administration: they assume that you always re-deploy the whole application with the updated data -- or store everything in an SQL database. The concept of a file in a file system seems to be alien to these people.
Comments
zefirodragon.livejournal.com 18 years, 1 month ago
What was the problem with the Java galleries, regarding upgrades?
Link | Replywoelfisch.livejournal.com 18 years, 1 month ago
jGallery: supposedly being able to include directories from elsewhere in the file system by evaluating the docBase of a different context. However, this doesn't work with anything newer than Tomcat 3.X. The workaround with the properties file does not seem to work as well. It doesn't follow symlinks from the unpacked servlet to the real location, either. Unfortunately, Tomcat does follow the symlink when undeploying the servlet, subsequently removing all my pictures.
ginp: well, it seems to be in a much better state. Apart from storing passwords in clear text, crappy thumbnail quality and resizing the pictures according to some arbitrary values. And apparently it re-creates the thumbnails on every request. At least the servlet itself can be re-deployed without losing any configuration data.
Anyway, the thing about Java programmers ignoring best practices of system administration: they assume that you always re-deploy the whole application with the updated data -- or store everything in an SQL database. The concept of a file in a file system seems to be alien to these people.
Link | ReplyNew Comment