I would avoid using domain objects in the rest layer generally .

Here especially, they are quite different: one could be named ModuleInfo or
something. Consider info about parameters as well, would it be in the non
rest class?
Le 26 sept. 2013 18:36, "Mark Fisher" <notifications@github.com> a écrit :

> In
> spring-xd-dirt/src/main/java/org/springframework/xd/dirt/stream/ModuleDefinition.java:
>
> > + *
> > + * Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on
> > + * an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the
> > + * specific language governing permissions and limitations under the License.
> > + */
> > +
> > +package org.springframework.xd.dirt.stream;
> > +
> > +import org.springframework.xd.dirt.core.BaseDefinition;
> > +
> > +/**
> > + * @author Glenn Renfro
> > + *
> > + * @since 1.0
> > + *
> > + */
>
> I was talking about org.springframework.xd.module.ModuleDefinition which
> is included in ModuleDeploymentRequest messages. So, that's actually
> different than the use of these "definitions" within the REST support
> layer, but it does have a very similar shape - I wonder if we should
> consider reusing it across both responsibilities?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/spring-projects/spring-xd/pull/315/files#r6605931>
> .
>