GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1334
CAMEL-10570 camel-salesforce: add metadata to generated DTOs
This commit adds SObjectDescription by making the DTOs extend
AbstractDescribedSObjectBase (new class) instead of AbstractSObjectBase.
The code generation is performed in Velocity template by recursing the
bean SObjectDescription properties. Helper methods are added to
GeneratorUtility that help track the stack of the recursive invocation.
To prevent hitting Java method length restriction (64K) some properties
are blacklisted: PicklistValues and ChildRelationships which most likely
would not be needed in the component operation anyways.
@dhirajsb would you mind taking a look at this?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zregvart/camel salesforce-metadata
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1334.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1334
----
commit a7cdf08cf52ef4f5cc6f418e6357142b5a441b9a
Author: Zoran Regvart <zo...@regvart.com>
Date: 2016-12-08T10:27:28Z
SObjectDescription metadata in DTOs
This commit adds SObjectDescription by making the DTOs extend
AbstractDescribedSObjectBase (new class) instead of AbstractSObjectBase.
The code generation is performed in Velocity template by recursing the
bean SObjectDescription properties. Helper methods are added to
GeneratorUtility that help track the stack of the recursive invocation.
To prevent hitting Java method length restriction (64K) some properties
are blacklisted: PicklistValues and ChildRelationships which most likely
would not be needed in the component operation anyways.
(cherry picked from commit 2d14fd8caa58f4520cf70801a27a0a57b023f492)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
