Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Help in calling a publish activity

RajaSekharReddy.MOct 28 2013 — edited Oct 29 2013

Hi,

I am trying to call a business service from a proxy using a publish activity. I am assigning a variable value to the body element

<soap-env:Body>.


${xquery to the variable}..


</soap-env:Body>

The above is the code snippet .This work fine as long as I don't use an xquery. But it throws a null pointer exception on using the xquery function to the variable.

I saw a part in the document qouting that reference variables would be sent as is(39.9.1 SOAP Services this section of doc) . Can you guys suggest any work around or solution for it rather than hardcoding the entire xml again ?

Thanks ....
This post has been answered by RajaSekharReddy.M on Oct 29 2013
Jump to Answer

Comments

Eric Elzinga

replace ./* in variable body with (xquery reference)

and then in your xquery contract the variable (<employeeRequest/> for example, skip the body-element)

and put this replace in the publish activity itself...should work

RajaSekharReddy.M

Hi Eric,

That was not helpful.

When i just used the entire xml payload in either of assign or replace activity it's good.

But when i specify the xml expression to the variable which has the payload in either of replace or assign . It throws a nullpointerexecption.

These are the parameters specified in replace

xpath  : ./*


in variable body


Expression ${deldata}

in the console i can see the value of the deldata which is good.

RajaSekharReddy.M
Answer

The way i did was right but i was sending a wrong payload to the proxy

Marked as Answer by RajaSekharReddy.M · Sep 27 2020
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Nov 26 2013
Added on Oct 28 2013
#soa-process-management, #soa-suite-discusssions
3 comments
228 views