Return-Path: 
 <java-dev-return-86653-apmail-axis-java-dev-archive=axis.apache.org@axis.apache.org>
X-Original-To: apmail-axis-java-dev-archive@www.apache.org
Delivered-To: apmail-axis-java-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 6E3739142
	for <apmail-axis-java-dev-archive@www.apache.org>;
 Mon, 30 Jan 2012 07:39:41 +0000 (UTC)
Received: (qmail 15908 invoked by uid 500); 30 Jan 2012 07:39:39 -0000
Delivered-To: apmail-axis-java-dev-archive@axis.apache.org
Received: (qmail 15759 invoked by uid 500); 30 Jan 2012 07:39:34 -0000
Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:java-dev-help@axis.apache.org>
List-Unsubscribe: <mailto:java-dev-unsubscribe@axis.apache.org>
List-Post: <mailto:java-dev@axis.apache.org>
List-Id: <java-dev.axis.apache.org>
Reply-To: java-dev@axis.apache.org
Delivered-To: mailing list java-dev@axis.apache.org
Received: (qmail 15744 invoked by uid 99); 30 Jan 2012 07:39:33 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2012 07:39:33 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2012 07:39:31 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 84FB516CD2E
	for <java-dev@axis.apache.org>; Mon, 30 Jan 2012 07:39:10 +0000 (UTC)
Date: Mon, 30 Jan 2012 07:39:10 +0000 (UTC)
From: "Sagara Gunathunga  (Updated) (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: 
 <223177776.6800.1327909150546.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1041649366.85046.1327657362337.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AXIS2-5234) Displaying a WARN message instead of
 failing a service deployment when a specified transport is not available.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/AXIS2-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sagara Gunathunga  updated AXIS2-5234:
--------------------------------------

    Affects Version/s:     (was: 1.7.0)
                       1.6.1
    
> Displaying a WARN message instead of failing a service deployment when a specified transport is not available.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-5234
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5234
>             Project: Axis2
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.6.1
>            Reporter: Sameera Jayasoma
>             Fix For: 1.7.0
>
>         Attachments: axis2-patch-27-Jun-2012.txt
>
>
> Axis2 throws exceptions when the specified transport of a service is not available. And the service becomes faulty as well. If this service has specified multiple transports and these other transports are available, Axis2 should expose the service in other transports, without simply failing the deployment. 
> e.g 1. Service Foo has specified http and https transports.
>         <transports>
>             <transport>https</transport>
>             <transport>http</transport>
>         </transports>
> Now We configured Axis2 only with Http transport. When we deploy the service Foo in Axis2, the default behavior of Axis2 is to fail the service deployment saying "Https transport is not available.".  But my suggestion is, we should deploy the service Foo in Http transport and display a WARN message to notify that this service will not be exposed in Https.
> e.g 2. Service Bar has specified https and jms transports.
>         <transports>
>             <transport>https</transport>
>             <transport>jms</transport>
>         </transports>
> We configured Axis2 only with Http transport. Now this service cannot be exposed in either Https or jms. Hence Axis2 should fail the deployment of the service Bar.
> I've created a patch to support this bahavior. I will attach a patch shortly.
> Thanks,
> Sameera.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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