On Dec 20, 2006, at 2:04 PM, Ignacio Silva-Lepe wrote:
I noticed that IntrospectionRegistryImpl.introspect uses
getAllPublicAndProtectedFields to obtain the fields on
which to invoke each processor's visitField. However,
the C&I spec seems to imply that it should be possible
to inject a conversation id (the spec still refers to it as
@SessionID but that's another matter) into a private
field.
I've already changed @SessionID in the latest version of the spec.
The other issue regarding private fields is a bug in the spec - it
should be protected or public. Could you file a JIRA at the OSOA site
so we don't loose track of that?
Thanks,
Jim
Should IntrospectionRegistryImpl.introspect be changed
or is the spec wrong in its assumption?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
