Dynamic Direct Binding reference

Hi all,
I've been searching for a way to modify the endpoint (address) of a direct binding reference in running time with no good results. I know that It's possible to use this property
<bpelx:inputProperty name="endpointURI"
variable="YaVoyEndPoint"/>
to override the endpoint in WebService references. Does anyone know the way to do the same with direct binding references?
Thanks in advance
Edited by: luismi fernandez on Sep 14, 2012 5:39 AM
Edited by: luismi fernandez on Sep 17, 2012 11:44 AM

Hi luismi fernandez,
Please follow the steps mentioned here:
http://www.oracle.com/technetwork/articles/carey-090553.html
Thanks,
Deepak.

Similar Messages

Errors in direct binding invocation from BPEL to OSB

Hi All,
I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
Any help about the management of this situation would be appreciated.
Thanks,
The log trace is the next one:
[component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
     at java.lang.Thread.run(Thread.java:662)
And this is the payload from the instance details:
<messages>
<input>
... input data....
</input>
<fault>
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>
</exception>
<root class="oracle.fabric.common.FabricInvocationException">
oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
<stack>
<f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
<f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
<f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
<f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
<f>java.security.AccessController.doPrivileged</f>
<f>javax.security.auth.Subject.doAs#396</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
<f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
<f>java.lang.reflect.Method.invoke#597</f>
<f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
<f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
<f>...</f>
</stack>
</root>
</fault>
</messages>
Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

Hi All,
I have a problem in direct binding invocations between BPEL instances and OSB, this is the detail:
There is in my composite a BPEL process that includes a catchAll component to manage all the faults resulting in the OSB invoke action and there is a fault policy too configured to manage the retry invocations. If the flow ends successfully there is no problem but if an error happens in the OSB part (time outs, bad address configuration in reference bindings details or something similar) the composite doesn't catch anything and retries aren't executed. The BPEL instance keeps in "running with errors" state from this moment.
Any help about the management of this situation would be appreciated.
Thanks,
The log trace is the next one:
[component_instance_id: 18440047] Failed to handle dispatch message ... exception ORABPEL-05002[[
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: JTA transaction is not in active state.
The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK".
The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163)
     at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source)
     at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name).
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262)
     at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60)
     at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155)
     ... 15 more
Consult the system administrator regarding this error.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
     at java.lang.Thread.run(Thread.java:662)
And this is the payload from the instance details:
<messages>
<input>
... input data....
</input>
<fault>
<exception class="com.collaxa.cube.engine.EngineException">
JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "18,440,048", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "18440048" for process "ErrorBPELProcess1" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more " . Consult the system administrator regarding this error.
<stack>
<f>com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive#107</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#352</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke#1070</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke#584</f>
<f>com.collaxa.cube.engine.ext.common.InvokeHandler.handle#132</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements#74</f>
<f>com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform#166</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#2687</f>
<f>com.collaxa.cube.engine.CubeEngine._handleWorkItem#1190</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1093</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#76</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#218</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#297</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4609</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#4540</f>
<f>com.collaxa.cube.engine.CubeEngine._createAndInvoke#713</f>
<f>...</f>
</stack>
</exception>
<root class="oracle.fabric.common.FabricInvocationException">
oracle.soa.api.invocation.InvocationException: com.bea.wli.sb.transports.client.SBTransportException: An error occured while un-marshalling the request message: com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). com.bea.alsb.ws.codec.CodecException: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:163) at com.bea.wli.sb.transports.sb.codec.SOAMessageHandler.createResponse(SOAMessageHandler.java:116) at com.bea.wli.sb.transports.sb.bean.SBDispatcherBean.invoke(SBDispatcherBean.java:355) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl.invoke(Unknown Source) at com.bea.wli.sb.transports.sb.bean.SBDispatcher_nwlqik_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667) at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518) at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: com.bea.alsb.ws.codec.CodecException: The SOAP envelope is not formatted according to the RPC style. The SOAP Body tag must have one and only one child element (named after the operation name). at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcCodec.unmarshallBody(SoapRpcCodec.java:107) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapCodec.unmarshall(SoapCodec.java:262) at com.bea.alsb.ws.codec.internal.runtime.soap.SoapRpcServiceCodec.unmarshall(SoapRpcServiceCodec.java:60) at com.bea.alsb.soa.codec.SOACodecUtil.unmarshall(SOACodecUtil.java:155) ... 15 more
<stack>
<f>oracle.integration.platform.blocks.direct.OutboundMessageDispatcher.request#124</f>
<f>oracle.integration.platform.blocks.direct.DirectExternalBindingComponent.request#190</f>
<f>oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest#139</f>
<f>oracle.integration.platform.blocks.mesh.MessageRouter.request#182</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl$2.run#178</f>
<f>java.security.AccessController.doPrivileged</f>
<f>javax.security.auth.Subject.doAs#396</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject#176</f>
<f>oracle.integration.platform.blocks.mesh.MeshImpl.request#151</f>
<f>sun.reflect.GeneratedMethodAccessor1294.invoke</f>
<f>sun.reflect.DelegatingMethodAccessorImpl.invoke#25</f>
<f>java.lang.reflect.Method.invoke#597</f>
<f>org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection#307</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint#182</f>
<f>org.springframework.aop.framework.ReflectiveMethodInvocation.proceed#149</f>
<f>oracle.integration.platform.metrics.PhaseEventAspect.invoke#71</f>
<f>...</f>
</stack>
</root>
</fault>
</messages>
Edited by: luismi fernandez on Aug 1, 2012 1:20 AM

