In the templates, is there any problem renaming the "create$BeanClass" Method of the manager Class to "createBean" ?
It's just to gain a little time coding with the generated classes...
Thank your for hints about this modification !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fervent adept of the autocompletion I never care about the length of the methods name. It may be a bias...
If you were going to change the manager.java.vm template to implement your above mentionned change, you should consider two "search and replace":
- "create$beanClass" to "createBean"
- "create${importedClass}" to "createBean"
I can see an added advantage to your proposed change: whatever manager you access, you always call the same method to create a new bean. It could however as well be seen as a danger... But for further code generation, it is clearly an advantage. OTOH...
Hope this helps,
Alain.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the templates, is there any problem renaming the "create$BeanClass" Method of the manager Class to "createBean" ?
It's just to gain a little time coding with the generated classes...
Thank your for hints about this modification !
Fervent adept of the autocompletion I never care about the length of the methods name. It may be a bias...
If you were going to change the manager.java.vm template to implement your above mentionned change, you should consider two "search and replace":
- "create$beanClass" to "createBean"
- "create${importedClass}" to "createBean"
I can see an added advantage to your proposed change: whatever manager you access, you always call the same method to create a new bean. It could however as well be seen as a danger... But for further code generation, it is clearly an advantage. OTOH...
Hope this helps,
Alain.