camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sohrab <sohrab.hosse...@gmail.com>
Subject camel-salesforce enum class generation overrides itself
Date Mon, 18 Apr 2016 03:38:09 GMT
I am not sure what is the reasoning behind stripping '__c' from the enum
class names when generating DTOs in camel-salesforce:

https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-maven-plugin/src/main/java/org/apache/camel/maven/CamelSalesforceMojo.java#L698

But it breaks when less-than-competent Salesforce vendors introduce fields
with the same name as OOTB fields.

For example, there is an OOTB field called 'Status' and the sf developer has
also introduced 'Status__c' (don't ask me why). When generating the classes,
it generates 'StatusEnum' class for 'Status__c' and then promptly overwrites
it with 'StatusEnum' class for 'Status'.

Does anyone know/remember why we just didn't do 'Status__cEnum' classes?
Would it break a whole lot of things (backward compatibility?) if we went
with that approach?



--
View this message in context: http://camel.465427.n5.nabble.com/camel-salesforce-enum-class-generation-overrides-itself-tp5781229.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message