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.
Should IntrospectionRegistryImpl.introspect be changed
or is the spec wrong in its assumption?

Reply via email to