[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Test for an optional XML element in an orchestration...

• To: xml-dev@l...
• Subject: Re: Test for an optional XML element in an orchestration...
• From: "Thomas B. Passin" <tpassin@c...>
• Date: Sat, 20 Apr 2002 23:21:40 -0400
• References: <20020421030046.62125.qmail@w...>

[tariq abdur-rahim]
>
> Is it possible to test for an optional XML element in
> an orchestration?
>
> If you have an orchestration with a decision, you can
> test for various values of elements in an incoming
> XML document. You can even test if an element
> is null "not isnull()".
>
> However, how can you test if an optional item exists
> in an incoming document?  If you try to expose the
> field ( so you can see it on the data page for example
> ) it provokes an error as the document
> comes in.
>
>

It depends on how you are doing it, after all.  With an xslt stylesheet,
it's easy - you get nothing if the element does not exist.  With SAX, no
handler for the element gets called.  With DOM you can ask for an element by
name(getElementsByTagName() or getElementsByTagName NS(), which return node
lists, possibly empty).  Or, with whatever your current approach is, you can
use a try/except structure to avoid error exits.

Tom P

• References:
  • Test for an optional XML element in an orchestration...
    • From: tariq abdur-rahim <ecliptoid330@y...>

• Prev by Date: Test for an optional XML element in an orchestration...
• Next by Date: Re: Can you stand yet another SOAP-RPC vs HTTP GET question?
• Previous by thread: Test for an optional XML element in an orchestration...
• Next by thread: What does SOAP really add?
• Index(es):
  • Date
  • Thread