As a quick workaround , you should just remove the *Streaming* stuff
from the persistence.xml file. It seems like the classloader gets
confused otherwise sometimes...
Thx for Reporting,
Norman
2010/4/23, Tim-Christian Mundt (JIRA) server-dev@james.apache.org:
JPAStreamingMessage vs JPAMessage
Hi Tim-Christian,
I stopped james 2 days ago for small config change (btw hot-config would
be great :)) and I received exactly the same exception (I already saw it
once or twice).
The exception was shown only when fetching mails on one specific account.
I deployed a fresh version of james
