> > > 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. > > Could it be feasible to add a UUID to the stream definition name or version when checked in to the registry? That would ensure uniqueness, but would cause a deviation of the registry name/version from the capp name/version. Perhaps we could work around user laziness (not renaming or versioning) by adding a UUID only if a duplicate name/version is present in the registry.
Thanks, Colin Roy-Ehri Software Engineer *WSO2, Inc. : wso2.com <http://wso2.com/>* *Mobile* : 812-219-6517
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
