On Wed, 12 Jul 2006, Charles O Nutter defenestrated me:
>    On 7/12/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
>        It would be nice if the magic load path element would be visible
>      and thus removable too.  Then that would give the flexibility to
>      remove classpath-based loading if  so desired.
> 
>    Yeah, I'd assume for command-line use (running it ruby-style) we would
>    not have this...you'd want to set up CLASSPATH like you would want to
>    see load path. For running within a container, though, we'd want the
>    magic load path element.

  Maybe.  I guess it depends on how much you want to lock down the
interpreters freedom to pull things in.  In a very controlled environment
you may not to load anything that may come in from the CLASSPATH?  
Brainstorming more than arguing the point...

-Tom

-- 
+ http://www.tc.umn.edu/~enebo +---- mailto:[EMAIL PROTECTED] ----+
| Thomas E Enebo, Protagonist  | "Luck favors the prepared    |
|                              |  mind." -Louis Pasteur       |


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jruby-devel mailing list
Jruby-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jruby-devel

Reply via email to