DD4T 2.0 with Java MVC - Is it possible to use the same CT for multiple components(based on same schema) schema) while using ViewModels Class

Question

Is it possible to use the same CT for multiple components(based on same schema) considering the mapping required at ViewModels Class for CT name. Because if we see the source for CT is same as using same TBBs "Generate dynamic component", "Publish binaries for page".

Idea is not to create new CT for each component which are based on same schema to reduce no. of CP items created in DB as end result which are huge.

Trying to achieve something as displayed below in snapshot:

Answer 1

Yes, it is possible to use the same CT for multiple components (based on a single schema), per ViewModel though.

It is sufficient to built one component template for every view model that you have. In Tridion, you will continue to use the same TBBs with your CT unless component template metadata is different based on your entity or view. You can add more TBBs to suit your requirement but the output should be "JSON".

Refer an useful article from Albert here

You will offcourse have to add your schemas to the linked schemas within the CT in Tridion.

Update

Well, I am having trouble interpreting your snapshot but I would like to point out that you would need one View Model for every schema that you built. Based on the code that you have below, you are missing the getter / setter methods for each of the fields that you have defined for your schema.

I think I already sent the article in another response to your other question but the following diagram (from Raimond's post) explains a lot.

I would appreciate if you can update your question with the code in comments and try to come up with clarification so that the community can address.

Answer 2

After reading the comment:

I need separate viewModel class for C1 and C2. because C1 and C2 has different set of content(based on same schema) and C1 and C2 has separate component JSP or component view.

I think I know what you mean. While having the different models under the same view model name or schema is a future improvement, in the mean time the dd4t-databind framework is flexible enough to have two different model classes for Component Presentations, with the same combination of Schema and Component Template. It's a bit hacky, but this is possible:

ViewModel A:

@ViewModel(
    viewModelNames = { "header_ct", "footer_ct"},
)
public class HeaderAndFooter extends TridionViewModelBase { } 

ViewModel B:

@ViewModel(
    rootElementNames = { "content" },
)
public class Content extends TridionViewModelBase { } 

This way, in your JSPs you can do:

View A:

<jsp:useBean id="header_ct" type="com.foo.HeaderAndFooter" scope="request"/>

View B:

<jsp:useBean id="content" type="com.foo.Content" scope="request"/>