IMHO, Spring should be logging the warning message, not OpenJPA. Registering a class transformer is defined explicitly by the spec and OpenJPA shouldn't be catching exceptions coming from 'Spring features' (The spec is pretty huge, so please correct me if I'm wrong).
Also, I don't think that it is possible for OpenJPA to detect that classes were enhanced at build time. To address the issue at hand, I think that it would be reasonable to have a property that allows a user to disable the registration of a class transformer. If a user has went through the process of enhancing their Entities at build time, I don't think that adding an additional property would be too much of a burden. -Rick Marc Logemann wrote: > > have just seen thats its mentioned in: > https://issues.apache.org/jira/browse/OPENJPA-72 > > Its not that a hughe bug, because its only a warning which could be > suppressed with better detection..... but it has 3 votes if that means > something :) > > Marc > > Am 03.03.2009 um 13:12 schrieb Marc Logemann: > >> Hi, >> >> this issue was discussed by Hoeller and Linskey more than a year ago >> and its still there. See here: >> >> http://forum.springframework.org/archive/index.php/t-44299.html >> >> What is the solution here? >> >> Marc > > > -- View this message in context: http://n2.nabble.com/cannot-apply-class-transformer-without-LoadTimeWeaver-tp2414782p2423895.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
