Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command Endpoint [SWS-18] #177

Closed
gregturn opened this issue Apr 3, 2006 · 3 comments
Closed

Command Endpoint [SWS-18] #177

gregturn opened this issue Apr 3, 2006 · 3 comments

Comments

@gregturn
Copy link
Contributor

gregturn commented Apr 3, 2006

Arjen Poutsma opened SWS-18 and commented

Provide a PayloadEndpoint implementation that resembles the CommandController in Spring-MVC. With this endpoint, it should be possible to populate a Java Bean with information from the incoming message. The population can take many forms. For instance, by providing a map with property names as keys, and XPath expressions as values. As a message comes in, the XPath expressions will be evaluated, and bound to the bean.

We should use the standard Spring Binding and Validation framework as part of this.


Issue Links:

@gregturn
Copy link
Contributor Author

gregturn commented Jun 5, 2006

Arjen Poutsma commented

We will probably also use the templating support in spring-modules, to render a response message based on a model created in the endpoint.

@gregturn
Copy link
Contributor Author

gregturn commented Sep 6, 2006

Arjen Poutsma commented

I'm not sure if this needs to be implemented for 1.0.

I've moved it out of the release plan for now, if you want to see it implemented, vote for it.

@gregturn
Copy link
Contributor Author

Arjen Poutsma commented

I think the new @XpathParam annotation, and O/X marshallers such as TopLink already provide a solution for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants