|The OMG-blessed term is "IOR profile". There is also a thing called "IIOP |context", which is a per-message stuff. An IIOP request to some target IOR |carries some of the data stuffed into the target IOR (the object key, |which includes the object id field), plus zero or more IIOP contexts (data |chunks typically used to carry info related with transactions and/or |security), plus the actual invocation info (operation and arguments).
interesting this is exactly my client interceptor design, only pure java. |Any profiles present in the target IOR are _not_ sent along with the |request. Hence there is no point in stuffing a container's JMX name |within an IOR profile. (I use a profile for codebase info, which is |needed at the client side for remote classloading, but is not required |to travel within every request.) I have a notion of 3 payloads as-is, marshalled, transient. |There is no point in putting the container's JMX name in an IIOP context |either, because the context is not a "per IOR" thing. | |So the JMX name must go within the object id. There is no other place. right which is part of the marshalled one in our case, the marshalled map can be anything though. as-is is meant for java JDK types. marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
