 0 | some classes that conflict with tomcat. I think a quick fix for your code would be to catch |
0 | an issue. Thank you for your quick reply. One thing that I realize immediately is that you defined |
0 | a quick solution. If the converter converts 99% of your data successfully, it would be better |
0 | and quick response was much appreciated. Application still not working: [ObjectDB 2.5.0 Enhancer] 1 |
0 | case). I suggest the following: As a quick workaround just to make your product work - replace |
0 | , however, is only my supposition. For me is important not only how to quick-fix the bug but, mostly, understand |
0 | XML data? If you do - this could be served for a quick initial implementation of this feature |
0 | is clear now, and we are working on a quick fix. Please try build 2.5.0_04, which seems to fix |
0 | ={"lastName","firstName"}) And for a single field simply @Unique on the field. Thanks for the quick reply! pezi |
0 | , so we will have to investigate this further. As a quick solution, you may try to remove the index, i.e. access |
