Web hosting colocation - Note for WebLogic 7.x and 8.1 users Note

Note for WebLogic 7.x and 8.1 users Note for WebSphere 4.0 Advanced Edition users Note for WebSphere and WebLogic users Chapter 11 Running and testing an enterprise bean Once you ve finished creating, compiling, and deploying an enterprise bean, you re ready to run it. For some servers, the quickest way to do that is to right-click its EJB module or the JAR file the module contains and select Run Using Defaults or Debug Using Defaults from the context menu. Or you can create a runtime configuration for your bean and select Run Using or Debug Using from the context menu.This starts the container for the currently selected application server using the JAR for this EJB module. Be patient as the start-up process takes a while. Context menu items for running or debugging don t appear when you right-click the JAR file or EJB module in the project pane. Deployment is not available at startup time for WebLogic 7.x and 8.1. Deploy your deployable modules after the server starts up. You can view the progress of the start-up process in the message pane. Any errors that occur will also appear there. If you want to run multiple JARs on the current application server, select multiple EJB modules. You must create an application module that contains your beans before deploying. For more information about application modules, see Creating an application module on page 111. After choosing Run or Debug from the toolbar, you must then take the extra step of choosing a Deploy menu command to deploy your beans. See Hot deploying to an application server on page 115. Testing your bean To test your bean, you can use the EJB Test Client wizard to generate test clients that make calls to your bean. The EJB Test Client wizard can generate three different types of test clients: An EJB test client application calls the methods of your bean. A JUnit test case makes use of the JUnit testing framework. It runs as a client in a separate VM from your EJB, passing parameters by value. A Cactus JUnit test case runs on the server, so it can access server-side resources and make local calls to your EJB from a web application. Chapter 11: Running and testing an enterprise bean 91
Our unmatched NT experience allows us to provide the most reliable and affordable hosting for our customers, just check NT Web Hosting services.


One Response to “Web hosting colocation - Note for WebLogic 7.x and 8.1 users Note”

  1. Jenzing Says:

    Great One…

    I must say, its worth it! My link, http://angelia.diblogotus.com/,thanks haha…

Leave a Reply