Return-Path: 
 <user-return-1352-apmail-karaf-user-archive=karaf.apache.org@karaf.apache.org>
X-Original-To: apmail-karaf-user-archive@minotaur.apache.org
Delivered-To: apmail-karaf-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C94D46E84
	for <apmail-karaf-user-archive@minotaur.apache.org>;
 Fri, 29 Jul 2011 21:16:49 +0000 (UTC)
Received: (qmail 67365 invoked by uid 500); 29 Jul 2011 21:16:49 -0000
Delivered-To: apmail-karaf-user-archive@karaf.apache.org
Received: (qmail 67228 invoked by uid 500); 29 Jul 2011 21:16:48 -0000
Mailing-List: contact user-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@karaf.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@karaf.apache.org>
List-Post: <mailto:user@karaf.apache.org>
List-Id: <user.karaf.apache.org>
Reply-To: user@karaf.apache.org
Delivered-To: mailing list user@karaf.apache.org
Received: (qmail 67220 invoked by uid 99); 29 Jul 2011 21:16:48 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2011 21:16:48 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [217.70.183.195] (HELO relay3-d.mail.gandi.net)
 (217.70.183.195)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2011 21:16:41 +0000
X-Originating-IP: 217.70.178.137
Received: from mfilter8-d.gandi.net (mfilter8-d.gandi.net [217.70.178.137])
	by relay3-d.mail.gandi.net (Postfix) with ESMTP id A97E4A807C
	for <user@karaf.apache.org>; Fri, 29 Jul 2011 23:16:20 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter8-d.gandi.net
Received: from relay3-d.mail.gandi.net ([217.70.183.195])
	by mfilter8-d.gandi.net (mfilter8-d.gandi.net [10.0.15.180]) (amavisd-new,
 port 10024)
	with ESMTP id vsQoMc6N+sg4 for <user@karaf.apache.org>;
	Fri, 29 Jul 2011 23:16:19 +0200 (CEST)
X-Originating-IP: 82.238.224.4
Received: from [192.168.134.20] (bre91-1-82-238-224-4.fbx.proxad.net
 [82.238.224.4])
	(Authenticated sender: jb@nanthrax.net)
	by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id B63D1A8075
	for <user@karaf.apache.org>; Fri, 29 Jul 2011 23:16:18 +0200 (CEST)
Message-ID: <4E33231E.4070502@nanthrax.net>
Date: Fri, 29 Jul 2011 23:16:14 +0200
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11
MIME-Version: 1.0
To: user@karaf.apache.org
Subject: Re: Assigning Wars To Ports And Subdirectories?
References: <1311972443345-3210710.post@n3.nabble.com>
In-Reply-To: <1311972443345-3210710.post@n3.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Gareth,

1/ currently, Pax Web support the webapp context path using the=20
following OSGi statements:

   <Web-ContextPath>/myapp</Web-ContextPath>
   <Webapp-Context>/myapp</Webapp-Context>

When you install the HTTP feature, it installs a jetty.xml file in the=20
etc folder.
In this jetty.xml file, you can define several port number for the=20
embedded jetty server.

Create a new Connector in the jetty.xml with an ID, like:

<Call name=3D"addConnector">
   <Arg>
     <New id=3D"my"=20
class=3D"org.eclipse.jetty.server.nio.SelectChannelConnector">
       ...
       <Set name=3D"port">5340491</Set>
       ...
     </New>
   </Arg>
</Call>

After, to associate the webapp with the Configured server, try to create=20
a etc/context.xml file containing:

<Configure class=3D"org.eclipse.jetty.webapp.WebAppContext">
   <Set name=3D"contextPath">/myapp</Set>
   <Set name=3D"connectorNames">
     <Array type=3D"String">
       <Item>my</Item>
     </Array>
   </Set>
</Configure>

Without guarantee, I never tried this before :)

2/ for the directory, you can create a new file in etc, for instance=20
etc/org.apache.felix.fileinstall-war.cfg containing:

felix.fileinstall.dir=3D${karaf.base}/war
felix.fileinstall.tmpdir=3D${karaf.data}/webapp
felix.fileinstall.poll=3D1000

Could you try this ?

Regards
JB

On 07/29/2011 10:47 PM, Gareth wrote:
> Hello,
>
> I am not sure whether this is a PAX Web question, or a Karaf question b=
ut:
>
> (1) If I install a war/wab file, is there any way of making it availabl=
e on
> certain ports? For example, I would probably want the Karaf console and
> Active MQ console on a separate port to my application wabs/wars (as my
> wabs/wars may be visible through a firewall whilst Karaf console should=
 not
> be).
>
> (2) Any way of installing wars (which are not OSGi wabs) to subdirector=
ies?
> In tomcat I could do this by adding a "#" as part of the war name (e.g.
> hosting#fred.war could be accessed by http://hostname/hosting/fred.war)=
.
> There isn't a similar feature in Karaf/PAX Web, is there?
>
> thanks in advance,
> Gareth
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Assigni=
ng-Wars-To-Ports-And-Subdirectories-tp3210710p3210710.html
> Sent from the Karaf - User mailing list archive at Nabble.com.

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com