Hi, One possible scenario is to delete endpoints when we delete services and WSDL after validating they are no longer be used. But this is will arise another issue if that endpoint is to be used again in the future as we cannot assume to delete endpoints once the service and WSDL is deleted. According to my understanding what has been reported is the correct behavior as endpoint's state will not when we remove service representation from G-Reg. We need to understand that we are maintaining meta data. So shall we keep the behavior as this ?
On Mon, Nov 5, 2012 at 5:35 PM, Shelan Perera <[email protected]> wrote: > Hi, > > So what is the best way to handle it? Are we going to fix it or leave as > it is? > > Thanks > > > On Fri, Nov 2, 2012 at 10:52 PM, Senaka Fernando <[email protected]> wrote: > >> Hi Chethiya, >> >> I read through the JIRA issue. It seems to be a constructed edge-case >> scenario. There are pros and cons for both #1 and #2. Also, Endpoint and >> WSDL are not coupled. At least in our ESB, we have adopted such an approach. >> >> Thanks, >> Senaka. >> >> On Fri, Nov 2, 2012 at 2:29 PM, Chethiya Abeysinghe <[email protected]>wrote: >> >>> Hi all, >>> >>> Trying to find a resolution for the jira [1]. There are two options we >>> see in here. Please comment to figure out what's the expected behaviour. >>> >>> 1. Delete endpoints when deleting the respective WSDL of it. >>> >>> If the user wants to delete a WSDL file, that implies no point of >>> keeping endpoints. i.e. If user wants to keep an Endpoint, user will not >>> delete respective WSDL file. We assume an endpoint can't be shared between >>> multiple WSDLs. >>> >>> 2. Keep it the way it is now. That is, if a WSDL is deleted, respective >>> Endpoints are persisted with their environments status too (Dev, Test, >>> Stag, Prod, etc) >>> >>> [1] - https://wso2.org/jira/browse/REGISTRY-1350 >>> >>> Thanks >>> -- >>> Chethiya Abeysinghe >>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>> >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > *Shelan Perera* > > Software Engineer > ** > *WSO2, Inc. : wso2.com* > lean.enterprise.middleware. > > *Home Page* : shelan.org > *Blog* : blog.shelan.org > *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 > *Twitter* :https://twitter.com/#!/shelan > > *Mobile* : +94 772 604 402 > > > -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* : shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
