We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The core reason is, that ApplicationDidFinishLaunchingNotification does not fire under servlet deployment.
A possible fix would be too add the following lines to end of the ERXApplication() constructor:
if(isDeployedAsServlet()) { NSNotificationCenter.defaultCenter().postNotification(WOApplication.ApplicationDidFinishLaunchingNotification, new NSNotification("", null)); }
The text was updated successfully, but these errors were encountered:
ensure notification trigger in servlet context
bf2e68a
fixes issue wocommunity#642
A ApplicationDidFinishLaunchingNotification will be posted if the ser…
1f4d4b4
…vlet has been initialized (Fix for wocommunity#642)
Merge branch 'develop'
460f422
* develop: Makes ERXPartial serializable. wocommunity#655 Makes ERXDisplayGroup serializable. wocommunity#651 Fix ERMoviesLogic migration bug, that caused the dependency on ERAttachment to be skipped due to an override returning null. With this change, migrations run fine on H2. A ApplicationDidFinishLaunchingNotification will be posted if the servlet has been initialized (Fix for wocommunity#642) reformatted source Replaced erxservletadaptor.jar by its source file ERXServletAdaptor.java * removed unnecessary imports * removed unnecessary casts * suppressed warning about potential null pointer exception Merged additional documentation and minor refactorings, courtesy of Miguel Arroz: http://sourceforge.net/p/wonder/code/11827/tree//branches/Wonder_2_0_0_WebObjects_5_4_Branch/Wonder/Frameworks/Core/ERExtensions/Sources/er/extensions/eof/ERXSQLQueryWithBindingsUtilities.java
Successfully merging a pull request may close this issue.
The core reason is, that ApplicationDidFinishLaunchingNotification does not fire under servlet deployment.
A possible fix would be too add the following lines to end of the ERXApplication() constructor:
The text was updated successfully, but these errors were encountered: