Hi Jody,
Jody Garnett schrieb:
I don't understand what you mean with using an java.util.Map to store
the complex information.
The default bindings handle things like xs:int and know enough to turn
that into an Integer. The default binding for an a complex type (at
least for an earlier
Hi
Is that my name being taken in vain? I think you mean Matthias. I'm
not at all suprised though that complex data type support requirements
are coming out of the wild, and being blamed on me :-)
Matthias - will you be at the OGC meeting in Darmstadt next week by
any chance? I'll be there,
Hi Rob!
Rob Atkinson schrieb:
Hi
Is that my name being taken in vain? I think you mean Matthias. I'm
not at all suprised though that complex data type support requirements
are coming out of the wild, and being blamed on me :-)
Matthias - will you be at the OGC meeting in Darmstadt next
Is that my name being taken in vain?
Not at all; we just finally have a friend for you has also found the
limits of what can be done.
Taking your name is almost never in vain - you are very good about answering.
All the best,
Jody
The default bindings handle things like xs:int and know enough to turn
that into an Integer. The default binding for an a complex type (at least
for an earlier version of the parser!) would produce a java.util.Map with
the keys as the element name and the value as appropriate.
I see! What
Jody Garnett schrieb:
The default bindings handle things like xs:int and know enough to turn
that into an Integer. The default binding for an a complex type (at least
for an earlier version of the parser!) would produce a java.util.Map with
the keys as the element name and the value as
Hi Justin, all,
upon your bug fix for the parsing problem I'm stucked with the next
problem: The WPS process requires three input parameters. Two of them
are literals and I can easily create them with
MapString, Object parameters = new HashMapString, Object();
parameters.put(scenarioScope,
Hi Matthias:
I have just been paying attention to the Parameter definitions in
order to make swing dialogs for the demo section. There is no
requirement for an object tree (we just take it when we can get it); I
would of expected a java.util.Map to hold the complex information (if
it was
