Hi guys,
I think I found the solution for this. We need to remove the option-text
field its redundant now. We can replace it easily by our new unbounded
option.
Both of the following configurations are rendered in the UI in the same way.
Option-text configuration
<table name="Endpoints">
<subheading>
<heading>Environments</heading>
<heading>URL</heading>
</subheading>
<field type="option-text" maxoccurs="unbounded">
<name label="Endpoint">Endpoint</name>
<values>
<value>None</value>
<value>Unknown</value>
<value>Dev</value>
<value>Test</value>
<value>Stag</value>
<value>Prod</value>
</values>
</field>
</table>
New configuration
<table name="Interface" maxoccurs="unbounded">
<field type="text">
<name label="WSDL/WADL URL">WSDL URL</name>
</field>
<field type="options">
<name label="Transport Protocols">Transport Protocols</name>
<values>
<value>None</value>
<value>Unknown</value>
<value>Dev</value>
<value>Test</value>
<value>Stag</value>
<value>Prod</value>
</values>
</field>
</table>
WDYT?
thanks
Eranda
On Wed, Aug 7, 2013 at 10:28 PM, Eranda Sooriyabandara <[email protected]>wrote:
> Hi All,
> Please find the screenshot of the generated endpoints custom view.
>
> thanks
> Eranda
>
>
> On Wed, Aug 7, 2013 at 10:14 PM, Eranda Sooriyabandara <[email protected]>wrote:
>
>> Hi Chandana,
>> As we discussed offline this is the expected behavior but this is the
>> content of the resource of a service where some endpoints are added when
>> adding its WSDL. See how wsdl endpoints added to the service content.
>>
>> <metadata xmlns="http://www.wso2.org/governance/metadata";>
>> <overview>
>> <scopes>
>> http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01/DefaultScope
>> </scopes>
>> <name>HelloService</name>
>> <types>{http://www.wso2.org/types}HelloServicePortType</types>
>> <namespace>http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
>> </namespace>
>> <axis2ns58:version xmlns:axis2ns58="
>> http://www.wso2.org/governance/metadata";>1.0.0-SNAPSHOT</axis2ns58:
>> version>
>> </overview>
>> <endpoints>
>> <axis2ns117:entry xmlns:axis2ns117="
>> http://www.wso2.org/governance/metadata";>
>> :https://10.100.0.126:9444/services/HelloService
>> </axis2ns117:entry>
>> <axis2ns118:entry xmlns:axis2ns118="
>> http://www.wso2.org/governance/metadata";>:local:///services/HelloService
>> </axis2ns118:entry>
>> <axis2ns119:entry xmlns:axis2ns119="
>> http://www.wso2.org/governance/metadata";>
>> :http://
>> 10.100.0.126:9764/services/HelloService.HelloServiceHttpSoap11Endpoint/
>> </axis2ns119:entry>
>> <axis2ns120:entry xmlns:axis2ns120="
>> http://www.wso2.org/governance/metadata";>
>> :https://
>> 10.100.0.126:9444/services/HelloService.HelloServiceHttpsSoap11Endpoint/
>> </axis2ns120:entry>
>> <axis2ns121:entry xmlns:axis2ns121="
>> http://www.wso2.org/governance/metadata";>
>> :http://
>> 10.100.0.126:9764/services/HelloService.HelloServiceHttpSoap12Endpoint/
>> </axis2ns121:entry>
>> <axis2ns122:entry xmlns:axis2ns122="
>> http://www.wso2.org/governance/metadata";>
>> :https://
>> 10.100.0.126:9444/services/HelloService.HelloServiceHttpsSoap12Endpoint/
>> </axis2ns122:entry>
>> <axis2ns123:entry xmlns:axis2ns123="
>> http://www.wso2.org/governance/metadata";>
>> :https://10.100.0.126:9444/services/HelloService.
>> HelloServiceHttpsEndpoint/
>> </axis2ns123:entry>
>> <axis2ns124:entry xmlns:axis2ns124="
>> http://www.wso2.org/governance/metadata";>
>> :http://10.100.0.126:9764/services/HelloService.
>> HelloServiceHttpEndpoint/
>> </axis2ns124:entry>
>> </endpoints>
>> <endpoints>
>> <entry>:http://10.100.0.126:9764/services/HelloService</entry>
>> </endpoints>
>> <endpoints>
>> <entry>:local:///services/HelloService</entry>
>> </endpoints>
>> <interface>
>> <wsdlURL>/_system/governance/trunk/wsdls
>> /org/wso2/www/types/HelloService.wsdl</wsdlURL>
>> </interface>
>> <metadataVersion>1</metadataVersion>
>> </metadata>
>>
>> thanks
>> Eranda
>>
>>
>> On Wed, Aug 7, 2013 at 9:20 PM, Eranda Sooriyabandara <[email protected]>wrote:
>>
>>> Hi Chandana,
>>> In previous releases the Service (GovernanceArtifact) content was like
>>> [1] and now its like [2]. Is this the expected model with your new design
>>> of infinite entries?
>>> It seems to be a bug for me. Please add some explanation too.
>>>
>>> thanks
>>> Eranda
>>>
>>> [1].
>>> <metadata xmlns="http://www.wso2.org/governance/metadata";>
>>> <overview>
>>> <scopes>
>>> http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01/DefaultScope
>>> </scopes>
>>> <name>HelloService</name>
>>> <types>{http://www.wso2.org/types}HelloServicePortType</types>
>>> <namespace>http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
>>> </namespace>
>>> </overview>
>>> <endpoints>
>>> <entry>:https://10.100.0.126:9444/services/HelloService</entry>
>>> <entry>:http://10.100.0.126:9764/services/HelloService</entry>
>>> <entry>:local:///services/HelloService</entry>
>>> </endpoints>
>>> <interface>
>>> <wsdlURL>http://10.100.0.126:9764/services/HelloService?wsdl</
>>> wsdlURL>
>>> </interface>
>>> <metadataVersion>1</metadataVersion>
>>> </metadata>
>>>
>>> [2].
>>> <metadata xmlns="http://www.wso2.org/governance/metadata";>
>>> <overview>
>>> <scopes>
>>> http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01/DefaultScope
>>> </scopes>
>>> <name>HelloService</name>
>>> <types>{http://www.wso2.org/types}HelloServicePortType</types>
>>> <namespace>http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
>>> </namespace>
>>> </overview>
>>> <endpoints>
>>> <entry>:https://10.100.0.126:9444/services/HelloService</entry>
>>> </endpoints>
>>> <endpoints>
>>> <entry>:http://10.100.0.126:9764/services/HelloService</entry>
>>> </endpoints>
>>> <endpoints>
>>> <entry>:local:///services/HelloService</entry>
>>> </endpoints>
>>> <interface>
>>> <wsdlURL>http://10.100.0.126:9764/services/HelloService?wsdl</
>>> wsdlURL>
>>> </interface>
>>> <metadataVersion>1</metadataVersion>
>>> </metadata>
>>>
>>>
>>> --
>>> *Eranda Sooriyabandara
>>> *Senior Software Engineer;
>>> Integration Technologies Team;
>>> WSO2 Inc.; http://wso2.com
>>> Lean . Enterprise . Middleware
>>>
>>> E-mail: eranda AT wso2.com
>>> Mobile: +94 716 472 816
>>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>>> Blog: http://emsooriyabandara.blogspot.com/
>>>
>>>
>>>
>>> *
>>> *
>>>
>>
>>
>>
>> --
>> *Eranda Sooriyabandara
>> *Senior Software Engineer;
>> Integration Technologies Team;
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> E-mail: eranda AT wso2.com
>> Mobile: +94 716 472 816
>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>> Blog: http://emsooriyabandara.blogspot.com/
>>
>>
>>
>> *
>> *
>>
>
>
>
> --
> *Eranda Sooriyabandara
> *Senior Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> E-mail: eranda AT wso2.com
> Mobile: +94 716 472 816
> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
> Blog: http://emsooriyabandara.blogspot.com/
>
>
>
> *
> *
>
--
*Eranda Sooriyabandara
*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
*
*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
