1 2 Previous Next 24 Replies Latest reply on Jul 12, 2013 10:25 AM by Slava Uchitel

    WS Soap Proxy

    Jaime Pallares Newbie

      Hi,

       

      I will like to make WS Soap Proxy, without importing WSDL as mule ESB.

       

      Mule Example:

      <flow name="mule-configFlow3">
         <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081" />
         <logger level="INFO" message="1-> #[groovy:payload.getClass()]" />
         <cxf:proxy-service payload="body" />
         <logger level="INFO"  message="2-> #[groovy:payload.getClass()]"/>
         <cxf:proxy-client payload="body" enableMuleSoapHeaders="true"/>
         <logger level="INFO"  message="3-> #[groovy:payload.getClass()]"/>
         <http:outbound-endpoint exchange-pattern="request-response" address="http://localhost:65082/services/EchoUMO"/>
      </flow>

       

      I have trying with camel example, but I need more transparent solution.

       

      My intention is to make ws proxy app for public services for protect central ws backend.


      But for every change on Central repository I’ don’t want to compile and deploy ws proxy app.

      All WSDL have to be on ws central backend, not duplicate on proxy app.

       

      Is possible?

       

      Please, provide example.

       

      Best regards,

        • 1. Re: WS Soap Proxy
          Keith Babo Master

          The path to a WSDL can be local to the deployment (as it is in the soap-proxy quickstart) or it can be a file or http URL to an external WSDL.  Using this quickstart as an example:

          https://github.com/jboss-switchyard/quickstarts/tree/master/camel-soap-proxy

           

          You could use an http:// URL for the WSDL instead of META-INF/ReverseService.wsdl in these two places:

          https://github.com/jboss-switchyard/quickstarts/blob/master/camel-soap-proxy/src/main/resources/META-INF/switchyard.xml#L7

          https://github.com/jboss-switchyard/quickstarts/blob/master/camel-soap-proxy/src/main/resources/META-INF/switchyard.xml#L23

           

          That would provide a dynamic WSDL for the front end of the proxy.

          • 2. Re: WS Soap Proxy
            Slava Uchitel Newbie

            camel-soap-proxy switchyard.xml file contains 5 references to WSDL. Would I need to replace alll of them with reference to remote WSDL?

            I tried to adapt that quick-start project to my own needs and replaced all WSDL references with URL to remote WSDL. Eclipse dowsn't flag any errors, but when I deploy switchyard project to JBoss, I see following in the console:

            12:49:32,730 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service

            id=org.switchyard.component.soap.endpoint.BaseWebService

            address=http://localhost:8080/dmles-esb/CatalogService

            implementor=org.switchyard.component.soap.endpoint.BaseWebService

            invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker

            serviceName={http://dmlss/ws/wsdl}CatalogService

            portName={http://dmlss/ws/wsdl}CatalogServicePort

            wsdlLocation=http://localhost:8080/dmlss-services/CatalogService?wsdl

            mtomEnabled=false

            I did not specify port for service soap binding in properties, and I assumed that it will run on the same port as JBoss (port 80). I then tried to specify port, tried few different ports but no metter what I do, address stays the same. I tried changing endpoint address - it also had no effect. How can I change port? I'd prefere it to be the same as port on which JBoss web listener listens, bit if that's not possible - I'd like it to be something else the 8080 because I have another listener on this port already (one that supplies remote WSDL and service I try to proxy).

            • 3. Re: WS Soap Proxy
              Magesh Bojan Master

              Hi,

               

              Which version of JBoss is running on port 80? When running in application server environment the port value is ignored. The endpointAddress property is to override the address for reference bindings only.

               

              https://docs.jboss.org/author/display/SWITCHYARD/SOAP

               

              For AS7 the port is changed like this in the config xml

                  <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
                      ...
                      <socket-binding name="http" port="80"/>
                      ...
                  </socket-binding-group>
              
              

               

              I tested with JBoss EAP 6.1.0.Final and it works fine.

              • 4. Re: WS Soap Proxy
                Slava Uchitel Newbie

                JBoss 7.1.1 and that's precicely why I use Switchyard and not JBoss ESB. It listens on port 80.

                Ok, I got is, modifications are for reference. What is the URL of soap listener of proxy service? App name is dmles-esb, port is 80 and service name is CatalogService. If I try http://localhost/dmles-esb/CatalogService?wsdl get "resource not found" error.

                • 5. Re: WS Soap Proxy
                  Magesh Bojan Master

                  What do you see under?

                   

                  INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service

                  • 6. Re: WS Soap Proxy
                    Slava Uchitel Newbie

                    I do not see the exact line you ask for but here are all relevant lines from JBoss server.log:

                    21:35:36,719 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-2) Add Service

                    id=org.switchyard.component.soap.endpoint.BaseWebService

                    address=http://localhost:8080/dmles-esb/CatalogService

                    implementor=org.switchyard.component.soap.endpoint.BaseWebService

                    invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker

                    serviceName={http://dmlss/ws/wsdl}CatalogService

                    portName={http://dmlss/ws/wsdl}CatalogServicePort

                    wsdlLocation=http://localhost:8080/dmlss-services/CatalogService?wsdl

                    mtomEnabled=false

                    21:35:36,813 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://dmlss/ws/wsdl}CatalogService from WSDL: http://localhost:8080/dmlss-services/CatalogService?wsdl

                    21:35:37,765 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-2) Setting new service endpoint address in wsdl: http://localhost:8080/dmlss-services/CatalogService

                    21:35:37,766 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-2) Setting new service endpoint address in wsdl: http://localhost:8080/dmles-esb/CatalogService

                    21:35:37,860 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/dmles-esb/CatalogService

                    21:35:38,281 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-2) WSDL published to: file:/C:/Projects/RTOP3/jboss-as-7.1.1.Final/standalone/data/wsdl/dmles-esb.deployment/CatalogService.wsdl

                    21:35:38,281 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-2) register: jboss.ws:context=dmles-esb,endpoint=org.switchyard.component.soap.endpoint.BaseWebService

                     

                    I assume http://localhost:8080/dmles-esb/CatalogService?wsdl is where service listener is making wsdl available (note 8080 port? jboss is on port 80), but when I hit thsis URL, i get http error 404.

                    • 7. Re: WS Soap Proxy
                      Matej Sirc Newbie

                      Hi Slava,

                      I believe that the wsdl is available on address http://localhost:8080/dmlss-services/CatalogService?wsdl as stated in the log under "wsdlLocation".

                      And since JBoss started the service on port 8080, it means that JBoss alone is running on port 8080 (and not 80). Check again your socket-binding name="http" in standalone.xml (or appropriate xml config for your domain).

                       

                      Cheers

                      • 8. Re: WS Soap Proxy
                        Magesh Bojan Master

                        Could you please attach both the boot.log and server.log?

                        • 9. Re: WS Soap Proxy
                          Slava Uchitel Newbie

                          http://localhost:8080/dmlss-services/CatalogService?wsdl is the enpoint where original service ( the one I am trying to proxy with switchyard) is published. It runs on tomcat on port 8080.

                          • 10. Re: WS Soap Proxy
                            Magesh Bojan Master

                            Along with the logs, please also attach the switchyard.xml.

                             

                            thanks,

                            Magesh

                            • 11. Re: WS Soap Proxy
                              Slava Uchitel Newbie

                              I do not see "attach file" link or button anywhere, so I'll just add hem inline as text.

                               

                              ********************************************boot.log********************************************

                              20:50:17,985 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

                              20:50:21,027 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

                              20:50:21,152 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

                              20:50:21,183 DEBUG [org.jboss.as.config] Configured system properties:

                                  awt.toolkit = sun.awt.windows.WToolkit

                                  file.encoding = Cp1252

                                  file.encoding.pkg = sun.io

                                  file.separator = \

                                  java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

                                  java.awt.printerjob = sun.awt.windows.WPrinterJob

                                  java.class.path = C:\Projects\RTOP3\jboss-as-7.1.1.Final\jboss-modules.jar

                                  java.class.version = 51.0

                                  java.endorsed.dirs = c:\Program Files\Java\jdk1.7.0\jre\lib\endorsed

                                  java.ext.dirs = c:\Program Files\Java\jdk1.7.0\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

                                  java.home = c:\Program Files\Java\jdk1.7.0\jre

                                  java.io.tmpdir = C:\Users\uchitel\AppData\Local\Temp\

                                  java.library.path = c:\Program Files\Java\jdk1.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\RA2HP\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files\Attachmate\Reflection\;c:\Temp\grails-1.3.4\grails-1.3.4\bin;c:\Program Files\Java\jdk1.7.0\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Programs\apache-maven-3.0.4\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\WinMerge;c:\Projects\RTOP3\apache-ant-1.9.0\bin;C:\Projects\RTOP3\apache-maven-3.0.5\bin;.

                                  java.net.preferIPv4Stack = true

                                  java.runtime.name = Java(TM) SE Runtime Environment

                                  java.runtime.version = 1.7.0-b147

                                  java.specification.name = Java Platform API Specification

                                  java.specification.vendor = Oracle Corporation

                                  java.specification.version = 1.7

                                  java.util.logging.manager = org.jboss.logmanager.LogManager

                                  java.vendor = Oracle Corporation

                                  java.vendor.url = http://java.oracle.com/

                                  java.vendor.url.bug = http://bugreport.sun.com/bugreport/

                                  java.version = 1.7.0

                                  java.vm.info = mixed mode

                                  java.vm.name = Java HotSpot(TM) Client VM

                                  java.vm.specification.name = Java Virtual Machine Specification

                                  java.vm.specification.vendor = Oracle Corporation

                                  java.vm.specification.version = 1.7

                                  java.vm.vendor = Oracle Corporation

                                  java.vm.version = 21.0-b17

                                  javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

                                  javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

                                  javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

                                  javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

                                  javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

                                  javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

                                  javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

                                  javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

                                  javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

                                  javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

                                  jboss.home.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final

                                  jboss.host.name = suchitel

                                  jboss.modules.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\modules

                                  jboss.modules.system.pkgs = org.jboss.byteman

                                  jboss.node.name = suchitel

                                  jboss.qualified.host.name = suchitel

                                  jboss.server.base.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone

                                  jboss.server.config.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\configuration

                                  jboss.server.data.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\data

                                  jboss.server.default.config = standalone.xml

                                  jboss.server.deploy.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\data\content

                                  jboss.server.log.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\log

                                  jboss.server.name = suchitel

                                  jboss.server.temp.dir = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\tmp

                                  line.separator =

                               

                                  logging.configuration = file:C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone/configuration/logging.properties

                                  module.path = C:\Projects\RTOP3\jboss-as-7.1.1.Final\modules

                                  org.jboss.boot.log.file = C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\log\boot.log

                                  org.jboss.resolver.warning = true

                                  org.xml.sax.driver = __redirected.__XMLReaderFactory

                                  os.arch = x86

                                  os.name = Windows Vista

                                  os.version = 6.0

                                  path.separator = ;

                                  program.name = standalone.bat

                                  sun.arch.data.model = 32

                                  sun.boot.class.path = c:\Program Files\Java\jdk1.7.0\jre\lib\resources.jar;c:\Program Files\Java\jdk1.7.0\jre\lib\rt.jar;c:\Program Files\Java\jdk1.7.0\jre\lib\sunrsasign.jar;c:\Program Files\Java\jdk1.7.0\jre\lib\jsse.jar;c:\Program Files\Java\jdk1.7.0\jre\lib\jce.jar;c:\Program Files\Java\jdk1.7.0\jre\lib\charsets.jar;c:\Program Files\Java\jdk1.7.0\jre\classes

                                  sun.boot.library.path = c:\Program Files\Java\jdk1.7.0\jre\bin

                                  sun.cpu.endian = little

                                  sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

                                  sun.desktop = windows

                                  sun.io.unicode.encoding = UnicodeLittle

                                  sun.java.command = C:\Projects\RTOP3\jboss-as-7.1.1.Final\jboss-modules.jar -mp C:\Projects\RTOP3\jboss-as-7.1.1.Final\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\Projects\RTOP3\jboss-as-7.1.1.Final

                                  sun.java.launcher = SUN_STANDARD

                                  sun.jnu.encoding = Cp1252

                                  sun.management.compiler = HotSpot Client Compiler

                                  sun.os.patch.level = Service Pack 2

                                  sun.rmi.dgc.client.gcInterval = 3600000

                                  sun.rmi.dgc.server.gcInterval = 3600000

                                  user.country = US

                                  user.dir = c:\Projects\RTOP3\jboss-as-7.1.1.Final\bin

                                  user.home = C:\Users\uchitel

                                  user.language = en

                                  user.name = uchitel

                                  user.script =

                                  user.timezone = America/New_York

                                  user.variant =

                              20:50:21,292 DEBUG [org.jboss.as.config] VM Arguments: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms512M -Xmx512M -XX:MaxPermSize=512M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.config=standalone.xml -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -Xrs -XX:+UseTLAB -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Dorg.jboss.boot.log.file=C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\log\boot.log -Dlogging.configuration=file:C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone/configuration/logging.properties

                              20:50:36,113 INFO  [org.switchyard] SwitchYard version 0.8.0.Final

                              20:50:37,127 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

                              20:50:37,174 INFO  [org.xnio] XNIO Version 3.0.3.GA

                              20:50:37,283 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

                              20:50:37,377 INFO  [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.

                              20:50:37,408 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

                               

                              ********************************************server.log********************************************

                              20:50:37,611 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 65) JBAS015537: Activating WebServices Extension

                              20:50:37,658 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 43) JBAS016200: Activating ConfigAdmin Subsystem

                              20:50:38,094 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.3.GA

                              20:50:38,266 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

                              20:50:38,687 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

                              20:50:38,968 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

                              20:50:39,436 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                              20:50:40,107 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

                              20:50:42,260 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)

                              20:50:48,718 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA

                              20:50:51,152 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-443

                              20:50:51,214 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                              20:50:51,214 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/jbpmDS]

                              20:50:51,214 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:/OracleDS]

                              20:50:51,526 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\Projects\RTOP3\jboss-as-7.1.1.Final\standalone\deployments

                              20:50:51,557 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found switchyard-bpel-console.war in deployment directory. To trigger deployment create a file called switchyard-bpel-console.war.dodeploy

                              20:50:51,588 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:9999

                              20:50:51,588 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:4447

                              20:50:53,180 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "dmlss-common.jar"

                              20:50:53,180 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "dmles-esb.jar"

                              20:50:53,180 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "switchyard-bpel-console.war"

                              20:50:53,180 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "switchyard-bpel-console-server.war"

                              20:50:54,459 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment dmles-esb.jar

                              20:50:54,818 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016005: Starting Services for CDI deployment: dmles-esb.jar

                              20:50:55,348 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900 1.1.6 (Final)

                              20:50:55,379 INFO  [org.switchyard] (MSC service thread 1-4) Deploying SwitchYard application 'dmles-esb.jar'

                              20:50:55,426 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment dmles-esb.jar

                              20:50:55,582 INFO  [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /switchyard-bpel-console

                              20:50:56,892 INFO  [org.switchyard] (MSC service thread 1-4) Starting SwitchYard service

                              20:50:57,938 INFO  [org.apache.camel.management.ManagementStrategyFactory] (MSC service thread 1-4) JMX enabled.

                              20:50:58,296 INFO  [org.switchyard.security.SecurityProvider] (MSC service thread 1-4) Using SecurityProvider implementation: org.switchyard.security.jboss.JBossJaasSecurityProvider

                              20:50:58,328 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Apache Camel 0.8.0.Final (CamelContext: camel-1) is starting

                              20:50:58,343 INFO  [org.apache.camel.management.DefaultManagementLifecycleStrategy] (MSC service thread 1-4) StatisticsLevel at All so enabling load performance statistics

                              20:50:59,856 INFO  [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-4) Loaded 179 type converters

                              20:50:59,934 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Total 0 routes, of which 0 is started.

                              20:50:59,950 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Apache Camel 0.8.0.Final (CamelContext: camel-1) started in 1.606 seconds

                              20:51:01,869 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxrs:main") which may be changed or removed in future versions without notice.

                              20:51:01,900 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxrs:main") which may be changed or removed in future versions without notice.

                              20:51:01,931 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxb-provider:main") which may be changed or removed in future versions without notice.

                              20:51:01,962 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-jaxb-provider:main") which may be changed or removed in future versions without notice.

                              20:51:02,446 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-multipart-provider:main") which may be changed or removed in future versions without notice.

                              20:51:02,477 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.switchyard-bpel-console-server.war" is using a private module ("org.jboss.resteasy.resteasy-multipart-provider:main") which may be changed or removed in future versions without notice.

                              20:51:04,084 INFO  [org.apache.camel.impl.converter.DefaultTypeConverter] (MSC service thread 1-4) Loaded 179 type converters

                              20:51:05,036 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Deploying javax.ws.rs.core.Application: class org.jboss.bpm.console.server.ConsoleServerApplication

                              20:51:05,145 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.ProcessHistoryFacade from Application javax.ws.rs.core.Application

                              20:51:05,160 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.report.ReportFacade from Application javax.ws.rs.core.Application

                              20:51:05,192 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.InfoFacade from Application javax.ws.rs.core.Application

                              20:51:05,207 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.TaskMgmtFacade from Application javax.ws.rs.core.Application

                              20:51:05,238 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.ProcessMgmtFacade from Application javax.ws.rs.core.Application

                              20:51:05,254 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.EngineFacade from Application javax.ws.rs.core.Application

                              20:51:05,285 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.FormProcessingFacade from Application javax.ws.rs.core.Application

                              20:51:05,301 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.TaskListFacade from Application javax.ws.rs.core.Application

                              20:51:05,316 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-3) Adding singleton resource org.jboss.bpm.console.server.UserMgmtFacade from Application javax.ws.rs.core.Application

                              20:51:05,784 INFO  [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /bpel-console-server

                              20:51:08,358 INFO  [org.switchyard.component.soap.OutboundHandler] (MSC service thread 1-4) Creating dispatch with WSDL http://localhost:8080/dmlss-services/CatalogService?wsdl

                              20:51:10,745 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Route: direct:{urn:switchyard-quickstart:camel-soap-proxy:1.0}CatalogWS started and consuming from: Endpoint[direct://%7Burn:switchyard-quickstart:camel-soap-proxy:1.0%7DCatalogWS]

                              20:51:10,901 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Route: route1 started and consuming from: Endpoint[switchyard://CatalogProxyService?namespace=urn%3Aswitchyard-quickstart%3Acamel-soap-proxy%3A1.0]

                              20:51:11,946 INFO  [org.switchyard.common.camel.SwitchYardCamelContext] (MSC service thread 1-4) Route: direct:{urn:switchyard-quickstart:camel-soap-proxy:1.0}PromotedCatalogProxyService started and consuming from: Endpoint[direct://%7Burn:switchyard-quickstart:camel-soap-proxy:1.0%7DPromotedCatalogProxyService]

                              20:51:13,179 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service

                              id=org.switchyard.component.soap.endpoint.BaseWebService

                              address=http://localhost:8080/dmles-esb/CatalogService

                              implementor=org.switchyard.component.soap.endpoint.BaseWebService

                              invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker

                              serviceName={http://dmlss/ws/wsdl}CatalogService

                              portName={http://dmlss/ws/wsdl}CatalogServicePort

                              wsdlLocation=http://localhost:8080/dmlss-services/CatalogService?wsdl

                              mtomEnabled=false

                              20:51:13,304 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://dmlss/ws/wsdl}CatalogService from WSDL: http://localhost:8080/dmlss-services/CatalogService?wsdl

                              20:51:13,990 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-4) Setting new service endpoint address in wsdl: http://localhost:8080/dmlss-services/CatalogService

                              20:51:14,037 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-4) Setting new service endpoint address in wsdl: http://localhost:8080/dmles-esb/CatalogService

                              20:51:14,162 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/dmles-esb/CatalogService

                              20:51:14,286 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/C:/Projects/RTOP3/jboss-as-7.1.1.Final/standalone/data/wsdl/dmles-esb.deployment/CatalogService.wsdl

                              20:51:14,318 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) register: jboss.ws:context=dmles-esb,endpoint=org.switchyard.component.soap.endpoint.BaseWebService

                              20:51:14,349 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015951: Admin console listening on http://127.0.0.1:9990

                              20:51:14,364 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 58345ms - Started 298 of 383 services (82 services are passive or on-demand)

                              20:51:14,630 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "switchyard-bpel-console.war"

                              20:51:14,645 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "switchyard-bpel-console-server.war"

                              20:51:14,661 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dmlss-common.jar"

                              20:51:14,661 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dmles-esb.jar"

                               

                              ********************************************switchyard.xml********************************************

                              <?xml version="1.0" encoding="UTF-8"?>

                              <switchyard xmlns="urn:switchyard-config:switchyard:1.0" xmlns:camel="urn:switchyard-component-camel:config:1.0" xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912" xmlns:soap="urn:switchyard-component-soap:config:1.0">

                                <sca:composite name="camel-soap-proxy" targetNamespace="urn:switchyard-quickstart:camel-soap-proxy:1.0">

                                  <sca:service name="PromotedCatalogProxyService" promote="CatalogProxyService/CatalogProxyService">

                                    <soap:binding.soap>

                                      <soap:contextMapper/>

                                      <soap:wsdl>http://localhost:8080/dmlss-services/CatalogService?wsdl</soap:wsdl>

                                      <soap:contextPath>dmles-esb</soap:contextPath>

                                      <soap:endpointAddress>http://localhost/dmles-esb/CatalogService</soap:endpointAddress>

                                    </soap:binding.soap>

                                  </sca:service>

                                  <sca:reference name="CatalogWS" multiplicity="0..1" promote="CatalogProxyService/CatalogWS">

                                    <soap:binding.soap>

                                      <soap:contextMapper/>

                                      <soap:wsdl>http://localhost:8080/dmlss-services/CatalogService?wsdl</soap:wsdl>

                                      <soap:endpointAddress>http://localhost:8080/dmlss-services/CatalogService</soap:endpointAddress>

                                    </soap:binding.soap>

                                  </sca:reference>

                                  <sca:component name="CatalogProxyService">

                                    <camel:implementation.camel>

                                      <camel:xml path="META-INF/route.xml"/>

                                    </camel:implementation.camel>

                                    <sca:service name="CatalogProxyService">

                                      <sca:interface.wsdl interface="http://localhost:8080/dmlss-services/CatalogService?wsdl=1#wsdl.porttype(CatalogWS)"/>

                                    </sca:service>

                                    <sca:reference name="CatalogWS">

                                      <sca:interface.wsdl interface="http://localhost:8080/dmlss-services/CatalogService?wsdl=1#wsdl.porttype(CatalogWS)"/>

                                    </sca:reference>

                                  </sca:component>

                                </sca:composite>

                              </switchyard>

                               

                              Thanks,

                                   Slava

                              • 12. Re: WS Soap Proxy
                                Magesh Bojan Master

                                To attach files, you will have to click on the "Use advanced editor" link on the right handside of the reply box.

                                 

                                So you are using standalone.xml configuration and something seem to be amiss there. This line

                                20:50:51,152 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-443

                                in the server log tells me that you have not enabled the port 80 at all. I suspect you have set the http port to 443.

                                 

                                You can remove the address property for PromotedCatalogProxyService in your switchyard.xml, that will not be used.

                                • 13. Re: WS Soap Proxy
                                  Magesh Bojan Master

                                  Could you please attach the standalone.xml configuration file?

                                  • 14. Re: WS Soap Proxy
                                    Slava Uchitel Newbie

                                    Standalone.xml attached. I am pretty sure port 80 is enabled since initial connection to another app that I develop on it is done with http on default port.

                                    Thanks,

                                         Slava

                                    1 2 Previous Next