1 2 3 Previous Next 43 Replies Latest reply: Dec 1, 2010 9:39 AM by Igor JStarter RSS

RiftSaw - how to invoke an external web service

Igor JStarter Novice

Hello!

 

I exposed a web service through RiftSaw. I made a test in SoapUI and it worked..

Then I tried to invoke a external web service with the same data.

I added a assign that copies the bpel web service's input to the external web service input.

 

Then I added an INVOKE and created a global partner link which I added succesfully... I see the web service (reference) in my wsdl created as part of the bpel file myprocessArtifacts.wsdl...

 

When deploying I get this output:

15:12:51,346 INFO  [BPELDeployer] Deploy: zgurE.jar relativePath=bpel-deploy.xml
15:12:51,439 INFO  [ProcessStoreImpl] Starting deployment of processes from directory "D:\KKISSWORK\jboss-5.1.0.GA\server\default\tmp\5c4o1o20-fxd1ux-gg3pf9uy-1-gg3puuqa-ct\zgurE.jar".
15:12:51,439 INFO  [ClassPathXmlApplicationContext] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@69d42b: display name [org.springframework.context.support.ClassPathXmlApplicationContext@69d42b]; startup date [Thu Nov 04 15:12:51 CET 2010]; root of context hierarchy
15:12:51,439 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [beans.xml]
15:12:51,439 INFO  [DeploymentUnitDir] Can't initialize beans.xml application context org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [beans.xml]; nested exception is java.io.FileNotFoundException: class path resource [beans.xml] cannot be opened because it does not exist for zgurE.jar
15:12:51,471 INFO  [BpelC] info: [CompilingProcess] Compiling BPEL process.
15:12:51,486 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl
15:12:51,642 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl
15:12:51,721 INFO  [WSDLRegistry] WSDL at http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl is a duplicate import, your documents should all be in different namespaces (its's not nice but will still work).
15:12:51,721 INFO  [WSDLRegistry] WSDL at http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl is already imported, this denotes a circular reference.
15:12:51,767 INFO  [ProcessStoreImpl] Process {http://samples/zgurE}zgurE-0 deployed from "{http://samples/zgurE}zgurE-0".
15:12:51,892 INFO  [CronScheduler] Cancelling PROCESS CRON jobs for: {http://samples/zgurE}zgurE-0
15:12:51,892 INFO  [CronScheduler] Scheduling PROCESS CRON jobs for: {http://samples/zgurE}zgurE-0
15:12:51,924 INFO  [JAXWSBindingContext] Activate my role endpoint: {http://samples/zgurE}zgurE:zgurEPort
15:12:51,924 INFO  [STDOUT] Retrieving document at 'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-fxd1ux-gg3pf9uy-1-gg3puuqa-ct/zgurE.jar/zgurEArtifacts.wsdl'.
15:12:51,986 INFO  [STDOUT] Retrieving document at 'http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl', relative to 'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-fxd1ux-gg3pf9uy-1-gg3puuqa-ct/zgurE.jar/zgurEArtifacts.wsdl'.
15:12:51,986 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl
15:12:52,471 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.
15:12:52,471 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.
15:12:52,502 INFO  [WSDLFilePublisher] WSDL published to: file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/data/wsdl/riftsaw-27f52c14-8dc2-419e-8f38-5efe0144f3e9.war/zgurEArtifacts.wsdl
15:12:52,533 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=bpel,endpoint=Endpoint-27f52c14-8dc2-419e-8f38-5efe0144f3e9
15:12:52,564 INFO  [DefaultEndpointRegistry] remove: jboss.ws:context=bpel,endpoint=Endpoint-27f52c14-8dc2-419e-8f38-5efe0144f3e9
15:12:52,564 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-27f52c14-8dc2-419e-8f38-5efe0144f3e9.war/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.web.deployment:war=/bpel

 

Can somebody help me pleasE?

 

Or tell me how you invoked a external webservice from bpel ?

 

Tnx in advance!

 

BR, Igor!

  • 1. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    Hi Igor

     

    There is an example of invoking an external web service in the riftsaw/samples/quickstart/simple_invoke.

     

    From the log messages, it looks like you have a WSDL import statement that uses a http: URL. Apache ODE does not allow wsdls to be imported from such URLs. You need to store a copy of the WSDL locally and reference it using a relative path.

     

    Regards

    Gary

  • 2. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    Thank you for your answer!

     

    I copied the wsdl and made it validate... Still I get almost the same logs:

    17:10:47,774 INFO  [BPELDeployer] Deploy: zgurE.jar relativePath=bpel-deploy.xml
    17:10:47,961 INFO  [ProcessStoreImpl] Starting deployment of processes from directory "D:\KKISSWORK\jboss-5.1.0.GA\server\default\tmp\5c4o1o20-fxd1ux-gg3pf9uy-1-gg3u2ixq-d4\zgurE.jar".
    17:10:47,961 INFO  [ClassPathXmlApplicationContext] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@c1f258: display name [org.springframework.context.support.ClassPathXmlApplicationContext@c1f258]; startup date [Thu Nov 04 17:10:47 CET 2010]; root of context hierarchy
    17:10:47,961 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [beans.xml]
    17:10:47,961 INFO  [DeploymentUnitDir] Can't initialize beans.xml application context org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [beans.xml]; nested exception is java.io.FileNotFoundException: class path resource [beans.xml] cannot be opened because it does not exist for zgurE.jar
    17:10:47,977 INFO  [BpelC] info: [CompilingProcess] Compiling BPEL process.
    17:10:48,008 WARN  [BpelObjectFactory] Unrecognized element in BPEL dom: import
    17:10:48,008 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl
    17:10:48,414 INFO  [ProcessStoreImpl] Process {http://samples/zgurE}zgurE-0 deployed from "{http://samples/zgurE}zgurE-0".
    17:10:48,508 INFO  [CronScheduler] Cancelling PROCESS CRON jobs for: {http://samples/zgurE}zgurE-0
    17:10:48,508 INFO  [CronScheduler] Scheduling PROCESS CRON jobs for: {http://samples/zgurE}zgurE-0
    17:10:48,508 INFO  [JAXWSBindingContext] Activate my role endpoint: {http://samples/zgurE}zgurE:zgurEPort
    17:10:48,508 INFO  [STDOUT] Retrieving document at 'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-fxd1ux-gg3pf9uy-1-gg3u2ixq-d4/zgurE.jar/RectangleCalculator.wsdl'.
    17:10:48,524 INFO  [STDOUT] Retrieving document at 'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-fxd1ux-gg3pf9uy-1-gg3u2ixq-d4/zgurE.jar/zgurEArtifacts.wsdl'.
    17:10:48,586 INFO  [STDOUT] Retrieving document at 'http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl', relative to 'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-fxd1ux-gg3pf9uy-1-gg3u2ixq-d4/zgurE.jar/zgurEArtifacts.wsdl'.
    17:10:48,602 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl
    17:10:49,727 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.
    17:10:49,727 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.
    17:10:49,727 INFO  [WSDLFilePublisher] WSDL published to: file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/data/wsdl/riftsaw-51f86c91-bc24-45c6-8e27-8a20ac1973f1.war/zgurEArtifacts.wsdl
    17:10:49,774 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=bpel,endpoint=Endpoint-51f86c91-bc24-45c6-8e27-8a20ac1973f1
    17:10:49,805 INFO  [DefaultEndpointRegistry] remove: jboss.ws:context=bpel,endpoint=Endpoint-51f86c91-bc24-45c6-8e27-8a20ac1973f1
    17:10:49,805 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-51f86c91-bc24-45c6-8e27-8a20ac1973f1.war/ state=PreReal mode=Manual requiredState=Real

     

    I changed the original wsdl start <wsdl:definitions> to <definitions> 'cause I get the:The prefix "wsdl" for element "wsdl:definitions" is not bound.

    But probably thats not the point...

     

    Original: http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl'

     

    Mine:

    <?xml version="1.0" encoding="utf-8" ?>
    <definitions targetNamespace="http://rectangle.bple.tps"
                xmlns='http://schemas.xmlsoap.org/wsdl/'
                xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
                xmlns:xsd='http://www.w3.org/2001/XMLSchema'
                xmlns:impl='http://rectangle.bple.tps' >

     

     


    <!--
    WSDL created by Apache Axis version: 1.4
    Built on Apr 22, 2006 (06:55:48 PDT)

    -->

     

    <types>

     

    <xs:schema elementFormDefault="qualified" targetNamespace="http://rectangle.bple.tps" xmlns:impl='http://rectangle.bple.tps' xmlns:xs='http://www.w3.org/2001/XMLSchema'>

     

    <xs:element name="area">

     

    <xs:complexType>

     

    <xs:sequence>
    <xs:element name="h" type="xsd:double"/>
    <xs:element name="b" type="xsd:double"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>

     

    <xs:element name="areaResponse">

     

    <xs:complexType>

     

    <xs:sequence>
    <xs:element name="areaReturn" type="xsd:double"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>

    </types>

     

    <message name="areaRequest">
    <part element="impl:area" name="parameters"/>
    </message>

     

    <message name="areaResponse">
    <part element="impl:areaResponse" name="parameters"/>
    </message>

     

    <portType name="RectangleCalculator">

     

    <operation name="area">
    <input message="impl:areaRequest" name="areaRequest"/>
    <output message="impl:areaResponse" name="areaResponse"/>
    </operation>
    </portType>

     

    <binding name="RectangleCalculatorSoapBinding" type="impl:RectangleCalculator">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

     

    <operation name="area">
    <soap:operation soapAction=""/>

     

    <input name="areaRequest">
    <soap:body use="literal"/>
    </input>

     

    <output name="areaResponse">
    <soap:body use="literal"/>
    </output>
    </operation>
    </binding>

     

    <service name="RectangleCalculatorService">

     

    <port binding="impl:RectangleCalculatorSoapBinding" name="RectangleCalculator">
    <soap:address location="http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator"/>
    </port>
    </service>
    </definitions>

     

    I hope you'll reply...)  This partner links are making me crazy .) I think if i'll do one external webservice call, i could easily make my whole project, but i'm, stuck.

  • 3. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    I thought i should solve this problem:

    17:10:49,805 ERROR [AbstractKernelController] Error installing to Real:  name=vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-51f86c91-bc24-45c6-8e27-8a20ac1973f1.war/  state=PreReal mode=Manual requiredState=Real

     

    And found a thread here where they say i should look at the JBossWS-Installation.

    But that works! On http://localhost:8080/jbossws/services i see my deployed services and when i invoke them, the data refreshes...

     

    So... can I exclude the JbossWS problem ?

  • 4. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    You still have the error:

     

    Igor JStarter wrote:


    17:10:48,008 FATAL [DefaultResourceFinder] openResource: invalid scheme (should be urn:)  http://157.159.110.224:9000/RectangleComputation/services/RectangleCalculator?wsdl

     

    which means you must still have a WSDL import in your WSDL or BPEL files that specify this URL. You need to make sure that all URLs are changed to reference the local WSDL.

     

    Regards

    Gary

  • 5. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    You were right!   (but that means, if the wsdl uses an external xsd, i had to import the xsd too .... but it worked)

     

    Now i don't get this FATAL [DefaultResourceFinder] openResource anymore !

     

    But still the deploy fails at the list line:

    17:10:49,805 ERROR [AbstractKernelController] Error installing to Real:    name=vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-51f86c91-bc24-45c6-8e27-8a20ac1973f1.war/   state=PreReal mode=Manual requiredState=Real

  • 6. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    Are there any errors in the log that might indicate what the problem is?

     

    If not you may have to attach your project.

     

    Regards

    Gary

  • 7. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    No other errors...

    I messed up my projects... and always when i add a partner link my service in artifacts.WSDL erases the params...

    so instead of request and response there says element or type undefined..

     

    I will post my project when i make a fresh one ready to deploy...

     

    One project is still without errors... just one string web service... (imported wsdl and xsd)

     

    11:50:56,364 INFO  [ProcessStoreImpl] Starting  deployment of processes from directory  "D:\KKISSWORK\jboss-5.1.0.GA\server\default\tmp\5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr\zgurF.jar".

    11:50:56,364 INFO  [ClassPathXmlApplicationContext]  Refreshing  org.springframework.context.support.ClassPathXmlApplicationContext@559ced:  display name  [org.springframework.context.support.ClassPathXmlApplicationContext@559ced];  startup date [Fri Nov 05 11:50:56 CET 2010]; root of context hierarchy

    11:50:56,364 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [beans.xml]

    11:50:56,364  INFO  [DeploymentUnitDir] Can't initialize beans.xml application  context org.springframework.beans.factory.BeanDefinitionStoreException:  IOException parsing XML document from class path resource [beans.xml];  nested exception is java.io.FileNotFoundException: class path resource  [beans.xml] cannot be opened because it does not exist for zgurF.jar

    11:50:56,395 INFO  [BpelC] info: [CompilingProcess] Compiling BPEL process.

    11:50:56,723 INFO  [ProcessStoreImpl] Process {http://samples/zgurF}zgurF-0 deployed from "{http://samples/zgurF}zgurF-0".

    11:50:56,723 WARN  [ProcessStoreImpl] Database out of synch for DU zgurF

    11:50:56,926 INFO  [CronScheduler] Cancelling PROCESS CRON jobs for: {http://samples/zgurF}zgurF-0

    11:50:56,926 INFO  [CronScheduler] Scheduling PROCESS CRON jobs for: {http://samples/zgurF}zgurF-0

    11:50:56,957 INFO  [JAXWSBindingContext] Activate my role endpoint: {http://samples/zgurF}zgurF:zgurFPort

    11:50:56,957  INFO  [STDOUT] Retrieving document at  'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr/zgurF.jar/OneStringService.wsdl'.

    11:50:56,973  INFO  [STDOUT] Retrieving schema at 'OneStringService.xsd', relative to   'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr/zgurF.jar/OneStringService.wsdl'.

    11:50:56,973  INFO  [STDOUT] Retrieving document at  'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr/zgurF.jar/zgurFArtifacts.wsdl'.

    11:50:56,973  INFO  [STDOUT] Retrieving document at 'OneStringService.wsdl', relative  to  'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr/zgurF.jar/zgurFArtifacts.wsdl'.

    11:50:56,973  INFO  [STDOUT] Retrieving schema at 'OneStringService.xsd', relative to   'file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/5c4o1o20-hf1h2v-gg4xhn3g-1-gg4y315v-cr/zgurF.jar/OneStringService.wsdl'.

    11:50:57,442 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.

    11:50:57,442 WARN  [WSDL11Reader] UsingAddressing extensibility element not supported yet.

    11:50:57,457  INFO  [WSDLFilePublisher] WSDL published to:  file:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/data/wsdl/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/zgurFArtifacts.wsdl

    11:50:57,567  INFO  [DefaultEndpointRegistry] register:  jboss.ws:context=bpel,endpoint=Endpoint-45fd06ec-306f-4f88-a34c-ea48e40e0fce

    11:50:57,582 WARN  [AbstractDeploymentContext] Unable to register deployment mbean jboss.web.deployment:war=/bpel

    javax.management.InstanceAlreadyExistsException:  jboss.deployment:id="jboss.web.deployment:war=/bpel",type=Component  already registered.

        at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)

        at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)

        at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

        at java.lang.reflect.Method.invoke(Unknown Source)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

        at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)

        at java.security.AccessController.doPrivileged(Native Method)

        at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)

        at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)

        at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.registerMBeans(AbstractDeploymentContext.java:1030)

        at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.addComponent(AbstractDeploymentContext.java:722)

        at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.addComponent(AbstractDeploymentUnit.java:251)

        at org.jboss.system.deployers.ServiceDeploymentDeployer.addServiceComponent(ServiceDeploymentDeployer.java:62)

        at org.jboss.system.deployers.ServiceDeploymentDeployer$ServiceMetaDataVisitor.deploy(ServiceDeploymentDeployer.java:150)

        at org.jboss.system.deployers.ServiceDeploymentDeployer$ServiceMetaDataVisitor.deploy(ServiceDeploymentDeployer.java:141)

        at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)

        at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.deployComponents(AbstractComponentDeployer.java:102)

        at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:82)

        at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

        at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:552)

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:174)

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92)

        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:606)

        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:354)

        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:586)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:58)

         at  org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:641)

        at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:618)

        at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:624)

        at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:302)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:176)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:103)

    11:50:57,614  INFO  [DefaultEndpointRegistry] remove:  jboss.ws:context=bpel,endpoint=Endpoint-45fd06ec-306f-4f88-a34c-ea48e40e0fce

    11:50:57,614  ERROR [AbstractKernelController] Error installing to Real:  name=vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/  state=PreReal mode=Manual requiredState=Real

    org.jboss.deployers.spi.DeploymentException: Error deploying: jboss.web.deployment:war=/bpel

        at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

        at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:118)

        at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)

        at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

        at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

        at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

        at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:552)

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:174)

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92)

        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:606)

        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:354)

        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:586)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:58)

         at  org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:641)

        at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:618)

        at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:624)

        at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:302)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:176)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:103)

    Caused by: java.lang.IllegalStateException: jboss.web.deployment:war=/bpel is already installed.

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:716)

        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)

        at org.jboss.system.ServiceController.doInstall(ServiceController.java:670)

        at org.jboss.system.ServiceController.install(ServiceController.java:273)

        at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:90)

        ... 30 more

    11:50:57,629 WARN  [ProcessStoreImpl] Deployment failed within the engine, store undeploying process.

    org.apache.ode.bpel.iapi.ContextException: Failed to activate endpoint

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:97)

        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:606)

        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:354)

        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:586)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:58)

         at  org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:641)

        at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:618)

        at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:624)

        at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:302)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:176)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:103)

    Caused by: org.jboss.soa.bpel.runtime.ws.EndpointManagementException: Failed to create endpoint

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:194)

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92)

        ... 11 more

    Caused  by: org.jboss.deployers.client.spi.IncompleteDeploymentException:  Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

     

    *** DEPLOYMENTS IN ERROR: Name -> Error

     

    vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/  -> org.jboss.deployers.spi.DeploymentException: Error deploying:  jboss.web.deployment:war=/bpel

     

     

    DEPLOYMENTS IN ERROR:

     

       Deployment  "vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/"  is in error due to the following reason(s):  java.lang.IllegalStateException: jboss.web.deployment:war=/bpel is  already installed.

     

        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)

        at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:565)

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:174)

        ... 12 more

    11:50:57,629 ERROR [RiftSawProcessStore] Unknown error

    org.apache.ode.bpel.iapi.ContextException: Failed to activate endpoint

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:97)

        at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:606)

        at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:354)

        at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:586)

        at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:58)

         at  org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:641)

        at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:618)

        at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:624)

        at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:302)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:176)

        at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:103)

    Caused by: org.jboss.soa.bpel.runtime.ws.EndpointManagementException: Failed to create endpoint

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:194)

        at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92)

        ... 11 more

    Caused  by: org.jboss.deployers.client.spi.IncompleteDeploymentException:  Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

     

    *** DEPLOYMENTS IN ERROR: Name -> Error

     

    vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/  -> org.jboss.deployers.spi.DeploymentException: Error deploying:  jboss.web.deployment:war=/bpel

     

     

    DEPLOYMENTS IN ERROR:

     

       Deployment  "vfsfile:/D:/KKISSWORK/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-45fd06ec-306f-4f88-a34c-ea48e40e0fce.war/"  is in error due to the following reason(s):  java.lang.IllegalStateException: jboss.web.deployment:war=/bpel is  already installed.

     

        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)

        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)

        at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:565)

        at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:174)

        ... 12 more

  • 8. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    Looks like you have more than one BPEL process that has a URL starting with 'bpel/....'. The first part of the URL must be unique across all web services.

     

    ODE uses Axis, which requires all BPEL process's web services to be referenced using a URL with a base context of "ode/". RiftSaw uses JAX-WS, so all web services are not made available through a single servlet, and therefore each must have a unique web context.

     

    Regards

    Gary

  • 9. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    I don't believe it... IT LOOKS LIKE IT'S WORKING !!!

     

    Give me some time/hours to realize.) I hope I want post for today anymore

     

    Just a question... I test the service in SoapUI. There I see 2 ports - 2 requests...

    One is my BPEL web service...

    Second is the service I'm calling from BPEL...

     

    Is this ok? Can i made the second one not visible for partners? ... it's not their bussiness

     

    What i know up to know.. If I want to execute some JAVA code in BPEL, the only way is to write the JAVA code as WEB SERVICE to execute..

    So, everyone would see all my JAVA methods....

     

     

    THANK YOU Gary Brown !!!

  • 10. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    Igor JStarter wrote:

     

    Just a question... I test the service in SoapUI. There I see 2 ports - 2 requests...

    One is my BPEL web service...

    Second is the service I'm calling from BPEL...

     

    Is this ok? Can i made the second one not visible for partners? ... it's not their bussiness

     

    SoapUI should only show the ports that are part of the service in your wsdl, so if you have two separate services and therefore wsdls, then you only need to provide access to the public WSDL. I might be misunderstanding, so it would be useful to see the WSDL for your main public service.

     

    In terms of protecting the service from external use, the only option may be to deploy the main service to a server that is publicly accessible, and put the other web service on an internal server that can only be accessed by your internal network.

     

    Igor JStarter wrote:

     

    What i know up to know.. If I want to execute some JAVA code in BPEL, the only way is to write the JAVA code as WEB SERVICE to execute..

    So, everyone would see all my JAVA methods....


     

    Best way is to implement a JAX-WS service, and only expose the methods you want used externally in the Java API for the web service.

     

    Regards

    Gary

  • 11. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    How I'm doing the BPEL project:

     

    First i copy the (local copy) wsdl to the bpelContent directory.

     

    When I make a new BPEL process file, i get the .bpel and .wsdl...

    This WSDL is the web service, that i want to expose to my partners... -> let say myprojectnameArtifacts.wsdl.

     

    If i got you previous reply right, for BPEL everything should be a WS call no matter if I want to call a partners external JAX-WS service or

    execute some java code (the easiest way is again... expose it as JAX-WS) I have to call a web service - wsdl.

     

    For every JAX-WS  I'm calling I have to add an import to the WSDL (the import is generated if I just add an invoke to my bpel process).

    And my SoapUI test (for myprojectnameArtifacts.wsdl ... which imports my partners JAX-WS) showed me, that I can call both, my projectnameService and my partners JAX-WS. Like I exposed my and my partners service through the myprojectnameArtifacts.wsdl.

     

    So that is my reply to the WSDL question... I my myprojectnameArtifacts.wsdl there is nothing to see for the partners JAX-WS, just the import line

    <import location="OneStringService.wsdl" namespace="http://onestring.si/"/>. But that exposes the partners methods !

     

    That is what I didn't like when i test it..

  • 12. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    I wrote too much .)

     

    U're teeling me that if a WSDL imports a second WSDL, the methods of both are visible... for let say SoapUI.

    But I can make the methods of the second WSDL not accesible ...

     

    That's the way ...

  • 13. Re: RiftSaw - how to invoke an external web service
    Gary Brown Master

    Is it necessary to import the partner service's wsdl?

     

    If you are just sharing type definitions, then it may be better to place them in a separate file that they both reference.

     

    Regards

    Gary

  • 14. Re: RiftSaw - how to invoke an external web service
    Igor JStarter Novice

    Oooo I see... SoapUI isn't getting a response from the partners method(exposed because of the bpel import) anyway...

     

    So I'm able now to expose a web service which calls other services and actually do something more that you add a string...THANKS!

     

    Thinking loud :

     

    I need 2 web services...

     

    1. A partner needs to pass some parameters which i almost forward to a second partner.

    I can do everything in BPEL. Do the WSDL, add just some ASSIGN and one INVOKE of the partners service...

    Then I need to return a string which consists of a date + iterator. I think I can't get the DATE in bpel. So I will need to write an additional JAX-WS and invoke it... Then return the myJAX-WS response to the partner (who invoked my main service).

     

    2. A partner needs to pass some parameters, which I have to check and then write to DB and a file...

    Writting to DB and writing to FILE needs again a JAX-WS who will do that...

     

    I wasn't able to expose that just over JBossESB, but I can do it now just over BPEL.

    I think that in a complex scenario, ESB and RiftSaw should be mixed.I think the ESB should be similar to BPEL editor, where I would add/remove my BPELs... For my project I don't see I way to connect them ...

1 2 3 Previous Next