Does Creator WAR work with Weblogic 7.x

Question

Hi,
When I try to deploy Creator generated WAR on WebLogic 7.x, I get the following error:
<Feb 21, 2005 4:50:25 PM CST> <Error> <HTTP> <101216> <Servlet: "Faces Servlet"
failed to preload on startup in webapp: "webapp1"
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
Has anybody been able to successfully deploy on Weblogic 7.x and if so what the steps needed to do that, other than simply dropping the WAR file, into the appropriate directory.
Thanks!
Haroon

Answer 1

Hi Haroon,
We have a tutorial we've been working on in this area - here's some of the notes we've got so far - hope it will help!
best,
v
========================================
Configuring the Classpath SettingsCopy the following JAR files from your Java Studio Creator installation directory into a directory of your choosing.
Creator_install_dir/modules/autoload/ext/jstl.jar
Creator_install_dir/modules/autoload/ext/standard.jar
Edit your startWebLogic.cmd (or .sh) file and add the following line. For a default installation of version 8.1 on Microsoft Windows XP, the command file to start the server is at BEA-home\user_projects\domains\creator\startWebLogic.cmd
set CLASSPATH=your_dir\jstl.jar;your_dir\standard.jar;%CLASSPATH%
Restart the application server.
Creating and Configuring a JDBC Data SourceIn the right pane of the console home page, click Service Configurations > JDBC > Data Sources.
Clcik the Configure a New JDBC Sata Source. The JDBC Data Source assistant opens in the right pane.
Enter the following information: Name--Enter a name for this JDBC data source. This name is used in the configuration (weblogic.xml) file. JNDI Name--ENter the JNDI path to where this JDBC data source sill be bound. Click Continue to associate the JDBC data source with a connection pool. Click Configure a new JDBC Connection Pool.
Enter the following Database Type--select the DBMS of the database that you want to connect to.
Database Driver--select the JBDC driver you want to use to connect the database.
Click Continue.
On the Define Connection Properties page provide the information requested. The required attributes vary by the DBMS and JDBC driver you selected in the previous step. Consult your driver's documentation for the correct values. For the Sun Java System JDBC drivers, the classname is com.sun.sql.datasource.DriverAdapter.
Click Continue.
In Test Database Connection, verify the connection properties and then click Test Driver Configuration.
If the text is successful, the Create and Deploy page is displayed. If the test is unsuccessful, check the values on the page, correct any errors, then text the connection again.
In Create and Dploy, select the servers and cluster on which you want to deploy the connection pool. Click Create and Deploy to complete this process.
Exporting the WAR FileYou must create a web application archive (WAR) file for the application that you developed in the Java Studio Creator IDE. The WAR file will contain the complete web application in compressed form..
Open your project in the IDE.
In the Project Navigator, right-click the project name and choose Export WAR file.
In the Export WAR dialog box, choose the J2EE 1.4 specification.
Enter the location to which to export the WAR file and click OK.
Adding weblogic.xml to the WAR
Just like WEB-INF/sun-web.xml, you need a WEB-INF/weblogic.xml file. Create this file and add it to your WAR.
In a command-line window, change to the directory where you saved the WAR file.
Create a subdirectory named WEB-INF.
Change to the WEB-INF directory and create a file called weblogic-web.xml with contents similar to the code shown in the following sample. For the <res-ref-name> and <jndi-name> tags specify the value you entered in the JNDI Name field when you created the JDBC resource.
Code Sample 1: weblogic.xml Code
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC '-//BEA Systems, Inc.//DTD Web Application 7.0//EN'
'http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd'>
<weblogic-web-app>
<resource-description>
<res-ref-name>jdbc/Travel</res-ref-name>
<jndi-name>jdbc/Travel</jndi-name>
</resource-description>
</weblogic-web-app>
Return to the directory that contains the WAR file and update it to include the weblogic.xml file.
jar uf your_app.war WEB-INF/weblogic-web.xml
For more information, visit the BEA website weblogic.xml Deployment Descriptor Elements.
Starting the WebLogic Application Server and Builder ToolStart the WebLogic application server if it is not already running.
Open the WebLogic Builder application and connect it to your WebLogic server.
The right box on the status line should say Connected. If it does not, choose Tools > Connect to Server and fill in the dialog box.
The JavaServer Pages (JSP pages) 1.2 specifications require that JSP containers process tag library descriptor (TLD) files that are embedded in a JAR file.
Adding a Listener to the WebLogic Deployment DescriptorThe JavaServer Pages (JSP pages) 1.2 specifications require that JSP containers process tag library descriptor (TLD) files that are embedded in a JAR file. The IDE relies on this feature to initialize the JSF runtime environment when the application is first loaded. A ServletContextListener is declared inside a tag library descriptor in jsf-impl.jar. WebLogic servers do not implement this feature, so the listener must be explicitly included in the WebLogic deployment descriptor.
Copy the WAR file to another location. Otherwise, the changes you make in this section will be removed when the project is rebuilt or cleaned.
Using the WebLogic Builder, choose File > Open in the Builder main menu. Navigate to the directory you selected in the previous step and select MessagesEx.war.
Click the Listener node in the right-hand tree pane.
Click the Add button.
In the dialog box that appears, enter com.sun.faces.config.ConfigureListener to the listener class text box and click OK. The listener class should now appear in the right pane.
Save the WAR file by choosing File > Save.
The Messages pane (shown in the preceding figure) diaplays Created weblogic.xml. Each application server can define its own XML configuration file(s). One of the primary uses for this file is to connect container-specific resources to a contained application. The WebLogic Builder generates this file automatically. Directly deploying an application created with the Java Studio Creator IDE into a WebLogic server will fail because this file is not generated by the IDE.
Deploying the Application to the WebLogic Server You can now deploy the modified WAR file to the WebLogic server.
In the WebLogic Builder, choose Tools > Deploy Module.
Click the Deploy Module button.
The dialog box closes. The message Module MessagesEx.war descriptors successfully loaded appears in the Builder Messages pane. The application has been deployed to your WebLogic server.
Test your application by opening a web browser and entering the URL http://hostname:7001/MessagesEx, where hostname is the name of your WebLogic server.
The Messages tutorial web page should appear. You can enter sample values into it as described in the Using Message Components tutorial.