Hi Eranda,

In my case, interface -> provider -> endpoint. So, when an endpoint is
created, user select only who is the provider. Then, I want to
automatically create an association from interface -> endpoint which can be
used to get all endpoints under a particular interface.

Only ways to do this are,

   - either writing a handler
   - introducing a new field to specify the interface as well(which is
   redundant as we should be able to derive it from the provider)
   - if it allows ../../ stuff, then also it can be created as rxt
   developer know the resource structure in advance.

For the moment, I decided to go by writing a handler. But, it would be
better to add that support in a future release as it is a standard usage
pattern of paths.

/Ruchira

On Sun, Sep 30, 2012 at 10:08 AM, Eranda Sooriyabandara <[email protected]>wrote:

> Hi Ruchira,
> There is a work around for this.
> You can specify a field, lets say associates_endpoint which is a text
> field in provider. When adding a endpoint we can specify to set
> associations automatically. Since you already have the providers address,
> there won't be a overhead.
>
> <relationships>
> <association type="depends"  source="@{associates_endpoint}"/>
> </relationships>
>
> <table name="Associates">
> <field type="text" path="true">
> <name>Endpoint</name>
>  </field>
> </table>
>
> thanks
> Eranda
>
>
> *
> *
>
>


-- 
*Ruchira Wageesha
Senior Software Engineer & Member, Management Committee, Development
Technologies*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: [email protected],   blog: ruchirawageesha.blogspot.com,   mobile:
+94 77 5493444*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to