WebLogic Workshop Projects

All WebLogic Workshop web services are developed and run within a project. A project provides the directory structure in which web service files, including supporting files, reside.

# Contents of a Project

A project may contain multiple web services. The web services in the project may be organized in several hierarchical directories (folders).

There are four types of files you typically work with. Select the links below to learn more about the various file types:

- JWS Files: Java Web Services: Java Web Service files that contain the source code to a web service.

- CTRL Files: Control files that contain interfaces to WebLogic Workshop controls, including controls that represent other web services, databases and other resources.

- WSDL Files: Web Service Descriptions: Web Service Description Language files that contain XML descriptions of your web service or of other services your web services use.

- XMLMAP Files: XML map files that contain maps that may be shared by more than one method and/or web service.

- JSX files: ECMAScript (also known as JavaScript) files that use the ECMAScript XML extensions defined by WebLogic Workshop to perform mapping between XML and Java. JSX files are referred to by XML maps in JWS files. See Handling XML with ECMAScript Extensions.

- JAVA files: You may include additional JAVA files in your project, and web services may access classes defined in JAVA files.

Note: Files in the project may be served in source form by WebLogic Server. To avoid exposing your JAVA source files to clients, place them a subdirectory of your project's WEB-INF directory (but not in the classes or lib subdirectories).

In addition to the files you use to implement web service code, projects also contain files and directories that are required by WebLogic Server to support your web services. These directories will be most useful to advanced users.

You may notice the following project directory in a directory:

- WEB-INF: This directory contains supporting code for your web services. This supporting code may include Java classes that you have added so that you may use them from your code. Code that is automatically generated by WebLogic Workshop to implement your web services is also placed here. You may add class files to the classes folder or jar files to the lib folder, but you should not modify the other contents of this directory.

If you already have some experience using WebLogic Server, you may recognize that a WebLogic Workshop project is very similar to a WebLogic Server Web Application (webapp).

# Location of WebLogic Workshop Projects

A WebLogic Workshop project must be a valid WebLogic Server webapp, which must in turn reside in a WebLogic Server domain. The default location for WebLogic Workshop projects is <install>/weblogic700/samples/workshop/applications.

Note: <install> refers to your WebLogic Server installation directory. If you accepted the defaults during installation, the value of <install> is:

- c:\bea on systems running Microsoft Windows

- /home/<user>/bea on systems running Linux

- $HOME/bea on systems running Solaris

WebLogic Workshop is installed with two projects: 'samples' and 'DefaultWebApp'.

# The 'samples' Project

WebLogic Workshop is installed with a project named 'samples'. The samples project contains many example web services that demonstrate specific features or capabilities of WebLogic Workshop web services.

You may create additional web services in the samples project. When you begin to develop web services that you intend to deploy and publish, create one or more new projects to hold the new services.

For descriptions of the web services in the samples project, see Samples.

# Project Name

Web services are accessed via URLs. For example, the Hello World sample web service, which is located in the samples project is accessed by the following URL:

http://localhost:7001/samples/HelloWorld.jws

Notice that the project name is part of the URL for the web service. This is true for all WebLogic Workshop web services. Since you will be publishing your web services by publishing their URLs, you should choose project names that will make sense in the resulting URLs.

Note: In the example URL above, localhost would be replaced by an actual hostname or IP address in the CTRL or WSDL files used to publish the web service's location to others.

# Browsing a WebLogic Workshop Project

WebLogic Workshop provides a facility for browsing WebLogic Workshop projects. To access this facility, browse to the URL of any WebLogic Workshop project with /jwsdir appended to the URL. For example:

http://localhost:7001/samples/jwsdir

The directory shows only JWS files by default. Select Show all files to see other file types and subdirectories.

In addition to allowing a user to explore the structure of a project and access web service Test View pages, this view also displays the "Clean All" button. This button may be used to clear the state of web services deployed in WebLogic Server. This can be useful when errors in a web service under development lead to erroneous server behavior.

Related Topics

Web Service Development Cycle