[prev in list] [next in list] [prev in thread] [next in thread] 

List:       synapse-dev
Subject:    Re: Spring mediator having a different namespace??
From:       Charith Wickramarachchi <charith.dhanushka () gmail ! com>
Date:       2010-08-22 22:54:40
Message-ID: AANLkTik+6pqtJ5eyxFauerJrzLLPzg4tSAuYZ1UQEpZc () mail ! gmail ! com
[Download RAW message or body]

On Mon, Aug 16, 2010 at 2:05 PM, Ruwan Linton <ruwan.linton@gmail.com>wrote:

> Folks,
>
> Does anybody know why we have a different namespace for spring mediator?? I
> was thinking because it is an extension, but I realized that the script,
> throttle and xquery are also extension mediators which belongs to the same
> synapse namespace. So I guess we should unify the spring mediator to also
> use the the synapse namespace.
>
>


> WDYT?
>
>

i think it is because author may had an idea in his mind to introduce some
other artifacts for synapse based on spring so that all the spring artifacts
can be under the same namespace.example may be a Spring based Task

but since its not clear and seems like not continued. it has become a
inconsistency. So +1 for the purposed change.


> Ruwan
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>



-- 
Charith Dhanushka Wickramarachchi
http://charithwiki.blogspot.com/

[Attachment #3 (text/html)]

<br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 2:05 PM, Ruwan Linton <span \
dir="ltr">&lt;<a href="mailto:ruwan.linton@gmail.com">ruwan.linton@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> Folks,<br><br>Does anybody know why we have a \
different namespace for spring mediator?? I was thinking because it is an extension, \
but I realized that the script, throttle and xquery are also extension mediators \
which belongs to the same synapse namespace. So I guess we should unify the spring \
mediator to also use the the synapse namespace.<br>

<br></blockquote><div><br></div><div>    </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;">WDYT?<br><br></blockquote><div><br></div><div><br></div><div>i \
think it is because author may had an idea in his mind to introduce some other \
artifacts for synapse based on spring so that all the spring artifacts can be under \
the same namespace.example may be a Spring based Task</div> <div><br></div><div>but \
since its not clear and seems like not continued. it has become a inconsistency. So \
+1 for the purposed change.</div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Ruwan<br \
clear="all"><br>-- <br>Ruwan Linton<br>Software Architect &amp; Product Manager, WSO2 \
ESB; <a href="http://wso2.org/esb" target="_blank">http://wso2.org/esb</a><br>WSO2 \
Inc.; <a href="http://wso2.org" target="_blank">http://wso2.org</a><br>

<br>Lean . Enterprise . Middleware<br><br>phone: +1 408 754 7388 ext 51789<br>email: \
<a href="mailto:ruwan@wso2.com" target="_blank">ruwan@wso2.com</a>; cell: +94 77 341 \
3097<br>blog: <a href="http://blog.ruwan.org" \
target="_blank">http://blog.ruwan.org</a><br>

linkedin: <a href="http://www.linkedin.com/in/ruwanlinton" \
target="_blank">http://www.linkedin.com/in/ruwanlinton</a><br>google: <a \
href="http://www.google.com/profiles/ruwan.linton" \
target="_blank">http://www.google.com/profiles/ruwan.linton</a><br>

tweet: <a href="http://twitter.com/ruwanlinton" \
target="_blank">http://twitter.com/ruwanlinton</a><br> </blockquote></div><br><br \
clear="all"><br>-- <br>Charith Dhanushka Wickramarachchi<br><a \
href="http://charithwiki.blogspot.com/">http://charithwiki.blogspot.com/</a><br><br>



[prev in list] [next in list] [prev in thread] [next in thread]