Setting bind references at run-time

Hi,
I am working on a dynamic form,which will instantiate questions based on some instructions specified in XML when the form loads up, much like John Brinkman's example
http://blogs.adobe.com/formfeed/2009/03/a_form_to_design_a_form.html
At design time, it is not know which node in the data dom the field should be bound to, so I would like to be able to simulate a match="dataRef" ref="$.myNode" statement at run-time.
However, my recollection is that the binding reference can't be changed at run time. Does anyone know if it can be done, and how to do it?
John

Hi,
Thanks for the quick response. Your suggestion works almost
perfectly. I can now change the flv to any flv I want, and it plays
the video I want. However, even though I am specifying
autoPlay=false, it still plays automatically when the page loads.
Here is my actionscript:
flvPlayback.playPauseButton = myplayPause;
flvPlayback.seekBar = mySeek;
flvPlayback.muteButton = myMute;
flvPlayback.contentPath = newPath;
flvPlayback.autoPlay = autoStart;
and here is my html:
<object
classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="
http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=8,0,0,0"
width="326" height="266" id="xxx" align="middle">
<param name="allowScriptAccess" value="sameDomain" />
<param name="movie" value="pokflvplayer.swf">
<param name="FlashVars"
value="autoStart=false&newPath=holiday_message_2007.flv" />
<param name="quality" value="high" />
<param name="bgcolor" value="#666666" />
<embed src="pokflvplayer.swf"
FlashVars="newPath=holiday_message_2007.flv&autoStart=false"
quality="high" bgcolor="#666666" width="326" height="266"
name="medical_imaging" align="middle"
allowScriptAccess="sameDomain" type="application/x-shockwave-flash"
pluginspage="
http://www.macromedia.com/go/getflashplayer">
</embed>
</object>
Any idea why it will not recognize the autoStart paramenter?
By the way, I had to change your myFLV.autoStart - autoS to
flvPlayback.autoPlay=autoStart. The actual name of the parmameter
is autoPlay, not autoStart. My guess is that was just a typo on
your part. Thanks again for your help.
Bob

Difference between Direct binding , Web service Adapter and HTTP Binding

Can any one help what is the differnce between
*1) Direct binding*
*2) Webservice Adapter*
*3) HTTP Binding*
I am trying to use the above service adapters as references in BPEL.
I had invoked a web service hosted in OSB from BPEL via web service adapter and was successful
On going through few docs came through the other two service adapters but was not able to figure out what exactly is the differnce .
I learnt +"*Direct binding*"+ can be used to call OSB+ . How does it vary from Webservice Adapter+

