Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "J2EE Smoke Test (WTP 2.0)"

(New page: ;Setup: Install a J2EE-compatible server, such as JOnAS or WebSphere Add the server in Window->Preferences...->Server->Installed Runtimes Install the XDoclet support (1.2.1, 1.2.2, or 1.2...)
 
m (Export the Web project)
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
;Setup:
+
== J2EE 1.4 ==
  
Install a J2EE-compatible server, such as JOnAS or WebSphere
+
=== Setup ===
Add the server in Window->Preferences...->Server->Installed Runtimes
+
* Install a J2EE 1.4-compatible server, such as JOnAS, JBoss or WebSphere
Install the XDoclet support (1.2.1, 1.2.2, or 1.2.3)
+
* Add the server in Window -> Preferences... -> Server -> Installed Runtimes
Add the XDoclet support in Window->Preferences...->XDoclet
+
* Install the XDoclet support (1.2.1, 1.2.2 or 1.2.3)
Expand the XDoclet node and configure the ejbdoclet and webdoclet support for your installed server(s).
+
* Add the XDoclet support in Window -> Preferences... -> XDoclet
 +
* Expand the XDoclet node and configure the ejbdoclet and webdoclet support for your installed server(s).
  
Verify the following function:
+
=== Create resources ===
  
;Create resources
+
==== Create a Web 2.4 project ====
:Create a web project, targeted at a server
+
* Target it at the installed J2EE server
:Create a servlet inside the project - Java Package of test, specify a name, and select "Generate an annotated servlet class file"
+
* Choose "Dynamic Web Project with XDoclet" from Configurations
:Create a JSP inside the project - file name index.jsp
+
* Create a servlet inside the project
:Add the following text into the body: <body>This is the Smoke Test.</body>
+
** enter "test" for Java package
:Ensure it builds and is targeted to a server correctly
+
** specify a name
 +
** select the "Generate an annotated servlet class file" checkbox
 +
** give "test" for servlet's name (second page)
 +
** leave only the "doGet" checkbox checked (third page - inherited abstract methods)
 +
** add the following code in the doGet() method of the servlet class
 +
response.getOutputStream().println("This is a test servlet. ");
 +
* Create a JSP inside the project
 +
** file name: index.jsp
 +
** add the following text inside the <body> tag
 +
This is the Smoke Test.
 +
* Ensure the project builds and is targeted to the server correctly
  
:Create an EAR project, targeted at a server
+
==== Create an EAR 1.4 project ====
 +
* Target it at the installed J2EE server
 +
* Select the Web 2.4 project as J2EE module (third page)
  
:Create an EJB project, targeted at a server
+
==== Create an EJB 2.1 project ====
 +
* Target it at the installed J2EE server
 +
* Choose "EJB Project with XDoclet" from Configurations
 +
* Choose "Add project to an EAR" and choose the previously created EAR project
 +
* Create a new XDoclet Enterprise JavaBean
 +
** choose Session Bean as a type
 +
** enter "test" for Java package
  
;Add EJB to an EAR
+
=== Verify Project Explorer content ===
:Bring up the Properties dialog of the EAR project
+
:Select J2EE Modules
+
:Check the checkbox next to the EJB project name
+
:Press OK
+
  
;Add a bean to the EJB project
+
==== Verify the Web project ====
:Create a new XDoclet Enterprise JavaBean as a Session Bean in package test
+
* verify there is a node for the deployment descriptor
 +
* the deployment descriptor node should specify version 2.4
 +
* verify that the servlet class is listed under the "Servlets" node
 +
* verify that the "/test ->" url mapping is listed under the "Servlet Mappings" node
  
;Verify the EAR module in the navigator
+
==== Verify the EJB project ====
:Expand the EAR - verify that there is a node for the deployment descriptor.
+
* verify there is a node for the deployment descriptor
:Expand the deployment descriptor node- verify that there are "Modules" and "Utility JARs" nodes
+
* the deployment descriptor node should specify version 2.1
:Expand the Modules node - verify that the EJB reference is shown
+
* verify that the there is a node for the bean under the "Session Beans" node
 +
** verify that under this node all bean classes and interfaces are listed
  
;Export the projects
+
==== Verify the EAR project ====
:Export the web project - verify that the deployment descriptor, Servlet class, and libraries are included in the WAR.
+
* verify there is a node for the deployment descriptor
:Export the EJB project - verify that all of the classes and the deployment descriptor are included in the EJB JAR.
+
* the deployment descriptor node should specify version 1.4
 +
* expand the deployment descriptor node
 +
** verify there are "Modules" and "Utility JARs" nodes
 +
* expand the Modules node
 +
** verify there are references to the Web and EJB modules
  
;See also
+
=== Export the projects ===
:[[WTP Smoke Test Scenarios R15 | Click here to view smoke test scenarios for WTP 1.5.]]
+
 
:[[WTP Smoke Test Scenarios R20 | Click here to view smoke test scenarios for WTP 2.0.]]
+
==== Export the Web project ====
:[[WTP Smoke Test Scenarios R30 | Click here to view smoke test scenarios for WTP 3.0.]]
+
* verify that the deployment descriptor XML, Servlet classes, JSP files and libraries are included in the WAR
:[[WTP Smoke Test Results | Click here to view WTP smoke test results.]]
+
 
:[[Web_Tools_Project | Back to Web Tools Wiki Home]]
+
==== Export the EJB project ====
 +
* verify that all of the classes and the deployment descriptor XML are included in the EJB JAR
 +
 
 +
==== Export the EAR project ====
 +
* verify that deployment descriptor XML and the WARs and EJB JARs of the referenced J2EE modules are included
 +
 
 +
=== Deploy and Run the application ===
 +
* Run the test servlet
 +
** Right click on the servlet node in the deployment descriptor tree and choose Run As -> Run on Server
 +
** Select the targeted J2EE server
 +
** The internal browser should request the test servlet and show the result page
 +
* Run the index.jsp
 +
** Right click on the index.jsp and choose Run As -> Run on Server
 +
** Select the targeted J2EE server
 +
** The internal browser should request the index.jsp and show the result page
 +
 
 +
== Java EE 5 ==
 +
 
 +
=== Setup ===
 +
* Install a Java EE 5-compatible server, such as Glassfish or JBoss
 +
* Add the server in Window -> Preferences... -> Server -> Installed Runtimes
 +
 
 +
=== Create resources ===
 +
 
 +
==== Create a Web 2.5 project ====
 +
* Target it at the installed Java EE server
 +
* Create a servlet inside the project
 +
** enter "test" for Java package
 +
** specify a name
 +
** give "test" for servlet's name (second page)
 +
** leave only the "doGet" checkbox checked (third page - inherited abstract methods)
 +
** add the following code in the doGet() method of the servlet class
 +
response.getOutputStream().println("This is a test servlet. ");
 +
* Create a JSP inside the project
 +
** file name: index.jsp
 +
** add the following text inside the <body> tag
 +
This is the Smoke Test.
 +
* Ensure the project builds and is targeted to the server correctly
 +
 
 +
==== Create an EAR 5 project ====
 +
* Target it at the installed Java EE server
 +
* Select the Web 2.5 project as J2EE module (third page)
 +
 
 +
==== Create an EJB 3.0 project ====
 +
* Target it at the installed Java EE server
 +
* Choose "Add project to an EAR" and choose the previously created EAR 5 project
 +
 
 +
=== Verify Project Explorer content ===
 +
 
 +
==== Verify the Web project ====
 +
* verify there is no node for the deployment descriptor
 +
* verify there is a web.xml file under the WEB-INF folder
 +
* verify that the servlet and its mapping are described in the web.xml
 +
 
 +
==== Verify the EJB project ====
 +
* verify there is no node for the deployment descriptor
 +
* verify there is no ejb-jar.xml file under the META-INF directory
 +
 
 +
==== Verify the EAR project ====
 +
* verify there is no node for the deployment descriptor
 +
* verify there is no application.xml file under the META-INF directory
 +
* verify that the Web and EJB modules are listed and checked in the J2EE Module Dependencies property page
 +
 
 +
=== Export the projects ===
 +
 
 +
==== Export the Web project ====
 +
* verify that the deployment descriptor XML, Servlet classes, JSP files and libraries are included in the WAR
 +
 
 +
==== Export the EJB project ====
 +
* verify that all of the classes are included in the EJB JAR
 +
* verify there is no deployment descriptor XML
 +
 
 +
==== Export the EAR project ====
 +
* verify that the WARs and EJB JARs of the referenced J2EE modules are included
 +
* verify there is no deployment descriptor XML
 +
 
 +
=== Deploy and Run the application ===
 +
* Run the test servlet
 +
** Right click on the servlet class and choose Run As -> Run on Server
 +
** Select the targeted Java EE server
 +
** The internal browser should request the test servlet and show the result page
 +
* Run the index.jsp
 +
** Right click on the index.jsp and choose Run As -> Run on Server
 +
** Select the targeted Java EE server
 +
** The internal browser should request the index.jsp and show the result page
 +
 
 +
== See also ==
 +
{{J2EE_Smoke_Test_See_Also_Links}}
 +
 
 +
[[Category:Eclipse Web Tools Platform Project]][[Category:WTP Testing Related| ]]

Latest revision as of 04:51, 21 September 2007

J2EE 1.4

Setup

  • Install a J2EE 1.4-compatible server, such as JOnAS, JBoss or WebSphere
  • Add the server in Window -> Preferences... -> Server -> Installed Runtimes
  • Install the XDoclet support (1.2.1, 1.2.2 or 1.2.3)
  • Add the XDoclet support in Window -> Preferences... -> XDoclet
  • Expand the XDoclet node and configure the ejbdoclet and webdoclet support for your installed server(s).

Create resources

Create a Web 2.4 project

  • Target it at the installed J2EE server
  • Choose "Dynamic Web Project with XDoclet" from Configurations
  • Create a servlet inside the project
    • enter "test" for Java package
    • specify a name
    • select the "Generate an annotated servlet class file" checkbox
    • give "test" for servlet's name (second page)
    • leave only the "doGet" checkbox checked (third page - inherited abstract methods)
    • add the following code in the doGet() method of the servlet class
response.getOutputStream().println("This is a test servlet. ");
  • Create a JSP inside the project
    • file name: index.jsp
    • add the following text inside the <body> tag
This is the Smoke Test.
  • Ensure the project builds and is targeted to the server correctly

Create an EAR 1.4 project

  • Target it at the installed J2EE server
  • Select the Web 2.4 project as J2EE module (third page)

Create an EJB 2.1 project

  • Target it at the installed J2EE server
  • Choose "EJB Project with XDoclet" from Configurations
  • Choose "Add project to an EAR" and choose the previously created EAR project
  • Create a new XDoclet Enterprise JavaBean
    • choose Session Bean as a type
    • enter "test" for Java package

Verify Project Explorer content

Verify the Web project

  • verify there is a node for the deployment descriptor
  • the deployment descriptor node should specify version 2.4
  • verify that the servlet class is listed under the "Servlets" node
  • verify that the "/test ->" url mapping is listed under the "Servlet Mappings" node

Verify the EJB project

  • verify there is a node for the deployment descriptor
  • the deployment descriptor node should specify version 2.1
  • verify that the there is a node for the bean under the "Session Beans" node
    • verify that under this node all bean classes and interfaces are listed

Verify the EAR project

  • verify there is a node for the deployment descriptor
  • the deployment descriptor node should specify version 1.4
  • expand the deployment descriptor node
    • verify there are "Modules" and "Utility JARs" nodes
  • expand the Modules node
    • verify there are references to the Web and EJB modules

Export the projects

Export the Web project

  • verify that the deployment descriptor XML, Servlet classes, JSP files and libraries are included in the WAR

Export the EJB project

  • verify that all of the classes and the deployment descriptor XML are included in the EJB JAR

Export the EAR project

  • verify that deployment descriptor XML and the WARs and EJB JARs of the referenced J2EE modules are included

Deploy and Run the application

  • Run the test servlet
    • Right click on the servlet node in the deployment descriptor tree and choose Run As -> Run on Server
    • Select the targeted J2EE server
    • The internal browser should request the test servlet and show the result page
  • Run the index.jsp
    • Right click on the index.jsp and choose Run As -> Run on Server
    • Select the targeted J2EE server
    • The internal browser should request the index.jsp and show the result page

Java EE 5

Setup

  • Install a Java EE 5-compatible server, such as Glassfish or JBoss
  • Add the server in Window -> Preferences... -> Server -> Installed Runtimes

Create resources

Create a Web 2.5 project

  • Target it at the installed Java EE server
  • Create a servlet inside the project
    • enter "test" for Java package
    • specify a name
    • give "test" for servlet's name (second page)
    • leave only the "doGet" checkbox checked (third page - inherited abstract methods)
    • add the following code in the doGet() method of the servlet class
response.getOutputStream().println("This is a test servlet. ");
  • Create a JSP inside the project
    • file name: index.jsp
    • add the following text inside the <body> tag
This is the Smoke Test.
  • Ensure the project builds and is targeted to the server correctly

Create an EAR 5 project

  • Target it at the installed Java EE server
  • Select the Web 2.5 project as J2EE module (third page)

Create an EJB 3.0 project

  • Target it at the installed Java EE server
  • Choose "Add project to an EAR" and choose the previously created EAR 5 project

Verify Project Explorer content

Verify the Web project

  • verify there is no node for the deployment descriptor
  • verify there is a web.xml file under the WEB-INF folder
  • verify that the servlet and its mapping are described in the web.xml

Verify the EJB project

  • verify there is no node for the deployment descriptor
  • verify there is no ejb-jar.xml file under the META-INF directory

Verify the EAR project

  • verify there is no node for the deployment descriptor
  • verify there is no application.xml file under the META-INF directory
  • verify that the Web and EJB modules are listed and checked in the J2EE Module Dependencies property page

Export the projects

Export the Web project

  • verify that the deployment descriptor XML, Servlet classes, JSP files and libraries are included in the WAR

Export the EJB project

  • verify that all of the classes are included in the EJB JAR
  • verify there is no deployment descriptor XML

Export the EAR project

  • verify that the WARs and EJB JARs of the referenced J2EE modules are included
  • verify there is no deployment descriptor XML

Deploy and Run the application

  • Run the test servlet
    • Right click on the servlet class and choose Run As -> Run on Server
    • Select the targeted Java EE server
    • The internal browser should request the test servlet and show the result page
  • Run the index.jsp
    • Right click on the index.jsp and choose Run As -> Run on Server
    • Select the targeted Java EE server
    • The internal browser should request the index.jsp and show the result page

See also

Click here to view smoke test scenarios for WTP 1.5.
Click here to view smoke test scenarios for WTP 2.0.
Click here to view smoke test scenarios for WTP 3.0.
Click here to view WTP smoke test results.
Back to Web Tools Wiki Home

Copyright © Eclipse Foundation, Inc. All Rights Reserved.