geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1621) [Daytrader] TradeWSAction class is not a Servlet
Date Wed, 15 Feb 2006 10:09:11 GMT
    [ ] 

Vincent Massol commented on GERONIMO-1621:

Matt, you can close this issue with "won't fix", thanks. I got the answer from the Jetty team
(Jan Bartel). Here it is for the record:

Jetty concentrates on the servlet spec, which doesn't provide for POJOs declared as <servlet>
in the web.xml.  However, when Jetty is deployed in Geronimo, Geronimo provides the webservices
integration that lets (eg) the daytrader app be deployed into Jetty. 

JBoss has done a similar integration for Tomcat and we plan to do it too as part of the jetty-jboss.sar
that we provide for people who want to run JBoss with Jetty.

With Jetty6 we also plan to make it an optional feature, using maybe XFire. It's on the todo
list for Jetty5.x:

and now your email has prompted me to put it in the jetty6 JIRA too:

> [Daytrader] TradeWSAction class is not a Servlet
> ------------------------------------------------
>          Key: GERONIMO-1621
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: sample apps
>     Versions: 1.0
>     Reporter: Vincent Massol

> When trying to deploy the web/ module to Jetty I'm getting the following error:
> Servlet class org.apache.geronimo.samples.daytrader.TradeWSAction is not a javax.servlet.Servlet
> Indeed, looking at the class reveals that it's not a Servlet and thus
it shouldn't be declared as a Servlet in web.xml:
>       <servlet id="Servlet_30">
>          <display-name>org_apache_geronimo_samples_daytrader_TradeWSAction</display-name>
>          <servlet-name>org_apache_geronimo_samples_daytrader_TradeWSAction</servlet-name>
>          <servlet-class>org.apache.geronimo.samples.daytrader.TradeWSAction</servlet-class>
>       </servlet>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message