From user-return-8731-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org Fri Jan 04 21:25:05 2008 Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 85617 invoked from network); 4 Jan 2008 21:25:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jan 2008 21:25:05 -0000 Received: (qmail 57462 invoked by uid 500); 4 Jan 2008 21:24:52 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 57434 invoked by uid 500); 4 Jan 2008 21:24:52 -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 57423 invoked by uid 99); 4 Jan 2008 21:24:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 13:24:52 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jgawor@gmail.com designates 209.85.146.182 as permitted sender) Received: from [209.85.146.182] (HELO wa-out-1112.google.com) (209.85.146.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jan 2008 21:24:29 +0000 Received: by wa-out-1112.google.com with SMTP id j4so14703046wah.1 for ; Fri, 04 Jan 2008 13:24:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=hKYmhViRMgVCKRF7/RA1zMynvDNGweXidQWJILjI8Q8=; b=XMC7+fk3zVdTy25tPUg8eZMkLgqfdXS6QA5mCLl66Taky0G+FmzNjKpLu0HwhzuxwbkBDi5Zai+lcmQaoEL5pM4wKwk7upFF7F0Ffa9GGZFgmP7ZUXU9WeDkH6cODc9yPtS2d/D9cE8ZRSK599vuBYIU8lA77PxRRQXn8a6a2rg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pn9VKojEMqPDmeLLqs7POU4mnePXKBGVPsNerB8itzPGfDz4sU6OX0/kJCv7Tj1Og9MlfZfl/5c32Vx+PURXiV4Jfr7BPzsqZb+A1Btcbkue36QZYaeu6fz9k0fALVOUm4JNeYBWEJwNjxrIrpAMReoSXj79x7VqkIA+BVKiuYU= Received: by 10.114.174.2 with SMTP id w2mr17940666wae.17.1199481874476; Fri, 04 Jan 2008 13:24:34 -0800 (PST) Received: by 10.114.150.10 with HTTP; Fri, 4 Jan 2008 13:24:34 -0800 (PST) Message-ID: <5eb405c70801041324j6c96fab2oc6df443f478a2811@mail.gmail.com> Date: Fri, 4 Jan 2008 16:24:34 -0500 From: "Jarek Gawor" To: user@geronimo.apache.org Subject: Re: JAX-WS 2.0 Service packaged as an EAR In-Reply-To: <878bf2af0801041309t3ef8dba5pc2ed633df17243f0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <878bf2af0801041309t3ef8dba5pc2ed633df17243f0@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Look for "Configuring EJB JAX-WS Web Service: " log message in the var/log/geronimo.log file. That log message will also contain the uri address at which the service is published at. The rules for default uri addresses are different for ejb or servlet -based web services. Jarek On Jan 4, 2008 4:09 PM, Sam Merrell wrote: > I've gotten my JAX-WS 2.0 EJB3-based web service working when its deployed > as a WAR, but I am not sure how to access the web service when its packaged > as an EAR. When I deploy as a war, I can get the WSDL back from > http://localhost:8080/EJBService/EJBHelloService?wsdl but I can't get to it > like that when I deploy as an EAR. > > The EAR is packaged like this: > > EJBService.ear > ------META-INF > -----Application.xml > ------EJBService.jar > > Here is my Application.xml > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee > http://java.sun.com/xml/ns/javaee/application_5.xsd"> > > EJB3 Based JAX-WS 2.0 Web Service > EJB3 Based JAX-WS 2.0 Web Service > > EJBService.jar > > > > I've also tried to deploy the EAR without an application.xml since Java EE 5 > allows an EAR to be deployed without it, but I had no luck with that either. > Any suggestions? > > -- > Sam Merrell