adding ReferenceProperties to TxContext

[odin69]

Hi All,
I want to alter the JaxRPCHeaderContextProcessor to add a ReferenceProperties Element to the outgoing Context of a SOAPMessage. The ReferenceProperties Element should contain an Element address with a namespace as attribute and a String as content.

Unfortunately I am stuck right now because I don't know how to create the NamedElement/ElementContent.

Are there any docs about this topic someone could point me to or am I completely wrong trying to alter the Handler in order to alter the outgoing context?

THX in advance

[marklittle]

The ReferenceProperties are set by the EPR minter. Are you (or the code you are describing) acting in that role?

[odin69]

Mmh well I don't really know what you mean by EPR minter, the altered JaxRPCHeaderContextProcessor is the ClientHandler where the Context will be created, if this helps.

So maybe you have a minute to give me a short description what you mean by EPR minter, that would be awesome.

thx

[marklittle]

The "minter" of the EPR is the thing that created it. The ReferenceProperties/ReferenceParameters come in the EPR when it is created and are then propagated into the "top level" of the SOAP header when it is used. They are supposed to be opaque to anything other than the ultimate destination. You should not be looking to modify them once the EPR from which they come has been created. Is that what you are trying to do?

[odin69]

Well yes this is what I had in mind... so I have looked through the code but so far I wasn't really successful in finding the minter to add the referenceProperties directly at the source.

If I understood you right then I shouldn't try to alter the context in a handler, right? So except finding the minter and add the referenceProperties directly at the source is there another way to do it, and if not can you point me to the location of the minter?

thx so much

[marklittle]

Yes, you should really be modifying the context at the source. Now the next question is: why do you want to modify the TxContext?

[odin69]

I want to make a JBoss client to start a transaction with a web service which is implemented with apache Kandula. So as far as I can see right now the only difference between the two context are that in Jboss the instanceIdentifier is contained in a referenceParameters element whereas kandula uses a referenceProperties element.

So I have tried to modify the context send out from JBoss to see if the client and service can have a transaction together. Does anyone have some experience with this topic allready? Well maybe I am totally wrong with the context-solution but I guess its worth a try.

[marklittle]

"odin69" wrote:
I want to make a JBoss client to start a transaction with a web service which is implemented with apache Kandula.

So the JBossTS Web Services Transactions implementation isn't in this picture? If that's the case, then are you using JBossWS?

So as far as I can see right now the only difference between the two context are that in Jboss the instanceIdentifier is contained in a referenceParameters element whereas kandula uses a referenceProperties element.

So I have tried to modify the context send out from JBoss to see if the client and service can have a transaction together. Does anyone have some experience with this topic allready? Well maybe I am totally wrong with the context-solution but I guess its worth a try.

I don't have experience with Kandula, except to say that it wasn't one of the implementations that took part in any of the interoperability workshops that we held with IBM, Microsoft etc. So there may be other issues waiting for you to discover as well.