axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sameera Jayasoma (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AXIS2-5234) Displaying a WARN message instead of failing a service deployment when a specified transport is not available.
Date Fri, 27 Jan 2012 13:40:44 GMT

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

Sameera Jayasoma updated AXIS2-5234:
------------------------------------

    Attachment: axis2-patch-27-Jun-2012.txt

Attaching the patch
                
> 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.7.0
>            Reporter: Sameera Jayasoma
>         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


Mime
View raw message