Hi Fabian,

copying values in to an array is not natively supported by BPEL. You
will need to use an XSLT script to do that. This can be invoked by the
doXSLTransform XPath function. If I'm not mistaken, the BPEL 2.0 spec
contains an example for such a scenario.

Best,
  Tammo

karoudja wrote:
> Thanks Tammo,
> Finally I have begin all this from scratch and it's work! It was a problem
> in the namespace.
> I have again a small question about tue <copy> tag
> 
>  <assign name="Assign1">
>             <copy>
>                 <from variable="Ehealth1CallOperationIn"
> part="part1"></from>
>                 <to variable="StockageIn" part="parameters" ></to>
>             </copy>
>         </assign>
> 
> The problem is that "Ehealth1CallOperationIn - part1" is a string and
> "StockageIn - parameters" is a complex type declared as this:
> 
> <xs:sequence>
> <xs:element minOccurs="0" name="artefact" nillable="true" type="xs:string"/>
> </xs:sequence>
> </xs:complexType>
> 
> How could I copy "Ehealth1CallOperationIn - part1" into the string arraylist
> "StockageIn - parameters"
> 
> Any ideas?
> Thanks,
> Fabian.
> 
> 
> i haven't time to check your project in these days.
> i hope you could find out it by yourself.
> 
> ciao
> 
> 
> On Fri, Mar 19, 2010 at 11:51, Tammo van Lessen <[email protected]>wrote:
> 
>> Hi,
>>
>> looks like your local prefix declaration of tns does not override the
>> global prefix. Please try to use unique prefixes, eg binding hwsdl to
>> http://j2ee.netbeans.org/wsdl/BPEL_HelloWorld/hello and then using
>> hwsdl:CallPort for the portType attribute.
>>
>> HTH,
>>  Tammo
>>
>>
>> karoudja wrote:
>>
>>> Hi,
>>> I think I have found my error it was an error related with the
>>> partnerLink.
>>> I haven't specified the right parameters. So now I would like made an
>>> "Invoke" with a partnerLink but I have a very strange error:
>>>
>>> ERROR: If the portType attribute is included for readability, in a
>>> <receive>,<reply>,<invoke>,<onEvent>  or<onMessage>  element, the value
>>> of
>>> the portType attribute must match the portType value implied by the
>>> combination of the specified partnerLink and the role implicitly
>>> specified
>>> by the activity. It means that Invoke requires partnerRole, another -
>>> myRole.
>>>
>>> Have you an idea?
>>> I insert my code here:
>>> http://old.nabble.com/file/p27950922/src.zipsrc.zip
>>>
>>> Thanks,
>>> Fabian
>>>
> 


-- 
Tammo van Lessen - http://www.taval.de

Reply via email to