Satheesh Bandaram wrote: > This helps, but I still don't know what is causing the problem. I > currently believe this is because of some configuration issue. > > If you can isolate a test case using IJ, I think that would help solve > the problem. > >> interesting is that I tryied Ij, and the error didn't occured. >> But, Ij is not using pt_BR messages, and I suspect error is related > > This configuration of Tomcat and Derby is used offen and running > aggregates is also common. Current aggregate code seems to load the > class dynamically, so if there are any configuration issues, you could > see this problem. (like Stan's message)
I don't think a test case with ij will be possible. Most likely the aggregate class is being loaded from the same jar as the rest of the engine, but through a different class loader. Dan.
