Hi Senaka, Thanks for the response. Yes. It makes sense to display it in one tab rather than in two, as those are dependant, and the consumer can look into the details of the service in one place. After further discussion with the team, if this fits good in a consumer point of view, I'll proceed with this way.
Shazni Nazeer Senior Software Engineer Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Tue, Nov 25, 2014 at 3:29 PM, Senaka Fernando <[email protected]> wrote: > Hi Shazni, > > Has to be dependent. And also needs to sync with this new Metadata model > that we are talking about. > > Thanks, > Senaka. > > On Tue, Nov 25, 2014 at 4:36 AM, Shazni Nazeer <[email protected]> wrote: > >> Hi All, >> >> In the extension that I was working I now have made the necessary changes >> to the publisher end so that we could add services and wsdl from the >> publisher and view those in a list. When clicked on the relevant service or >> wsdl it shows up an overview page with details. The wsdl we add through the >> publisher also creates the relevant service. The service support >> 'ServiceLifecycle' by default, which is not the case with the publisher end >> in ES feature, which attaches the store life cycle. We are yet to finalize >> the life-cycle to be associated and how to proceed with that. >> >> Going on to the the store end, how would it be best viewed? Should we be >> having two different tabs for service and wsdl? Or will it be concise >> showing the wsdl in the service view it self as both are dependant? I'm >> planning to work on the store end and your input on this will be >> appreciated. >> >> thanks >> >> Shazni Nazeer >> >> Senior Software Engineer >> >> Mob : +94 777737331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> >> On Wed, Aug 6, 2014 at 4:55 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi Subash, >>> >>> Well I don't think that's just it. We had something running for the 2013 >>> WSO2Con, and Chandana was looking into moving that into the Store as well. >>> Not sure whether he did that. >>> >>> Apart from this, in terms of plans, what I had in mind is what we >>> discussed offline. >>> >>> Thanks, >>> Senaka. >>> >>> >>> On Wed, Aug 6, 2014 at 1:03 AM, Subash Chaturanga <[email protected]> >>> wrote: >>> >>>> Hi Senaka et al, >>>> >>>> Had a quick look at what Shazni did compared to Chandana's one. In >>>> provider's view we seems in line with what was there initially with the >>>> reduced service RXT. @Senaka, anyway with the unified gov model, we >>>> probably end up a more reduced version for service and with some updates. >>>> Let's keep it till then. >>>> >>>> For Doc links, even in service store we have this same old 3 doc link >>>> field with type/url/comment. @Ruchira is it possible to have something for >>>> documentation like whats there in AM ? >>>> >>>> @Senaka >>>> Have we thought about the store front for services ? Currently (even >>>> with Chandana's impl) you can't do anything in store other than >>>> tag/rate/comment. >>>> What were the plans you had on service store ? >>>> >>>> >>>> >>>> >>>> On Tue, Aug 5, 2014 at 11:54 AM, Shazni Nazeer <[email protected]> wrote: >>>> >>>>> Hi Chandana, >>>>> >>>>> Thanks for the information. >>>>> >>>>> Yes. That's what I'm trying to achieve at the moment. With the new ES, >>>>> first we need to be able to add a service through a wsdl url. In the >>>>> earlier work, was that happening in the same service UI? If so what would >>>>> be the case for the other fields such as the name-space? Was it getting >>>>> hidden dynamically or is it simply getting ignored when the wsdl url is >>>>> provided? >>>>> >>>>> Regarding addition of wsdl addition by zip files, there can still be >>>>> issues as you mentioned. Depending on that, we might not consider that and >>>>> wsdl addition using url for the first milestone. >>>>> >>>>> Appreciate your feedback. >>>>> >>>>> regards >>>>> >>>>> Shazni Nazeer >>>>> >>>>> Senior Software Engineer >>>>> >>>>> Mob : +94 777737331 >>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>>> Blog : http://shazninazeer.blogspot.com >>>>> >>>>> >>>>> On Sat, Aug 2, 2014 at 7:34 PM, Chandana Napagoda <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Shazni, >>>>>> >>>>>> Service creation using WSDL URLs was already implemented in an older >>>>>> version of ES. But there was a problem with service creation using a zip >>>>>> file of WSDLs [1]. Will send you a separate mail with exiting code blocks >>>>>> for service creation using a WSDL URL. >>>>>> >>>>>> [1]. [Architecture] Jaggery unzips all folders? >>>>>> >>>>>> Regards, >>>>>> Chandana >>>>>> >>>>>> >>>>>> On Sat, Aug 2, 2014 at 10:00 AM, Chandana Napagoda <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> Hi Shazni, >>>>>>> >>>>>>> Service creation using WSDL URLs was already implemented in an older >>>>>>> version of ES. But there was a problem with service creation using a zip >>>>>>> file of WSDLs [1]. Will send you a separate mail with exiting code >>>>>>> blocks >>>>>>> for service creation using a WSDL URL. >>>>>>> >>>>>>> [1]. [Architecture] Jaggery unzips all folders? >>>>>>> >>>>>>> Regards, >>>>>>> Chandana >>>>>>> >>>>>>> >>>>>>> On Fri, Aug 1, 2014 at 2:35 PM, Shazni Nazeer <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Senaka, >>>>>>>> >>>>>>>> First of all thanks for the information. >>>>>>>> >>>>>>>> I already had a call with Chandana together with SameeraM regarding >>>>>>>> this. It was understood that the work Chandana did (which was working >>>>>>>> earlier in an older version of enterprise-store), wouldn't directly >>>>>>>> imply >>>>>>>> with the latest modifications done in the enterprise store. @Chandana, >>>>>>>> please confirm. With the latest changes in the enterprise store (which >>>>>>>> is >>>>>>>> more greg focused) Chandana's work could be achieved with comparatively >>>>>>>> minimal work with the extension points provided in the enterprise >>>>>>>> store. >>>>>>>> @SameeraM - please confirm. >>>>>>>> >>>>>>>> +1 for an offline discussion and figure out what needs to be done. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Shazni Nazeer >>>>>>>> >>>>>>>> Senior Software Engineer >>>>>>>> >>>>>>>> Mob : +94 777737331 >>>>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>>>>>> Blog : http://shazninazeer.blogspot.com >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Aug 1, 2014 at 8:44 PM, Senaka Fernando <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Please find my responses in-line. >>>>>>>>> >>>>>>>>> On Fri, Aug 1, 2014 at 10:13 AM, Shazni Nazeer <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Senaka etal, >>>>>>>>>> >>>>>>>>>> I'm in the process of adding the service UI to the service store >>>>>>>>>> feature that would be included Governance Registry. This involves >>>>>>>>>> extending >>>>>>>>>> already available service UI in the store feature to make it >>>>>>>>>> compatible >>>>>>>>>> with the Governance Registries model, in adding a service from the >>>>>>>>>> extension point given by the store feature. I've currently performed >>>>>>>>>> following. (Note: The changes are being changed/tested currently in >>>>>>>>>> the >>>>>>>>>> enterprise-store as the store feature in the GREG doesn't allow yet >>>>>>>>>> to >>>>>>>>>> login to the publisher and store. Once it's done, the service >>>>>>>>>> extensions >>>>>>>>>> need to be placed inside the publisher app inside the GREG. >>>>>>>>>> >>>>>>>>>> As it was decided to have minimal information to be available in >>>>>>>>>> the service UI, had to hide/modify the default view, which contains >>>>>>>>>> all the >>>>>>>>>> details that we find in the management console of the Governance >>>>>>>>>> Registry. >>>>>>>>>> >>>>>>>>>> The default service UI from store doesn't add the services in the >>>>>>>>>> correct path when the namespace of the service is provided. That's >>>>>>>>>> corrected in the extension point. >>>>>>>>>> >>>>>>>>>> Apart from these I've few more concerns. >>>>>>>>>> >>>>>>>>>> 1. Once the service is published it would show up in the service >>>>>>>>>> store in a new tab. As our G-Reg's service rxt doesn't have a >>>>>>>>>> thumbnail >>>>>>>>>> field, the service store show up services without a thumbnail. Is it >>>>>>>>>> o.k to >>>>>>>>>> leave it like this for the time being? Or else what can we do on >>>>>>>>>> this. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Well, as Ruchira pointed out as well, I wouldn't worry too much >>>>>>>>> about this right now. We can keep the default icon as it is. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2. As we know services can be added from a wsdl url. The current >>>>>>>>>> level of work doesn't allow adding service's from a wsdl. Do we need >>>>>>>>>> to >>>>>>>>>> have the ability to add services from wsdl's in service UI? Or >>>>>>>>>> should we >>>>>>>>>> create a separate rxt for wsdl's as in the G-Reg? >>>>>>>>>> >>>>>>>>> >>>>>>>>> I was under the impression that Chandana already started doing >>>>>>>>> this, and perhaps completed some of it. If you are unaware of this, >>>>>>>>> its >>>>>>>>> best to get him involved in a call first and discuss what was done >>>>>>>>> and what >>>>>>>>> you can use. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> @Senaka; Do you have some time to have a call on this to discuss >>>>>>>>>> further? If so what would the convenient time for you? >>>>>>>>>> >>>>>>>>> >>>>>>>>> Based on above, if you already have an understanding and expanding >>>>>>>>> what Chandana was working on, then +1 for setting up a call next >>>>>>>>> week. Lets >>>>>>>>> discuss offline and find a that works for everybody. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Senaka. >>>>>>>>> >>>>>>>>>> Shazni Nazeer >>>>>>>>>> >>>>>>>>>> Senior Software Engineer >>>>>>>>>> >>>>>>>>>> Mob : +94 777737331 >>>>>>>>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>>>>>>>> Blog : http://shazninazeer.blogspot.com >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> >>>>>>>>> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >>>>>>>>> Software Architect; WSO2 Inc.; http://wso2.com >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> * Member; Apache Software Foundation; http://apache.org >>>>>>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: >>>>>>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>>>>>>>> >>>>>>>>> >>>>>>>>> *M: +44 782 741 1966 <%2B44%20782%20741%201966> Linked-In: >>>>>>>>> http://linkedin.com/in/senakafernando >>>>>>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . >>>>>>>>> Middleware >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Chandana Napagoda* >>>>>>> Senior Software Engineer >>>>>>> WSO2 Inc. - http://wso2.org >>>>>>> >>>>>>> *Email : [email protected] <[email protected]> **Mobile : >>>>>>> +94718169299 <%2B94718169299>* >>>>>>> >>>>>>> *Blog : http://cnapagoda.blogspot.com >>>>>>> <http://cnapagoda.blogspot.com>* >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Chandana Napagoda* >>>>>> Senior Software Engineer >>>>>> WSO2 Inc. - http://wso2.org >>>>>> >>>>>> *Email : [email protected] <[email protected]> **Mobile : >>>>>> +94718169299 <%2B94718169299>* >>>>>> >>>>>> *Blog : http://cnapagoda.blogspot.com >>>>>> <http://cnapagoda.blogspot.com>* >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks >>>> /subash >>>> >>>> *Subash Chaturanga* >>>> Senior Software Engineer & Lead WSO2 Governance Registry >>>> Platform TG; WSO2 Inc. http://wso2.com >>>> Contact: >>>> email: [email protected] >>>> blog: http://subashsdm.blogspot.com/ >>>> twitter: @subash89 >>>> phone: +9477 2225922 >>>> Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> >>> >>> *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* >>> Software Architect; WSO2 Inc.; http://wso2.com >>> >>> >>> >>> * Member; Apache Software Foundation; http://apache.org >>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>> >>> >>> *M: +44 782 741 1966 <%2B44%20782%20741%201966> Linked-In: >>> http://linkedin.com/in/senakafernando >>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >>> >> >> > > > -- > > > *[image: http://wso2.com] <http://wso2.com>Senaka Fernando* > Solutions Architect; WSO2 Inc.; http://wso2.com > > > > *Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; > > > *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In: > http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
