This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
no pollable reply channel has been configuredPage Title Module
With regards to this issue we are thinking in terms of EventMessage pattern. So in your case although you have no arguments to path it is stil an event, agree? If so, the Event Message would still have to have some payload (we do not allow 'null' payloads and probably will never do) and we'll provide a way, probably via annotation, to specify what that is. So with regards to your use case what do you think such value woud be?
I guess it would have been easier explaining my situation with a well known pattern...
I don't envision having anything specific that would be required for the payload. I did figure that we may put some metadata into the message header (not sure exactly what that will be yet). I guess if the payload is not going to be used on the receiving end, it could be some constant representing a null/empty object.
You can just add a @Payload annotation on a method of the gateway interface (with a SpEL expression as its value), OR you can provide a "payload-expression" attribute in the <method> XML sub-element of a <gateway>.