Hi Amila, On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi <[email protected]> wrote:
> > > On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando <[email protected]> wrote: > >> Hi again, >> >> I was mistaken. In G-Reg 4.1.1, we have imported, event server, event >> common and qpid server features. In trunk, the feature imports in P2 >> profile are the same. > > > For branch you need to have Qpid feature and for trunk you can remove it. > Ok. > > >> Also after reading through r117481, its just a fix to the versions, and >> has no impact on this. >> >> So, it is not the feature imports but something else as it seems. Can you >> check? >> > > if you look at the event feature here[1] it does not include the qpid > feature. So if GReg getting it in the distribution it should be some other > problem. Please check from which feature GReg getting Qpid bundle. > In both branch and trunk, the Qpid feature is directly imported from the product's P2 profile. So, from what I understand, we have not gotten rid of the Qpid feature from trunk which is what we should be doing. Also, I just tried out eventing on trunk and it is not working. Have you made any changes to the code or the way it works? I'm getting, ++++++++++++++++++++++++++++++++++++++++ ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} - Can not send the notification org.wso2.carbon.event.core.exception.EventBrokerException: Event dispatcher with name /registry/notifications is not exists at org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59) at org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) ++++++++++++++++++++++++++++++++++++++++ The code in the registry eventing component is identical in branch and trunk, so I believe that this is directly related to something in the event component. So, in addition to getting rid of Qpid what should I do? Thanks, Senaka. > > thanks, > Amila. > > [1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event > >> >> Thanks, >> Senaka. >> >> >> On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi Amila, >>> >>> I found this in G-Reg (checked ESB and it seems to be ok - not sure >>> about other products), and yes the Qpid feature is not excluded. I believe >>> that r117481 did not make it to the trunk. I will fix this and commit. >>> >>> Thanks, >>> Senaka. >>> >>> >>> On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi <[email protected]>wrote: >>> >>>> >>>> >>>> On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando <[email protected]>wrote: >>>> >>>>> Hi Amila, >>>>> >>>>> I believe that it was decided to get rid of the embedded Qpid Broker >>>>> from products, which was done on the 3.2.x branch. Now when starting the >>>>> servers on the trunk I see Qpid is still hanging around. Any reason to why >>>>> this was not removed from trunk? >>>>> >>>> >>>> What is the product? Can you please check whether the product has >>>> explicitly imported that? >>>> >>>> thanks >>>> Amila. >>>> >>>>> >>>>> Thanks, >>>>> Senaka. >>>>> >>>>> -- >>>>> *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://linkedin.com/in/senakafernando >>>>> >>>>> *Lean . Enterprise . Middleware >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Amila Suriarachchi* >>>> >>>> Software Architect >>>> WSO2 Inc. ; http://wso2.com >>>> lean . enterprise . middleware >>>> >>>> phone : +94 71 3082805 >>>> >>>> >>> >>> >>> -- >>> *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://linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> *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://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > > -- *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://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
