should be ok on trunk Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014/1/14 Karl-Philipp Richter <[email protected]>: > Thanks! I've just seen that the DEBUG value for > openejb.validation.output.level is not used (and therefore refused), but > maybe it could be introduced. Someone who triggers debug output > shouldn't care about performance. > > On 13.01.2014 19:02, Romain Manni-Bucau wrote: >> here it is >> http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/resources/default.exclusions >> >> in tomee there are few more (from catalina.properties) >> >> I prefer to not log them since it will slow down a bit startup but >> would be doable if really needed >> >> last note: this is overridable through exclusions.list >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2014/1/13 Karl-Philipp Richter <[email protected]>: >>> Hi Romain, >>> After chaning the name, it worked indeed. Thanks a lot!! Is there a list >>> of other prefixes which are filtered? Does it make sense to make an >>> enhancement request to print this list to console if the property >>> openejb.validation.output.level is set to VERBOSE or DEBUG? >>> >>> Kind Regards, >>> Karl >>> >>> On 13.01.2014 07:59, Romain Manni-Bucau wrote: >>>> Hi >>>> >>>> maybe rename it issue-hibernate, IIRC hibernate prefix is filtered >>>> Romain Manni-Bucau >>>> Twitter: @rmannibucau >>>> Blog: http://rmannibucau.wordpress.com/ >>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>> Github: https://github.com/rmannibucau >>>> >>>> >>>> >>>> 2014/1/13 Karl-Philipp Richter <[email protected]>: >>>>> Hi together, >>>>> While creating an example to investigate an issue with hibernate and >>>>> openejb in embedded unit testing, I cut down my example to the least >>>>> possible and I tried to get it running for 3 hours now. I used this >>>>> approach for about 100 unit test I've been writing so far and it worked >>>>> always very well, intuitive and out-of-the-box, so I no longer >>>>> understand the world. I read the "Application discovery via the >>>>> classpath" article and investigated with the troubleshooting approach. >>>>> >>>>> Can somebody help me, please?! >>> >
