[
https://issues.apache.org/activemq/browse/SM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Matias Urbieta reopened SM-1756:
--------------------------------------
Hi, Jetty is started when service units are packaged as cxf-bc SU but
lightweight one. When it is declared as a lightweight component, it works as
expected using the registered CXFManagedServlet instead of starting Jetty.
I have attached the apache-servicemix-web (distribution) project with three
tests that describe usage scenarios:
1) lightweight cxf consumer endpoint that works ok (PASSES)
2) a cxf consumer endpoint packaged as a SU (wsdl first derived example[1])
that do not work as expected starting a jetty server. (FAILS)
3) variation of configuration where a spring ServletContextLoader is used
instead of the listener version. The bug is still present. (FAILS)
I think, the cxf-bc component should follow managed approach used in the http
component.
NOTES
* The environment corresponds to SMX 3.3.1 and 2010.01 components
* [1] wsdl first example was modified adding the locationURI parameter to the
cxf consumer endpoint.
> add CXFManagedServlet to apache-servicemix-web to enable servicemix-cxf-bc
> endpoint deploy into servlet container without starting jetty
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1756
> URL: https://issues.apache.org/activemq/browse/SM-1756
> Project: ServiceMix
> Issue Type: New Feature
> Components: servicemix-cxf-bc, servicemix-web-console
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 3.3.1, 3.2.4
>
> Attachments: apache-servicemix-web.zip, SM-1756.patch
>
>
> we need add CXFManagedServlet in the web.xml to replace the http transport
> with cxf servlet transport.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
