Application Platform 10.3 | Developing with Application Platform in Designer | About Using Services in Application Platform | Generating POJO Wrappers for IS Document Types and Specifications | Coding Considerations
 
Coding Considerations
You must keep the following points in mind when generating POJO wrappers for IS document types and specifications:
*You cannot generate service wrappers for product services from Wm packages, but you can generate POJO wrappers for IS document types and specifications, residing in Wm packages and then reference these data structures from custom services.
*You can use nested document types, but you cannot generate a service wrapper for a document type that includes a recursive reference, for example, when a field in an IS document type refers to itself.
*You can use document types and specifications that contain object references only to String, Date and primitive data types. You cannot generate a service wrapper for a document or specification that contains a reference to an IS IData object.
*The valid identifiers for field and record names in Integration Server differ from valid Java identifiers. To address this when generating identifiers for Java services, Application Platform substitutes characters, that are illegal in Java with underscores.