Re: problem of activity pick

[NGUYEN Cong Kinh]

Hi Matthieu,

This is the BPEL file. There are some changed things. However, errors are
same.


> I'll need to see your BPEL file, you've only attached the deployment
> descriptor and WSDLs.
>
> Thanks,
> Matthieu
>

Thanks,
Kinh

Asyn.wsdl
Description: XML document

AsynArtifacts.wsdl
Description: XML document

<!--
  ~ Licensed to the Apache Software Foundation (ASF) under one
  ~ or more contributor license agreements.  See the NOTICE file
  ~ distributed with this work for additional information
  ~ regarding copyright ownership.  The ASF licenses this file
  ~ to you under the Apache License, Version 2.0 (the
  ~ "License"); you may not use this file except in compliance
  ~ with the License.  You may obtain a copy of the License at
  ~
  ~    http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing,
  ~ software distributed under the License is distributed on an
  ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  ~ KIND, either express or implied.  See the License for the
  ~ specific language governing permissions and limitations
  ~ under the License.
  -->
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03";
	xmlns:main="http://www.tsi.enst.fr/paam"; 
	xmlns:mws="http://www.tsi.enst.fr/paam";
	xmlns:resp="http://paam";
	xmlns:rws="http://paam";>

	<process name="main:Asyn">
		<active>true</active>
		<provide partnerLink="client">
			<service name="mws:AsynService" port="AsynPort"/>
		</provide>
		<invoke partnerLink="linkVideo">
			<service name="rws:VideoService" port="Video"/>
		</invoke>
	</process>
	<!-- 
	<process name="resp:DynPartnerResponder">
		<in-memory>true</in-memory>
                <type>resp:DynPartnerResponder</type>
		<provide partnerLink="mainPartnerLink">
			<service name="rws:DynResponderService" port="DynResponderPort"/>
		</provide>
	</process>
	-->
</deploy>

Video.wsdl
Description: XML document