Project: mule
Issue MULE-9168: Users should not be forced to use @Parameter to expose pojo fields
In order to expose pojo fields users are force to annotate the each field with @Parameter. When users consumes external jar, they cannot modify the code. Also if they generate java stubs from a WSDL using CXF, they will need to modify a huge amount of Pojos just to get this to work properly, and what is worst, if a new version of the WSDL goes out and you try to update your connector, you will lose everything after generating the new stubs. The mechanism should be that if the Pojo has any field annotated with @Parameter, then the current logic is valid and should only expose those fields. However, if the Pojo has no @Parameter, every single field that has a gettter and setter should be taken into account (including nested pojo fields)
Story points: 8