[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-user-ja
Subject:    [jira] [Updated] (AXIS2-5234) Displaying a WARN message instead of failing a service deployment when
From:       "Sagara Gunathunga  (Updated) (JIRA)" <jira () apache ! org>
Date:       2012-01-30 7:39:10
Message-ID: 223177776.6800.1327909150546.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ 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


[prev in list] [next in list] [prev in thread] [next in thread]