senthil.arumugam wrote:
Hi Willem,
Our use case is, we need to save or update the entity.
For eg,
We have a message of instance Foo and we need to decide whether the instance
to be saved or updated etc. This behavior is common across all the messages.
So we are wrapping Foo (actual message entity) with SampleMessage<T> which
has a generic property and a String property of type.
Based on the type, we will route the message body to actual bean to process
the same.
I meant by the term 'actual message', the entity which holds the body of the
Message.
I would be interested to hear from you, how did your thought process go when
you got to think to replace proxy instance.
Oh, forget what I just said, I'm thinking your implementation is based
on the proxy, but after thinking it twice the message body is
BeanInvocation instance and it have nothing to do with your wrapping
implementation.
Thanks,
- SK
Willem
