Hi Gihan, This is what I believe. As there is no way to edit or delete streams properly in BAM at present, the user should not be able to edit or delete a stream once created. Created streams should be shown as uneditable in UI. It will give the sense to the user that the created streams cannot be edited or deleted. It will be more inconvenient if the user edit an existing stream and face this problem. He will have no idea about the error. The exception will not appear immediately and will happen after he restart the server which will confuse the user more.
* Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 On Wed, Apr 24, 2013 at 3:15 PM, Gihan Anuruddha <[email protected]> wrote: > Hi Maninda, > > I think we can't block stream definition updating from user. It may cause > some inconvenience in user point of view. What we can do that catch the > "org.wso2.carbon.databridge.commons.exception.DifferentStreamDefinitionAlreadyDefinedException" > exception and show proper error message regarding the version no. and user > can decide the version no. > > WDYT? > > Thanks. > Gihan > > > On Wed, Apr 24, 2013 at 2:15 PM, Maninda Edirisooriya <[email protected]>wrote: > >> First, the main problem have to be fixed is to prevent a stream (i.e., >> name + version) from getting updated once created. Then the user have to >> create a new stream with a new version. Not getting updated in Synapse XML >> is another problem. Actually it a kind of feature in ESB. So let's ignore >> it for now. When a new stream version is created it is the responsibility >> of the user to update the Synapse XML. As the old existing stream cannot be >> modified, the given error will not come. If the user wants to use the new >> stream version he has to explicitly do it. >> >> * >> Maninda Edirisooriya* >> Software Engineer >> *WSO2, Inc. >> *lean.enterprise.middleware. >> >> *Blog* : http://maninda.blogspot.com/ >> *Phone* : +94 777603226 >> >> >> On Wed, Apr 24, 2013 at 1:30 PM, Gihan Anuruddha <[email protected]> wrote: >> >>> Hi, >>> >>> We can create BAM profiles in ESB after adding BAM Mediator feature to >>> the ESB. In this BAM profiles >>> you can add/update stream definitions. Currently once you update the >>> existing stream definition version no. will not get incrementality update >>> automatically unless if you manually updated it. But sometimes users forget >>> to update this once they did small changes to stream properties. Due to >>> this; cassandra throws errors since it try to save another stream >>> definition with same row id details (like stream1:1.0.0). >>> >>> We can add version auto incremental feature from Mediator agent side but >>> the problem is what is the proper way. We can either increment micro >>> version like 1.0.0, 1.0.1, 1.0.2 ... or major version like 1.0.0, 2.0.0, >>> 3.0.0 .... . What is the best way to do? >>> >>> >>> Thanks, >>> Gihan >>> -- >>> --- >>> W.G. Gihan Anuruddha >>> Senior Software Engineer | WSO2, Inc. >>> M: +94772272595 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > --- > W.G. Gihan Anuruddha > Senior Software Engineer | WSO2, Inc. > M: +94772272595 >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
