[
https://issues.apache.org/jira/browse/OFBIZ-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446661#comment-13446661
]
Adrian Crum commented on OFBIZ-5020:
------------------------------------
What you call a "column name trick" is what I call an ugly hack that will lead
to hours spent trying to debug quirky behavior. The "trick" will not work on
databases that use upper case column names.
There are many instances where OFBiz provides more than one path to a solution.
I don't agree that this pattern causes confusion.
This could be a simple enhancement, but both of you are trying to make it
unnecessarily complicated. Add the new field and a bit of code to use it and
you're done.
> change serviceName by customMethod on Content
> ---------------------------------------------
>
> Key: OFBIZ-5020
> URL: https://issues.apache.org/jira/browse/OFBIZ-5020
> Project: OFBiz
> Issue Type: Improvement
> Components: content
> Affects Versions: SVN trunk
> Reporter: Nicolas Malin
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: OFBIZ-5020.patch, OFBIZ-5020.patch, OFBIZ-5020.patch
>
>
> At this time, when you use a content as template, the content.serviceName
> value use to call the context populate service before rendering.
> I propose to replace serviceName field by customMethodId and use customMethod
> pattern for more flexibility.
> serviceName field will be move to oldServiceName field for backward
> compatibility
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
