The SU should contain a WSDL file which has the same name
as the bpel process, but with a ".wsdl" extension.  It will be imported
and should contain all the needed definitions.

Btw, you may want to try the ODE Service Engine instead of servicemix-bpe
which uses an unmaintained portion of code from the Ode project.

On 11/23/06, Federico Ragona <[EMAIL PROTECTED]> wrote:
Hello,
i'm having troubles while deploying a bpe-su to servicemix.

 Here's the stack trace i get whenever i try to deploy it:

[INFO] Unable to deploy project, Error accessing ServiceMix administration

<?xml version="1.0" encoding="UTF-8"?>
<jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message";
version="1.0">
<jbi-task-result>
<frmwk-task-result>
<frmwk-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
</task-result-details>
</frmwk-task-result-details>
</frmwk-task-result>
<component-task-result xmlns="
http://java.sun.com/xml/ns/jbi/management-message";>
        <component-name>servicemix-jsr181</component-name>
        <component-task-result-details>
                <task-result-details>
                        <task-id>deploy</task-id>
                        <task-result>SUCCESS</task-result>
                </task-result-details>
        </component-task-result-details>
</component-task-result>
<component-task-result xmlns="
http://java.sun.com/xml/ns/jbi/management-message";>
        <component-name>servicemix-http</component-name>
        <component-task-result-details>
                <task-result-details>
                        <task-id>deploy</task-id>
                        <task-result>SUCCESS</task-result>
                </task-result-details>
        </component-task-result-details>
</component-task-result>
<component-task-result>
<component-name>servicemix-bpe</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg>
<msg-loc-info>
<loc-token/>
<loc-message>Unable to parse result string</loc-message>
</msg-loc-info>
</task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<loc-token/>
<loc-message>org.apache.ode.bpe.deployment.bpel.DeploymentException:
[BpelService] message type aservice:ExecRequest not found. Make sure the
WSDL has been imported and namespaces have been set up
consistently.</loc-message>
<stack-trace><![CDATA[javax.jbi.management.DeploymentException:
org.apache.ode.bpe.deployment.bpel.DeploymentException: [BpelService]
message type aservice:ExecRequest not found. Make sure the WSDL has been
imported and namespaces have been set up consistently.
        at org.apache.servicemix.bpe.BPEDeployer.deploy(BPEDeployer.java
:119)
        at org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(
BaseServiceUnitManager.java:88)
        at org.apache.servicemix.common.BaseServiceUnitManager.deploy(
BaseServiceUnitManager.java:69)
        at
org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(
DeploymentService.java:527)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(
AutoDeploymentService.java:294)
        at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExternalArchive
(AutoDeploymentService.java:184)
        at
org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(
JBIContainer.java:469)
        at
org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(
JBIContainer.java:479)
        at
org.apache.servicemix.jbi.framework.AdminCommandsService.deployServiceAssembly
(AdminCommandsService.java:240)
        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.apache.commons.beanutils.MethodUtils.invokeMethod(
MethodUtils.java:216)
        at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(
BaseStandardMBean.java:316)
        at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(
DynamicMetaDataImpl.java:213)
        at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java
:220)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(
DefaultMBeanServerInterceptor.java:815)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java
:784)
        at javax.management.remote.rmi.RMIConnectionImpl.doOperation(
RMIConnectionImpl.java:1408)
        at javax.management.remote.rmi.RMIConnectionImpl.access$100(
RMIConnectionImpl.java:81)
        at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(
RMIConnectionImpl.java:1245)
        at java.security.AccessController.doPrivileged(Native Method)
        at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(
RMIConnectionImpl.java:1348)
        at javax.management.remote.rmi.RMIConnectionImpl.invoke(
RMIConnectionImpl.java:782)
        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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java
:294)
        at sun.rmi.transport.Transport$1.run(Transport.java:153)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(
TCPTransport.java:466)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(
TCPTransport.java:707)
        at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.ode.bpe.deployment.bpel.DeploymentException:
[BpelService] message type aservice:ExecRequest not found. Make sure the
WSDL has been imported and namespaces have been set up consistently.
        at org.apache.ode.bpe.deployment.bpel.BPELUtil.throwNewException(
BPELUtil.java:45)
        at org.apache.ode.bpe.deployment.bpel.BPELWSDLVariable.<init>(
BPELWSDLVariable.java:65)
        at
org.apache.ode.bpe.deployment.bpel.BPELRepositoryHandler.buildVariable(
BPELRepositoryHandler.java:302)
        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.apache.ode.bpe.deployment.bpel.BPELSAXHandler.startElement(
BPELSAXHandler.java:105)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
        at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(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 javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
        at org.apache.ode.bpe.deployment.bpel.BPELParser.parseBPEL(
BPELParser.java:95)
        at org.apache.ode.bpe.deployment.bpel.BPELDeploy.deployJar(
BPELDeploy.java:177)
        at
org.apache.ode.bpe.bped.unmanaged.BPELDeployerSLImpl.loadDefinition(
BPELDeployerSLImpl.java:78)
        at org.apache.servicemix.bpe.BPEDeployer.deploy(BPEDeployer.java:86)
        ... 35 more
]]></stack-trace>
</exception-info>
</task-result-details>
</component-task-result-details>
</component-task-result>
</jbi-task-result>
</jbi-task>

I'd like to focus on the "
org.apache.ode.bpe.deployment.bpel.DeploymentException: [BpelService]
message type aservice:ExecRequest not found. Make sure the WSDL has been
imported and namespaces have been set up consistently" error, rather than
on  "Error accessing ServiceMix administration": i read another mail posted
months ago, concerning the very same error, but couldn't find a solution to
my problem...

here is the bpel file:

<process name="BpelService" targetNamespace="
http://localhost:8192/BpelService";
  xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/";
  xmlns:tns="http://localhost:8192/BpelService";
  xmlns:aservice="http://localhost:8192/AService/main.wsdl";
  xmlns:bservice="http://localhost:8192/FirstService/main.wsdl";
  xmlns:bpel="http://schemas.xmlsoap.org/ws/2003/03/business-process/";>

  <partnerLinks>
    <partnerLink name="AService" partnerLinkType="aservice:ALink"
partnerRole="FirstService" />
    <partnerLink name="BService" partnerLinkType="bservice:BLink"
partnerRole="SecondService" />
  </partnerLinks>

  <variables>
    <variable name="ARequest" messageType="aservice:ExecRequest" />
    <variable name="AResponse" messageType="aservice:ExecResponse" />
    <variable name="AFault" messageType="aservice:ExecFault" />
    <variable name="BRequest" messageType="bservice:FirstOperation" />
    <variable name="BResponse" messageType="bservice:FirstOperationResponse"
/>
  </variables>

<!-- ................... -->

</process>




--
Cheers,
Guillaume Nodet

Reply via email to