Hi John, On Wed, Jul 8, 2015 at 4:10 PM, John Hawkins <jo...@wso2.com> wrote:
> I'm following our ESB lab and in lab 14 (embedded registry) it tells me to > 1) create a new registry resource project > 2) create a new address endpoint > 3) make it a dynamic endpoint > 4) select the registry project I just created > 5) target to the governance registry/endpoints path > > However - when i follow those steps, there is no "endpoints" path. So I'm > wondering how to get that endpoints path. You seem to say that it's created > automatically - but how does that work in this case? > I would split your step 5 into two steps. 5.1 - Target to the governance registry and click OK(See attached "selectParent.png"). Still there is no "endpoints" collection under governance registry and there will be only event, permission, repository and trunk collections. Once you select the governance registry and click OK, content of "Registry Path" text box will be "gov:" 5.2 Then add "/endpoints" string part at the end of "gov:" manually and click finish. When you click finish, the content of "Registry Path" text box should be "gov:/endpoints". Please note that still there is no collection called "endpoints" in the governance registry. As Kishanthan mentioned in his previous comment, while the deployment of this endpoint(registry resource), a collection called "endpoints" will be created inside the governance registry and this endpoint will be deployed to "gov:/endpoints" path. (Additionally, if you set "gov:/foo/bar" as the registry path from Developer Studio, while the deployment "foo" & "bar" collections will be created) Thanks, Viraj. > > many thanks, > John. > > John Hawkins > Director: Solutions Architecture > > > On Wed, Jul 8, 2015 at 10:42 AM, Kishanthan Thangarajah < > kishant...@wso2.com> wrote: > >> Hi John, >> >> Are you trying out the registry resource project from dev-studio? If >> there are endpoints added under a specific registry path, then it should be >> created automatically at ESB when you deploy registry resource project from >> dev-studio. >> >> But by default - event, permission, repository and trunk collections are >> found under the governance collection. And any newly added collections from >> dev-studio will be added to ESB registry space by deploying the registry >> resource project. >> >> Let me also add some dev-studio team members to this thread to get some >> better responses, if the above does not provide information on what you >> seek. >> >> Thanks, >> >> On Wed, Jul 8, 2015 at 2:42 PM, John Hawkins <jo...@wso2.com> wrote: >> >>> Hi Folks, >>> any thoughts on this - is it a bug or expected behaviour ? >>> >>> many thanks, >>> >>> John, >>> >>> John Hawkins >>> Director: Solutions Architecture >>> >>> >>> On Mon, Jul 6, 2015 at 10:59 AM, John Hawkins <jo...@wso2.com> wrote: >>> >>>> Hi Folks, >>>> >>>> Using the ESB v4.8.1; I've just created a new governance registry using >>>> dev studio v3.7.1 and I see that it's created the collections: event, >>>> permission, repository and trunk collections under the governance context. >>>> But, it hasn't created the endpoint collection though. Should it have done? >>>> And, if I have to create it manually, are there any instructions on what >>>> has to go under the governance/endpoints/ collection? >>>> >>>> many thanks, >>>> John. >>>> >>>> John Hawkins >>>> Director: Solutions Architecture >>>> >>>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Kishanthan Thangarajah* >> Associate Technical Lead, >> Platform Technologies Team, >> WSO2, Inc. >> lean.enterprise.middleware >> >> Mobile - +94773426635 >> Blog - *http://kishanthan.wordpress.com >> <http://kishanthan.wordpress.com>* >> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* >> > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
