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 ji...@apache.org on 2004/06/01 15:25:00 UTC
[jira] Created: (AXIS-1378) No information is returned to user when deployment failed
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1378
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1378
Summary: No information is returned to user when deployment failed
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
Deployment / Registries
Versions:
1.1
Assignee:
Reporter: easyproglife
Created: Tue, 1 Jun 2004 6:24 AM
Updated: Tue, 1 Jun 2004 6:24 AM
Environment: PC / Win2000 / JDK1.4.2
Description:
I am trying to deploy "deploy.wsdd" file using Admin servlet.
When a class that defined in deploy.wsdd (in my case it's in type mapping element) could not be found by the Axis engine, nothing is reported to the user. The user have no idea why the service has not been deployed. He even doesn't know if the service is deployed or not. I have to go to "http://<myhost>/<myApp>/services" to see if it has been deployed.
The solution is very simple!!!
After a few hours of debugging I have found that in class org.apache.axis.deployment.wsdd.WSDDDeployment line 245 (it's in the constructor) there is an empty "catch (WSDDNonFatalException ex)" block.
I think that at least a warning message with the cause to the exception should be written to the log. In my case the problem was: "ClassCastException" along with the missing class. Having this piece of information caused me to solve the problem immediatlly.
A better solution should return the failure details to the user via the web service response. But a log line is the easiest minimum you can do to solve this bug.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXIS-1378) No information is returned to user when deployment failed
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Tue, 8 Jun 2004 10:41 AM
- replace log.debug with log.info in 1 instance of try/catch
- added log.info in 2 other locations.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1378
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1378
Summary: No information is returned to user when deployment failed
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Components:
Deployment / Registries
Fix Fors:
current (nightly)
Versions:
1.1
Assignee:
Reporter: easyproglife
Created: Tue, 1 Jun 2004 6:24 AM
Updated: Tue, 8 Jun 2004 10:41 AM
Environment: PC / Win2000 / JDK1.4.2
Description:
I am trying to deploy "deploy.wsdd" file using Admin servlet.
When a class that defined in deploy.wsdd (in my case it's in type mapping element) could not be found by the Axis engine, nothing is reported to the user. The user have no idea why the service has not been deployed. He even doesn't know if the service is deployed or not. I have to go to "http://<myhost>/<myApp>/services" to see if it has been deployed.
The solution is very simple!!!
After a few hours of debugging I have found that in class org.apache.axis.deployment.wsdd.WSDDDeployment line 245 (it's in the constructor) there is an empty "catch (WSDDNonFatalException ex)" block.
I think that at least a warning message with the cause to the exception should be written to the log. In my case the problem was: "ClassCastException" along with the missing class. Having this piece of information caused me to solve the problem immediatlly.
A better solution should return the failure details to the user via the web service response. But a log line is the easiest minimum you can do to solve this bug.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira