Two services that are causing me problems.
==========
wm.tn.doc.xml:bizdocToRecord
- Declared Input: bizdoc
- Declared Output: boundNode
Problem: Unfortunately, the service leaves an undeclared output -
recordName. Worse, it drops its input variable bizdoc on the third
step!
=====
wm.tn.doc.xml:<strong>recordToBizdoc</strong>
- Declared Input: boundNode, doctypeIdentifier, rootTag, htmlEncode,
recordName, generateRequiredTags, TN_parms - Declared Output: bizdoc, TN_parms
Problem: ALL inputs got dropped, except for TN_parms.
=====
I think both of these are unacceptable. Leaving undeclared variables in the
pipeline cause problems for services which call these. They interfer with
services called later – e.g. Calling bizdocToRecord, and another service which
accepts recordName as optional input, will result in error if the 2nd
service is process another input record. Pretty much, variables are popping up
beyond developers’ control. Dropping input variables is again problematic.
Developers don’t expect their variables (which still shows up in their pipeline
when developing) have actually disappeared. The disappearance of variables being
decided by webMehods, rather than the developer.
On TN 6.*, the services are protected by the
<wmprivate> ACL, so takes a bit of work to fix. I’ve
raised the issue w/wM support, but they are telling me that “it’s the correct
behavior”. What to do? What to do? Code my own services? I don’t really want to
modify them, as they could very well get overwritten during an upgrade. Any
thoughts on these?