Software: Apache. PHP/5.5.15 

uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 

SYSTEM 

Safe-mode: OFF (not secure)

E:\nuevo\tomcat\webapps\docs\   drwxrwxrwx
Free 10.09 GB of 239.26 GB (4.22%)
Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ]
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     class-loader-howto.html (20.23 KB)      -rw-rw-rw-

Apache Tomcat 7
Version 7.0.42, Jul 2 2013
Links
Docs Home
FAQ
User Comments
User Guide
1) Introduction
2) Setup
3) First webapp
4) Deployer
5) Manager
6) Realms and AAA
7) Security Manager
8) JNDI Resources
9) JDBC DataSources
10) Classloading
11) JSPs
12) SSL
13) SSI
14) CGI
15) Proxy Support
16) MBean Descriptor
17) Default Servlet
18) Clustering
19) Load Balancer
20) Connectors
21) Monitoring and Management
22) Logging
23) APR/Native
24) Virtual Hosting
25) Advanced IO
26) Additional Components
27) Mavenized
28) Security Considerations
29) Windows Service
30) Windows Authentication
31) Tomcat's JDBC Pool
32) WebSocket
Reference
Release Notes
Configuration
Tomcat Javadocs
Servlet Javadocs
JSP 2.2 Javadocs
EL 2.2 Javadocs
JK 1.2 Documentation
Apache Tomcat Development
Building
Changelog
Status
Developers
Architecture
Functional Specs.
Tribes
Class Loader HOW-TO
Table of Contents

Overview
Class Loader Definitions
XML Parsers and Java
Running under a security manager
Overview


Like many server applications, Tomcat installs a variety of class loaders
(that is, classes that implement java.lang.ClassLoader) to allow
different portions of the container, and the web applications running on the
container, to have access to different repositories of available classes and
resources.  This mechanism is used to provide the functionality defined in the
Servlet Specification, version 2.4 — in particular, Sections 9.4
and 9.6.

In a Java environment, class loaders are
arranged in a parent-child tree.  Normally, when a class loader is asked to
load a particular class or resource, it delegates the request to a parent
class loader first, and then looks in its own repositories only if the parent
class loader(s) cannot find the requested class or resource.  Note, that the
model for web application class loaders differs slightly from this,
as discussed below, but the main principles are the same.

When Tomcat is started, it creates a set of class loaders that are
organized into the following parent-child relationships, where the parent
class loader is above the child class loader:

      Bootstrap
          
bool(false)


:: Command execute ::
Enter: 
 
Select: 
-----------------------------------------------------------show opened ports 




 
:: Search ::
  - regexp 

 
:: Upload ::
 
[ ok ]



:: Make Dir ::
 
[ ok ]
:: Make File ::
 
[ ok ]

:: Go Dir ::
 
:: Go File ::
 

--[ c99shell v. 1.0 pre-release build #13 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0156 ]--