Hi Hassan and David, Thanks, for the response. Hassan of course you're right, there are always some standard for internal paths that have to be adhered to. However with relative paths coming from editors that edit html their documents can be seen exactly on the file system as they can be seen on a web server such as apache or IIS. For other editors that just use word documents the "Save As" HTML function packages all internal links relatively so once again the internal links just work when deploying on standard web-servers. They upload, no work from me ;).. Same goes with a number of other technologies (InDesign, Framemaker). I think I have come up with a solution though,, Redeploying my .war file was overwriting all the files I had under it's webapps/servletname directory. Seems to me if every time I re-deploy the war and copy the WEB-INF folder into another folder webapps/mysites all files in mysites remain intact and the servlet fires when accessing them (using <url-pattern>/*</url-pattern>). I haven't tested it thoroughly but it does seem to be working.
Thanks, Spencer On Dec 18, 2007 5:14 PM, David Smith <[EMAIL PROTECTED]> wrote: > Just by chance, could we see a sample url to one of your pages and a > sample internal link? It doesn't seem like this should be a big deal. > > --David > > > Spencer Tickner wrote: > > Hi Hassan, > > > > > > > > I wish I could establish a convention for internal links.. > > Unfortunately it's not possible as we get content from a diverse > > editor base where our system may not be the primary delivery method. > > Looking through our correspondence it would seem that I am trying to > > address the problem when I should just be stating it.. My problem is > > internal links are breaking in content served through my security > > servlet. Thanks so much for the time and patience.. I do really > > appreciate it. > > > > Spencer > > > > On Dec 18, 2007 3:33 PM, Hassan Schroeder <[EMAIL PROTECTED]> wrote: > > > >> On Dec 18, 2007 11:41 AM, Spencer Tickner <[EMAIL PROTECTED]> wrote: > >> > >> > >>> Once again thanks for the feedback,, the issue I would have with the > >>> solution above is that content (html, pdf, xml) is maintained by > >>> editors that I have no control over. They simply make their content > >>> look the way the want and then upload it to my application. > >>> > >> So you establish a convention for internal links; if they don't follow > >> it, their stuff is broken. Not your problem then, eh? :-) > >> > >> > >>> My app is responsible for controlling logging and accessing to these > >>> documents (Administrators have an interface for granting access to > >>> users on documents uploaded by the editor). I just can't seem to serve > >>> these documents up. > >>> > >> Is the issue broken internal links, or what? I do this kind of thing on > >> pretty much every site, so I'm afraid I'm not understanding where the > >> disconnect lies. > >> > >> -- > >> > >> Hassan Schroeder ------------------------ [EMAIL PROTECTED] > >> > >> --------------------------------------------------------------------- > >> To start a new topic, e-mail: users@tomcat.apache.org > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
