Technical data

14 BEA WebLogic Integration Release Notes

Design-Time Web Application JSP Delivery Change

The following information will be added to “Migrating Adapters to WebLogic

Integration 2.1” in Developing Adapters in a future release.

As of WebLogic Integration 2.1 Service Pack 1, sample adapters (eMail, DBMS, and

sample) no longer distribute the JSP pages in a Web application archive (WAR).

Rather, the JSP pages are precompiled into Java Servlet classes. This approach

eliminates the need to precompile JSP pages when WebLogic Server starts. The Java

Servlet classes are delivered in the

WEB-INF\classes\jsp_servlet directory in a

WAR file. Since the JSP pages are not bundled into the WAR file, the adapter

developer needs to establish the mapping between a URL pattern and a specific Java

Servlet class in the Web application descriptor

WEB-INF/web.xml.

For each JSP page for your adapter, provide a Servlet declaration. For example,

<servlet-name>confconn</servlet-name>

<servlet-class>jsp_servlet.__confconn</servlet-class>

</servlet>

This declares a Servlet named confconn and associates it with a Java Servlet class

jsp_servlet.__confconn. The Web application container looks for this class in the

WEB-INF/classes directory in the WAR file. After declaring all Servlet classes,

associate each Servlet with a URL pattern via a

servlet-mapping.

<servlet-mapping>

<servlet-name>confconn</servlet-name>

<url-pattern>confconn.jsp</url-pattern>

</servlet-mapping>

This servlet-mapping associates all HTTP requests for confconn.jsp to the

confconn Servlet in your Web application. The adapter developer must have a

servlet-mapping for all Servlets in the Web application. See the sample adapter’s

web.xml file for an example of all Servlet declarations and mappings needed for an

adapter.

Sample Email Adapter Deprecated

The sample Email adapter is deprecated in this release of WebLogic Integration. The

Email adapter will be removed from the product in a future release.