What Eugen posted is right, I actually had chance to look at his machine which also had the Bean Instantiation Exception javax.persistance.* ... and found out that by commenting out the OMContextListener in the web.xml the error is gone (of course it doesn't boot completely without this context listener because the webAppRootKey is not set). It seems to me that depending on the hardware/machine this OMContextListener is intialized too early so that the Persistance-Context gets initialized too early. But it cannot be generalized, on the majority of sytem it works on some it fails.
@Maxim: You got an idea of another place to put this context initialization code so that it boots correctly? Maybe we can simply put it into ScopeApplicationAdapter::appStart() ? Thanks, Sebastian 2011/12/11 Eugen Schwert <[email protected]>: > About the beanloading configuration error: > > If you comment out this part of the web.xml > > <listener> > <listener-class>org.openmeetings.utils.OMContextListener</ > listener-class> > </listener> > > the server does startup without instatiation problem of spring beans > > -- > You received this message because you are subscribed to the Google Groups > "OpenMeetings developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/openmeetings-dev?hl=en. > -- Sebastian Wagner http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected] -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
