On Tue, Feb 15, 2011 at 5:47 PM, Senaka Fernando <[email protected]> wrote:
> > > On Tue, Feb 15, 2011 at 3:29 PM, Afkham Azeez <[email protected]> wrote: > >> Worse, I heard that G-Reg is planning to ship with the old API. So, we >> will have multiple product with the sample platform using different eventing >> APIs. We always find creative ways to screw up. :) >> >> >> On Tue, Feb 15, 2011 at 3:05 PM, Tharindu Mathew <[email protected]>wrote: >> >>> >>> >>> On Tue, Feb 15, 2011 at 3:00 PM, Senaka Fernando <[email protected]>wrote: >>> >>>> >>>> >>>> On Tue, Feb 15, 2011 at 2:46 PM, Tharindu Mathew <[email protected]>wrote: >>>> >>>>> We have decided to have a hackathon to move into the new eventing impl. >>>>> as this is causing issues at product startups, etc. >>>>> >>>>> We will be having this on Monday (21st) morning 10 AM. We need one >>>>> member from each product team for this. >>>>> >>>> >>>> -1, please see the reply to the other thread. Let's schedule a meeting >>>> first and identify the mapping between the current API and the new API, and >>>> determine whether there is no loss of functionality when moving into the >>>> new >>>> API. IIRC, Multi-tenancy etc was not complete in the new API. >>>> >>> >>> It seems that G-Reg is not moving to this because of it's own custom >>> implementation. Moving forward in this space is a MUST from BAM's >>> perspective to achieve a working state OOTB. Other products have already >>> started moving. >>> >> >>> So, if G-Reg has a problem, we should halt on moving eventing in G-Reg >>> and proceed with the others. >>> >> > Please do not start moving until we have a clear understanding of what > needs to be done. As Azeez pointed out earlier, Its a mess right now. > Creating a new API which is not backward compatible, overnight does not make > it a good reason for a product to migrate to it the next week. > > Not really G-Reg's problem here. The subscription manager model, the model > of the event, topic etc, all of it has been redefined. > > It is not the fact that we are rigid and don't want to move. We are looking > forward to a release by end of March, and making drastic changes to > something that's stable, at this moment, is extremely risky. Charitha might > want to add to this. I think its best to hold back till we meet on Monday. > AFAIK only BAM (data publishers + core), DSS and Registry uses event component. Out of these changes to be done to BAM and DSS are trivial. But for registry there are many changes. The new model assumes a pure broker model since it has to based on JMS. As I descussed with Senaka old event implementaion has written some registry specific code within the event and it let users of the broker API to mange the place where to save subscriptions etc .. But if we take any JMS Broker it won't let users at the JMS Api level to configure subscription storage place etc .. If the registry has a critical release in march I think the better solution is to move the old event implement modules to registry it self and keep it there until they have time to migrate to new API. thanks, Amila. > Can you list the issues that are required to be fixed for BAM to work? I'd > like to know what doesn't work with the existing model. I understand ESB's > requirements. (P.S. Sorry if I missed an old thread on subject. If so, > please do point me to it.) > > Thanks, > Senaka. > > >> >>> >> >>>> By the way, let's stick to a single mail thread. >>>> >>> >>> Yes, please reply to this thread. >>> >>>> >>>> Thanks, >>>> Senaka. >>>> >>>>> >>>>> The identified teams are: >>>>> >>>>> - AS >>>>> - ESB >>>>> - DSS >>>>> - G-Reg >>>>> - BAM >>>>> >>>>> >>>>> On Tue, Feb 15, 2011 at 2:16 PM, Amila Jayasekara <[email protected]>wrote: >>>>> >>>>>> On Tue, Feb 15, 2011 at 1:37 PM, Tharindu Mathew <[email protected]> >>>>>> wrote: >>>>>> > Hi Amila, >>>>>> > This is due to the new eventing model not being adopted on ESB. This >>>>>> was >>>>>> > discussed in an earlier thread. >>>>>> > If you remove everything except event.broker from the event-feature >>>>>> and >>>>>> > rebuild the feature + product you will not see this error. >>>>>> >>>>>> Thanks Tharindu, i am no longer getting the error. It will be great if >>>>>> we can have a permanent solution. >>>>>> >>>>>> Thanks >>>>>> AmilaJ >>>>>> >>>>>> > >>>>>> > On Tue, Feb 15, 2011 at 1:25 PM, Amila Jayasekara <[email protected]> >>>>>> wrote: >>>>>> >> >>>>>> >> Hi All, >>>>>> >> I am getting following error when starting esb in trunk (Complete >>>>>> log >>>>>> >> attached). First i found out that qpid is not in esb profile in >>>>>> >> features/pom.xml. But adding qpid to esb profile of >>>>>> features/pom.xml >>>>>> >> didnt solve the issue. It seems qpid is not added as a feature >>>>>> >> artifact in esb/modules/p2-profile/pom.xml. I assume that is the >>>>>> cause >>>>>> >> for following error ? If so, what is the correct action ? Should we >>>>>> >> have qpid as a feature artifact in esb/modules/p2-profile/pom.xml ? >>>>>> >> >>>>>> >> Feedback appreciated. >>>>>> >> >>>>>> >> Thanks >>>>>> >> AmilaJ >>>>>> >> >>>>>> >> [2011-02-15 12:46:19,400] ERROR - Axis2ServiceRegistry Error >>>>>> building >>>>>> >> service from bundle : Symbolic Name: >>>>>> >> org.wso2.carbon.event.admin,Bundle Version: 3.2.0.SNAPSHOT, ID: 142 >>>>>> >> java.lang.NoClassDefFoundError: >>>>>> >> [Lorg/wso2/carbon/qpid/commons/SubscriptionDetails; >>>>>> >> at java.lang.Class.getDeclaredMethods0(Native Method) >>>>>> >> at >>>>>> java.lang.Class.privateGetDeclaredMethods(Class.java:2427) >>>>>> >> at java.lang.Class.privateGetPublicMethods(Class.java:2547) >>>>>> >> at java.lang.Class.getMethods(Class.java:1410) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.description.java2wsdl.bytecode.MethodTable.loadMethods(MethodTable.java:43) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.description.java2wsdl.bytecode.MethodTable.<init>(MethodTable.java:33) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.<init>(DefaultSchemaGenerator.java:141) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:389) >>>>>> >> at >>>>>> >> >>>>>> org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101) >>>>>> >> at >>>>>> >> >>>>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:216) >>>>>> >> 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) >>>>>> >> Caused by: java.lang.ClassNotFoundException: >>>>>> >> org.wso2.carbon.qpid.commons.SubscriptionDetails >>>>>> >> at >>>>>> >> >>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489) >>>>>> >> at >>>>>> >> >>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405) >>>>>> >> at >>>>>> >> >>>>>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393) >>>>>> >> at >>>>>> >> >>>>>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105) >>>>>> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:252) >>>>>> >> at >>>>>> java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) >>>>>> >> ... 19 more >>>>>> >> [2011-02-15 12:46:19,476] ERROR - Axis2ServiceRegistry Error >>>>>> building >>>>>> >> service from bundle : Symbolic Name: org.wso2.carbon.event.ws >>>>>> ,Bundle >>>>>> >> Version: 3.2.0.SNAPSHOT, ID: 148 >>>>>> >> 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) >>>>>> >> [2011-02-15 12:46:20,937] INFO - DeploymentInterceptor Deploying >>>>>> >> Axis2 service: wso2carbon-sts {super-tenant} >>>>>> >> >>>>>> >> _______________________________________________ >>>>>> >> Carbon-dev mailing list >>>>>> >> [email protected] >>>>>> >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >> >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Regards, >>>>>> > >>>>>> > Tharindu Mathew >>>>>> > Software Engineer, >>>>>> > WSO2 Inc., >>>>>> > http://wso2.com >>>>>> > >>>>>> > _______________________________________________ >>>>>> > Carbon-dev mailing list >>>>>> > [email protected] >>>>>> > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> > >>>>>> > >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> [email protected] >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Tharindu Mathew >>>>> >>>>> Software Engineer, >>>>> WSO2 Inc., >>>>> http://wso2.com >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Product Manager - WSO2 Governance Registry; >>>> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://www.linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> Regards, >>> >>> Tharindu Mathew >>> >>> Software Engineer, >>> WSO2 Inc., >>> http://wso2.com >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> * >> * >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> * >> email: **[email protected]* <[email protected]>* 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* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2, Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://www.linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
