You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by izgur <ig...@gmail.com> on 2011/02/04 12:35:42 UTC
IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
bpel:condition doesn't work correct in a Array problem !!!
--
View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30843031.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by Karolis Petrauskas <k....@gmail.com>.
Sorry, I missed that point. I had similar problems too. Things started
to work when i changed "...[$index]..." to "...[position() =
$index]...". For example,
<bpel:condition>$validators/exp:validator[position() =
$indexOfHTToComplete]/@completed = 'false'</bpel:condition>
Karolis
On Fri, Feb 4, 2011 at 2:41 PM, izgur <ig...@gmail.com> wrote:
>
> My problem is not the assignment ... it goes well well with:
> <bpel:copy>
> <bpel:from>
> <![CDATA[$input.payload/tns:arrSubscriber/tns:User[round($iterator)]/tns:sMultimediaIP]]>
> </bpel:from>
> <bpel:to variable="checkString"></bpel:to>
> </bpel:copy>
>
> But the bpel:condition function has issues on array:
> <bpel:if name="CheckMultimediaIP">
> <bpel:condition
> expressionLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0"><![CDATA[$input.payload/tns:arrSubscriber/tns:User[round($iterator)/tns:sMultimediaIP]</bpel:condition>
>
> It returns the correct value only for the first element(user) in my array
>
>
> --
> View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30844104.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by izgur <ig...@gmail.com>.
My problem is not the assignment ... it goes well well with:
<bpel:copy>
<bpel:from>
<![CDATA[$input.payload/tns:arrSubscriber/tns:User[round($iterator)]/tns:sMultimediaIP]]>
</bpel:from>
<bpel:to variable="checkString"></bpel:to>
</bpel:copy>
But the bpel:condition function has issues on array:
<bpel:if name="CheckMultimediaIP">
<bpel:condition
expressionLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath2.0"><![CDATA[$input.payload/tns:arrSubscriber/tns:User[round($iterator)/tns:sMultimediaIP]</bpel:condition>
It returns the correct value only for the first element(user) in my array
--
View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30844104.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by Karolis Petrauskas <k....@gmail.com>.
>From my experience, most reliable and flexible way of doing
non-trivial asignments is to use xslt transformations and pass all
needed elements to it as parameters. For example,
<bpel:assign name="CollectData">
<bpel:copy>
<bpel:from>
bpel:doXslTransform(
'urn:/CollectData.xsl',
$input.payload,
'initiator', $initiatotor.getInfoResponse/ldapt:dn
)
</bpel:from>
<bpel:to variable="validators"/>
</bpel:copy>
</bpel:assign>
Karolis
On Fri, Feb 4, 2011 at 2:26 PM, izgur <ig...@gmail.com> wrote:
>
> OK. I except all your critics ... Sorry... I just couldn't handle another
> problem/bug about arrays...
> And i've got a deadline next week, so I'm nervous. Sorry...
>
> You said it is fixed ... https://issues.apache.org/jira/browse/ODE-178
> but I tell you it's not working in Riftsaw 2.2.0 ang Gary said Riftsaw2.2
> is like ODE 1.3.5 using JBossWS insteead of axis...
>
> I'm trying now a workaround... coping from array to local variable and then
> it should work, because i haven't found any issues on bpel:condition a local
> variable... just array problem ...
>
> Thanks in advance!
>
> Regards, Igor!
>
>
>
> Tammo van Lessen wrote:
>>
>> Status: Resolved
>> Resolution: Fixed
>> Fix Version/s: 1.1.1
>>
>> It's been fixed since 2007. And as a general remark: Shouting does not
>> help to get a faster or better answer, neither a collection of
>> exclamation marks do. Better is to provide a simple example that
>> showcases what works and what does not.
>>
>> Tammo
>>
>> On 04.02.2011 12:35, izgur wrote:
>>>
>>> bpel:condition doesn't work correct in a Array problem !!!
>>
>> --
>> Tammo van Lessen - http://www.taval.de
>>
>>
>
> --
> View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30843986.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by izgur <ig...@gmail.com>.
OK. I except all your critics ... Sorry... I just couldn't handle another
problem/bug about arrays...
And i've got a deadline next week, so I'm nervous. Sorry...
You said it is fixed ... https://issues.apache.org/jira/browse/ODE-178
but I tell you it's not working in Riftsaw 2.2.0 ang Gary said Riftsaw2.2
is like ODE 1.3.5 using JBossWS insteead of axis...
I'm trying now a workaround... coping from array to local variable and then
it should work, because i haven't found any issues on bpel:condition a local
variable... just array problem ...
Thanks in advance!
Regards, Igor!
Tammo van Lessen wrote:
>
> Status: Resolved
> Resolution: Fixed
> Fix Version/s: 1.1.1
>
> It's been fixed since 2007. And as a general remark: Shouting does not
> help to get a faster or better answer, neither a collection of
> exclamation marks do. Better is to provide a simple example that
> showcases what works and what does not.
>
> Tammo
>
> On 04.02.2011 12:35, izgur wrote:
>>
>> bpel:condition doesn't work correct in a Array problem !!!
>
> --
> Tammo van Lessen - http://www.taval.de
>
>
--
View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30843986.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by Tammo van Lessen <tv...@gmail.com>.
Status: Resolved
Resolution: Fixed
Fix Version/s: 1.1.1
It's been fixed since 2007. And as a general remark: Shouting does not
help to get a faster or better answer, neither a collection of
exclamation marks do. Better is to provide a simple example that
showcases what works and what does not.
Tammo
On 04.02.2011 12:35, izgur wrote:
>
> bpel:condition doesn't work correct in a Array problem !!!
--
Tammo van Lessen - http://www.taval.de
Re: IS https://issues.apache.org/jira/browse/ODE-178 FIXED ??
Posted by Karolis Petrauskas <k....@gmail.com>.
Some of us should read something like section "How to have your
emails..." from here: http://www.jboss.org/drools/lists.html.
Karolis
On Fri, Feb 4, 2011 at 1:35 PM, izgur <ig...@gmail.com> wrote:
>
> bpel:condition doesn't work correct in a Array problem !!!
> --
> View this message in context: http://old.nabble.com/IS-https%3A--issues.apache.org-jira-browse-ODE-178-FIXED----tp30843031p30843031.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.