Sorry Jules, I wasn't sure where to post it. But I was posting this more as a design discussion and a continuation of an earlier post about the njar protocol and whether it was really a good idea. Not that it isn't slick piece of encapsulation. I will try your recommendation and copy the .jsp into the my.war directory.
As far as the tool, Ultradev/Drumbeat/MX, I believe its Live Data feature predates the use of .war(s) to bundle .jsp(s) and servlets. But even that isn't the issue. Easy to use GUI tools lower development costs. Just because the spec says we are allowed to hide how we access an archive, doesn't mean its a good idea not to provide an "interface" by which development tools can interact with the container. If the above approach doesn't work, maybe we need to design one that does. If it does, we should document it and submit as a standard. Fred. At 05:29 PM 6/30/2002, Jules Gosnell wrote: >This should really be posted to jboss-user or the forums - jboss-dev is >for discussion amongst developers of (not 'on') JBoss. > >It's a BAD idea for any tool to be second guessing where a WebContainer >will be unpacking it's wars - because the spec does not say anything about >it. In fact the WebContainer may just run them packed. > >If your tool will only work with unpacked dirs - then deploy your war >unpacked (a dir hierarchy called e.g. my.war that mirrors the packed >tree), and write your files back into this. I THINK that Jasper will spot >the changes and react accordingly..... > > >Jules > > >Frederick N. Brier wrote: >>Let us say you are using a tool like Macromedia Dreamweaver UltraDev/MX >>and their LiveUpdate feature. This is where you are using a wysiwyg >>HTML/JSP editor and you can click a button, it uploads a temporary >>version of the file to the server, it invokes the JSP generating the >>page, gets the results, correlates the generated page to the original >>JSP, and displays as a web page. You can fill in data, press buttons, >>follow hyperlinks etc. You are working with a live page. Very cool and >>useful. But you have to be able to copy/ftp the JSP to a real directory. >>Now it was a mildly annoying, under JBoss 2.4.x, that with the hot deploy >>the temporary directory name could keep changing because Dreamweaver >>didn't know how to deal with it, but it worked. So the question is, how >>do I do that now with the .war appearing to be bundled up? Where would I >>copy the JSP? >>Fred. >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>Jboss-development mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
