I guess you are trying with 3.0.1-SNAPSHOT, else the code snipped would not work (it should be much easier to do that with 3.1).
You may need to force spring to initialize the lifecycle. could you try adding a depends-on="config" attribute on the servicemix-http bean ? On 10/20/06, Marrad <[EMAIL PROTECTED]> wrote:
I'm trying to use the HttpComponent and HttpManagedServlet that was fixed in SM-578, http://issues.apache.org/activemq/browse/SM-578, but I get an error when deploying the war: java.lang.IllegalStateException: ServerManager is not managed at org.apache.servicemix.http.jetty.JettyContextManager.getMainProcessor(JettyContextManager.java:447) The problem seems to be that the property "managed" is not set to true until after the context manager is set in HttpLifeCycle doInit(). My configuration in applicationContext.xml is as suggested in a previous thread: <sm:activationSpec componentName="servicemix-http" component="#servicemix-http" /> ... <bean id="servicemix-http" class="org.apache.servicemix.http.HttpComponent" /> <bean id="lf" factory-bean="servicemix-http" factory-method="getLifeCycle" /> <bean id="config" factory-bean="lf" factory-method="getConfiguration"> <property name="managed" value="true" /> </bean> Is there another way to configure this? Regards Markus -- View this message in context: http://www.nabble.com/Usage-of-HttpManagedServlet-tf2480882.html#a6918022 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
