Actually this has to be fixed in the event feature. The event broker jar should be removed from this feature.
Thanks, Supun.. On Thu, Mar 31, 2011 at 2:42 PM, Kasun Indrasiri <[email protected]> wrote: > Hi Supun, > So, can we get rid of the following error at the ESB startup with this > modification? > > ERROR - Axis2ServiceRegistry Error building service from bundle : Symbolic > Name: org.wso2.carbon.event.ws,Bundle Version: 3.2.0.SNAPSHOT, ID: 181 > org.apache.axis2.AxisFault: Two services cannot have same name. A service > with the EventBrokerService [null] name already exists in the system. > at > org.apache.axis2.engine.AxisConfiguration.addToAllServicesMap(AxisConfiguration.java:492) > at > org.apache.axis2.description.AxisServiceGroup.addService(AxisServiceGroup.java:110) > at > org.apache.axis2.deployment.DeploymentEngine.fillServiceGroup(DeploymentEngine.java:752) > at > org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:608) > at > org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217) > at > org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:106) > at > org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:92) > at > org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:462) > at > org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:282) > at > org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916) > at > org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) > at > org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330) > > On Thu, Mar 31, 2011 at 2:16 PM, Supun Kamburugamuva <[email protected]> wrote: >> >> ESB has moved to the new Event implementation with the new event >> mediator. Now user can dispatch messages to given topic using the >> event mediator. The previous mediator used to send event to a event >> source. >> >> Thanks, >> -- >> Supun Kamburugamuva >> Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com >> Member, Apache Software Foundation; http://www.apache.org >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 431 3585 >> Blog: http://supunk.blogspot.com >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > -- > Kasun Indrasiri > Senior Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 71 536 4128 > Blog : http://kasunpanorama.blogspot.com/ > -- Supun Kamburugamuva Technical Lead & Product Manager, WSO2 Inc.; http://wso2.com Member, Apache Software Foundation; http://www.apache.org WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
