[
https://issues.apache.org/jira/browse/CAMEL-16666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435509#comment-17435509
]
Jeremy Ross commented on CAMEL-16666:
-------------------------------------
[~jawwad124] From an API perspective, the package prefixes are nothing more
than naming conventions for Objects and Fields. The DTO generation should
handle this without issue. If you've gone from un-prefixed to prefixed, I think
you're just going to have to update your mapping layer as you said. There's no
way Camel could know which objects (and even harder) which fields should be
prefixed.
> Support for Salesforce Package Namespaces
> -----------------------------------------
>
> Key: CAMEL-16666
> URL: https://issues.apache.org/jira/browse/CAMEL-16666
> Project: Camel
> Issue Type: New Feature
> Components: camel-salesforce
> Reporter: Jawad Ahmad
> Priority: Minor
> Labels: help-wanted
>
> When packaging an app for Salesforce App Exchange, it's required to provide a
> package namespace to avoid conflicts. This namespace is usually prefixed to
> every custom object, its fields, and event.
> E.g a custom object of 'Invoice __ c' would become 'namespace __ Invoice __ c'
> Just a thought, if we can provide some configuration for Salesforce component
> to specify a namespace as property to of route to make it easier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
