Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of andreas.veithen@gmail.com
 designates 72.14.220.159 as permitted sender)
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=OdGZgcEQbUcMLopJod1b6xc3XzsDKdYeI9d5DLo1Ed6jYqheVm04DVslTwOeqH3X4h
         dE1nI0f2o9ekgQgYHCZ7iWkfq3LYy+1lHv9NY0qymzwymzPnEWD5Ro0otAgrZTAKm7EE
         9pqucSuJaWn8vHkNMthDYGZ6O+lBHmrqfjVws=
Message-ID: <b67458760811031319v15992a9br1edcf92c586de83a@mail.gmail.com>
Date: Mon, 3 Nov 2008 22:19:46 +0100
From: "Andreas Veithen" <andreas.veithen@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: JMS,SMTP sample configurations missing from axis2.xml
In-Reply-To: <490F1A9F.5090103@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <358531180811030723w2a4bd45cj76bcccdc402a1a76@mail.gmail.com>
	 <490F1A9F.5090103@apache.org>

On one hand, given that the transports have been split into several
modules, it makes sense to not activate the less common ones by
default, because it would result in an error when they are not on the
classpath. But I also see your point, Asankha, that if these
transports are on the classpath, it is annoying that people are forced
to write their own axis2.xml in order to use them. Maybe the best
solution would be to allow to mark transports in axis2.xml as
"optional" and enhance Axis2 so that if the implementation class of a
transport marked this way can't be loaded, it just ignores it.

Andreas

On Mon, Nov 3, 2008 at 16:37, Asankha Perera <asankha@apache.org> wrote:
> Sumedha
>>
>> Until recently we used to have commented out blocks of JMS & SMTP sample
>> configurations within axis2.xml. But I do not see these now.
>> Were these removed on purpose? Or did these get deleted accidentally
>> during recent transport module relocation? If so shall I add them back?
>> I want to add a sample configuration for XMPP transport & wondering where
>> to put it.
>
> Yes, also I noticed that someone had commented the JMSSender from the
> default axis2.xml, which makes a default client unable to use the JMS sender
> which is quite troublesome for users IMHO. Its not the first time this
> happened as I remember :-( .. we should have all possible transports enabled
> on the default axis2.xml files, and also include example configuration
> options where applicable
>
> asankha
>
> --
> Asankha C. Perera
> http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org