[Dev] Issue when installing MB features in products that use carbon.event.core
Hi All, We ran to in to the above problem when trying to install MB features in the IOTServer. As we discovered when investigating, root cause of the problem was the use of event-broker.xml, which is used for loading configurations in both components. MB uses the andes.event.core component which has now come to replace the event.core from back in the day (event.core is still referred to from governance components and synapse). Since both components refer to the same file, each try to load contradictory (internal) classes that lead to class not found exceptions. As a workaround to overcome this problem, we will have to rename the event-broker.xml file from event.core feature to something like carbon-event-core.xml to ensure the co-existing of both components in harmony. In addition we will also have to remove specific checks for andes/qpid packages inside of the event.core. I have done the changes against the 4.4.8 tag in a separate branch on my personal repository [1]. Can we get a 4.4.9 version released with this change [2] for us to move forward with the milestone? [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 [2] - https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
I propose changing the file name at MB side. so the changes are minimal. we plan to further optimize this area in upcoming versions. @Hemika, shall we do this? On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara wrote: > Hi All, > > We ran to in to the above problem when trying to install MB features in > the IOTServer. As we discovered when investigating, root cause of the > problem was the use of event-broker.xml, which is used for loading > configurations in both components. > > MB uses the andes.event.core component which has now come to replace the > event.core from back in the day (event.core is still referred to from > governance components and synapse). Since both components refer to the same > file, each try to load contradictory (internal) classes that lead to class > not found exceptions. > > As a workaround to overcome this problem, we will have to rename the > event-broker.xml file from event.core feature to something like > carbon-event-core.xml to ensure the co-existing of both components in > harmony. In addition we will also have to remove specific checks for > andes/qpid packages inside of the event.core. > > I have done the changes against the 4.4.8 tag in a separate branch on my > personal repository [1]. Can we get a 4.4.9 version released with this > change [2] for us to move forward with the milestone? > > [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 > [2] - > https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a > > Thanks and Regards, > > Ruwan Yatawara > > Senior Software Engineer, > WSO2 Inc. > > email : ruw...@wso2.com > mobile : +94 77 9110413 > blog : http://ruwansrants.blogspot.com/ > www: :http://wso2.com > > -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: ram...@wso2.com P: +94 777542851 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
Yeah, I'll look into the proposed change. Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe wrote: > I propose changing the file name at MB side. so the changes are minimal. > we plan to further optimize this area in upcoming versions. > @Hemika, shall we do this? > > On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara wrote: > >> Hi All, >> >> We ran to in to the above problem when trying to install MB features in >> the IOTServer. As we discovered when investigating, root cause of the >> problem was the use of event-broker.xml, which is used for loading >> configurations in both components. >> >> MB uses the andes.event.core component which has now come to replace the >> event.core from back in the day (event.core is still referred to from >> governance components and synapse). Since both components refer to the same >> file, each try to load contradictory (internal) classes that lead to class >> not found exceptions. >> >> As a workaround to overcome this problem, we will have to rename the >> event-broker.xml file from event.core feature to something like >> carbon-event-core.xml to ensure the co-existing of both components in >> harmony. In addition we will also have to remove specific checks for >> andes/qpid packages inside of the event.core. >> >> I have done the changes against the 4.4.8 tag in a separate branch on my >> personal repository [1]. Can we get a 4.4.9 version released with this >> change [2] for us to move forward with the milestone? >> >> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 >> [2] - >> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a >> >> Thanks and Regards, >> >> Ruwan Yatawara >> >> Senior Software Engineer, >> WSO2 Inc. >> >> email : ruw...@wso2.com >> mobile : +94 77 9110413 >> blog : http://ruwansrants.blogspot.com/ >> www: :http://wso2.com >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: ram...@wso2.com > P: +94 777542851 > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
Thanks Ramith and Hemaka. On a side note, we will still have to do code change in event.core to take out the check for andes/qpid packages, for the fix to work properly. Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Wed, Jan 6, 2016 at 3:08 PM, Hemika Kodikara wrote: > Yeah, I'll look into the proposed change. > > Hemika Kodikara > Software Engineer > WSO2 Inc. > lean . enterprise . middleware > http://wso2.com > > Mobile : +9477762 > > On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe wrote: > >> I propose changing the file name at MB side. so the changes are minimal. >> we plan to further optimize this area in upcoming versions. >> @Hemika, shall we do this? >> >> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara wrote: >> >>> Hi All, >>> >>> We ran to in to the above problem when trying to install MB features in >>> the IOTServer. As we discovered when investigating, root cause of the >>> problem was the use of event-broker.xml, which is used for loading >>> configurations in both components. >>> >>> MB uses the andes.event.core component which has now come to replace the >>> event.core from back in the day (event.core is still referred to from >>> governance components and synapse). Since both components refer to the same >>> file, each try to load contradictory (internal) classes that lead to class >>> not found exceptions. >>> >>> As a workaround to overcome this problem, we will have to rename the >>> event-broker.xml file from event.core feature to something like >>> carbon-event-core.xml to ensure the co-existing of both components in >>> harmony. In addition we will also have to remove specific checks for >>> andes/qpid packages inside of the event.core. >>> >>> I have done the changes against the 4.4.8 tag in a separate branch on my >>> personal repository [1]. Can we get a 4.4.9 version released with this >>> change [2] for us to move forward with the milestone? >>> >>> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 >>> [2] - >>> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a >>> >>> Thanks and Regards, >>> >>> Ruwan Yatawara >>> >>> Senior Software Engineer, >>> WSO2 Inc. >>> >>> email : ruw...@wso2.com >>> mobile : +94 77 9110413 >>> blog : http://ruwansrants.blogspot.com/ >>> www: :http://wso2.com >>> >>> >> >> >> -- >> Ramith Jayasinghe >> Technical Lead >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> E: ram...@wso2.com >> P: +94 777542851 >> >> > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
Hi Ruwan, event.core modules in carbon-commons does not have an owner and will be deprecated since we moved the implementations into carbon-registry [1]. Might not be a good idea to commit changes to that? [1] subject: Moving carbon-commons eventing components to registry On Wed, Jan 6, 2016 at 3:16 PM, Ruwan Yatawara wrote: > Thanks Ramith and Hemaka. On a side note, we will still have to do code > change in event.core to take out the check for andes/qpid packages, for the > fix to work properly. > > Thanks and Regards, > > Ruwan Yatawara > > Senior Software Engineer, > WSO2 Inc. > > email : ruw...@wso2.com > mobile : +94 77 9110413 > blog : http://ruwansrants.blogspot.com/ > www: :http://wso2.com > > > On Wed, Jan 6, 2016 at 3:08 PM, Hemika Kodikara wrote: > >> Yeah, I'll look into the proposed change. >> >> Hemika Kodikara >> Software Engineer >> WSO2 Inc. >> lean . enterprise . middleware >> http://wso2.com >> >> Mobile : +9477762 >> >> On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe >> wrote: >> >>> I propose changing the file name at MB side. so the changes are minimal. >>> we plan to further optimize this area in upcoming versions. >>> @Hemika, shall we do this? >>> >>> On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara wrote: >>> Hi All, We ran to in to the above problem when trying to install MB features in the IOTServer. As we discovered when investigating, root cause of the problem was the use of event-broker.xml, which is used for loading configurations in both components. MB uses the andes.event.core component which has now come to replace the event.core from back in the day (event.core is still referred to from governance components and synapse). Since both components refer to the same file, each try to load contradictory (internal) classes that lead to class not found exceptions. As a workaround to overcome this problem, we will have to rename the event-broker.xml file from event.core feature to something like carbon-event-core.xml to ensure the co-existing of both components in harmony. In addition we will also have to remove specific checks for andes/qpid packages inside of the event.core. I have done the changes against the 4.4.8 tag in a separate branch on my personal repository [1]. Can we get a 4.4.9 version released with this change [2] for us to move forward with the milestone? [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 [2] - https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a Thanks and Regards, Ruwan Yatawara Senior Software Engineer, WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com >>> >>> >>> -- >>> Ramith Jayasinghe >>> Technical Lead >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> E: ram...@wso2.com >>> P: +94 777542851 >>> >>> >> > -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when installing MB features in products that use carbon.event.core
I propose to change the name of 'master-datasources.xml' as well. When we tried to install MB features in the IoT server, we had to manually add mb-store configurations into their master-datasources.xml from the code level. Thank you On Wed, Jan 6, 2016 at 3:00 PM, Ramith Jayasinghe wrote: > I propose changing the file name at MB side. so the changes are minimal. > we plan to further optimize this area in upcoming versions. > @Hemika, shall we do this? > > On Wed, Jan 6, 2016 at 2:52 PM, Ruwan Yatawara wrote: > >> Hi All, >> >> We ran to in to the above problem when trying to install MB features in >> the IOTServer. As we discovered when investigating, root cause of the >> problem was the use of event-broker.xml, which is used for loading >> configurations in both components. >> >> MB uses the andes.event.core component which has now come to replace the >> event.core from back in the day (event.core is still referred to from >> governance components and synapse). Since both components refer to the same >> file, each try to load contradictory (internal) classes that lead to class >> not found exceptions. >> >> As a workaround to overcome this problem, we will have to rename the >> event-broker.xml file from event.core feature to something like >> carbon-event-core.xml to ensure the co-existing of both components in >> harmony. In addition we will also have to remove specific checks for >> andes/qpid packages inside of the event.core. >> >> I have done the changes against the 4.4.8 tag in a separate branch on my >> personal repository [1]. Can we get a 4.4.9 version released with this >> change [2] for us to move forward with the milestone? >> >> [1] - https://github.com/ruwany/carbon-commons/tree/IoTS-1.0.0-M1 >> [2] - >> https://github.com/ruwany/carbon-commons/commit/4ea0f1f52b7fa9bc57b856e2271ffcad25eb965a >> >> Thanks and Regards, >> >> Ruwan Yatawara >> >> Senior Software Engineer, >> WSO2 Inc. >> >> email : ruw...@wso2.com >> mobile : +94 77 9110413 >> blog : http://ruwansrants.blogspot.com/ >> www: :http://wso2.com >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: ram...@wso2.com > P: +94 777542851 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sasikala Kottegoda *Software Engineer* WSO2 Inc., http://wso2.com/ lean. enterprise. middleware Mobile: +94 774835928/712792401 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
