[
https://issues.apache.org/jira/browse/AXIS2-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1133.
--------------------------------------
Resolution: Fixed
Fixed in the current SVN
> Use of Application Scope Mandates the specification of "ServiceClass"
> parameter in services.xml
> -----------------------------------------------------------------------------------------------
>
> Key: AXIS2-1133
> URL: https://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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
