[ 
https://issues.apache.org/jira/browse/SYNCOPE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291648#comment-14291648
 ] 

Sergey Beryozkin commented on SYNCOPE-630:
------------------------------------------

Hi, 
It will get it past a compilation issue, yes, if WADL is fed into a CXF wadl to 
java generator because the CXF one would check the resource method ids (might 
work with a Jersey one too but I'm not sure), but the generated interface would 
still end up with having two methods, list(@MatrixParam mp) and 
filter(@MatrixParam mp). 

Setting a generator property would only applies to overloaded methods 
supporting the same Path which is typically a non-standard situation; an 
overloaded method with most parameters is chosen for the introspection. 
Example, in a case if a(), a(b)m and a(b,c) it will be a(b,c) that will be 
selected and in our case a no-op list() method is ignored. 

Keeping a list(Long) still preserves both options; I'm not sure what is worse, 
the current  java->wadl->java generation issue or removing an option to filter 
to get the generation issue fixed :-). May be a property option is OK ? I'll 
support whatever decision you take anyway :-), 

Thanks, Sergey

> Eliminate duplicate Syncope WADL methods
> ----------------------------------------
>
>                 Key: SYNCOPE-630
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-630
>             Project: Syncope
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.1.8, 1.2.1
>            Reporter: Sergey Beryozkin
>            Priority: Minor
>             Fix For: 1.2.2, 1.3.0
>
>         Attachments: SYNCOPE-630.patch
>
>
> See A "Minor Syncope WADL issue" [dev email 
> thread|http://markmail.org/message/utoomopbte6awen4]. The auto-generated WADL 
> has duplicate resource methods for one of the resources which is actually not 
> an error per se but it makes it difficult to convert such WADL back to Java 
> with Java to wadl tools.
> One of the options is to set a new 'ignoreOverloadedMethods' WADLGenerator 
> property to true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to