Hello,
Are there any documents discussing the philosophy behind the objects in OpenAPI? We just spent several hours poking around in the Javadocs trying to figure out how to extract task file comments. We finally found it about 6 objects below tasks. It might be easier to navigate the Javadocs if we had an idea what the OpenAPI developers were thinking.
For example, why does everything have a data object? For example, to get the name of a task, you have to call getTaskData(), then access the field of that object. Seems like a lot of work just to get the name. I would have expected something like getTaskName() right off the task object.
I'm also curious why so many methods require IWWorkflowService to be specified. If I have to specify the service to get the task in the first place, shouldn't the task object remember from whence it came and use the same service for all it's methods?
I'm sure there's good reasons for they way the API is set up, I just can't see it. A primer on why the classes are the way they are would go a long way to helping us use the API.
<P>
==
Terry Luedtke
National Library of Medicine
terry_luedtke@nlm.nih.gov
