You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Kirk Spencer <ks...@playboox.com> on 2009/03/04 19:31:20 UTC
Re: Turning off Jetty
Freeman wrote:
>The problem you see comes from that after you install cxf bc component >and SA, then restart the tomcat, the context listener(which load >servicemix container and then start the intalled cxf bc and sa) always >run before the CXFServlet(which replace the servlet transport), so that >the cxf bc has no chance to use the bus with replaced servlet transport.>If you run tomcat with clean servicemix (remove data and servicemixDB >folder in $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install >sharedLib, CXF component and your SA, then it works(because in this case >the CXFServlet get initialized first).>I will figure out how to resolve the case when you restart tomcat.
>Freeman
Did you figure out a way to resolve the case when the tomcat instance is
restarted?
--
Kirk Spencer
Playboox | Senior Software Engineer
Re: Turning off Jetty
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
Today I get some time to play with your testcase, it's ok for me after
restarting tomcat, I can see the wsdl from http://localhost:8080/apache-servicemix-web-3.3.1/services/testCxf?wsdl
.
You need ensure your SA status is start from the web console.
What the exact problem you saw?
I also go through your patch and google a bit, seems use
ContextLoaderServlet instead of ContextLoaderListener is not a good
idea, as ContextLoaderServlet is deprecated and can't work with modern
servlet container (servlet api 2.4), the ContextLoaderListener is
recommand to use
Freeman
On 2009-6-26, at 上午3:23, Benoît Clouet wrote:
> Hi,
>
>
> I tested with the 3.3.1 and the problem was still present. The
> modification hereunder solved my issue. I'm not sure though that
> this won't have any side effects.
>
> Benoît
>
> Le 25 juin 2009 à 18:24, ffang <fr...@gmail.com> a écrit :
>
>> Hi,
>> Thanks. This solution looks good for me.
>>
>> And do you ever test your testcase with new released smx 3.3.1,
>> does this version work for you? I still believe my fix should
>> address this issue, sorry but I get no chance to run your testcase
>> from my side yet.
>>
>> Freeman
>>
>> 在 2009-6-25，下午11:30， Benoît Clouet 写道：
>>
>>>
>>>
>>> Freeman Fang wrote:
>>>>
>>>> The problem you see comes from that after you install cxf bc
>>>> component and
>>>> SA, then restart the tomcat, the context listener(which load
>>>> servicemix
>>>> container and then start the intalled cxf bc and sa) always run
>>>> before the
>>>> CXFServlet(which replace the servlet transport), so that the cxf
>>>> bc has no
>>>> chance to use the bus with replaced servlet transport. If you run
>>>> tomcat
>>>> with clean servicemix (remove data and servicemixDB folder in
>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>>> sharedLib,
>>>> CXF component and your SA, then it works(because in this case the
>>>> CXFServlet get initialized first). I will figure out how to
>>>> resolve the
>>>> case.
>>>>
>>>>> Hi,
>>>>> Thanks
>>>>> And just one note, generally we append attachment through nabble
>>>>> on > the
>>>>> mailling list.
>>>>> Freeman
>>>>
>>>
>>> Hi,
>>>
>>> did you figure out how to solve this issue ?
>>>
>>> Meanwhile I digged in the Spring documentation and I think I found
>>> a way to
>>> work this around.
>>>
>>> To sum up, the trick is to get the context loaded after the
>>> CXFManagedServlet. So I tried to use the alternative to the
>>> ContextLoaderListener ie. the ContextLoaderServlet.
>>>
>>> This involves a slight modification of the web.xml. You have to
>>> comment out
>>> :
>>> <listener>
>>>
>>> <listener-class>org.springframework.web.context.ContextLoaderListener
>>> </listener-class>
>>> </listener>
>>> and to replace this by the servlet context loader equivalent :
>>> <servlet>
>>> <servlet-name>context</servlet-name>
>>>
>>> <servlet-
>>> class>org.springframework.web.context.ContextLoaderServlet</
>>> servlet-class>
>>> <load-on-startup>3</load-on-startup>
>>> </servlet>
>>>
>>> Note that the load-on-startup is greater than the one of the
>>> CXFManagedServlet.
>>>
>>> This seems to work for me, as Tomcat startups now run fine even
>>> when all the
>>> SA are already deployed.
>>>
>>> Since I'm not an expert of spring and neither of servicemix, I do
>>> not know
>>> if this is a viable way to proceed.
>>>
>>> Any idea on this Freeman ?
>>>
>>> Thanks in advance for your advice.
>>>
>>> Kind regards,
>>>
>>> Benoît
>>>
>>> PS: please find attached the zip mentioned in my previous post as
>>> suggested.
>>> http://www.nabble.com/file/p24205542/test_cxf.zip test_cxf.zip
>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/Re%3A-Turning-off-Jetty-tp22336288p24205542.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Turning off Jetty
Posted by ffang <fr...@gmail.com>.
Hi,
Thanks
Could you please reopen SM-1756 and append your patch there?
Freeman
在 2009-6-26，上午3:23， Benoît Clouet 写道：
> Hi,
>
>
> I tested with the 3.3.1 and the problem was still present. The
> modification hereunder solved my issue. I'm not sure though that
> this won't have any side effects.
>
> Benoît
>
> Le 25 juin 2009 à 18:24, ffang <fr...@gmail.com> a écrit :
>
>> Hi,
>> Thanks. This solution looks good for me.
>>
>> And do you ever test your testcase with new released smx 3.3.1,
>> does this version work for you? I still believe my fix should
>> address this issue, sorry but I get no chance to run your testcase
>> from my side yet.
>>
>> Freeman
>>
>> 在 2009-6-25，下午11:30， Benoît Clouet 写道：
>>
>>>
>>>
>>> Freeman Fang wrote:
>>>>
>>>> The problem you see comes from that after you install cxf bc
>>>> component and
>>>> SA, then restart the tomcat, the context listener(which load
>>>> servicemix
>>>> container and then start the intalled cxf bc and sa) always run
>>>> before the
>>>> CXFServlet(which replace the servlet transport), so that the cxf
>>>> bc has no
>>>> chance to use the bus with replaced servlet transport. If you run
>>>> tomcat
>>>> with clean servicemix (remove data and servicemixDB folder in
>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>>> sharedLib,
>>>> CXF component and your SA, then it works(because in this case the
>>>> CXFServlet get initialized first). I will figure out how to
>>>> resolve the
>>>> case.
>>>>
>>>>> Hi,
>>>>> Thanks
>>>>> And just one note, generally we append attachment through nabble
>>>>> on > the
>>>>> mailling list.
>>>>> Freeman
>>>>
>>>
>>> Hi,
>>>
>>> did you figure out how to solve this issue ?
>>>
>>> Meanwhile I digged in the Spring documentation and I think I found
>>> a way to
>>> work this around.
>>>
>>> To sum up, the trick is to get the context loaded after the
>>> CXFManagedServlet. So I tried to use the alternative to the
>>> ContextLoaderListener ie. the ContextLoaderServlet.
>>>
>>> This involves a slight modification of the web.xml. You have to
>>> comment out
>>> :
>>> <listener>
>>>
>>> <listener-class>org.springframework.web.context.ContextLoaderListener
>>> </listener-class>
>>> </listener>
>>> and to replace this by the servlet context loader equivalent :
>>> <servlet>
>>> <servlet-name>context</servlet-name>
>>>
>>> <servlet-
>>> class>org.springframework.web.context.ContextLoaderServlet</
>>> servlet-class>
>>> <load-on-startup>3</load-on-startup>
>>> </servlet>
>>>
>>> Note that the load-on-startup is greater than the one of the
>>> CXFManagedServlet.
>>>
>>> This seems to work for me, as Tomcat startups now run fine even
>>> when all the
>>> SA are already deployed.
>>>
>>> Since I'm not an expert of spring and neither of servicemix, I do
>>> not know
>>> if this is a viable way to proceed.
>>>
>>> Any idea on this Freeman ?
>>>
>>> Thanks in advance for your advice.
>>>
>>> Kind regards,
>>>
>>> Benoît
>>>
>>> PS: please find attached the zip mentioned in my previous post as
>>> suggested.
>>> http://www.nabble.com/file/p24205542/test_cxf.zip test_cxf.zip
>>>
>>>
>>> --
>>> View this message in context: http://www.nabble.com/Re%3A-Turning-off-Jetty-tp22336288p24205542.html
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Hi,
I tested with the 3.3.1 and the problem was still present. The
modification hereunder solved my issue. I'm not sure though that this
won't have any side effects.
Benoît
Le 25 juin 2009 à 18:24, ffang <fr...@gmail.com> a écrit :
> Hi,
> Thanks. This solution looks good for me.
>
> And do you ever test your testcase with new released smx 3.3.1, does
> this version work for you? I still believe my fix should address
> this issue, sorry but I get no chance to run your testcase from my
> side yet.
>
> Freeman
>
> 在 2009-6-25，下午11:30， Benoît Clouet 写道：
>
>>
>>
>> Freeman Fang wrote:
>>>
>>> The problem you see comes from that after you install cxf bc
>>> component and
>>> SA, then restart the tomcat, the context listener(which load
>>> servicemix
>>> container and then start the intalled cxf bc and sa) always run
>>> before the
>>> CXFServlet(which replace the servlet transport), so that the cxf
>>> bc has no
>>> chance to use the bus with replaced servlet transport. If you run
>>> tomcat
>>> with clean servicemix (remove data and servicemixDB folder in
>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>> sharedLib,
>>> CXF component and your SA, then it works(because in this case the
>>> CXFServlet get initialized first). I will figure out how to
>>> resolve the
>>> case.
>>>
>>>> Hi,
>>>> Thanks
>>>> And just one note, generally we append attachment through nabble
>>>> on > the
>>>> mailling list.
>>>> Freeman
>>>
>>
>> Hi,
>>
>> did you figure out how to solve this issue ?
>>
>> Meanwhile I digged in the Spring documentation and I think I found
>> a way to
>> work this around.
>>
>> To sum up, the trick is to get the context loaded after the
>> CXFManagedServlet. So I tried to use the alternative to the
>> ContextLoaderListener ie. the ContextLoaderServlet.
>>
>> This involves a slight modification of the web.xml. You have to
>> comment out
>> :
>> <listener>
>>
>> <listener-
>> class>org.springframework.web.context.ContextLoaderListener</
>> listener-class>
>> </listener>
>> and to replace this by the servlet context loader equivalent :
>> <servlet>
>> <servlet-name>context</servlet-name>
>>
>> <servlet-
>> class>org.springframework.web.context.ContextLoaderServlet</servlet-
>> class>
>> <load-on-startup>3</load-on-startup>
>> </servlet>
>>
>> Note that the load-on-startup is greater than the one of the
>> CXFManagedServlet.
>>
>> This seems to work for me, as Tomcat startups now run fine even
>> when all the
>> SA are already deployed.
>>
>> Since I'm not an expert of spring and neither of servicemix, I do
>> not know
>> if this is a viable way to proceed.
>>
>> Any idea on this Freeman ?
>>
>> Thanks in advance for your advice.
>>
>> Kind regards,
>>
>> Benoît
>>
>> PS: please find attached the zip mentioned in my previous post as
>> suggested.
>> http://www.nabble.com/file/p24205542/test_cxf.zip test_cxf.zip
>>
>>
>> --
>> View this message in context: http://www.nabble.com/Re%3A-Turning-off-Jetty-tp22336288p24205542.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
Re: Turning off Jetty
Posted by ffang <fr...@gmail.com>.
Hi,
Thanks. This solution looks good for me.
And do you ever test your testcase with new released smx 3.3.1, does
this version work for you? I still believe my fix should address this
issue, sorry but I get no chance to run your testcase from my side yet.
Freeman
在 2009-6-25，下午11:30， Benoît Clouet 写道：
>
>
> Freeman Fang wrote:
>>
>> The problem you see comes from that after you install cxf bc
>> component and
>> SA, then restart the tomcat, the context listener(which load
>> servicemix
>> container and then start the intalled cxf bc and sa) always run
>> before the
>> CXFServlet(which replace the servlet transport), so that the cxf bc
>> has no
>> chance to use the bus with replaced servlet transport. If you run
>> tomcat
>> with clean servicemix (remove data and servicemixDB folder in
>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>> sharedLib,
>> CXF component and your SA, then it works(because in this case the
>> CXFServlet get initialized first). I will figure out how to resolve
>> the
>> case.
>>
>>> Hi,
>>> Thanks
>>> And just one note, generally we append attachment through nabble
>>> on > the
>>> mailling list.
>>> Freeman
>>
>
> Hi,
>
> did you figure out how to solve this issue ?
>
> Meanwhile I digged in the Spring documentation and I think I found a
> way to
> work this around.
>
> To sum up, the trick is to get the context loaded after the
> CXFManagedServlet. So I tried to use the alternative to the
> ContextLoaderListener ie. the ContextLoaderServlet.
>
> This involves a slight modification of the web.xml. You have to
> comment out
> :
> <listener>
>
> <listener-
> class>org.springframework.web.context.ContextLoaderListener</
> listener-class>
> </listener>
> and to replace this by the servlet context loader equivalent :
> <servlet>
> <servlet-name>context</servlet-name>
>
> <servlet-class>org.springframework.web.context.ContextLoaderServlet</
> servlet-class>
> <load-on-startup>3</load-on-startup>
> </servlet>
>
> Note that the load-on-startup is greater than the one of the
> CXFManagedServlet.
>
> This seems to work for me, as Tomcat startups now run fine even when
> all the
> SA are already deployed.
>
> Since I'm not an expert of spring and neither of servicemix, I do
> not know
> if this is a viable way to proceed.
>
> Any idea on this Freeman ?
>
> Thanks in advance for your advice.
>
> Kind regards,
>
> Benoît
>
> PS: please find attached the zip mentioned in my previous post as
> suggested.
> http://www.nabble.com/file/p24205542/test_cxf.zip test_cxf.zip
>
>
> --
> View this message in context: http://www.nabble.com/Re%3A-Turning-off-Jetty-tp22336288p24205542.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Freeman Fang wrote:
>
> The problem you see comes from that after you install cxf bc component and
> SA, then restart the tomcat, the context listener(which load servicemix
> container and then start the intalled cxf bc and sa) always run before the
> CXFServlet(which replace the servlet transport), so that the cxf bc has no
> chance to use the bus with replaced servlet transport. If you run tomcat
> with clean servicemix (remove data and servicemixDB folder in
> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install sharedLib,
> CXF component and your SA, then it works(because in this case the
> CXFServlet get initialized first). I will figure out how to resolve the
> case.
>
>> Hi,
>> Thanks
>> And just one note, generally we append attachment through nabble on > the
>> mailling list.
>> Freeman
>
Hi,
did you figure out how to solve this issue ?
Meanwhile I digged in the Spring documentation and I think I found a way to
work this around.
To sum up, the trick is to get the context loaded after the
CXFManagedServlet. So I tried to use the alternative to the
ContextLoaderListener ie. the ContextLoaderServlet.
This involves a slight modification of the web.xml. You have to comment out
:
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
and to replace this by the servlet context loader equivalent :
<servlet>
<servlet-name>context</servlet-name>
<servlet-class>org.springframework.web.context.ContextLoaderServlet</servlet-class>
<load-on-startup>3</load-on-startup>
</servlet>
Note that the load-on-startup is greater than the one of the
CXFManagedServlet.
This seems to work for me, as Tomcat startups now run fine even when all the
SA are already deployed.
Since I'm not an expert of spring and neither of servicemix, I do not know
if this is a viable way to proceed.
Any idea on this Freeman ?
Thanks in advance for your advice.
Kind regards,
Benoît
PS: please find attached the zip mentioned in my previous post as suggested.
http://www.nabble.com/file/p24205542/test_cxf.zip test_cxf.zip
--
View this message in context: http://www.nabble.com/Re%3A-Turning-off-Jetty-tp22336288p24205542.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Turning off Jetty
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
Thanks
And just one note, generally we append attachment through nabble on the
mailling list.
Freeman
Benoît Clouet wrote:
> Just in case the attachement gets dropped ->
> http://b.clouet.free.fr/test_cxf.zip
>
> 2009/6/11 Benoît Clouet <be...@gmail.com>
>
>
>> Hi,
>>
>> yes I think I picked up the fix.
>>
>> Please find attached the example SA in order to reproduce the problem.
>> And let me know if the attachement gets dropped.
>>
>> Kind regards,
>>
>> Benoît
>>
>> On Thu, Jun 11, 2009 at 8:48 AM, Freeman Fang <fr...@gmail.com>
>> wrote:
>>
>>> Hi,
>>> So you update from [1] and build apache-servicemix-web distribution, and
>>>
>> install the cxf bc component you build from [2]?
>>
>>> If you, I believe you already pick up this fix, it's wired to me, any
>>>
>> chance you append your SA(you can simplify to remove your business and just
>> reproduce the problem)?
>>
>>> [1]
>>>
>> http://svn.apache.org/repos/asf/servicemix/smx3/trunk/distributions/apache-servicemix-web/
>>
>>> [2]
>>>
>> http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/
>>
>>> Thanks
>>> Freeman
>>>
>>> Benoît Clouet wrote:
>>>
>>>> Hi,
>>>>
>>>> In fact I checked out the servicemix-web module containing the commit
>>>>
>> mentioned in the jira ticket, did the same with the cxf-bc and compiled
>> them.
>>
>>>> On the first deployment of the sa & su relying on this fix, everything
>>>>
>> runs fine but subsequent restart go into the error mentioned hereunder. Is
>> there anything more to checkout, for example cxf snapshots ?
>>
>>>> Benoît
>>>>
>>>> Le 11 juin 09 à 02:06, Freeman Fang <fr...@gmail.com> a écrit :
>>>>
>>>>
>>>>> Hi,
>>>>> You build latest snapshot yourself from smx3 trunk, right? This fix not
>>>>>
>> get released officially so far.
>>
>>>>> If so, you mean you still see the problem after restarting tomcat?
>>>>> Freeman
>>>>>
>>>>> Benoît Clouet wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> it seems this issue still happens, at least on Tomcat and at least on
>>>>>>
>> the
>>
>>>>>> smx3 trunk (gave a try also on the 3.2 branch with no success either).
>>>>>>
>>>>>> The CXF thing continues to start before the replaceDestinationFactory
>>>>>>
>> method
>>
>>>>>> takes place thus resulting into a :
>>>>>> javax.jbi.management.DeploymentException:
>>>>>>
>> java.net.MalformedURLException: no
>>
>>>>>> protocol: /MyRequest
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
>>
>>>>>> at
>>>>>>
>>>>>>
>> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
>>
>>>>>> Before this, I see lots of messages related to the startup of the CXF
>>>>>>
>> bus.
>>
>>>>>> Maybe there would be a possiblity to force CXF to call the
>>>>>>
>>>>>>
>> org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
>>
>>>>>> before the CXF jbi component gets started ?
>>>>>>
>>>>>> Any idea on this ?
>>>>>>
>>>>>> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang <fr...@gmail.com>
>>>>>>
>> wrote:
>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> This already get resolved, [1] tracked this issue
>>>>>>>
>>>>>>> [1]https://issues.apache.org/activemq/browse/SM-1756
>>>>>>> Freeman
>>>>>>>
>>>>>>>
>>>>>>> Kirk Spencer wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Freeman wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> The problem you see comes from that after you install cxf bc
>>>>>>>>>
>> component
>>
>>>>>>>>>> and SA, then restart the tomcat, the context listener(which load
>>>>>>>>>> servicemix container and then start the intalled cxf bc and sa)
>>>>>>>>>>
>> always >run
>>
>>>>>>>>> before the CXFServlet(which replace the servlet transport), so that
>>>>>>>>>
>>> the cxf
>>>
>>>>>>>>> bc has no chance to use the bus with replaced servlet transport.>If
>>>>>>>>>
>> you run
>>
>>>>>>>>> tomcat with clean servicemix (remove data and servicemixDB >folder
>>>>>>>>>
>> in
>>
>>>>>>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>>>>>>>>
>>> sharedLib,
>>>
>>>>>>>>> CXF component and your SA, then it works(because in this case >the
>>>>>>>>> CXFServlet get initialized first).>I will figure out how to resolve
>>>>>>>>>
>> the case
>>
>>>>>>>>> when you restart tomcat.
>>>>>>>>> Freeman
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Did you figure out a way to resolve the case when the tomcat
>>>>>>>>
>> instance is
>>
>>>>>>>> restarted?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>> --Freeman Fang
>>>>> ------------------------
>>>>> Open Source SOA: http://fusesource.com
>>>>>
>>>>>
>>> --
>>> Freeman Fang
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>>
>>>
>
>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Just in case the attachement gets dropped ->
http://b.clouet.free.fr/test_cxf.zip
2009/6/11 Benoît Clouet <be...@gmail.com>
> Hi,
>
> yes I think I picked up the fix.
>
> Please find attached the example SA in order to reproduce the problem.
> And let me know if the attachement gets dropped.
>
> Kind regards,
>
> Benoît
>
> On Thu, Jun 11, 2009 at 8:48 AM, Freeman Fang <fr...@gmail.com>
> wrote:
> >
> > Hi,
> > So you update from [1] and build apache-servicemix-web distribution, and
> install the cxf bc component you build from [2]?
> > If you, I believe you already pick up this fix, it's wired to me, any
> chance you append your SA(you can simplify to remove your business and just
> reproduce the problem)?
> > [1]
> http://svn.apache.org/repos/asf/servicemix/smx3/trunk/distributions/apache-servicemix-web/
> > [2]
> http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/
> > Thanks
> > Freeman
> >
> > Benoît Clouet wrote:
> >>
> >> Hi,
> >>
> >> In fact I checked out the servicemix-web module containing the commit
> mentioned in the jira ticket, did the same with the cxf-bc and compiled
> them.
> >>
> >> On the first deployment of the sa & su relying on this fix, everything
> runs fine but subsequent restart go into the error mentioned hereunder. Is
> there anything more to checkout, for example cxf snapshots ?
> >>
> >> Benoît
> >>
> >> Le 11 juin 09 à 02:06, Freeman Fang <fr...@gmail.com> a écrit :
> >>
> >>> Hi,
> >>> You build latest snapshot yourself from smx3 trunk, right? This fix not
> get released officially so far.
> >>> If so, you mean you still see the problem after restarting tomcat?
> >>> Freeman
> >>>
> >>> Benoît Clouet wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> it seems this issue still happens, at least on Tomcat and at least on
> the
> >>>> smx3 trunk (gave a try also on the 3.2 branch with no success either).
> >>>>
> >>>> The CXF thing continues to start before the replaceDestinationFactory
> method
> >>>> takes place thus resulting into a :
> >>>> javax.jbi.management.DeploymentException:
> java.net.MalformedURLException: no
> >>>> protocol: /MyRequest
> >>>> at
> >>>>
> org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
> >>>> at
> >>>>
> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
> >>>> at
> >>>>
> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
> >>>> at
> >>>>
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
> >>>> at
> >>>>
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
> >>>> at
> >>>>
> org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
> >>>> at
> >>>>
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
> >>>>
> >>>> Before this, I see lots of messages related to the startup of the CXF
> bus.
> >>>> Maybe there would be a possiblity to force CXF to call the
> >>>>
> org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
> >>>> before the CXF jbi component gets started ?
> >>>>
> >>>> Any idea on this ?
> >>>>
> >>>> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang <fr...@gmail.com>
> wrote:
> >>>>
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> This already get resolved, [1] tracked this issue
> >>>>>
> >>>>> [1]https://issues.apache.org/activemq/browse/SM-1756
> >>>>> Freeman
> >>>>>
> >>>>>
> >>>>> Kirk Spencer wrote:
> >>>>>
> >>>>>
> >>>>>> Freeman wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> The problem you see comes from that after you install cxf bc
> component
> >>>>>>>
> >>>>>>>> and SA, then restart the tomcat, the context listener(which load
> >>>>>>>> servicemix container and then start the intalled cxf bc and sa)
> always >run
> >>>>>>>>
> >>>>>>> before the CXFServlet(which replace the servlet transport), so that
> >the cxf
> >>>>>>> bc has no chance to use the bus with replaced servlet transport.>If
> you run
> >>>>>>> tomcat with clean servicemix (remove data and servicemixDB >folder
> in
> >>>>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
> >sharedLib,
> >>>>>>> CXF component and your SA, then it works(because in this case >the
> >>>>>>> CXFServlet get initialized first).>I will figure out how to resolve
> the case
> >>>>>>> when you restart tomcat.
> >>>>>>> Freeman
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> Did you figure out a way to resolve the case when the tomcat
> instance is
> >>>>>> restarted?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --Freeman Fang
> >>> ------------------------
> >>> Open Source SOA: http://fusesource.com
> >>>
> >>
> >
> >
> > --
> > Freeman Fang
> > ------------------------
> > Open Source SOA: http://fusesource.com
> >
>
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Hi,
yes I think I picked up the fix.
Please find attached the example SA in order to reproduce the problem.
And let me know if the attachement gets dropped.
Kind regards,
Benoît
On Thu, Jun 11, 2009 at 8:48 AM, Freeman Fang <fr...@gmail.com> wrote:
>
> Hi,
> So you update from [1] and build apache-servicemix-web distribution, and install the cxf bc component you build from [2]?
> If you, I believe you already pick up this fix, it's wired to me, any chance you append your SA(you can simplify to remove your business and just reproduce the problem)?
> [1]http://svn.apache.org/repos/asf/servicemix/smx3/trunk/distributions/apache-servicemix-web/
> [2]http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/
> Thanks
> Freeman
>
> Benoît Clouet wrote:
>>
>> Hi,
>>
>> In fact I checked out the servicemix-web module containing the commit mentioned in the jira ticket, did the same with the cxf-bc and compiled them.
>>
>> On the first deployment of the sa & su relying on this fix, everything runs fine but subsequent restart go into the error mentioned hereunder. Is there anything more to checkout, for example cxf snapshots ?
>>
>> Benoît
>>
>> Le 11 juin 09 à 02:06, Freeman Fang <fr...@gmail.com> a écrit :
>>
>>> Hi,
>>> You build latest snapshot yourself from smx3 trunk, right? This fix not get released officially so far.
>>> If so, you mean you still see the problem after restarting tomcat?
>>> Freeman
>>>
>>> Benoît Clouet wrote:
>>>>
>>>> Hi,
>>>>
>>>> it seems this issue still happens, at least on Tomcat and at least on the
>>>> smx3 trunk (gave a try also on the 3.2 branch with no success either).
>>>>
>>>> The CXF thing continues to start before the replaceDestinationFactory method
>>>> takes place thus resulting into a :
>>>> javax.jbi.management.DeploymentException: java.net.MalformedURLException: no
>>>> protocol: /MyRequest
>>>> at
>>>> org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
>>>> at
>>>> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
>>>> at
>>>> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
>>>> at
>>>> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
>>>> at
>>>> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
>>>> at
>>>> org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
>>>> at
>>>> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
>>>>
>>>> Before this, I see lots of messages related to the startup of the CXF bus.
>>>> Maybe there would be a possiblity to force CXF to call the
>>>> org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
>>>> before the CXF jbi component gets started ?
>>>>
>>>> Any idea on this ?
>>>>
>>>> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang <fr...@gmail.com> wrote:
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> This already get resolved, [1] tracked this issue
>>>>>
>>>>> [1]https://issues.apache.org/activemq/browse/SM-1756
>>>>> Freeman
>>>>>
>>>>>
>>>>> Kirk Spencer wrote:
>>>>>
>>>>>
>>>>>> Freeman wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> The problem you see comes from that after you install cxf bc component
>>>>>>>
>>>>>>>> and SA, then restart the tomcat, the context listener(which load
>>>>>>>> servicemix container and then start the intalled cxf bc and sa) always >run
>>>>>>>>
>>>>>>> before the CXFServlet(which replace the servlet transport), so that >the cxf
>>>>>>> bc has no chance to use the bus with replaced servlet transport.>If you run
>>>>>>> tomcat with clean servicemix (remove data and servicemixDB >folder in
>>>>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install >sharedLib,
>>>>>>> CXF component and your SA, then it works(because in this case >the
>>>>>>> CXFServlet get initialized first).>I will figure out how to resolve the case
>>>>>>> when you restart tomcat.
>>>>>>> Freeman
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> Did you figure out a way to resolve the case when the tomcat instance is
>>>>>> restarted?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --Freeman Fang
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>>
>>
>
>
> --
> Freeman Fang
> ------------------------
> Open Source SOA: http://fusesource.com
>
Re: Turning off Jetty
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
So you update from [1] and build apache-servicemix-web distribution, and
install the cxf bc component you build from [2]?
If you, I believe you already pick up this fix, it's wired to me, any
chance you append your SA(you can simplify to remove your business and
just reproduce the problem)?
[1]http://svn.apache.org/repos/asf/servicemix/smx3/trunk/distributions/apache-servicemix-web/
[2]http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-cxf-bc/trunk/
Thanks
Freeman
Benoît Clouet wrote:
> Hi,
>
> In fact I checked out the servicemix-web module containing the commit
> mentioned in the jira ticket, did the same with the cxf-bc and
> compiled them.
>
> On the first deployment of the sa & su relying on this fix, everything
> runs fine but subsequent restart go into the error mentioned
> hereunder. Is there anything more to checkout, for example cxf
> snapshots ?
>
> Benoît
>
> Le 11 juin 09 à 02:06, Freeman Fang <fr...@gmail.com> a écrit :
>
>> Hi,
>> You build latest snapshot yourself from smx3 trunk, right? This fix
>> not get released officially so far.
>> If so, you mean you still see the problem after restarting tomcat?
>> Freeman
>>
>> Benoît Clouet wrote:
>>> Hi,
>>>
>>> it seems this issue still happens, at least on Tomcat and at least
>>> on the
>>> smx3 trunk (gave a try also on the 3.2 branch with no success either).
>>>
>>> The CXF thing continues to start before the
>>> replaceDestinationFactory method
>>> takes place thus resulting into a :
>>> javax.jbi.management.DeploymentException:
>>> java.net.MalformedURLException: no
>>> protocol: /MyRequest
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
>>>
>>> at
>>> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
>>>
>>> at
>>> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
>>>
>>> at
>>> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
>>>
>>> at
>>> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
>>>
>>> at
>>> org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
>>>
>>> at
>>> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
>>>
>>>
>>> Before this, I see lots of messages related to the startup of the
>>> CXF bus.
>>> Maybe there would be a possiblity to force CXF to call the
>>> org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
>>>
>>> before the CXF jbi component gets started ?
>>>
>>> Any idea on this ?
>>>
>>> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang
>>> <fr...@gmail.com> wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> This already get resolved, [1] tracked this issue
>>>>
>>>> [1]https://issues.apache.org/activemq/browse/SM-1756
>>>> Freeman
>>>>
>>>>
>>>> Kirk Spencer wrote:
>>>>
>>>>
>>>>> Freeman wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> The problem you see comes from that after you install cxf bc
>>>>>> component
>>>>>>
>>>>>>> and SA, then restart the tomcat, the context listener(which load
>>>>>>> servicemix container and then start the intalled cxf bc and sa)
>>>>>>> always >run
>>>>>>>
>>>>>> before the CXFServlet(which replace the servlet transport), so
>>>>>> that >the cxf
>>>>>> bc has no chance to use the bus with replaced servlet
>>>>>> transport.>If you run
>>>>>> tomcat with clean servicemix (remove data and servicemixDB
>>>>>> >folder in
>>>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>>>>> >sharedLib,
>>>>>> CXF component and your SA, then it works(because in this case >the
>>>>>> CXFServlet get initialized first).>I will figure out how to
>>>>>> resolve the case
>>>>>> when you restart tomcat.
>>>>>> Freeman
>>>>>>
>>>>>>
>>>>>>
>>>>> Did you figure out a way to resolve the case when the tomcat
>>>>> instance is
>>>>> restarted?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>> --Freeman Fang
>> ------------------------
>> Open Source SOA: http://fusesource.com
>>
>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Hi,
In fact I checked out the servicemix-web module containing the commit
mentioned in the jira ticket, did the same with the cxf-bc and
compiled them.
On the first deployment of the sa & su relying on this fix, everything
runs fine but subsequent restart go into the error mentioned
hereunder. Is there anything more to checkout, for example cxf
snapshots ?
Benoît
Le 11 juin 09 à 02:06, Freeman Fang <fr...@gmail.com> a écrit :
> Hi,
> You build latest snapshot yourself from smx3 trunk, right? This fix
> not get released officially so far.
> If so, you mean you still see the problem after restarting tomcat?
> Freeman
>
> Benoît Clouet wrote:
>> Hi,
>>
>> it seems this issue still happens, at least on Tomcat and at least
>> on the
>> smx3 trunk (gave a try also on the 3.2 branch with no success
>> either).
>>
>> The CXF thing continues to start before the
>> replaceDestinationFactory method
>> takes place thus resulting into a :
>> javax.jbi.management.DeploymentException:
>> java.net.MalformedURLException: no
>> protocol: /MyRequest
>> at
>> org.
>> apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:
>> 504)
>> at
>> org.
>> apache.
>> servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
>> at
>> org.
>> apache.
>> servicemix.
>> common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
>> at
>> org.
>> apache.
>> servicemix.
>> common.
>> xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
>> at
>> org.
>> apache.
>> servicemix.
>> common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:
>> 88)
>> at
>> org.
>> apache.
>> servicemix.
>> common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
>> at
>> org.
>> apache.
>> servicemix.
>> jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
>>
>> Before this, I see lots of messages related to the startup of the
>> CXF bus.
>> Maybe there would be a possiblity to force CXF to call the
>> org.
>> apache.
>> cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
>> before the CXF jbi component gets started ?
>>
>> Any idea on this ?
>>
>> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang
>> <fr...@gmail.com> wrote:
>>
>>
>>> Hi,
>>>
>>> This already get resolved, [1] tracked this issue
>>>
>>> [1]https://issues.apache.org/activemq/browse/SM-1756
>>> Freeman
>>>
>>>
>>> Kirk Spencer wrote:
>>>
>>>
>>>> Freeman wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> The problem you see comes from that after you install cxf bc
>>>>> component
>>>>>
>>>>>> and SA, then restart the tomcat, the context listener(which load
>>>>>> servicemix container and then start the intalled cxf bc and sa)
>>>>>> always >run
>>>>>>
>>>>> before the CXFServlet(which replace the servlet transport), so
>>>>> that >the cxf
>>>>> bc has no chance to use the bus with replaced servlet
>>>>> transport.>If you run
>>>>> tomcat with clean servicemix (remove data and servicemixDB
>>>>> >folder in
>>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install
>>>>> >sharedLib,
>>>>> CXF component and your SA, then it works(because in this case >the
>>>>> CXFServlet get initialized first).>I will figure out how to
>>>>> resolve the case
>>>>> when you restart tomcat.
>>>>> Freeman
>>>>>
>>>>>
>>>>>
>>>> Did you figure out a way to resolve the case when the tomcat
>>>> instance is
>>>> restarted?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>
>
> --
> Freeman Fang
> ------------------------
> Open Source SOA: http://fusesource.com
>
Re: Turning off Jetty
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
You build latest snapshot yourself from smx3 trunk, right? This fix not
get released officially so far.
If so, you mean you still see the problem after restarting tomcat?
Freeman
Benoît Clouet wrote:
> Hi,
>
> it seems this issue still happens, at least on Tomcat and at least on the
> smx3 trunk (gave a try also on the 3.2 branch with no success either).
>
> The CXF thing continues to start before the replaceDestinationFactory method
> takes place thus resulting into a :
> javax.jbi.management.DeploymentException: java.net.MalformedURLException: no
> protocol: /MyRequest
> at
> org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
> at
> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
> at
> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
> at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
> at
> org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
> at
> org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
>
> Before this, I see lots of messages related to the startup of the CXF bus.
> Maybe there would be a possiblity to force CXF to call the
> org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
> before the CXF jbi component gets started ?
>
> Any idea on this ?
>
> On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang <fr...@gmail.com> wrote:
>
>
>> Hi,
>>
>> This already get resolved, [1] tracked this issue
>>
>> [1]https://issues.apache.org/activemq/browse/SM-1756
>> Freeman
>>
>>
>> Kirk Spencer wrote:
>>
>>
>>> Freeman wrote:
>>>
>>>
>>>
>>>
>>>> The problem you see comes from that after you install cxf bc component
>>>>
>>>>> and SA, then restart the tomcat, the context listener(which load
>>>>> servicemix container and then start the intalled cxf bc and sa) always >run
>>>>>
>>>> before the CXFServlet(which replace the servlet transport), so that >the cxf
>>>> bc has no chance to use the bus with replaced servlet transport.>If you run
>>>> tomcat with clean servicemix (remove data and servicemixDB >folder in
>>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install >sharedLib,
>>>> CXF component and your SA, then it works(because in this case >the
>>>> CXFServlet get initialized first).>I will figure out how to resolve the case
>>>> when you restart tomcat.
>>>> Freeman
>>>>
>>>>
>>>>
>>> Did you figure out a way to resolve the case when the tomcat instance is
>>> restarted?
>>>
>>>
>>>
>>>
>>>
>>
>
>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Turning off Jetty
Posted by Benoît Clouet <be...@gmail.com>.
Hi,
it seems this issue still happens, at least on Tomcat and at least on the
smx3 trunk (gave a try also on the 3.2 branch with no success either).
The CXF thing continues to start before the replaceDestinationFactory method
takes place thus resulting into a :
javax.jbi.management.DeploymentException: java.net.MalformedURLException: no
protocol: /MyRequest
at
org.apache.servicemix.cxfbc.CxfBcConsumer.validate(CxfBcConsumer.java:504)
at
org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
at
org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
at
org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:97)
at
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
at
org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:109)
at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)
Before this, I see lots of messages related to the startup of the CXF bus.
Maybe there would be a possiblity to force CXF to call the
org.apache.cxf.transport.servlet.AbstractCXFServlet.replaceDestinationFactory
before the CXF jbi component gets started ?
Any idea on this ?
On Thu, Mar 5, 2009 at 3:57 AM, Freeman Fang <fr...@gmail.com> wrote:
> Hi,
>
> This already get resolved, [1] tracked this issue
>
> [1]https://issues.apache.org/activemq/browse/SM-1756
> Freeman
>
>
> Kirk Spencer wrote:
>
>> Freeman wrote:
>>
>>
>>
>>> The problem you see comes from that after you install cxf bc component
>>> >and SA, then restart the tomcat, the context listener(which load
>>> >servicemix container and then start the intalled cxf bc and sa) always >run
>>> before the CXFServlet(which replace the servlet transport), so that >the cxf
>>> bc has no chance to use the bus with replaced servlet transport.>If you run
>>> tomcat with clean servicemix (remove data and servicemixDB >folder in
>>> $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install >sharedLib,
>>> CXF component and your SA, then it works(because in this case >the
>>> CXFServlet get initialized first).>I will figure out how to resolve the case
>>> when you restart tomcat.
>>> Freeman
>>>
>>>
>>
>> Did you figure out a way to resolve the case when the tomcat instance is
>> restarted?
>>
>>
>>
>>
>
>
Re: Turning off Jetty
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
This already get resolved, [1] tracked this issue
[1]https://issues.apache.org/activemq/browse/SM-1756
Freeman
Kirk Spencer wrote:
> Freeman wrote:
>
>
>> The problem you see comes from that after you install cxf bc component >and SA, then restart the tomcat, the context listener(which load >servicemix container and then start the intalled cxf bc and sa) always >run before the CXFServlet(which replace the servlet transport), so that >the cxf bc has no chance to use the bus with replaced servlet transport.>If you run tomcat with clean servicemix (remove data and servicemixDB >folder in $TOMCAT_HOME/bin, but add CXFServlet in web.xml), then install >sharedLib, CXF component and your SA, then it works(because in this case >the CXFServlet get initialized first).>I will figure out how to resolve the case when you restart tomcat.
>> Freeman
>>
>
> Did you figure out a way to resolve the case when the tomcat instance is
> restarted?
>
>
>