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 <[email protected]>
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 <[email protected]> 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 <[email protected]>
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
