Another idea - if you are on 1.1.*, switch to Cayenne 1.2M3 - it has a bit
different approach to bootstrapping a ClassLoader that is less sensitive
to the container ClassLoader hierarchy issues.
Or do this old proven but ugly hack on startup:
Configuration.bootstrapSharedConfiguration(edot.todolist.ToDo.class)
Andrus
>> I am not sure if i did understand you right.
>> The problem still occurs. Changing the order in serveral ways did not
>> solve the problem.
>>
>> I have send you the picture to your private address.
>>
>> thx for your continues help.
>>
>> sastan
>
> Hmm ... At this point I am pretty sure you have a nested ClassLoader
> issue. However your classpath looks right ... So without having access
> to your environment, I don't even know what else to check :-/
>
> All I can suggest is to start Jetty in debug mode in Eclipse and put
> breakpoints in Cayenne DataDomain where the exception is thrown.
>
> Andrus
This archive was generated by hypermail 2.0.0 : Fri Apr 29 2005 - 12:00:19 EDT