"[email protected]" wrote : I suspect that the extra data is passed as
extensions in the WS messages, though I cannot tell for sure that this is the
case. You might be able to do something similar using a standard JAX-RPC
Handler to achieve the result you desire.
Hi,
thanks for this hint! you are right, I tested this in a WLP 10.2 consumer -
JBoss Portal 2.6.4 producer scenario and managed to pass data using BEA's
custom transfer mechanism. Basically, from WLP portlet backing file you can add
the object to the request something like:
request.setAttribute(MarkupRequestState.KEY, "TEST");
The WLP consumer will serialize, encode this object (Base64) and add an
extension to the SOAP message (getMarkup) with the result, something like:
<v1:extensions>
<ext1:MarkupRequestState xmlns:ext1='urn:bea:wsrp:ext:v1:types'>
<ext1:state>
rO0ABXQAC0dFT1JHRSBURVNU
</ext1:state>
</ext1:MarkupRequestState>
</v1:extensions>
As you mentioned, this value can be extracted from the SOAP message, Base64
decoded and deserialized on the JBoss Portal side using a custom JAX-RPC
handler (for the MarkupService).
However, a downside of this approach is that, in case of sending custom
objects, you need to have the same version of the class on the producer as
well, otherwise the deserialization will fail. Therefore is safer to use
primitives and common java objects.
Cheers,
George
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215631#4215631
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215631
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
