I see.
There *will be* something at /{type}/{name}, and it will represent the
module as a whole (not just its definition)


On Thu, Oct 31, 2013 at 3:37 PM, Gunnar Hillert <notifications@github.com>wrote:

> In
> spring-xd-dirt/src/main/java/org/springframework/xd/dirt/rest/ModulesController.java:
>
> > @@ -134,4 +146,66 @@ private ModuleType determineType(List<ModuleDeploymentRequest> modules) {
> >  		throw new IllegalArgumentException("invalid module composition; must expose input and/or output channel");
> >  	}
> >
> > +	/**
> > +	 * Retrieve the configuration file for the provided module information.
> > +	 *
> > +	 * @param name the name of an existing resource (required)
> > +	 * @param type the type of the module (required)
> > +	 */
> > +	@RequestMapping(value = "/{type}/{name}", method = RequestMethod.GET, produces = MediaType.TEXT_PLAIN_VALUE)
>
> Thought about using the URL /{type}/{name}/definition. Decided against it
> as we then don't have anything for /{type}/{name} right now --> *See
> Question 2* on top of this PR *Should we create a Jira to return the
> Meta-information for a specific definition* (Out-of scope for this Jira)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/spring-projects/spring-xd/pull/377/files#r7343078>
> .
>