Hello, During my latest tests with JRE 8 and LSC 2.1.3, i used to work with java.util.Vector for that type of problem.
Regards, Le 17/11/15 16:27, Raphaël Ouazana-Sustowski <[email protected]> a écrit : > > Hi, > > Le 2015-11-17 15:40, Ludovic Pouzenc a écrit : > > Hi, > > > > I'm a LSC user, and I fall into those things some times ago, I will > > try to write some Unit Tests and submit a bug on this. > > > > In my point of view, there is some problems when LSC converts > > script-based objects back into Java objects. In many cases, conversion > > fails and just uses toString() method as fallback. This problem > > depends on data type in the script, the JRE used (Oracle / not Oracle) > > and JRE version. This could lead to transform a multi-valued item into > > a string with some delimiter, or worse : use the string > > "java.Object@0x1984354" instead of the effective values. > > > > For now, I totally skipped the use of scripts to modify things if > > there is multi-valued fields. > > I can confirm there some issues depending on JRE, JS lib, etc. used. > For now the recommended way is to return multi-valued fields as > java.util.List. As far as I know, it never fails like this. > > Regards, > Raphaël Ouazana. > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users > -- Frederic Poisson
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
