That's fine. I was primarily confused by the url under tmp/deploy which ended up with bits that looked like there was a directory under deploy (not tmp/deploy) which had the same name as the jar. This just confused me as I was trying to find out why a FNF exception was thrown.
--jason Scott M Stark wrote: >I find this easier to debug, not harder. There may be another >way to use the original url, but until its proven we are not >going change the deploy structure. > >xxxxxxxxxxxxxxxxxxxxxxxx >Scott Stark >Chief Technology Officer >JBoss Group, LLC >xxxxxxxxxxxxxxxxxxxxxxxx >----- Original Message ----- >From: "Jason Dillon" <[EMAIL PROTECTED]> >To: "David Jencks" <[EMAIL PROTECTED]> >Cc: <[EMAIL PROTECTED]> >Sent: Tuesday, February 26, 2002 3:50 PM >Subject: Re: [JBoss-dev] Long tmp deploy urls > > >>Well, it would be nice to not need them... seems like there has to be a >>better way to do this... what I don't know. >> >>Any way to trick java into thinking that the codebase is where the jar >>orginated from? >> >>--jason >> >> >>David Jencks wrote: >> >>>On 2002.02.26 04:31:22 -0500 Jason Dillon wrote: >>> >>>>These are murder when trying to debug something with deployment... do we >>>>really need this? >>>> >>>>--jason >>>> >>>I think so. They got longer so security permissions were determinable. >>>They also let you predict where your deployment package will end up. Try >>>putting jboss near the root of your filesystem;-) >>> >>>david jencks >>> > > > >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
