-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
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
Document more Spring integration patterns for Bayeux services #54
Comments
Originally reported by sbordet on 2009-12-09T10:05:35Z |
sbordet on 2009-12-09T10:59:17Z: |
sritd on 2009-12-16T14:33:00Z: and was able to reference the bean using the lazy-init from one of my service classes. This way I avoided adding the glue code and also let spring manage the service bean. If your service bean needs other resources, like dao, or other services, you might have to pass in as a constructor argument just like your pass in the bayeux bean. Hope this helps. If you think that this may not solve my issue, please do comment. Thanks, |
sbordet on 2009-12-18T09:37:01Z: |
When using Spring along with other frameworks (such as, for example, Struts2), the strategy of overriding Spring's default loading mechanism may not work, because the framework may need to initialize Spring before the CometD servlet.
For example, Struts2 is configured via a servlet filter which cannot be configured using
<load-on-startup>
to be initialized after the CometD servlet. When Struts2 is integrated with Spring, initialization of the Struts2 filter triggers Spring initialization.Document the pattern of using lazy initialization for Bayeux services.
The text was updated successfully, but these errors were encountered: