Based on our discussion, I did a basic POC of removing event component and
doing the changes to deploy the bam data publishers, and seems that we will
have to change at least the publisher service endpoint address, and patch
BAM.

This is because if the event WS is already in the product (and it most
probably will be since registry, deployment synchronizer needs it), and the
name will clash if we use the same name for the BAM publisher WS. So if we
use a different name, the service endpoint will change, thus, requiring us
to change at least a line of code in BAM.

On Mon, Jun 6, 2011 at 2:20 PM, Sanjiva Weerawarana <[email protected]>wrote:

> Oneven Mon, Jun 6, 2011 at 2:04 PM, Amila Suriarachchi <[email protected]>wrote:
>
>>
>>
>> On Mon, Jun 6, 2011 at 1:28 PM, Sumedha Rubasinghe <[email protected]>wrote:
>>
>>> This is the conclusion from the discussion happened little while ago.
>>>
>>> As Amila mentioned, we can switch to in-memory storage from Qpid. But
>>> this has not been fully test. We will test this set up (in-memory) using BAM
>>> & then make the change permanent for 3.2.0.
>>>
>>> This way, each of the products will have a minimum impact from a code
>>> change perspective.
>>>
>>
>> One product can have only one broker. i.e if bam publisher in ESB wants to
>> use the in memory one, then all the other components, GReg, Deployment
>> synchronizer, publish  mediator should use that.
>>
>
> ARGHHHHH. This is NOT going to work guys. Can we please reconvene and
> rehash the discussion?
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Regards,

Tharindu
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to