[gatein-dev] Picket Link and Org Service TCK alignment

Hi, recently we worked on making the eXo Core OrganizationService TCK implemented for the picket link implementation. (I think it was not implemented because the TCK came after the PL implementation and then nobody was aware that it was kind of existing, anyway better late than never…) We came through a few conflicting behavior between what the TCK defines and the original PL implementation testsuite: 1/ testRemoveGroup(org.exoplatform.services.tck.organization.TestGroupHandler) conflict between TCK and PL test when removing a group having at least 1 child + TCK assumes an exception is thrown + PL assumes this group will be removed and its children will be removed too 2/ testFindUserProfileByName(org.exoplatform.services.tck.organization.TestUserProfileHandler): Expected: <null> but was: org.exoplatform.services.organization.impl.UserProfileImpl@40773f4b conflict between TCK and PL test when a non existing user profile of existing user is searched via find: + TCK suppose null is returned + PL suppose an empty profile is returned 3/ - testFindUsersByQuery(org.exoplatform.services.tck.organization.TestUserHandler): expected:<1> but was:<0> - testFindUsers(org.exoplatform.services.tck.organization.TestUserHandler): expected:<1> but was:<0> In method: UserHandler#findUsersByQuery(Query query) TCK suppose that case sensitivity does not matter in a search user but PicketLink implementation is case sensitive somehow we need to make this consistent. Our take is that we should align Picket Link with the TCK. Comments are open. cheers Julien