Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57186CC7A for ; Tue, 14 Aug 2012 01:32:26 +0000 (UTC) Received: (qmail 20712 invoked by uid 500); 14 Aug 2012 01:32:26 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 20622 invoked by uid 500); 14 Aug 2012 01:32:26 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 20614 invoked by uid 99); 14 Aug 2012 01:32:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 01:32:25 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xhhsld@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-wi0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 01:32:21 +0000 Received: by wicr5 with SMTP id r5so2466482wic.13 for ; Mon, 13 Aug 2012 18:32:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PrzehmS83JCULPmoeFnx8zGnvUgpHGjH5OL8cXSqlO4=; b=LJd8hqUsO0qL9s4vcsxRPJCsvua8oamh9FKc49cE7inqVHlST6KqgZnAgUAh9tZqXa 5+5y2DMfQzLWmhnIdJm8c1CRDgPrqrqu5YlI52ShwlFqzb3r0O4w7ONORlk3h+5f+lOb qY3Xb6l4jr2YWmD1M6FuIL1lc49W9AZvlJzzFPU3FH/ryZh15rniWE/+LqBD0CYF8bq/ MptCCdJf2LUNQ2Q6TO6zlp+Ugu5Tn0+fUbyc3FQsBdzWXQkMWHSm5n/9bsotclMW41Qf QelkoRhiwrgoe4v7dIZCC+bhrp906Jp0NO+lEW26O3W15nA+B9iPLPeqhvb2pwk+SSBx TgUQ== MIME-Version: 1.0 Received: by 10.216.29.17 with SMTP id h17mr5285931wea.221.1344907919963; Mon, 13 Aug 2012 18:31:59 -0700 (PDT) Received: by 10.227.151.131 with HTTP; Mon, 13 Aug 2012 18:31:59 -0700 (PDT) In-Reply-To: <1344865618498-3985595.post@n3.nabble.com> References: <1344865618498-3985595.post@n3.nabble.com> Date: Tue, 14 Aug 2012 09:31:59 +0800 Message-ID: Subject: Re: Use other port for webservices on same wasce instance From: Ivan To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=0016e6dbe2a0d337ab04c72fc606 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dbe2a0d337ab04c72fc606 Content-Type: text/plain; charset=ISO-8859-1 Guess that the web service things are included in the web application, do you mean that, you would like to use one port 8180 to serve web service requests, and port 8080 to serve other parts of the web application ? 2012/8/13 soegaard > Hello, > > Can anyone help with this issue. > > Using another port for some new webservices - still on localhost. We have a > website running on 8080 and we want to use another port for webservices > (8180). > > Please help. > > There are examples of this in some wasce documentation, but it is not > correct. I have found several places where people has complained about the > same issue and not finding a solution, because what the doc example is > incorrect. > > It is possible to create a new connector in WASCE - either using the > geronimo-web.xml or via the admin console. I have done it via > geronimo-web.xml where I also create the new web-container, engine and host > as the doc example indicates. > > It deploys and in the admin cosnole I can see there has been created a new > connector, but I cannot reach the new port (8180) > > > > > > -- > View this message in context: > http://apache-geronimo.328035.n3.nabble.com/Use-other-port-for-webservices-on-same-wasce-instance-tp3985595.html > Sent from the Development mailing list archive at Nabble.com. > -- Ivan --0016e6dbe2a0d337ab04c72fc606 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Guess that the web service things are included in the web application, do y= ou mean that, you would like to use one port 8180 to serve web service requ= ests, and port 8080 to serve other parts of the web application ?

2012/8/13 soegaard <Bjarne.Soeegaard@= stab.rm.dk>
Hello,

Can anyone help with this issue.

Using another port for some new webservices - still on localhost. We have a=
website running on 8080 and we want to use another port for webservices
(8180).

Please help.

There are examples of this in some wasce documentation, but it is not
correct. I have found several places where people has complained about the<= br> same issue and not finding a solution, because what the doc example is
incorrect.

It is possible to create a new connector in WASCE - either using the
geronimo-web.xml or via the admin console. I have done it via
geronimo-web.xml where I also create the new web-container, engine and host=
as the doc example indicates.

It deploys and in the admin cosnole I can see there has been created a new<= br> connector, but I cannot reach the new port (8180)





--
View this message in context: http://apache-geronimo.328035.n3.nabble.com/Use-othe= r-port-for-webservices-on-same-wasce-instance-tp3985595.html
Sent from the Development mailing list archive at Nabble.com.



--
Ivan
--0016e6dbe2a0d337ab04c72fc606--