[ http://issues.apache.org/jira/browse/MUSE-139?page=comments#action_12446984 ] Dan Jemiolo commented on MUSE-139: ----------------------------------
We had to make them static because we only wanted one instance of the service for the multiple context paths that we had to specify in Axis2. That is, Axis2's service.xml requires us to specify each resource type as a <service/> element, with the WS-A Action URIs it supports, or requests will not get through to Muse. Since the <service/> element requires us to specify a service class for it to load, we can't have a non-static class. In order for Muse to allow different ws-resource types to communicate with one another inside the application, they must be handled by the same ResourceManager, and thus, the same Axis2 service instance. > AxisEnvironment usings unnecessary static methods > ------------------------------------------------- > > Key: MUSE-139 > URL: http://issues.apache.org/jira/browse/MUSE-139 > Project: Muse > Issue Type: Improvement > Components: Deployment - Axis2 > Affects Versions: 2.0.0 > Reporter: James Shiell > Assigned To: Dan Jemiolo > Priority: Minor > > The AxisEnvironment class has many static methods that have no reason for a > static modifier. Could these please be removed to aid in the ease of > extending this class? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