hi Eric ,
Thanks for clarification ..
OSB does not generate WSDL and web service adapter in BPEL mandates WSDL .
I had to create WSDL separately and then feed into Web service adapter in BPEL to call OSB Proxy service. Though successful , felt its not an better approach.
Please advice is there any way thatWSDL is generated in OSB itself . .if i try to create webservice on Proxy service the wsdl resulted from it has only binding and porty type .
Is it the same case for ++Direct binding++ .I assume it should not be the case

Import Direct Binding Service WSDL in OSB

I was wondering how to import direct binding service wsdl in OEPL. I tried the below but getting an error. Any help is greatly appreciated.
File - Import - File System. .... After importing the WSDL, I'm getting an error. So I was not sure if I'm on the right track or not.
Thanks
NC

If you have brought in the whole directory structure then you can simply drag the WSDL into the corrct directory that relates to your imports.
Then you can delete the unwanted directories using the delete key.
If you don't want the directory structory to import you need to be conscience every time that you need to uncheck a check box that is checked by default. Can't remember the exact name but basiclly something like import directory structure.
Once the WSDL in correct folder and still having issues, open up and view the source. Make sure all references are correct for the project directory structure.
cheers
James

Dynamic value binding for InputTextField - Expression within an expression

Hi,
I have this requirement where I have to use an EL expression's output as a bean's property in the value attribute of a InputTextField. E.g.
          <h:dataTable value="#{entity.formats}" var="field">
               <h:column>
                    <h:outputLabel value="#{field.shortDesr}"/>
               </h:column>
               <h:column>
                    <h:inputText value="#{*entity."+#{field.shortDesr}+*"}"/>
               </h:column>
          </h:dataTable>
The JSF page will be a generic one so the fields within a form will be dynamic and will be formed at run-time. Since the exact bean property(entity in the code above) for a particular field is not known before, it needs to be dynamicaly built
To give more clarity. In the following snippet, i know that entity is the bean to be used but which property(XXX) the text field has to be bound is not known and needs to be assigned at run-time.
<h:inputText value="#{entity.*XXX*"/>
Is this possible? Are there any direct JSF solution or work arounds for it? Appreciate your inputs.
Thanks
Ranjith

A: Dynamic value binding for InputTextField - Expression within an expression

Hi BaluSC,
Your solution is totally acceptable. But I was also looking for something that can make possible direct binding to the bean properties without going through a Map.
In the meantime, I worked around the problem by not using the DataTable. Instead I loop the collection and add the Form elements programatically (code given below). With this I am able to achieve the desired effect of binding directly to the bean's property. But I am hitting another problem now, On submit the form Seam throws up 'No active conversational context" error while binding the #{sdmManager.grid} attribute. Now, I am trying to figure out how to come across it.
JSF
     <h:panelGrid columns="2" binding="#{sdmManager.grid}">
