I reproduced your senario on my side and found it is rational to make an improvement on the Component Development Tool to resolve the trouble you encounter.
The change taken on the tool is that when selecting java.lang.string as an input/output parameter of an operation, the generated function Java class would be String someMethod(String foo) instead of java.lang.String someMethod(java.lang.String foo).
The update will come up in next release.
Thank you again for using our product and sharing your experience with us. The product would be better by your valuable advice.
I'm very excited to see that change coming down the pipe. Is there anyway to make it smart enough to handle custom data types as well? I always assumed that I could add my packages to runtime --> import classes and that it should import them as necessary. Is there a mailing list to learn when new versions are released?
Untill now, there is no plan for us to develop the feature of generating component with custom data type automatically, so this feature will not come up in next release. As a result, you need to do coding manually to add a custom data type as input/output.
However, your requirement is very valuable for us to design enhancement feature for this tool in further release.
Thank you again,