Hi Manoj,
> Is there specific requirement to package same stream definition(name, > version) in two CApps. > This is something the user is responsible that we don't have a control :( . StreamDefinition is something that can be generated even automatically, according to a message delivered to the server. Control is only on the user side. IMO, there is no specific reason for having two stream defs with the same name and the version. That is why I said if the same stream def is going to be saved, even if there is no conflicts, we have to fail that. if it is a car file deployment, entire carfile deployment gets failed and kept that as a faulty cApp. @suho, @anjana please can we have your input also here? Do we have any specific reason for having two streamdefs with the same name and the version? Thanks, -Ayash > Regards, > Manoj > > > -- Ayashkantha Ramasinghe Software Engineer WSO2, Inc. email: [email protected] <[email protected]>; TP: +94 77 7 487 669
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
