Hmm, I can't guess what the use-cases are that only require only-way relations. However, the intuitive logic is for two-way. It is simply not possible to have a one-way relation with something like owner/owned. If someone doesn't want to see those relations at a later date then fair enough, we should add options into the creation of the relation that says e.g. 'only show this direction'. But, to not have two-way by default is, to my mind, missing the point on dependancy relationships and simplificiation for the user.
regards, john. John Hawkins Director: Solutions Architecture On Fri, Nov 6, 2015 at 11:04 AM, Sameera Kannangara <[email protected]> wrote: > Hi John, > > G-Reg associations are by design represents only one-way associations. > Reason behind this design is that some use cases need only one way of > association not both ways. > > But if a user wants associations to be added to reflect both ways of the > relation, > User has to add both associations separately from both asset views. > > However there is a config file that needs to be updated in order add other > association type in to the system before deployment. > > config file - <G-REG_HOME>/repository/conf/governance.xml. > > There is a section, > > <Association type="restservice"> > <security>policy</security> > <ownedBy>restservice,soapservice,wsdl</ownedBy> > <usedBy>restservice,soapservice,wsdl</usedBy> > > <dependancies>restservice,soapservice,wsdl,endpoint</dependancies> > </Association> > > You need to add a new association type to "restservice" extension type by > adding > > <owns>restservice,soapservice,wsdl</owns> > > in to association element. > After adding new line config element will look like following. > > <Association type="restservice"> > <security>policy</security> > <ownedBy>restservice,soapservice,wsdl</ownedBy> > <usedBy>restservice,soapservice,wsdl</usedBy> > > <dependancies>restservice,soapservice,wsdl,endpoint</dependancies> > *<owns>restservice,soapservice,wsdl</owns>* > </Association> > > With this config you can restart the G-reg server, and associate API2 with > API1 using "owns" association type. > This way you can represent 2 way association. > > Thank you, > SameeraK. > > > > On Wed, Nov 4, 2015 at 10:22 PM, John Hawkins <[email protected]> wrote: > >> Hi Folks, >> >> I just downloaded and ran G-REG 5.1 - nice UI !! >> >> I then created two REST API's (API1 and API2) >> I associated API1 with API2 ( API1 is 'owned by' API2) >> I then drilled down from API1 to the impact analysis which showed the >> dependency that correctly says API1 is owned by API2. >> >> However, when I drill down from API2 to the dependency analysis it >> doesn't show that API2 owns API1. >> >> To my mind it should, shouldn't it ? After all owner and ownee is a >> two-way relation? >> >> thanks, >> John. >> >> John Hawkins >> Director: Solutions Architecture >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Sameera Kannangara* > Software Engineer > Platform TG; WSO2 Inc. http://wso2.com > Contact: > phone: +94719541577 > Lean . Enterprise . Middleware >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
