| Problem deploying .war file for tomcat [message #98962] |
Sat, 19 July 2008 04:27  |
Eclipse User |
|
|
|
Originally posted by: daniel.xxx.de
Hi,
I have a problem creating the .war file for the tomcat server, although I
followed the instructions from the online tutorial. (Thanks Elias!)
First, I realized that the content of my build directory is different than
in the tutorial. (also, my PDE Export seems to run much shorter as in the
tutorial) The eclipse directory contains only a configuration directory
and a launch.ini-file. The features and plugin directories are missing.
When I run the application on the tomcat server I get the following error
message:
javax.servlet.ServletException: Servlet.init() for servlet
equinoxbridgeservlet threw exception
...
root cause
java.lang.RuntimeException: Could not find framework
...
Does anybody know what went wrong? When I start the application in eclipse
it runs fine.
Thanks in advance for your help,
Regards,
Daniel
|
|
|
|
|
|
|
|
| Re: Problem deploying .war file for tomcat [message #100289 is a reply to message #99142] |
Mon, 28 July 2008 04:27  |
| Eclipse User |
|
|
|
Originally posted by: daniel.xxx.de
Hi Elias,
first of all: I followed the recommendation from Philipp to upgrade to
Eclipse 3.4. I think, I am getting closer, ;-). The pde export did run
much longer and I have all the necessary directories.
But when I deploy it to Tomcat it still doesn't work. Now the output is:
HTTP Status 404 - BridgeServlet: /ats/rap
------------------------------------------------------------ --------------------
type Status report
message BridgeServlet: /ats/rap
description The requested resource (BridgeServlet: /ats/rap) is not
available.
I know that error message was described in the newsgroup earlier, but I
couldn't find anything that would help me.
I will also post the webappBuilder:
<?xml version="1.0"?>
<project name="project" default="default">
<description>
Example of a webapplication build script for RAP applications that use
the equinox servlet bridge to run in a servlet container.
</description>
<!-- =================================
target: init
================================= -->
<target name="init">
<property name="proj.dir" value="${basedir}/.." />
<!--
This script assumes that the servlet bridge project is available
in the current workspace. Note: The location is hardcoded and must
be
adjusted to your needs.
-->
<property name="servletbridge.dir"
value="C:/Dokumente und Einstellungen/Daniel
Popp/workspace/org.eclipse.equinox.servletbridge" />
<!--
On windows be cautious about long file names for ${build.dir}
These long path problems were resolved in JRE 1.5.0_08
-->
<property name="build.dir" value="${proj.dir}/build" />
<property name="templates.dir" value="${proj.dir}/templates" />
<property name="webapp.name" value="demo" />
<property name="features" value="com.ats.ui.demo.feature" />
<!--
If you are using this script in a head-less build define the following
properties:
"ignore.pdeExportFeatures" (available only in the IDE - do the feature
export with PDE Build)
"ignore.servletbridge.jar" (if you're compiling or extracting the jar
yourself)
-->
</target>
<!-- =================================
target: prepare
================================= -->
<target name="prepare" depends="init">
<delete dir="${build.dir}/${webapp.name}" />
<mkdir dir="${build.dir}/${webapp.name}/WEB-INF/lib" />
</target>
<!-- =================================
target: default
================================= -->
<target name="default"
depends="copyResources, servletbridge.jar, pdeExportFeatures" />
<!-- =================================
target: copyResources
================================= -->
<target name="copyResources" depends="prepare">
<copy todir="${build.dir}/${webapp.name}">
<fileset dir="${templates.dir}" />
</copy>
</target>
<!-- =================================
target: servletbridge.jar
================================= -->
<target name="servletbridge.jar"
depends="prepare"
unless="ignore.servletbridge.jar">
<antcall target="jar-servletbridge.jar" />
<antcall target="copy-servletbridge.jar" />
</target>
<!-- =================================
target: copy-servletbridge.jar
================================= -->
<target name="copy-servletbridge.jar" if="servletbridge.jar-present">
<copy todir="${build.dir}/${webapp.name}/WEB-INF/lib">
<fileset file="${servletbridge.dir}/servletbridge.jar" />
</copy>
</target>
<!-- =================================
target: jar-servletbridge.jar
================================= -->
<target name="jar-servletbridge.jar" unless="servletbridge.jar-present">
<jar
destfile="${build.dir}/${webapp.name}/WEB-INF/lib/servletbridge.jar ">
<fileset dir="${servletbridge.dir}/bin">
<include name="**/*.class" />
</fileset>
</jar>
</target>
<!-- =================================
target: pdeExportFeatures
================================= -->
<target name="pdeExportFeatures"
depends="prepare"
unless="ignore.pdeExportFeatures">
<!--
Features get built asynchronously but this approach is sometimes
convenient.
So that the pde.exportFeatures task is available in the IDE select
"Run in the same JRE as the workspace" from the JRE tab from "Run Ant.."
-->
<pde.exportFeatures features="${features}"
destination="${build.dir}/${webapp.name}/WEB-INF/eclipse"
exportType="directory"
useJARFormat="false"
exportSource="false" />
</target>
</project>
Hope, this helps and doesn't make my post too ugly, ;-).
Also: I don't have the console of tomcat.
Any help is appreciated, thanks in advance!!
Regards,
Daniel
|
|
|
| Re: Problem deploying .war file for tomcat [message #100531 is a reply to message #100289] |
Tue, 29 July 2008 04:38 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
did you check the equinox log files for additional stacktraces? If your
equinox instance started properly the log file should be located under
<path to tomcat
installation>\work\Catalina\localhost\<your-app-name>\eclipse\workspace\
..metadata
otherwise there may be a log file in
<path to tomcat
installation>\work\Catalina\localhost\<your-app-name>\eclipse\configurat
ion
If you want to show the console for debugging reasons reactivate the
commandline init-parameter that is commented out in the default web.xml.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Daniel Popp [mailto:daniel@xxx.de]
Bereitgestellt: Montag, 28. Juli 2008 10:27
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problem deploying .war file for tomcat
Betreff: Re: Problem deploying .war file for tomcat
Hi Elias,
first of all: I followed the recommendation from Philipp to upgrade to
Eclipse 3.4. I think, I am getting closer, ;-). The pde export did run
much longer and I have all the necessary directories.
But when I deploy it to Tomcat it still doesn't work. Now the output is:
HTTP Status 404 - BridgeServlet: /ats/rap
------------------------------------------------------------ ------------
--------
type Status report
message BridgeServlet: /ats/rap
description The requested resource (BridgeServlet: /ats/rap) is not
available.
I know that error message was described in the newsgroup earlier, but I
couldn't find anything that would help me.
I will also post the webappBuilder:
<?xml version="1.0"?>
<project name="project" default="default">
<description>
Example of a webapplication build script for RAP applications that
use
the equinox servlet bridge to run in a servlet container.
</description>
<!-- =================================
target: init
================================= -->
<target name="init">
<property name="proj.dir" value="${basedir}/.." />
<!--
This script assumes that the servlet bridge project is available
in the current workspace. Note: The location is hardcoded and
must
be
adjusted to your needs.
-->
<property name="servletbridge.dir"
value="C:/Dokumente und Einstellungen/Daniel
Popp/workspace/org.eclipse.equinox.servletbridge" />
<!--
On windows be cautious about long file names for
${build.dir}
These long path problems were resolved in JRE 1.5.0_08
-->
<property name="build.dir" value="${proj.dir}/build" />
<property name="templates.dir" value="${proj.dir}/templates" />
<property name="webapp.name" value="demo" />
<property name="features" value="com.ats.ui.demo.feature" />
<!--
If you are using this script in a head-less build define
the following
properties:
"ignore.pdeExportFeatures" (available only in the IDE -
do the feature
export with PDE Build)
"ignore.servletbridge.jar" (if you're compiling or
extracting the jar
yourself)
-->
</target>
<!-- =================================
target: prepare
================================= -->
<target name="prepare" depends="init">
<delete dir="${build.dir}/${webapp.name}" />
<mkdir dir="${build.dir}/${webapp.name}/WEB-INF/lib" />
</target>
<!-- =================================
target: default
================================= -->
<target name="default"
depends="copyResources, servletbridge.jar, pdeExportFeatures"
/>
<!-- =================================
target: copyResources
================================= -->
<target name="copyResources" depends="prepare">
<copy todir="${build.dir}/${webapp.name}">
<fileset dir="${templates.dir}" />
</copy>
</target>
<!-- =================================
target: servletbridge.jar
================================= -->
<target name="servletbridge.jar"
depends="prepare"
unless="ignore.servletbridge.jar">
<antcall target="jar-servletbridge.jar" />
<antcall target="copy-servletbridge.jar" />
</target>
<!-- =================================
target: copy-servletbridge.jar
================================= -->
<target name="copy-servletbridge.jar" if="servletbridge.jar-present">
<copy todir="${build.dir}/${webapp.name}/WEB-INF/lib">
<fileset file="${servletbridge.dir}/servletbridge.jar" />
</copy>
</target>
<!-- =================================
target: jar-servletbridge.jar
================================= -->
<target name="jar-servletbridge.jar"
unless="servletbridge.jar-present">
<jar
destfile="${build.dir}/${webapp.name}/WEB-INF/lib/servletbridge.jar ">
<fileset dir="${servletbridge.dir}/bin">
<include name="**/*.class" />
</fileset>
</jar>
</target>
<!-- =================================
target: pdeExportFeatures
================================= -->
<target name="pdeExportFeatures"
depends="prepare"
unless="ignore.pdeExportFeatures">
<!--
Features get built asynchronously but this approach is
sometimes
convenient.
So that the pde.exportFeatures task is available in the
IDE select
"Run in the same JRE as the workspace" from the JRE tab
from "Run Ant.."
-->
<pde.exportFeatures features="${features}"
destination="${build.dir}/${webapp.name}/WEB-INF/eclipse"
exportType="directory"
useJARFormat="false"
exportSource="false" />
</target>
</project>
Hope, this helps and doesn't make my post too ugly, ;-).
Also: I don't have the console of tomcat.
Any help is appreciated, thanks in advance!!
Regards,
Daniel
|
|
|
|
| Re: Problem deploying .war file for tomcat [message #100810 is a reply to message #100799] |
Tue, 29 July 2008 11:32 |
| Eclipse User |
|
|
|
Originally posted by: fappel.innoopract.com
Hi,
I don't know about your installation environment. What you can do is to
add a port number after the -console parameter (I think the syntax is
-console: 1234). Doing so it's possible to have an remote access to the
console via telnet...
Common problems with missing entry-point are, that the plugin.xml of
your bundle wasn't added to the build.properties file or the java
version with which you build your bundle is newer than that of the
runtime.
Ciao
Frank
-----Ursprüngliche Nachricht-----
Von: Daniel Popp [mailto:daniel@xxx.de]
Bereitgestellt: Dienstag, 29. Juli 2008 17:13
Bereitgestellt in: eclipse.technology.rap
Unterhaltung: Problem deploying .war file for tomcat
Betreff: Re: Problem deploying .war file for tomcat
Hi Frank,
thanks for your quick reply. I tried to get the same error message and
looked up the detailed error file. I found something about: could not
find
org.eclipse.update.configurator@start...
So I included the plugin into my project and get now a different error
message:
java.lang.IllegalArgumentException: An entry point named 'default' does
not exist.
org.eclipse.rwt.internal.lifecycle.EntryPointManager.createU I(EntryPoint
Manager.java:77)
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWT LifeCycle.ja
va:230)
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(R
WTLifeCycle.java:116)
java.lang.Thread.run(Unknown Source)
In eclipse the application works fine.
About the console: You were right, the console command is commented out.
Even when I correct this, I still don't have access to the console.
Thanks in advance,
Daniel
|
|
|
Powered by
FUDForum. Page generated in 0.04482 seconds
Home