On Mon, Apr 26, 2010 at 7:48 PM, Dumindu Pallewela <[email protected]> wrote:
> > > On Mon, Apr 26, 2010 at 7:31 PM, Amila Suriarachchi <[email protected]>wrote: > >> hi, >> >> I saw this code in bam BAMConfigAdminService even in the branch. >> >> try { >> //TODO: get the un/pw from ui >> BrokerClient client = new >> BrokerClient(BAMConfigServiceComponent.getConfigurationContextService().getServerConfigContext(), >> publisherURL, "admin", "admin"); >> return client.subscribe(topic, subscriberURL); >> >> is this mean if some one change the wsas username/password bam won't be >> able to work in eventing mode? >> > > ooops! no this is a bug. I've forgotten to fix the TODO when I committed! > This went in with a change that was done for data publishers in 3.0.0. > > BTW, I think we can release bam-data-publishers with BAM right (so that we > can fix this for BAM 1.1.0)? > Correct. And why do this new API need UN/PW. We did not need it in the old release??? Samisa... > > Thanks, > Dumindu. > > > -- > Dumindu Pallewela > WSO2 | "Lean . Enterprise . Middleware" | http://wso2.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://wso2.com/ - "lean . enterprise . middleware"
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
