This may seem an extreme suggestion, but how about avoiding the use of Java types altogether? Have everything pass through as strings?
According to the wM doc:
“Object and Object list variables constrained with a Java classes should be linked only to other Object and Object list variables of the same Java class or of unknown type. Although Developer permits a link between constrained Objects of different Java classes, the run-time behavior is undefined.”
I assume that’s what you’re doing. If not, please correct me.
This is a bit off-topic for the post but…
There seems to be a growing number of questions and comments about this general topic. Associating an Object field with a Java class is a pretty cool thing, but I wonder if some might be taking things a bit too far. I wonder about the wisdom of defining Document structures with fields defined as Object and associated with a Java type (long, integer, boolean, etc.).
I wanna hear from the 6.0 users out there–What are the real benefits to using data types other than string? Are you using such Document definitions as intermediate representations only or to interact with an existing Broker document definition? Does using them cause more pain than benefit?