Yeah we don't really do much with regular classpath, but there is nothing stopping us from calling ClassLoader.getSystemClassLoader().getResource() if we want to source something from there.
I might argue against this because it would become the 4th distinct way to load tc.properties though :-) > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Eugene Kuleshov > Sent: Monday, August 20, 2007 12:04 PM > To: [email protected] > Subject: Re: [tc-dev] basic config > > > Tim probably would chime in on that, but we don't normally see user > classpath from DSO code and vice versa. Not to mention that DSO stuff is > initialize much earlier then any user contexts... > > regards, > Eugene > > > Taylor Gautier wrote: > > Ok. That sounds to me like tc.properties ;-). > > > > However, I have a request. Is it possible to load tc.properties from > > the root classpath? e.g. getResource("/tc.properties") - loading them > > from the TC installation or the command line seems to be preventative > > from using them in a user context, even if that user is advanced. > > > > > > > > Steven Harris wrote: > >> I think the point is to have a way or place to have "default" > >> modules. We could of course hard code those but that is inflexible so > >> we are looking to add some sort of hook where we can have these > >> defaults but make them adjustable for the super advanced user. > >> Cheers, > >> Steve > >> > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
