Hi,
See https://issues.apache.org/jira/browse/CXF-6499
I've added a "usePathParamsToCompareOperations" property, could not
think of a better name :-), enabled by default, try to set it to false
and you should see all 3 operations sharing the same parent resource.
I thought nay be it should be di
On 15/07/2015 10:26, Sergey Beryozkin wrote:
Hi,
On 15/07/15 11:05, Francesco Chicchiriccò wrote:
On 14/07/2015 16:34, Sergey Beryozkin wrote:
Hi Francesco,
The generator checks which operations are the same path operations,
I've checked the code and it also compares a number of path and matri
Hi,
On 15/07/15 11:05, Francesco Chicchiriccò wrote:
On 14/07/2015 16:34, Sergey Beryozkin wrote:
Hi Francesco,
The generator checks which operations are the same path operations,
I've checked the code and it also compares a number of path and matrix
parameters, so PUT was also sharing the same
On 14/07/2015 16:34, Sergey Beryozkin wrote:
Hi Francesco,
The generator checks which operations are the same path operations,
I've checked the code and it also compares a number of path and matrix
parameters, so PUT was also sharing the same root resource, before it
had a keyId method parame
Hi Francesco,
The generator checks which operations are the same path operations, I've
checked the code and it also compares a number of path and matrix
parameters, so PUT was also sharing the same root resource, before it
had a keyId method parameter.
If PUT where inside a keyId resource th
Hi all,
any obvious reason why two distinct resources with path "/{key}" [1] are
generated from [2]?
TIA
Regards.
[1] https://paste.apache.org/lQbF
[2]
https://github.com/apache/syncope/blob/master/common/rest-api/src/main/java/org/apache/syncope/common/rest/api/service/AnyTypeService.java
