Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
I have just committed to `1_2_X` with
4adf879d3ce446e1054ddc03a929e31ae25bd248
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
Before closing this PR I'll cherry-pick and adapt to `master` + rework for
`1_2_X`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
I have just committed to `2_0_X` with
0e214e0046e3e9940cbe57dacf3f8bf56c1b5f9c
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
> Are you taking care of the rest or should I do a little cleanup ?
I am already at work, expect something soon :-)
---
If your project is set up for it, you can reply to this email and
Github user gonzalad commented on the issue:
https://github.com/apache/syncope/pull/40
@ilgrosso : yes I confirm, I forked from master (I didn't know I needed to
use another branch sorry !)
Are you taking care of the rest or should I do a little cleanup ?
If I need to do
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
@gonzalad thanks for your work, the changes now look very good!
I have some troubles when merging your PR directly (as you've forked from
the master branch, I think) + there are some minor
Github user gonzalad commented on the issue:
https://github.com/apache/syncope/pull/40
@ilgrosso : changes made, I've introduced the 2 new operators =~ and !~.
Thanks for the change in CXF fiqlParser !
2 problems in Travis CI :
* the build doesn't pass (cxf changes
Github user sberyozkin commented on the issue:
https://github.com/apache/syncope/pull/40
Hi Francesco, this looks fine.
In general, as far as the use of the CXF Search extension is concerned, it
might make it tricky to reuse a CXF ODataParser (delegates to Olingo) which
offers a
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
@gonzalad With
https://github.com/apache/cxf/commit/5156dd256f8f59d22ea2d1ca50197f1b5b3f1788
(for CXF's `3.1.x-fixes`, which is currently used by Syncope's `2_0_X`, but I
have also committed to
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
@gonzalad let me play a bit with CXF's `FiqlParser`...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user gonzalad commented on the issue:
https://github.com/apache/syncope/pull/40
Hi @ilgrosso, the problem is I don't know how to create custom FIQL
operators.
From what I've seen, we can't.
FiqlParser.operatorsMap is private & non-accessible :
Github user ilgrosso commented on the issue:
https://github.com/apache/syncope/pull/40
Hi @gonzalad thanks for your contribution!
I have noticed that you have defined an additional configuration parameter
which globally states if `EQ` and `LIKE` are to be considered as case
12 matches
Mail list logo
