> On Dec 2, 2016, at 1:51 PM, Martijn Dashorst <[email protected]> > wrote: > > But I doubt that either of these steps will solve the > ClassNotFoundException in wildfly.
This error: 15:21:14,804 ERROR [org.apache.directory.fortress.core.util.VUtil] (default task-3) static initialzier caught SecurityException=createInstance() className [org.openldap.fortress.util.time.Date] caught java.lang.ClassNotFoundException=java.lang.ClassNotFoundException: org.openldap.fortress.util.time.Date from [Module is result of this issue: https://issues.apache.org/jira/browse/FC-202 Stemming from a docker image load that uses an outdated fortress installation package that seeds configuration data containing invalid (outdated) class names that subsequently fail during instantiation. Running the run_tests script will correct this by seeding the directory with latest config data so the right set of dynamic classes are on the classpath at runtime. Yeah I know this needs to be fixed (hence the issue) but but I have a bigger concern about the wildfly usage. I have not tested with the fortress-realm container security so don’t know if this app will work in your dev env. But, we have to get the latest schema loaded in your docker image before you can actually run the run_tests script. In the meantime you can point to the vm restart/redeploy to wiildfly and see what happens? oh and sorry for the drama btw… our docker support needs some lovin… Shawn
