-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.2.0 GA1, 7.2.X, 7.3.X, Master
-
Fix Version/s: 7.2.10 DXP FP16, 7.2.X, 7.3.10.3 DXP SP3, 7.3.X, 7.4.13 DXP GA1, 7.4.3.4 CE GA4, Master
-
Component/s: Portal Configuration
-
Branch Version/s:7.3.x, 7.2.x
-
Backported to Branch:Committed
-
Fix Priority:3
-
OS:Mac OS X 10.9
-
JDK:Oracle Sun JDK 8
-
Application Servers:Apache Tomcat 9.0.x
-
Git Pull Request:
Following the documentation Liferay 7.2 - Configuring Endpoints And Extenders Programmatically I tried to configure a SOAP endpoint but I can't get it to work. If I do the configuration from the control panel it works.
I also noticed in documentation that the pid
com.liferay.portal.remote.soap.extender.configuration.SoapExtenderConfiguration
on 7.2 no longer exists, has been moved to
com.liferay.portal.remote.soap.extender.internal.configuration.SoapExtenderConfiguration
I also tried to rename the properties file with the new PID name but the same result: the endpoint configuration is not applied.
I preferred to use the config extension for configuration files. Management of this extension is planned, see ConfiguratorExtender
Furthermore, the format of the jaxWsHandlerFilterStrings property is not indicated in the case in which I have multiple values. I used the format used by the export function of the control panel configuration.
contextPaths=/custom-user jaxWsHandlerFilterStrings=[ \ "(mac.address.validator.jax.ws.handler.filters\=true)", \ "(audit.log.jax.ws.handler.filters\=true)", \ ] jaxWsServiceFilterStrings=(custom.user.jax.ws.service=true)
You will find the source code on my GitHub repository liferay-72-soap-client-examples
- relates
-
LRDOCS-7349 JAX-WS classes have been refactored
-
- Open
-