On Sat, Mar 24, 2012 at 11:12 PM, Senaka Fernando <[email protected]> wrote:

> Hi Amila,
>
> That is to provide additional documentation related to a service. It was
> decided to give people up to three entries by default, and if they want
> they always can change it. There is no concept of dynamic rows for types
> other than option-text, a problem that RXT 2.0 will address with its
> Jaggery-based UI.
>

Hi Amila,

Adding more, if you need to add a dynamic rows based solution to add
documents, I believe the ideal solution is to have another artifact type to
define documents(using configurable governance artifacts) and linking the
document artifact to the service artifact(like what we are doing for
WSDLs). I believe this method can be used with the existing RXT
implementation.

Thanks,
Janaka



> Thanks,
> Senaka.
>
> On Sat, Mar 24, 2012 at 4:08 PM, Amila Suriarachchi <[email protected]>wrote:
>
>> hi,
>>
>> What is the reason it has three static rows for that as well?
>>
>> thanks,
>> Amila.
>>
>>
>> *Amila Suriarachchi*
>>
>> Software Architect
>> WSO2 Inc. ; http://wso2.com
>> lean . enterprise . middleware
>>
>> phone : +94 71 3082805
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Janaka Ranabahu
Software Engineer
WSO2 Inc.

Mobile +94 718370861
Email : [email protected]
Blog : janakaranabahu.blogspot.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to