You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sameera Jayasoma (Created) (JIRA)" <ji...@apache.org> on 2012/01/27 10:42:42 UTC
[jira] [Created] (AXIS2-5234) Displaying a WARN message instead of
failing a service deployment when a specified transport is not available.
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
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
[jira] [Updated] (AXIS2-5234) Displaying a WARN message instead of
failing a service deployment when a specified transport is not available.
Posted by "Sameera Jayasoma (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AXIS2-5234) Displaying a WARN message instead
of failing a service deployment when a specified transport is not
available.
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195996#comment-13195996 ]
Hudson commented on AXIS2-5234:
-------------------------------
Integrated in Axis2 #1254 (See [https://builds.apache.org/job/Axis2/1254/])
Applied patch for AXIS2-5234 and AXIS2-5235.
sagara :
Files :
* /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/deployment/ServiceBuilder.java
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/axis2.xml
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService1
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService1/META-INF
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService1/META-INF/services.xml
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService2
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService2/META-INF
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService2/META-INF/services.xml
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService3
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService3/META-INF
* /axis/axis2/java/core/trunk/modules/kernel/test-resources/deployment/exposedTransportsRepo/services/echoService3/META-INF/services.xml
* /axis/axis2/java/core/trunk/modules/kernel/test/org/apache/axis2/deployment/DummyTransportListener.java
* /axis/axis2/java/core/trunk/modules/kernel/test/org/apache/axis2/deployment/ExposedTransportsTest.java
> 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
[jira] [Updated] (AXIS2-5234) Displaying a WARN message instead of
failing a service deployment when a specified transport is not available.
Posted by "Sagara Gunathunga (Updated) (JIRA)" <ji...@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
[jira] [Resolved] (AXIS2-5234) Displaying a WARN message instead of
failing a service deployment when a specified transport is not available.
Posted by "Sagara Gunathunga (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sagara Gunathunga resolved AXIS2-5234.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
Patch applied in r1237553. Thanks for your contribution.
> 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