Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 82039 invoked from network); 16 May 2007 18:09:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 May 2007 18:09:43 -0000 Received: (qmail 35371 invoked by uid 500); 16 May 2007 18:09:44 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 35293 invoked by uid 500); 16 May 2007 18:09:43 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 35264 invoked by uid 99); 16 May 2007 18:09:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 11:09:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of dlochart@capecomputing.com designates 67.94.168.2 as permitted sender) Received: from [67.94.168.2] (HELO dogfood.dsystems.net) (67.94.168.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2007 11:09:36 -0700 Received: from dogfood2.dsystems.net ([10.3.120.17]) by dogfood.dsystems.net (Post.Office MTA v3.5.2 release 221 ID# 0-71134U1000L100S0V35) with ESMTP id net for ; Wed, 16 May 2007 14:09:15 -0400 Received: from [10.3.120.106] ([67.94.168.60]) by dogfood2.dsystems.net (Post.Office MTA v3.5.2 release 221 ID# 0-71134U1000L100S0V35) with ESMTP id net for ; Wed, 16 May 2007 14:23:05 -0400 Message-ID: <464B48CA.9000403@capecomputing.com> Date: Wed, 16 May 2007 14:09:14 -0400 From: Doug Lochart Reply-To: dlochart@capecomputing.com MIME-Version: 1.0 To: user@geronimo.apache.org Subject: Web Application Migration to Geronimo Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Actually it is to the WebSphere Application Server Community Edition which runs Geronimo pre-wired with Tomcat. I have a web application deployed as an EAR (Stateless Session EJB (in ejb_jar) , Servlet(in .WAR) ) that combined is a WebService. I did not write the Application and I am real new to Web Services. My task is to deploy this web application to WAS CE (Geronimo). I tried simply deploying it as is but of course it failed giving me an error like this: Error: Unable to distribute FrancePolicyServer.ear: Unable to resolve reference "WebServiceContainer" in gbean default/Application_ID/1179336634177/car?EJBModule=FrancePolicyServer_EJB.jar,J2EEApplication=default/Application_ID/1179336634177/car,StatelessSessionBean=FrancePolicyServer,j2eeType=WSLink,name=FrancePolicyServer to a gbean matching the pattern [?name=TomcatWebContainer#] First of all any idea what this error means? I am sure it is a need for a plan but I would like to understand what is happening. I have read through several developerworks articles and numerous examples on geronimo (looks like a kick a$$ product by the way, I like the IoC design) and from what I gather I need to provide 1 or more extra deployment descriptors/deployment plans specific for geronimo. I was hoping for a good example of these plans so that I could hack it up and do some trial and error to learn but I still feel I lack the knowledge to even start down the right path. I don't know which ones I need and how to construct them. So what I am asking is based on my application I described what types of geronimo specific xml files do I need? According to the docs it looks like I need a geronimo-application.xml as a deployment plan but I did not see a good example of that and I was left feeling that I am missing something for the Web Service. In the META-INF directory of the ejb-jar file I see my webservices.xml and a mapping.xml and also 2 ibm (was 6.0) specific binding files ibm-webservices-ext.xmi and ibm-webservices-bnd.xmi which I have no clue how they come into play. I do know that the Servlet is merely a pass through to the Session Bean. thanks Doug