AnsweredAssumed Answered

How do you override the WSDL location for RmaDynamicWeb?

Question asked by on Apr 7, 2017
Latest reply on Apr 16, 2018 by

I am upgrading an application to Blaze Advisor 7.4 and deploying both an RMA and Rule Service to JBoss EAP 6.4.  I am encountering the following warning upon startup of the server with the RMA deployed.  I believe the important sections of the exception stack are highlighted below where the coded annotation for the WSDL Location of the RmaDynamicWeb application needs to be overridden for it's true location.


12:12:22,576 INFO  [] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider










properties=[ -> service jboss.deployment.unit."MyApplication_webapp-5.0.0.war".component."com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider".VIEW."com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider"]

12:12:23,525 WARNING [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Failed to parse WSDL: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'WEB-INF/wsdl/RmaDynamicWeb.wsdl'.: <<JBOSS_INSTALLATION_AREA>>\EAP-6.4.0\bin\WEB-INF\wsdl\RmaDynamicWeb.wsdl

(The system cannot find the path specified)

  at [wsdl4j-1.6.3.redhat-1.jar:1.6.3.redhat-1]

  at [wsdl4j-1.6.3.redhat-1.jar:1.6.3.redhat-1]

  at [wsdl4j-1.6.3.redhat-1.jar:1.6.3.redhat-1]

  at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition( [cxf-rt-core-2.7.14.redhat-1.jar:2.7.14.redhat-1]


Note: I masked the actual location of the JBoss EAP 6.4 installation area with <<JBOSS_INSTALLATION_AREA>>.


The file is not located in the folder EAP-6.4.0/bin/WEB-INF/wsdl.

It is located in the folder EAP-6.4.0/standalone/data/wsdl/MyApplication_webapp-5.0.0.war.


I have been searching the Blaze documentation and cannot find where this would need to be overridden.  I also cannot find the package for this class in the API javadoc: com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider



:::UPDATED INFO:::  The following lines are written just millseconds after the above warning:

16:16:29,965 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {}RmaDynamicWebService from class com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider

16:16:30,117 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/rma/RmaDynamicWebService

16:16:30,199 INFO  [] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/<<JBOSS_INSTALLATION_AREA>>/EAP-6.4.0/standalone/data/wsdl/MyApplication_webapp-5.0.0.war/RmaDynamicWeb.wsdl

16:16:30,570 INFO  [] (MSC service thread 1-2) JBAS015539: Starting service

16:16:30,581 INFO  [] (MSC service thread 1-1) JBAS015539: Starting service"ebipps-rma-7.4.0.war"."com.blazesoft.server.deploy.webservice.rma.NdRmaDynamicWebProvider"

16:16:30,597 INFO  [org.jboss.web] (ServerService Thread Pool -- 55) JBAS018210: Register web context: /rma





If the above warning is issued for an incorrect WSDL location, but the WSDL is ultimately written to a location that is confirmed by the JBoss/Apache CXF deployment process, does that mean we can ignore the warning and everything should work correctly?  Is there a way of eliminating the warning?