Fred, Yes.....and...
I think the real root issue is really how ARS maps it's ARS field into the XML universe. ( Including the dataType, Nillable and/or minOccurs properties.) Some dataTypes like "int", in Java, can not be set to null. However, again in Java, an Integer object can be null. I think the root/general issue is how ARS _by default_ creates the attributes in the inbound and outbound mappings for "optional" ARS fields. It does not set Nillable or minOccurs properties properly (IMHO) and the dataType values may need to be adjusted too. ( Even if only for better inter-operation with some environments. Generally mapping to objects when you can produces better results in my experience. I like to leave the primitives [dataTypes] to the primitives [primitive primates]. :) ) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Dec 20, 2007 10:04 AM, Grooms, Frederick W <[EMAIL PROTECTED]> wrote: > In the Web Service XML Maps (both Inbound and Outbound) you can set both > the Nillable and MinOccurrs attributes for a field. You can find more > info on this by pulling up the Help -> Contents and Index in the Admin > tool and viewing the entry on XML editing. > > Fred > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black > Sent: Thursday, December 20, 2007 5:48 AM > To: arslist@ARSLIST.ORG > Subject: Re: Consume AR System Web Services through .net framework 2.0 > > Misi, > > "Optional" ( in ARS) does not translate into the Web Service universe by > default. I have no idea why they skipped that important attribute. > In XML there is a "nillable" attribute/concept that will allow the > element to not be there. It is my understanding that nillable allows the > XML element to have no contents. > > Ref: http://www.w3.org/TR/xmlschema-1/#xsi_type > " > xsi:nil > > XML Schema: Structures introduces a mechanism for signaling that an > element should be accepted as *valid* when it has no content despite a > content type which does not require or even necessarily allow empty > content. An element may be *valid* without content if it has the > attribute xsi:nil with the value true. An element so labeled must be > empty, but can carry attributes if permitted by the corresponding > complex type. > " > > While the XML minOccurs attribute/concept allows the element to not be > in the xml at all.( "<element/>" vs "") > > > > However, I think the rub in this case is that in the Java universe (and > apparently in the .Net universe too) there are some data types that can > not be "null". So I think the real issue is likely the XML dataType for > the element instead of these other issues. :) Maybe if you use a > dataType that is a full object instead of a primitive that would allow > Java/.Net to deal with an "optional primitive" data element. Maybe > "integer" would map to the object classes in Java/.Net? > > Just a thought. > > HTH. > > -- > Carey Matthew Black > Remedy Skilled Professional (RSP) > ARS = Action Request System(Remedy) > > Love, then teach > Solution = People + Process + Tools > Fast, Accurate, Cheap.... Pick two. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
