Hi Ayash,
> 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. > This case can be handled by your artifact deployer logic (if required). Since CApp deployemnt process is atomic if even single artifact got failed to deploy the CApp deployment will be failed. In general AFAIK we don't recommend to have artifacts with same name and version since we map artifacts using name value pair. Regards, Manoj
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
