11 Replies Latest reply on May 4, 2006 5:39 AM by Koen Aers

    Problems deploying a BPEL process archive

    Nicholas Capito Newbie

      Hello all i am trying to deploy a very simple process archive. When i go to use the ant deploy process task here is the error i am getting.


      DeployServlet: deploying process archive: file:/C:/Nicks_Temp/Projects/BPELWorkspace/build/FusionWriter.par
      2006-05-01 13:40:00,937 DEBUG [org.jbpm.bpel.xml.ImportWsdlLocator] upgraded wsdl document: fusion.wsdl
      2006-05-01 13:40:00,937 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-bpel].[DeployServlet]] Servlet.service() for servlet DeployServlet threw exception
      java.lang.AbstractMethodError
      at com.ibm.wsdl.xml.WSDLReaderImpl.parseExtensibilityAttributes(WSDLReaderImpl.java:1285)
      at com.ibm.wsdl.xml.WSDLReaderImpl.parseInput(WSDLReaderImpl.java:1829)
      at com.ibm.wsdl.xml.WSDLReaderImpl.parseOperation(WSDLReaderImpl.java:1477)
      at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(WSDLReaderImpl.java:1421)
      at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:310)
      at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2133)
      at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2125)
      at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2150)
      at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2171)
      at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2201)
      at org.jbpm.bpel.xml.BpelReader.readWsdlDocument(BpelReader.java:338)
      at org.jbpm.bpel.par.DefinitionDescArchiveParser.readDocuments(DefinitionDescArchiveParser.java:68)
      at org.jbpm.bpel.par.DefinitionDescArchiveParser.readFromArchive(DefinitionDescArchiveParser.java:40)
      at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:46)
      at org.jbpm.bpel.web.deploy.DeployServlet.doGet(DeployServlet.java:45)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
      at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:54)
      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
      at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
      at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
      at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
      at java.lang.Thread.run(Thread.java:595)


      jboss 4.0.4
      bpel 4.0.2



      anyone got any ideas?



      Let me know if i need to provide some more info


      Thanks in advance

        • 1. Re: Problems deploying a BPEL process archive
          Alejandro Guizar Master

          jbpm bpel alpha 4 was only tested against jboss 4.0.2 and 4.0.3. Version 4.0.4 was not out there yet. It upgraded wsdl4j from 1.4 to 1.5.2 which is not fully compatible with the previous release.

          Please either use jboss 4.0.3 or wait for the upcoming jbpm bpel beta 1 release.

          • 2. Re: Problems deploying a BPEL process archive
            Nicholas Capito Newbie

            I would do that but the problem is 4.0.4 seems to be the only server that excepts by webservice packing. I have a webservice that i thought was packed right. But if i try to use any lower version of JBoss it will not deploy it. Here is the error i get:

            2006-05-01 14:04:57,968 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:57,968 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:57,968 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war -> C:\Nicks_temp\jboss-4.0.3SP1\server\all\tmp\deploy\tmp62597SimpleMessageWS.war
            2006-05-01 14:04:57,968 DEBUG [org.jboss.deployment.MainDeployer] using deployer MBeanProxyExt[jboss.web:service=WebServer]
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Begin init
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Unpacking war to: C:\Nicks_temp\jboss-4.0.3SP1\server\all\tmp\deploy\tmp62597SimpleMessageWS-exp.war
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Replaced war with unpacked contents
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] webContext: null
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] warURL: file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/
            2006-05-01 14:04:57,984 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.init,SimpleMessageWS.war
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] End init
            2006-05-01 14:04:57,984 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
            2006-05-01 14:04:57,984 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/
            2006-05-01 14:04:57,984 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@3570b0, cl=org.jboss.mx.loading.UnifiedClassLoader3@f61227{ url=file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/ ,addedOrder=0}
            2006-05-01 14:04:57,984 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@3570b0, cl=org.jboss.mx.loading.UnifiedClassLoader3@f61227{ url=file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/ ,addedOrder=0}
            2006-05-01 14:04:57,984 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@f61227{ url=file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/ ,addedOrder=0}
            2006-05-01 14:04:57,984 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:57,984 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:57,984 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:57,984 DEBUG [org.jboss.system.ServiceController] Creating service jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:57,984 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: []
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.WebModule] Creating jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:57,984 DEBUG [org.jboss.web.WebModule] Created jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:57,984 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365 dependents are: []
            2006-05-01 14:04:57,984 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.create,SimpleMessageWS.war
            2006-05-01 14:04:58,046 ERROR [org.jboss.webservice.ServiceDeployer] Cannot startup webservice for: SimpleMessageWS.war
            org.jboss.deployment.DeploymentException: Cannot obtain webservices meta data; - nested throwable: (org.jboss.xb.binding.JBossXBException: Failed to parse source.)
            at org.jboss.webservice.ServiceDeployer.parseWebservicesXML(ServiceDeployer.java:348)
            at org.jboss.webservice.ServiceDeployer.createWebservice(ServiceDeployer.java:163)
            at org.jboss.webservice.ServiceDeployerJSE.createWebservice(ServiceDeployerJSE.java:95)
            at org.jboss.webservice.ServiceDeployer.handleNotification(ServiceDeployer.java:108)
            at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:138)
            at $Proxy47.handleNotification(Unknown Source)
            at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotification(JBossNotificationBroadcasterSupport.java:112)
            at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotification(JBossNotificationBroadcasterSupport.java:95)
            at org.jboss.deployment.SubDeployerSupport.emitNotification(SubDeployerSupport.java:325)
            at org.jboss.deployment.SubDeployerSupport.create(SubDeployerSupport.java:282)
            at org.jboss.web.AbstractWebContainer.create(AbstractWebContainer.java:381)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
            at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
            at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
            at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
            at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
            at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:80)
            at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
            at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
            at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
            at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
            at $Proxy44.create(Unknown Source)
            at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
            at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
            at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
            at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
            at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
            at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
            at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
            at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
            at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
            at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
            at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
            at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
            at $Proxy9.deploy(Unknown Source)
            at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
            at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
            at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
            at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203)
            at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182)
            Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source.
            at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:138)
            at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:173)
            at org.jboss.webservice.ServiceDeployer.parseWebservicesXML(ServiceDeployer.java:339)
            ... 49 more
            Caused by: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'service-impl-beam'. One of '{"http://java.sun.com/xml/ns/j2ee":service-impl-bean}' is expected. @ *unknown*[14,23]
            at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:232)
            at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
            at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
            at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
            at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
            at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
            at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
            at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
            at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
            at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
            at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
            at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
            at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
            at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
            at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
            at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
            at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:134)
            ... 51 more
            2006-05-01 14:04:58,062 DEBUG [org.jboss.deployment.MainDeployer] Undeploying file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/deploy/SimpleMessageWS.war
            2006-05-01 14:04:58,062 DEBUG [org.jboss.system.ServiceController] stopping service: jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:58,062 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.stop,SimpleMessageWS.war
            2006-05-01 14:04:58,062 DEBUG [org.jboss.system.ServiceController] destroying service: jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:58,062 DEBUG [org.jboss.system.ServiceController] destroying dependent services for: jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365 dependent services are: []
            2006-05-01 14:04:58,062 DEBUG [org.jboss.web.WebModule] Destroying jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:58,062 DEBUG [org.jboss.web.WebModule] Destroyed jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:58,062 DEBUG [org.jboss.system.ServiceController] removing service: jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365
            2006-05-01 14:04:58,062 DEBUG [org.jboss.system.ServiceController] removing already unregistered jboss.web.deployment:war=SimpleMessageWS.war,id=-1106267365 from server
            2006-05-01 14:04:58,062 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.destroy,SimpleMessageWS.war
            2006-05-01 14:04:58,062 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3@f61227{ url=file:/C:/Nicks_temp/jboss-4.0.3SP1/server/all/tmp/deploy/tmp62597SimpleMessageWS-exp.war/ ,addedOrder=48}




            I am 90% sure everything is packaged right. So i am not sure why it isn't working.

            • 3. Re: Problems deploying a BPEL process archive
              Alejandro Guizar Master

              Errr... take a look at the stack trace. You used the tag service-impl-beam instead of service-impl-bean in your webservices.xml deployment descriptor. The location path for the related element is:

              /webservices/webservice-description/port-component/service-impl-bean


              • 4. Re: Problems deploying a BPEL process archive
                Nicholas Capito Newbie

                I thank you for your help... why didn't this error on 4.0.4?

                • 5. Re: Problems deploying a BPEL process archive
                  Nicholas Capito Newbie

                  I am so close!!!! I have everything packaged and i am to the point of deploying my process archive and this is the error i get:


                  2006-05-02 08:09:12,671 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-bpel]] DeployServlet: deploying process archive: file:/C:/Nicks_Temp/Projects/BPELWorkspace/build/FusionWriter.par
                  2006-05-02 08:09:12,671 DEBUG [org.jbpm.bpel.xml.util.LocalEntityResolver] bpel_definition_1_0.xsd maps to URL: jar:file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp21516jbpm-bpel.sar-contents/jbpm-bpel-1.0-alpha4.jar!/org/jbpm/bpel/xml/util/bpel_definition_1_0.xsd
                  2006-05-02 08:09:12,687 DEBUG [org.jboss.webservice.server.ServiceEndpointServletJSE] doGet: http://137.51.88.82:8080/SimpleMessageWS/SimpleWriter?wsdl
                  2006-05-02 08:09:12,687 DEBUG [org.jboss.webservice.server.ServiceEndpointServletJSE] Set transport.url=/SimpleMessageWS/SimpleWriter
                  2006-05-02 08:09:12,687 DEBUG [org.jboss.webservice.server.ServiceEndpointServletJSE] Process wsdl request
                  2006-05-02 08:09:12,687 DEBUG [org.jbpm.bpel.xml.ImportWsdlLocator] upgraded wsdl document: http://137.51.88.82:8080/SimpleMessageWS/SimpleWriter?wsdl
                  2006-05-02 08:09:12,703 INFO [org.jbpm.bpel.xml.BpelReader] read wsdl definitions: http://137.51.88.82:8080/SimpleMessageWS/SimpleWriter?wsdl
                  2006-05-02 08:09:12,703 DEBUG [org.jbpm.bpel.xml.ImportWsdlLocator] upgraded wsdl document: fusion.wsdl
                  2006-05-02 08:09:12,703 INFO [org.jbpm.bpel.xml.BpelReader] read wsdl definitions: fusion.wsdl
                  2006-05-02 08:09:12,703 DEBUG [org.jbpm.bpel.xml.util.LocalEntityResolver] bpel_1_1.xsd maps to URL: jar:file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp21516jbpm-bpel.sar-contents/jbpm-bpel-1.0-alpha4.jar!/org/jbpm/bpel/xml/util/bpel_1_1.xsd
                  2006-05-02 08:09:12,703 DEBUG [org.jbpm.bpel.xml.util.LocalEntityResolver] wsdl.xsd maps to URL: jar:file:/C:/Nicks_temp/jboss-4.0.2/server/all/tmp/deploy/tmp21516jbpm-bpel.sar-contents/jbpm-bpel-1.0-alpha4.jar!/org/jbpm/bpel/xml/util/wsdl.xsd
                  2006-05-02 08:09:12,734 DEBUG [org.jbpm.bpel.xml.BpelReader] upgraded bpel document: fusionWriter.bpel
                  2006-05-02 08:09:12,734 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm-bpel].[DeployServlet]] Servlet.service() for servlet DeployServlet threw exception
                  java.lang.NullPointerException
                  at org.jbpm.bpel.xml.BpelReader.getPortType(BpelReader.java:817)
                  at org.jbpm.bpel.xml.InvokeReader.readInvoker(InvokeReader.java:85)
                  at org.jbpm.bpel.xml.InvokeReader.readActivity(InvokeReader.java:72)
                  at org.jbpm.bpel.xml.ActivityReader.read(ActivityReader.java:39)
                  at org.jbpm.bpel.xml.InvokeReader.read(InvokeReader.java:36)
                  at org.jbpm.bpel.xml.BpelReader.readActivity(BpelReader.java:935)
                  at org.jbpm.bpel.xml.SequenceReader.readActivity(SequenceReader.java:27)
                  at org.jbpm.bpel.xml.ActivityReader.read(ActivityReader.java:39)
                  at org.jbpm.bpel.xml.BpelReader.readActivity(BpelReader.java:935)
                  at org.jbpm.bpel.xml.BpelReader.readScope(BpelReader.java:417)
                  at org.jbpm.bpel.xml.BpelReader.read(BpelReader.java:207)
                  at org.jbpm.bpel.xml.BpelReader.read(BpelReader.java:163)
                  at org.jbpm.bpel.par.BpelArchiveParser.readFromArchive(BpelArchiveParser.java:28)
                  at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:46)
                  at org.jbpm.bpel.web.deploy.DeployServlet.doGet(DeployServlet.java:45)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
                  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
                  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                  at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
                  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
                  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
                  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
                  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
                  at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
                  at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
                  at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
                  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
                  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
                  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
                  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
                  at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
                  at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
                  at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
                  at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
                  at java.lang.Thread.run(Thread.java:595)



                  I believe the error is in my callerLink here is the WSDL:

                  <?xml version="1.0" encoding="UTF-8"?>
                  
                  <definitions name="FusionCallerService"
                   targetNamespace="http://webservice" xmlns:tns="http://webservice"
                   xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
                   xmlns="http://schemas.xmlsoap.org/wsdl/"
                   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                   xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
                   xmlns:java="http://schemas.xmlsoap.org/wsdl/java/">
                  
                  <plnk:partnerLinkType name="callerLink">
                   <plnk:role name="callerService">
                   <plnk:portType name="tns:FusionCaller" />
                   </plnk:role>
                  </plnk:partnerLinkType>
                  
                  
                   <types />
                   <message name="requestMessage">
                   <part name="msg" type="xsd:string" />
                   </message>
                   <message name="responseMessage">
                   <part name="msg" type="xsd:int" />
                   </message>
                  
                   <portType name="FusionCaller">
                   <operation name="createFusionProcess">
                   <input message="tns:requestMessage" />
                   <output message="tns:responseMessage" />
                   </operation>
                   </portType>
                  
                   </definitions>


                  Here is my bpel:

                  <?xml version="1.0" encoding="UTF-8"?>
                  <process name="FusionProcess" targetNamespace="http://webservice"
                   xmlns:tns="http://webservice"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
                   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                   xsi:schemaLocation="http://schemas.xmlsoap.org/ws/2003/03/business-process/
                   http://schemas.xmlsoap.org/ws/2003/03/business-process/"
                  >
                  
                  
                   <partnerLinks>
                   <partnerLink name="writer" partnerLinkType="tns:writeLink" myRole="writeService"/>
                   <partnerLink name="caller" partnerLinkType="tns:callerLink" myRole="callerService"/>
                   </partnerLinks>
                  
                   <variables>
                   <variable name="request" messageType="tns:requestMessage"/>
                   <variable name="response" messageType="tns:responseMessage"/>
                   <variable name="writeVariable" messageType="tns:SimpleFileWriter_writeMessage"/>
                   <variable name="writeResponse" messageType="tns:SimpleFileWriter_writeMessageResponse"/>
                   </variables>
                   <sequence name="FusionWriteSequence">
                   <receive operation="createFusionProcess" partnerLink="caller" portType="tns:FusionCaller"
                   createInstance="yes" variable="request"/>
                   <assign name="copyRequest">
                   <copy>
                   <from variable="request" part="msg"/>
                   <to variable="writeVariable" part="String_1"/>
                   </copy>
                   </assign>
                   <invoke operation="writeMessage" partnerLink="writer" portType="tns:SimpleFileWriter"
                   inputVariable="writeVariable" outputVariable="writeResponse"/>
                   <assign name="returnCopy">
                   <copy>
                   <from variable="writeResponse" part="result"/>
                   <to variable="response" part="msg"/>
                   </copy>
                   </assign>
                   <reply operation="createFusionProcess" partnerLink="caller" portType="tns:FusionCaller"
                   variable="response" />
                   </sequence>
                  </process>



                  and my descriptor:

                  <?xml version="1.0" encoding="UTF-8"?>
                  <!-- specifies the location of the process definition -->
                  <bpelDefinition location="fusionWriter.bpel"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xsi:schemaLocation="http://jbpm.org/bpel
                   http://jbpm.org/bpel/bpel_definition_1_0.xsd"
                   xmlns="http://jbpm.org/bpel" >
                  
                   <!-- makes WSDL interface elements available to the process -->
                   <imports>
                   <wsdl namespace="http://webservice" location="http://137.51.88.82:8080/SimpleMessageWS/SimpleWriter?wsdl"/>
                   <wsdl namespace="http://webservice" location="fusion.wsdl"/>
                  </imports>
                  
                  </bpelDefinition>


                  I am currently working on a proof of concept so any help would be greatly appreciated. Thanks!

                  • 7. Re: Problems deploying a BPEL process archive
                    Alejandro Guizar Master

                    There is a problem in your BPEL document. You are invoking an operation on a partner link without a partnerRole. See:

                    <invoke operation="writeMessage" partnerLink="writer" portType="tns:SimpleFileWriter"
                     inputVariable="writeVariable" outputVariable="writeResponse"/>

                    The referenced partner link should specify the partnerRole:
                    <partnerLink name="writer" partnerLinkType="tns:writeLink" partnerRole="writeService"/>

                    You did not supply the definition of the writeLink partner link type, so I cannot tell for sure that my proposed fix makes sense.

                    Anyway, the error report is completely misleading. Could you open a JIRA issue to improve it?

                    • 8. Re: Problems deploying a BPEL process archive
                      Nicholas Capito Newbie

                      How do I open a JIRA issue?

                      FYI here is my other wsdl

                      <?xml version="1.0" encoding="UTF-8"?>
                      
                      
                      
                      
                      <definitions name="SimpleWriterService"
                       targetNamespace="http://webservice" xmlns:tns="http://webservice"
                       xmlns="http://schemas.xmlsoap.org/wsdl/"
                       xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                       xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
                       xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
                      
                       <types />
                      
                       <plnk:partnerLinkType name="writeLink">
                       <plnk:role name="writeService">
                       <plnk:portType name="tns:SimpleFileWriter" />
                       </plnk:role>
                       </plnk:partnerLinkType>
                      
                       <message name="SimpleFileWriter_writeMessage">
                       <part name="String_1" type="xsd:string" />
                       </message>
                       <message name="SimpleFileWriter_writeMessageResponse">
                       <part name="result" type="xsd:int" />
                       </message>
                       <portType name="SimpleFileWriter">
                       <operation name="writeMessage" parameterOrder="String_1">
                       <input message="tns:SimpleFileWriter_writeMessage" />
                       <output message="tns:SimpleFileWriter_writeMessageResponse" />
                       </operation>
                       </portType>
                       <binding name="SimpleFileWriterBinding"
                       type="tns:SimpleFileWriter">
                       <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
                       style="rpc" />
                       <operation name="writeMessage">
                       <soap:operation soapAction="" />
                       <input>
                       <soap:body use="literal" namespace="http://webservice" />
                       </input>
                       <output>
                       <soap:body use="literal" namespace="http://webservice" />
                       </output>
                       </operation>
                       </binding>
                       <service name="SimpleWriterService">
                       <port name="SimpleFileWriterPort"
                       binding="tns:SimpleFileWriterBinding">
                       <soap:address location="REPLACE_WITH_ACTUAL_URL" />
                       </port>
                       </service>
                      </definitions>


                      • 9. Re: Problems deploying a BPEL process archive
                        Nicholas Capito Newbie

                        FYI i changed the parter role of the write and redeployed and it worked.... so thank you for now.



                        <partnerLinks>
                         <partnerLink name="writer" partnerLinkType="tns:writeLink" partnerRole="writeService" />
                         <partnerLink name="caller" partnerLinkType="tns:callerLink" myRole="callerService"/>
                        </partnerLinks>


                        • 10. Re: Problems deploying a BPEL process archive
                          Alejandro Guizar Master

                           

                          "ncapito" wrote:
                          ... so thank you for now

                          Well, you are welcome for now :)

                          To report an issue:
                          go to the project tracking console
                          log in with the same access parameters you use for the JBoss site
                          Select "Create new issue"

                          • 11. Re: Problems deploying a BPEL process archive
                            Koen Aers Master

                            Use your JBoss login credentials and enter a new issue on http://jira.jboss.com.

                            Regards,
                            Koen