Hi Subash, Sorry. I got the high-level picture based on what Evanthika said. I'm asking the actual low-level steps of what's going on. Did you check that out? If so, can you answer my questions?
Thanks, Senaka. On Tue, May 8, 2012 at 5:20 PM, Subash Chaturanga <[email protected]> wrote: > > > On Tue, May 8, 2012 at 5:16 PM, Senaka Fernando <[email protected]> wrote: > >> Hi all, >> >> I didn't get the question here. What feature in ESB causes this to >> happen? Like how you end up getting the dead page? can you explain the flow? >> >> > Please go through [1], and there you can find the steps to reproduce. > > >> Thanks, >> Senaka. >> >> >> On Tue, May 8, 2012 at 4:57 PM, Ajith Vitharana <[email protected]> wrote: >> >>> >>> >>> On Tue, May 8, 2012 at 4:43 PM, Subash Chaturanga <[email protected]>wrote: >>> >>>> Hi Senaka, >>>> >>>> This is regarding CARBON-12790 [1] (ESB - Dead page returned when >>>> saving edited WSDLs/Schemas) . >>>> >>>> In ESB, it has the capability to add wsdls and schemas as registry >>>> resources, as it has some registry related features installed. >>>> But wsdls and schemas are governance artifacts. Suppose someone try to >>>> edit the added schema in ESB and save it. What happens is it redirects to >>>> the schema list. (redirects to schema.jsp with req params). >>>> >>>> But as ESB doesn't have governance meta data feature installed, it >>>> redirects to a dead page. To overcome this, there are two options AFAIS. >>>> >>>> 1. When redirection happens in registry.js, we should check whether >>>> governance meta data feature has installed already(which is also an >>>> expensive call), >>>> then redirect to governance related jsps or else keep it in the same >>>> page (do nothing). >>>> 2. ESB needs to be shipped with governance meta data feature(which is >>>> surely an overhead in binary size and etc as this is not a big use case for >>>> esb ), >>>> or ask user to install this feature manually. >>>> >>>> I don't know how frequently this use case takes places in ESB(editing >>>> governance artifacts), depends on that we can choose which to do. >>>> Any thoughts ? >>>> >>> >>> Hi Subash, >>> >>> We shouldn't ship governance meta data feature with ESB. If we have an >>> use case to store WSDLs and XSDs in ESB then we can install governance meta >>> data feature through the p2-repo. >>> >>> Thanks >>> Ajith >>> >>>> >>>> [1] - https://wso2.org/jira/browse/CARBON-12790 >>>> >>>> Thanks >>>> -- >>>> >>>> Subash Chaturanga >>>> Software Engineer >>>> WSO2 Inc. http://wso2.com >>>> >>>> email - [email protected] >>>> phone - 077 2225922 >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Ajith Vitharana. >>> WSO2 Inc. - http://wso2.org >>> Email : [email protected] >>> Mobile : +94714631794 >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate 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 >> >> > > > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - [email protected] > phone - 077 2225922 > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate 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
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
