Working with Allegro (9.2) Orblink, we occasionally get errors
such as the following:
[excuse the poor formatting...]
Debug: #<bad_param :repository_id "IDL:omg.org/CORBA/BAD_PARAM:1.0"
:minor 1000
:completed :completed_maybe. message.invoke.invoker-body: Bad response of
((#<edu/cmu/ozone:ordercapacitydata :orderdata #<edu/cmu/ozone:orderdata
:type
"AR-REQUEST" :receivertype "other" :name "AU1030400132" :ald 333297127 :rdd
333298927 :ead -1 :fdd 333297127 :fad -1 :pos -1 :depos -1 :status
"SCHEDULED"
:description "" :poe "017S" :pod "017S" :origin "017S S" :destination ""
:priority "1A1" :resource "" :schedulingcommand "" :annotation "" :impact ""
:locked nil :opid "Awaiting TACC Final" :mdstype "" :asgnmds "" :granted ""
:callsign "" :numaircraft -1 :contactinfo "" :altitude "200"
:reversetrack nil
:shorttrack nil :rendezvoustype nil :crewtype "" :extracrew -1
:mipstanker nil
:refueltanker nil :sparetype "" :fuel "" :code "" :timeontrack 0.5
:sequenceid
[etc, ...]
This goes on for a number of lines. Now the problem is that one of
the empty-string values ("") above are not what the client program
is expecting, but it can be quite time consuming to figure out
which one. Since the interface is well defined in the idl file,
and Orblink knows which field it's breaking on, I'd much prefer
a more specific error message.
Is there something I'm missing, and has anyone encountered a
better way to debug this type of problem?
Thanks,
Larry