synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Senaka Fernando (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SYNAPSE-426) Class mediator property setters should not have constrained ordering
Date Mon, 27 Oct 2008 14:38:44 GMT

     [ https://issues.apache.org/jira/browse/SYNAPSE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Senaka Fernando updated SYNAPSE-426:
------------------------------------

    Attachment: SYNAPSE-426.patch.txt

Replaced old patch with a new one due to changes in package names of patched source file.

> Class mediator property setters should not have constrained ordering 
> ---------------------------------------------------------------------
>
>                 Key: SYNAPSE-426
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-426
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>            Reporter: Senaka Fernando
>         Attachments: SYNAPSE-426.patch.txt
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> When we create a class that implements a Class Mediator in Synapse, we need to have setter
methods corresponding to the Class Mediator properties we set. Also there can be situations
where class mediator properties can accept both XML and non-XML data. This can be addressed
by having overloaded methods in the implementing class. However, according to the current
implementation the overloaded methods need to have a defined constrained ordering. However,
typically an implementor should have the freedom to select his/her preferred ordering.
> That means,
> class A implements mediator {
>    setB(OMElemet c)
>   {
>   }
>   setB(String c)
>   {
>   }
>    mediate() { }
> }
> as well as
> class A implements mediator {
>    setB(String c)
>   {
>   }
>    mediate() { }
>    setB(OMElemet c)
>   {
>   }
> }
> should be valid. Unfortunately, according to the current implementation they are not.
An exception is thrown while starting Synapse as a result.
> The attached patch solves this issue.
> Regards,
> Senaka

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message