[prev in list] [next in list] [prev in thread] [next in thread]
List: esb-java-dev
Subject: Re: [Dev] Why dot-segments ".." and "." aren't allowed in RXT paths
From: Ruchira Wageesha <ruchira () wso2 ! com>
Date: 2012-09-30 8:42:08
Message-ID: CA+RSUiKSrKFepMR8BZGEKc8PgUVCWSZVRvobURGcN8YgO2ar0A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <eranda@wso2.com>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: ruchira@wso2.com, blog: ruchirawageesha.blogspot.com, mobile:
+94 77 5493444*
[Attachment #5 (text/html)]
Hi Eranda,<div><br></div><div>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.</div> \
<div><br></div><div>Only ways to do this are, </div><div><ul><li>either writing a \
handler</li><li>introducing a new field to specify the interface as well(which is \
redundant as we should be able to derive it from the provider)</li> <li>if it allows \
../../ stuff, then also it can be created as rxt developer know the resource \
structure in advance.</li></ul><div>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.</div> \
</div><div><br></div><div>/Ruchira</div><div><br><div class="gmail_quote">On Sun, Sep \
30, 2012 at 10:08 AM, Eranda Sooriyabandara <span dir="ltr"><<a \
href="mailto:eranda@wso2.com" target="_blank">eranda@wso2.com</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">Hi Ruchira,<div>There is a work around for \
this.</div><div>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. </div>
<div> </div><div><div><relationships></div><div><span \
style="white-space:pre-wrap"> </span><association type="depends" \
source="@{associates_endpoint}"/></div><div><span \
style="white-space:pre-wrap"> </span></relationships> </div>
</div><div><br></div><div><div><table \
name="Associates"></div><div><span \
style="white-space:pre-wrap"> </span><field type="text" \
path="true"></div><div><span \
style="white-space:pre-wrap"> </span><name>Endpoint</name></div>
<div><span style="white-space:pre-wrap"> </span></field></div><div><span \
style="white-space:pre-wrap"> </span></table></div></div><div><br></div><div>thanks</div><span \
class="HOEnZb"><font color="#888888"><div> Eranda <br>
<br><div class="gmail_quote"><br></div><div><div><div><font color="#333333" \
face="garamond, serif" size="1"><i><br></i></font></div></div></div><br> </div>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><i><font \
face="georgia, serif">Ruchira Wageesha<br>Senior Software Engineer & Member, \
Management Committee, Development Technologies</font></i><div> <i><font \
face="georgia, serif">WSO2 Inc. - lean . enterprise . middleware | <a \
href="http://wso2.com" target="_blank">wso2.com</a></font></i></div><div><i><font \
face="georgia, serif"><br>email: <a href="mailto:ruchira@wso2.com" \
target="_blank">ruchira@wso2.com</a>, blog: <a \
href="http://ruchirawageesha.blogspot.com" \
target="_blank">ruchirawageesha.blogspot.com</a>, mobile: +94 77 \
5493444</font></i><br> </div><br>
</div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic