Hey! >>>>>>>>>>> the solution we're using now is to provide an installer that the client runs at installation (or whenever they change databases or other info in the deployment descriptor) that unzips the war archive, prompts them for values to put into the deployment descriptor, and then zips up the war archive again. this strikes me as cumbersome and wrong in some way, however. it may also make upgrading the webapp later tricky since the upgrade installer will have to merge the deployment descriptors from the currently installed product and the upgraded version. >>>>>>>>>>>
You are on the right track, IMO. Our applications are not shrink-wrapped and are internal only, but we are mandated to treat it the same way as shrink-wrap. This is the approach that we are using now. We wrote an application to address this issue. It's working fine for now. We feel it is just the cost of doing business. Sans adieu, Danny Rubis ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
