Hi Devs, I have now fixed the above issue and pushed the modification to master branch.
The problem was with the way we package CXF runtime into the distribution. We had written maven logic to get all the dependencies of the REST API/Web App feature and copy them into the CXF runtime folder. It has packaged Stratos dependencies to the CXF runtime and as a result Stratos components have been loaded by the Web App class loader. I removed this logic since CXF runtime is already packaged by the Carbon CXF feature. As a part of this effort I have also refined features, the way we have structured them and feature names. Thanks On Tue, Jan 27, 2015 at 12:28 PM, Imesh Gunaratne <[email protected]> wrote: > Hi Devs, > > Currently Mock IaaS resides in the Cloud Controller. However to verify > cloud bursting scenarios and Stratos product clustering features we need to > be able to run Mock IaaS as a separate product. To support this we could > expose Mock IaaS as a REST service and create a server profile. By doing > that we could start Mock IaaS as a separate product and configure cloud > controller to talk to it via the Mock Iaas API. > > I did almost all the changes required for this functionality and found a > problem in accessing Mock IaaS OSGi service from the Mock IaaS API web app. > It seems like Mock IaasS API web app creates a separate class loader and it > does not re-use the classes loaded by OSGi runtime. Will update the status > of this soon. > > https://issues.apache.org/jira/browse/STRATOS-1143 > > Thanks > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
