The answer is we don't. If the resource is not in a unique location, a global search is not preditable. I should have said more consistent.
You are correct, removal would cause an inconsistency, unless the resource->url cache also remembers the classloader. I'll add this check and commit it. Checking the WebIntegrationUnitTestCase at the moment, or was this already broken? Regards, Adrian >From: "Scott M Stark" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: <[EMAIL PROTECTED]> >Subject: Re: [JBoss-dev] Resource loading >Date: Sat, 31 Aug 2002 08:22:03 -0700 > >Ok, so you talking about another caching scheme based on a resource to url >mapping. >Your right this should be more efficient, but I don't see how this gives a >more predictable >result for non-unique resources. Its still a random selection depending on >the server >config and is a dynamic function of redeployment. Also, when a class loader >is removed >how do I know which resource to url mappings are affected and also need to >be >removed? > >----- Original Message ----- >From: "Adrian Brock" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Saturday, August 31, 2002 7:41 AM >Subject: Re: [JBoss-dev] Resource loading > > > > Efficieny > > --------- > > What does resource->classloader map give over resource->url? > > > > If the resource is unique they give the same result, the second > > more efficiently. > > > > Non unique non-local resource > > ----------------------------- > > If the resource is not unique, at least the resource->url gives > > predictable results within the same server session. > > > > Or are you saying I should fail the global getResource if it is not > > unique? > > > > This is not what happens at the moment. It returns a random > > resource depending on the current state of the packagesMap or the > > classLoaders HashSet. > > > > The resource->classloader map would also give a random result as each > > classloader discovers it has that resource name during a local lookup. > > > > Global resources not in the ULR > > ------------------------------- > > The resource->classloader could also fill up with entries that > > are actually unique. They are loaded through the parent boot classloader > > or system classpath during different local lookups. > > > > Regards, > > Adrian > > > > >------------------------------------------------------- >This sf.net email is sponsored by: OSDN - Tired of that same old >cell phone? Get a new here for FREE! >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >_______________________________________________ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
