archive-cr.com » CR » L » LLOBET.CO.CR

Total: 247

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Application Developer's Guide (8.0.24) - Development Processes
    to customize the Ant properties that are named in the build xml script This is done by creating a file named build properties in your project s top level directory The supported properties are listed in the comments inside the sample build xml script At a minimum you will generally need to define the catalina home property defining where Tomcat is installed and the manager application username and password You might end up with something like this Context path to install this application on app path hello Tomcat installation directory catalina home usr local apache tomcat version major minor Manager webapp username and password manager username myusername manager password mypassword In general you will not want to check the build properties file in to the CVS repository because it is unique to each developer s environment Now create the initial version of the web application deployment descriptor You can base web xml on the basic web xml file or code it from scratch cd my home directory cd myapp web WEB INF emacs web xml cvs add web xml cvs commit Note that this is only an example web xml file The full definition of the deployment descriptor file is in the Servlet Specification Edit Source Code and Pages The edit build test tasks will generally be your most common activities during development and maintenance The following general principles apply As described in Source Organization newly created source files should be located in the appropriate subdirectory under your project source directory Whenever you wish to refresh your development directory to reflect the work performed by other developers you will ask CVS to do it for you cd my home directory cd myapp cvs update dP To create a new file go to the appropriate directory create the file and register it with CVS When you are satisfied with it s contents after building and testing is successful commit the new file to the repository For example to create a new JSP page cd my home directory cd myapp web Ultimate destination is document root emacs mypage jsp cvs add mypage jsp build and test the application cvs commit Java source code that is defined in packages must be organized in a directory hierarchy under the src subdirectory that matches the package names For example a Java class named com mycompany mypackage MyClass java should be stored in file src com mycompany mypackage MyClass java Whenever you create a new subdirectory don t forget to register it with CVS To edit an existing source file you will generally just start editing and testing then commit the changed file when everything works Although CVS can be configured to required you to check out or lock a file you are going to be modifying this is generally not used Build the Web Application When you are ready to compile the application issue the following commands generally you will want a shell window open that is set to the project source directory so that

    Original URL path: http://www.llobet.co.cr/docs/appdev/processes.html (2015-10-31)
    Open archived version from archive


  • Sample Application
    sure your browser doesn t change file extension or append a new one The easiest way to run this application is simply to move the war file to your CATALINA HOME webapps directory Tomcat will automatically expand and deploy the application for you You can view it with the following URL assuming that you re running tomcat on port 8080 as is the default http localhost 8080 sample If you

    Original URL path: http://www.llobet.co.cr/docs/appdev/sample/ (2015-10-31)
    Open archived version from archive

  • Catalina Functional Specifications (8.0.24) - Administrative Apps - Supported Operations
    with this object Edit the configurable properties of the associated Manager Remove the associated Manager Create and configure a new Realm associated with this object Edit the configurable properties of the associated Realm Remove the associated Realm Create and configure a new Request Filter associated with this object Select and edit the configurable properties of an associated Request Filter Remove an associated Request Filter Default Context From the perspective of a particular Default Context it shall be possible to perform the following administrative operations Navigate to the owning Engine or Host Edit the configurable properties of this object Create and configure a new Environment Entry associated with this object Select and edit the configurable properties of an associated Environment Entry Remove an associated Environment Entry Create and configure a new JDBC Resource associated with this object Select and edit the configurable properties of an associated JDBC Resource Remove an associated JDBC Resource Engine From the perspective of a particular Engine it shall be possible to perform the following administrative operations Navigate to the owning Service Edit the configurable properties of this object Create and configure a new Access Logger associated with this object Edit the configurable properties of the associated Access Logger Remove the associated Access Logger Create and configure a new Default Context associated with this object Edit the configurable properties of the associated Default Context Remove the associated Default Context Create and configure a new Host associated with this object Select and edit the configurable properties of an associated Host Remove an associated Host Create and configure a new Realm associated with this object Edit the configurable properties of the associated Realm Remove the associated Realm Create and configure a new Request Filter associated with this object Select and edit the configurable properties of an associated Request Filter Remove an associated Request Filter Environment Entry From the perspective of a particular Environment Entry it shall be possible to perform the following administrative operations Navigate to the owning Context or Default Context Edit the configurable properties of this object Host From the perspective of a particular Host it shall be possible to perform the following administrative operations Navigate to the owning Engine Edit the configurable properties of this object Create and configure a new Access Logger associated with this object Edit the configurable properties of the associated Access Logger Remove the associated Access Logger Create and configure a new Context associated with this object Select and edit the configurable properties of an associated Context Remove an associated Context Create and configure a new Default Context associated with this object Edit the configurable properties of the associated Default Context Remove the associated Default Context Create and configure a new Realm associated with this object Edit the configurable properties of the associated Realm Remove the associated Realm Create and configure a new Request Filter associated with this object Select and edit the configurable properties of an associated Request Filter Remove an associated Request Filter JDBC Resource From the perspective of a

    Original URL path: http://www.llobet.co.cr/docs/funcspecs/fs-admin-opers.html (2015-10-31)
    Open archived version from archive


  • be controlled by specifying the tomcat output property in the build properties file NOTE Do not run the build as the root user Building and running Tomcat does not require root privileges 4 Updating sources and rebuilding It is recommended that you regularly update the downloaded Tomcat 8 0 sources using your SVN client For a quick rebuild of only modified code you can use cd tomcat source ant 5 Special builds There are several targets in Tomcat build files that are useful to be called separately They build components that you may want to build quickly or ones that are included in the full release and are not built during the default deploy build 5 1 Building documentation The documentation web application is built during the default deploy build It can be built quickly by using the following commands cd tomcat source ant build docs The output of this command will be found in the following directory output build webapps docs The API documentation Javadoc is built during a release build It is easy to build it separately by using the following commands cd tomcat source ant javadoc The output of this command will be found in the following directories output dist webapps docs api output dist webapps docs elapi output dist webapps docs jspapi output dist webapps docs servletapi 5 2 Building the extras commons logging webservices etc These components are documented on the Additional Components extras html page of documentation They are built during a release build You can build them by using the following commands cd tomcat source ant extras 5 3 Building the embedded packages These are built during a release build You can build them by using the following commands cd tomcat source ant embed 6 Building a full release as provided via the ASF download pages A full release includes the Windows installer which requires a Windows environment to be available to create it If not building in a Windows environment the build scripts assume that Wine is available If this is not the case the skip installer property may be set to skip the creation of the Windows installer 1 Configure GPG if needed If the released artifacts have to be cryptographically signed with a PGP signature like the official ASF releases are the following property can be added to the build properties file Location of GPG executable used only for releases gpg exec path to gpg You do not need it if you do not plan to sign the release If gpg exec property does not point to an existing file it will be ignored and this feature will be disabled You will be prompted for the GPG passphrase when the release build starts unless gpg passphrase property is set 2 If building the Windows installer If running the build in a UAC enabled environment building the Windows installer requires elevated privileges The simplest way to do this is to open the command prompt used for the build with the Run

    Original URL path: http://www.llobet.co.cr/docs/BUILDING.txt (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Architecture (8.0.24) - Architecture Overview
    a Service may have multiple Connectors the Engine receives and processes all requests from these connectors handing the response back to the appropriate connector for transmission to the client The Engine interface may be implemented to supply custom Engines though this is uncommon Note that the Engine may be used for Tomcat server clustering via the jvmRoute parameter Read the Clustering documentation for more information Host A Host is an association of a network name e g www yourcompany com to the Tomcat server An Engine may contain multiple hosts and the Host element also supports network aliases such as yourcompany com and abc yourcompany com Users rarely create custom Hosts because the StandardHost implementation provides significant additional functionality Connector A Connector handles communications with the client There are multiple connectors available with Tomcat These include the HTTP connector which is used for most HTTP traffic especially when running Tomcat as a standalone server and the AJP connector which implements the AJP protocol used when connecting Tomcat to a web server such as Apache HTTPD server Creating a customized connector is a significant effort Context A Context represents a web application A Host may contain multiple contexts each with a unique path The Context interface may be implemented to create custom Contexts but this is rarely the case because the StandardContext provides significant additional functionality Comments Tomcat is designed to be a fast and efficient implementation of the Servlet Specification Tomcat came about as the reference implementation of this specification and has remained rigorous in adhering to the specification At the same time significant attention has been paid to Tomcat s performance and it is now on par with other servlet containers including commercial ones In recent releases of Tomcat mostly starting with Tomcat 5 we have begun efforts to

    Original URL path: http://www.llobet.co.cr/docs/architecture/overview.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Architecture (8.0.24) - Startup
    service description A text description of the startup procedure is available here diagram A UML sequence diagram of the startup procedure is available here comments The startup process can be customized in many ways both by modifying Tomcat code and by implementing your own LifecycleListeners which are then registered in the server xml configuration file Comments Notice This comments section collects your suggestions on improving documentation for Apache Tomcat If

    Original URL path: http://www.llobet.co.cr/docs/architecture/startup.html (2015-10-31)
    Open archived version from archive

  • Apache Tomcat 8 Architecture (8.0.24) - Request Process Flow
    TODO diagrams A UML sequence diagram of the request process is available here A UML sequence diagram of the authentication process is available here comments The Servlet Specification provides many opportunities for listening in using Listeners or modifying using Filters the request handling process even before the request arrives at the servlet that will handle it Comments Notice This comments section collects your suggestions on improving documentation for Apache Tomcat

    Original URL path: http://www.llobet.co.cr/docs/architecture/requestProcess.html (2015-10-31)
    Open archived version from archive

  • Catalina Functional Specifications (8.0.24) - Administrative Apps - Overall Requirements
    administrative capabilities shall be disabled It shall be necessary for a system administrator to specifically enable the desired access methods such as by adding a username password with a specific role to the Tomcat user s database Administrative functions shall be realized as direct calls to corresponding Catalina APIs or through a business logic layer that is independent of the access method used to initiate it The common business logic components shall be implemented in package org apache catalina admin The common business logic components shall be built as part of the standard Catalina build process and made visible in the Catalina class loader The Java components required for each access method shall be implemented in subpackages of org apache catalina admin The build scripts should treat each access method as optional so that it will be built only if the corresponding required APIs are present at build time It shall be possible to save the configured state of the running Tomcat container such that this state can be reproduced when the container is shut down and restarted Administrative commands to start up and shut down the overall Tomcat container are out of scope for the purposes of these applications It is assumed that other usually platform specific mechanisms will be used for container startup and shutdown Dependencies Environmental Dependencies The following environmental dependencies must be met in order for administrative applications to operate correctly For access methods that require creation of server sockets the appropriate ports must be configured and available Container Dependencies Correct operation of administrative applications depends on the following specific features of the surrounding container To the maximum extent feasible Catalina components that offer direct administrative APIs and property setters shall support live changes to their operation without requiring a container restart External Technologies The availability of the following technologies can be assumed for the implementation and operation of the various access methods and the corresponding administrative business logic FIXME This list below is totally outdated but nobody cares about the administrative app anymore It is removed and unsupported since Tomcat 6 0 Java Standard Edition Version 1 2 or later Servlet 2 4 supported natively by Tomcat 5 JavaServer Pages 2 0 supported natively by Tomcat 5 JavaServer Pages Standard Tag Library 1 0 Jakarta Taglibs Standard 1 0 3 Struts Framework Version 1 0 MVC Framework for Web Applications TO BE DETERMINED Application for hosting SOAP based web services Functionality Properties of Administered Objects Functional requirements for administrative applications are specified in terms of Administered Objects whose definitions and detailed properties are listed here In general Administered Objects correspond to components in the Catalina architecture but these objects are defined separately here for the following reasons It is possible that the administrative applications do not expose every possible configurable facet of the underlying components In some cases an Administered Object from the perspective of an administrative operation is realized by more than one Catalina component at a finer grained level of detail It is

    Original URL path: http://www.llobet.co.cr/docs/funcspecs/fs-admin-apps.html (2015-10-31)
    Open archived version from archive



  •