Mark,
I guess I should elaborate on what I mean by “troublesome”. I think it parallels the steps involved in finding out sender/receiver ID after identifying the TN DocType. That is, it rarely make sense to being able to extract sender/receiver ID before identifying the TN DocType. You wouldn’t know which partner is identified by “100300400” unless you know that it is a DUNS number, for example.
So in the same way, I don’t quite understand how one would want to do RegEx to identify a DocType. Since you’re doing RegEx, that means you’re not quite sure where a certain tag or value would show up in the document – and by extension, you’re not exactly sure how the document is structured. For B2B purposes (which TN is intended), not having a strictly defined DocType (by Schema or DTD) is asking for trouble. There would be so many BRANCHes in a mapping flow, for example, since you won’t be sure which of the multiple documents you’re actually processing.
In other words, I’m thinking of using RegEx in identifying query as a way of matching multiple document structures as the same DocType. Really don’t sound like a good idea. I think having RegEx in XQL makes a lot more sense when doing queryDocument. But, I’d love to hear about any kind of real usage for RegEx in Identifying Query…
#Integration-Server-and-ESB#B2B-Integration#webMethods