...
When you want to get an exact copy of the Services from one registry instance to another, use the check-in client to get a check-out of the collection structure of the registry instance, and do a check-in operation to the collection structure of the other registry instance.
| Note |
|---|
You can use the check-in client tool only for registry/repository use cases. Therefore, you cannot use it for governance scenarios. |
However, when you do a check-in from the WSO2 G-Reg checkin/checkout client to one registry instance, it overrides the resources and collections that are under the path, which is specified in that instance. Also, the G-Reg check-in client does not have a merge option to use with the check-in operation. Hence, if the registry instance has some Services in the same path before doing the check-in operation, those services are replaced by the Services added by the check-in operation.
...
However, WSO2 G-Reg will support the registry check-in client merge option in future. For more information on this, see REGISTRY-665 JIRA issue.
| Info |
|---|
The check-in client tool does not support the '&' and 'space' characters, and thereby, you will get errors when resources have these special characters. Therefore, the asset names, which are authorized need to be handled by the check-in client tool as well. |
Extending WSO2 G-Reg
How to add content using HTML to a text input field of an asset in the G-Reg Publisher?
By default, WSO2 G-Reg does not support HTML tags inside text input fields. Text input fields are defined within RXT text areas, and RXTs do not support HTML content. However, you can do this by enabling Rich Text Format (RTF) for input text fields with HTML, and the WSO2 G-Reg extension model. For more information, see Adding HTML Content within an RXT Input Text FieldArea.