</h:panelGrid>
Bean code
     public HtmlPanelGrid getGrid(){
     grid = new HtmlPanelGrid();
     List<UIComponent> children = grid.getChildren();
     Collection<FieldFormatData> formats = dataManager.getFieldFormatData();
     for(FieldFormatData format:formats){
          HtmlOutputLabel outputLabel = new HtmlOutputLabel();
          outputLabel.setValue(format.getShortDesr());
          children.add(outputLabel);
          HtmlInputText inputText = new HtmlInputText();
          inputText.setSize(10);
          inputText.setMaxlength(10);
          System.out.println("Binding ................................... " + format.getEntityField());
          inputText.setValueBinding("value", FacesContext.getCurrentInstance().getApplication().createValueBinding("#{entity."+format.getEntityField()+"}"));
          children.add(inputText);
     return grid;

Direct binding faults getting FabricInvocationException

We have two BPEL composites. When one calls the other using SOAP, the caller receives a correct fault, but when I change to direct binding, the fault type is lost and I get a FabricInvocationException instead.
The called composite returns this fault:
<FaultVar>
<part name="fault">
    <PInitWorkflowTransactionFault>
      <nppTxId>
        <nppTransactionId>633919050</nppTransactionId>
        <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
        <nppIsRetryFlag>false</nppIsRetryFlag>
      </nppTxId>
      <clientTxId>
        <clientUserId>XYZ</clientUserId>
        <transactionId>100001</transactionId>
        <isRetry>false</isRetry>
      </clientTxId>
      <error>
        <errorClass>1</errorClass>
        <errorCode>10221</errorCode>
        <systemType>WorkflowManager-ProvInit</systemType>
        <errorMessage>Dummy error message</errorMessage>
      </error>
    </PInitWorkflowTransactionFault>
</part>
</FaultVar>In the SOAP version, caller sees this, which is correct:
<bpelFault>
<faultType>1</faultType>
<WFMFault>
    <part name="fault">
      <PInitWorkflowTransactionFault>
        <nppTxId>
          <nppTransactionId>633919050</nppTransactionId>
          <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
          <nppIsRetryFlag>false</nppIsRetryFlag>
        </nppTxId>
        <clientTxId>
          <clientUserId>XYZ</clientUserId>
          <transactionId>100001</transactionId>
          <isRetry>false</isRetry>
        </clientTxId>
        <error>
          <errorClass>1</errorClass>
          <errorCode>10221</errorCode>
          <systemType>WorkflowManager-ProvInit</systemType>
          <errorMessage>Dummy error message</errorMessage>
        </error>
      </PInitWorkflowTransactionFault>
    </part>
</WFMFault>
</bpelFault>When I switch to direct binding, using the following reference in the composite.xml, we see the problem.
<reference name="ProvInitializeWorkflowService" wsdlLocation="NPPProvInitializingWorkflow.wsdl">
<interface.wsdl interface="http://www.example.com/network/NPP/ProvInitWF#wsdl.interface(PInitWorkflowPortType)"/>
<binding.direct address="soadirect:/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct"
                  connection-factory="oracle.soa.api.JNDIDirectConnectionFactory">
    <property name="java.naming.provider.url" type="xs:string" many="false">t3://localhost:8001/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct</property>
</binding.direct>
</reference>Non-fault replies all work correctly, so we don't have a type mismatch.
Using direct binding, the caller sees this instead:
<bpelFault>
<faultType>0</faultType>
<remoteFault>
    <part name="summary">
      <summary>oracle.fabric.common.FabricInvocationException: oracle.fabric.common.FabricInvocationException:
               oracle.soa.api.invocation.FaultException: {http://www.example.com/network/NPP/ProvInitWF}WFMFault</summary>
    </part>
    <part name="detail">
      <detail>{http://www.example.com/network/NPP/ProvInitWF}WFMFault</detail>
    </part>
    <part name="code">
      <code>null</code>
    </part>
</remoteFault>
</bpelFault>I would really like to use direct binding, but I can't if faults do not work. Help?!
Thanks.

Hello guys,
did you manage to get a patch for your issue?
We have the same one here, a FabricInvocationException at the BPEL layer,
and in the logs
java.lang.ClassCastException: [B cannot be cast to com.bea.wli.sb.transports.client.SOAMessage
at com.bea.wli.sb.transports.direct.OSBDirectConnection.invoke(Unknown Source)
at com.bea.wli.sb.transports.direct.OSBDirectConnection.request(Unknown Source)
[ I use SOA Suite 11.1.1.5 ]
thanx
ydes

Dynamic context binding in web dynpro alv

I use dynamic context binding (see code below to show and edit the ALV table.
'DB_TABLE' is a tranparent table. It works fine.
But now this table should be expanded with additional fields which are only known at runtime and could be different from case to case.
How can I get these fields in the context dynamically?
DATA:
        rootnode_info TYPE REF TO if_wd_context_node_info,
        dyn_node      TYPE REF TO if_wd_context_node,
        tablename   TYPE string.
rootnode_info = wd_context->get_node_info( ).
tablename = 'DB_TABLE'.
cl_wd_dynamic_tool=>create_nodeinfo_from_struct(
    parent_info = rootnode_info
    node_name = tablename
    structure_name = tablename
    is_multiple = abap_true ).
DATA:
        stru_tab TYPE REF TO data.
FIELD-SYMBOLS: <tab> TYPE table.
CREATE DATA stru_tab TYPE TABLE OF (tablename).
ASSIGN stru_tab->* TO <tab>.
SELECT * FROM (tablename) INTO CORRESPONDING FIELDS OF TABLE <tab>.
dyn_node = wd_context->get_child_node( name = tablename ).
dyn_node->bind_table( <tab> ).

You should create a structure dynamically and use this as the context structure. See the coding below, where a structure is created, which contains CARRID and CONNID.
DATA: node_info type ref to if_wd_context_node_info,
      struct_type TYPE REF TO cl_abap_structdescr,
      table_type type ref to cl_abap_tabledescr,
      comp_tab    TYPE cl_abap_structdescr=>component_table,
      comp        LIKE LINE OF comp_tab,
      my_table    type ref to data,
      my_row      type ref to data.
field-symbols: <table> type table,
                 <row> type data,
                 <flight> type sflight.
* build a structure description from the list of single fields
comp-name = 'CARRID'.
comp-type ?= cl_abap_datadescr=>describe_by_name( 'S_CARR_ID' ).
APPEND comp TO comp_tab.
comp-name = 'CONNID'.
comp-type ?= cl_abap_datadescr=>describe_by_name( 'S_CONN_ID' ).
APPEND comp TO comp_tab.
* note this structure contains the fields "CONNID" and "CARRID"
struct_type = cl_abap_structdescr=>create( comp_tab ).
* now the nodeinfo is created
node_info = wd_context->get_node_info( ).
node_info = node_info->add_new_child_node(
    name                         = 'MY_NODE'
    IS_MANDATORY                 = ABAP_true
    IS_MULTIPLE                  = ABAP_true
    STATIC_ELEMENT_RTTI          = struct_type
    IS_STATIC                    = ABAP_false
* fill new node;
data: l_node type ref to if_wd_context_node,
        l_flight type STANDARD TABLE OF sflight.
l_node = wd_context->get_child_node( 'MY_NODE' ).
l_flight = wd_assist->get_flights( ).
* if you could create a local data type, would be fine, but if you have to do it dynamically ...
struct_type = node_info->GET_STATIC_ATTRIBUTES_TYPE( ).
* create tabledescriptor from structdescription (standard table, no keys)
table_type = cl_abap_tabledescr=>create( p_line_type = struct_type ).
create data my_table type handle table_type.
assign my_table->* to <table>.
loop at l_flight assigning <flight>.
    create data my_row type handle struct_type.
    assign my_row->* to <row>.
    move-corresponding <flight> to <row>.
    append <row> to <table>.
endloop.
l_node->bind_table( <table> ).

Dynamic service binding in ESB

Hi,
I am trying to do dynamic binding in ESB (using service registry key) and facing the following issue:
1>I have added the uddi Inquiry url in the esb_config.ini:
uddiInquiryURL=http://ossi-1042.idc.oracle.com:8888/registry/uddi/inquiry/
2>In the ESB, I am invoking BPEL through soap service. There are 2 BPEL processes, say B1 and B2. I am giving the wsdl location of B1, and in the endpoint properties i am adding the registry key of B2 (so that I can find out if the registry key property is working):
<endpointProperties>
<property name="registryServiceKey" value="uddi:797f8d80-fbbf-11dc-a4bb-27e52611a4ba"/>
</endpointProperties>
When I run the instance, always B1 is getting invoked, proving that the registry key is not being used and thus dynamic service binding is happening.
Kindly help me out in this.
Thanks and regards,
Pavan

I tried applying the patch, but it gives the following error:
OPatch detects your platform as 207 while this patch 6133448 supports platforms:
0 (Generic Platform)
This patch is not suitable for this operating system.
Please contact support for the correct patch.
ERROR: OPatch failed during pre-reqs check.
OPatch returns with error code = 150
I downloaded for the OS I am on, but always the generic patch downloads; i guess this generic one should work for all platforms. Opatch version is 1.0.0.0.56.

Field values directly binded to backend service are getting cleared.

Hi,
In HCM Forms & Process, for ex: in a form the header field values are directly binded to SAP_PA backend service and rest of the fields (dropdown list and free text fields) are getting from custom generic service. Now there is also a pushbutton in my form is used to calculate percentage of a field. Now when the form is displayed by default the header values are getting populated from SAP_PA backend service. When I click the push button with out selecting values(drop down list) getting from generic service all header field values are getting cleared. But if I select any dropdownlist value before selecting pushbutton and then if I click pushbutton all the header fields are retained with values. I am facing this problem for all the forms that I developed. I am looking for valuable answer.
Regards,
Nayani .

So you are or are not using a user event? Sounded like you were which was firing when the user selecpiushed the "button" for calculating fields. Whatever "event" you have tied that button too seems to be your culprit. Are you doing this calculation in Javascript off the button "onClick" even or passing it to a HCM P&F "user event" in the backend? If it is to a HCM P&F "user event", that's where I would make sure your fields are selected.
From the sounds of it, it seems when you do NOT select a dropdown list value, your generic service is not handling this gracefully and an error occurs. That would cause ALL other services NOT to run. It's an odd thing the framework does and often very frustrating to hunt down, but whenever any service errors, it will not run others.....hence no fields coming back correctly....even if those other services have NOTHING to do with yours (weird, I know).
Hope this helps.

Sample projects on direct binding in osb 10.3.1

Hi All,
Can anyone suggest me some sample projects in osb 10.3.1 describing direct binding
Thanks in Advance!!

Hi Roshni,
You can find examples for OSB 10.3.1 here, not sure if there's one for direct binding, but may be useful anyway...
http://java.net/projects/oracleservicebus1031/downloads?page=1&theme=java.net
Cheers,
Vlad

SOAP fault propagation for Direct Binding

Hello.We have following set-up
Composite A --- OSB -- Composite B
Composite A exposes HTTP interface (one-way operation) and refers to one-way operation of OSB (over direct binding) which again calls one-way operation of Composite B (again over soa-direct)
Error in composite B is propagated properly to the OSB. I've tested same also with HTTP proxy on OSB, HTTP 500 returned in case of error in Composite B
But Composiet A never raises error to the HTTP service. Thus Consumer is getting HTTP 200, regardless downstream error

try with a non blocking invoke. That will cause a new invoke message to be generated, and a commit of the currently active transaction. So, while the new invoking transaction will be rolled back, a catchable fault will be thrown, and the running tx will commit.
However, if you are not intending to use a transactional system integration, you could go the soap route as well.
your call, my 2cents.

Dynamic Directive in Java App

I created a JSP using the dynamic directives based on what is in the Application Development guide of mod_osso. I have the app deployed on a standalone oc4j 9.0.3. It doesn't seem to pick up the getRemoteUser...do I need to deploy in the OHS, or am I missing a requirement here?
Thanks in advance.

Eric, given that mod_osso is an apache module, it is a requirement to use OHS with OC4J.
Thanks.

Error handling for Direct binding

Hi
Anybody handled Direct binding exceptions. I have a requirement if the direct binding service is down I have to catch it and do some action. when I have catch or catchAll not catching it. I am getting rollback fault so my bpel waits continuously in running mode. I have a mediator then bpel. mediator times out but bpel is in running mode.
Thanks
comp

What are the limitations or disadvantages of SOA Direct Binding

What are the limitations or disadvantages of SOA Direct Binding.

When we call SOA service from another SOA service most of the time Local RMI call is used even you are using SOAP over http to invoke the service, this based on your SOA configuration - Refer the following url for more details on Local optimization.
Albin's Blog: Configuring Local Optimization in Oracle SOA 11g
SOAP binding will help us to invoke the service exposed with WSDL and accepts XML as request/response.
HTTP Binding will help us to invoke any services that will accept HTTP GET/POST messages but there is restriction with input/output message type(refer this document for more details Getting Started with Binding Components - 11g Release 1 (11.1.1.7)).
HTTP binding is light weight and provides better performance.
I hope this will help you.
Refer https://forum.java.sun.com/thread/2612466

Dynamic Direct Binding reference

Similar Messages

Maybe you are looking for