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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2006/12/04 21:30:21 UTC
[jira] Assigned: (AXIS2-1133) Use of Application Scope Mandates the
specification of "ServiceClass" parameter in services.xml
[ http://issues.apache.org/jira/browse/AXIS2-1133?page=all ]
Deepal Jayasinghe reassigned AXIS2-1133:
----------------------------------------
Assignee: Deepal Jayasinghe
> Use of Application Scope Mandates the specification of "ServiceClass" parameter in services.xml
> -----------------------------------------------------------------------------------------------
>
> Key: AXIS2-1133
> URL: http://issues.apache.org/jira/browse/AXIS2-1133
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Reporter: Thilina Gunarathne
> Assigned To: Deepal Jayasinghe
>
> When we use Application Scope as the scope of a deploying service Axis2 mandates the specifying of "ServiceClass" parameter in services.xml. Axis2 checks for that explicitly and If it's not found throws an exception.
> This is gives lot of inconvenience when some body is extending Axis2 using his own message receiver. One example is a service composition scenario like an BPEL engine, which uses it's own message receiver.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org