TN: Why not generate from one template multiple files?
JT: As inception review said it is not needed.
TN: Still it might be useful.
PP: CRUD application is our usecase.
JT: You can always call for (DataObject obj : ...)
RK: Let's solve in another phase and in another review.
PP: Enough to have multiple small templates, but it is necessary to show and
in Template Manager.
*TCA*: necessary to show and edit them in Template Manager meaninfully.
I think I have a fix, I'll attach a diff.
Created attachment 38423 [details]
One can use "simple" property to hide things from template manager
Looks good to me.
Can you explain the connection between the requirement ("enough to have multiple
small templates, but it is necessary to show and edit them in Template Manager")
and the fix (hide some folders from Template Manager)? There is no explanation
here of how you expect compound templates to work.
I see, sorry, I was talking to Martin A. and did not realize that others do
not know the details of our discussion.
> Enough to have multiple small templates, but it is necessary to show and
> edit them
> in Template Manager.
With this fix you can create a Templates/EJB3.0 folder and put there all the
small templates you need, and then you can create on "big" template
Templates/EntityJavaBean.instance that delegates to all the small templates in
the EJB3.0 folder and tell that it is "simple"=Boolean.FALSE. That way
this "big" template is not going to be visible in Template Manager, just in
New File wizard. Imho, this is the needed enhancement that
No more comments? Then I integrate tomorrow...
new revision: 1.36;
new revision: 1.13; previous revision: 1.12
new revision: 1.4;