Hi, Please find the status of MS.
1. Build status. Build is successful with all the tests. 2. Test status - any failing commented out tests. Jira links if so. No. 3. Code coverage - current coverage figures. line, %block, %method, %class, % 37% (847.4/2274)36% (3926/10862)49% (125/257)55% (28/51) 4. Status & severity of pending L1s/L2s L1 = 3 CARBON-12371 <https://wso2.org/jira/browse/CARBON-12371> CARBON-12635 <https://wso2.org/jira/browse/CARBON-12635> CARBON-12766 <https://wso2.org/jira/browse/CARBON-12766> L2 = 4 CARBON-11004 <https://wso2.org/jira/browse/CARBON-11004> CARBON-11825 <https://wso2.org/jira/browse/CARBON-11825> CARBON-12637 <https://wso2.org/jira/browse/CARBON-12637> CARBON-12645 <https://wso2.org/jira/browse/CARBON-12645> 5. Other issues & concerns. This was found by Lalaji while doing the smoke test in MS. 1) While server startup time,when samples deployment happen PersistanceExceptions[1] are thrown. 2) When a mashup saved/uploaded PersistanceExceptions[1] are thrown. 3) Cannot apply security for listed mashup services. 4) Cannot access Custom UIs for mashups and a null pointer thrown in backend.Created the jira [2] to track it. Other than that external/internal try-it, javascript stub generator,scraping assistant,mashup query param accessing works properly. [1] [2012-04-02 14:50:01,925] ERROR - Exception occurred while handling service update event. {super-tenant} org.wso2.carbon.core.persistence.PersistenceException: Unable to handle new service addition. Service: admin/RESTSample at org.wso2.carbon.core.persistence.AbstractPersistenceManager.handleExceptionWithRollback(AbstractPersistenceManager.java:564) at org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:299) at org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:283) at org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652) at org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406) at org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:606) at org.wso2.carbon.mashup.jsservices.deployer.JSDeployer.deploy(JSDeployer.java:191) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139) at org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:461) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95) at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65) at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:367) at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:262) at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) Caused by: java.lang.NullPointerException at org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:348) at org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:196 [2] https://wso2.org/jira/browse/CARBON-12766 Regards, Dilshan On Tue, Apr 3, 2012 at 8:41 PM, Afkham Azeez <az...@wso2.com> wrote: > RMs, > Please send in a report of the current state of your products. This should > include; > > 1. Build status > 2. Test status - any failing commented out tests. Jira links if so > 3. Code coverage - current coverage figures > 4. Status & severity of pending L1s/L2s > 5. Other issues & concerns > > Thanks > Azeez > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
