Dang, I overlooked this reply before sending mine. Thanks for confirming my train of thought :)
Jason On Wed, Jan 23, 2013 at 3:46 PM, Grooms, Frederick W < [email protected]> wrote: > There is a table on Pg 355 of the Integration guide > <name></name> Name=$NULL$ or xsd default > When the XML element has empty content, AR System first tries to use > the xsd default if it exists. (There are two different defaults-the AR > System default value and the xsd default value. For empty contents, AR > System always uses the xsd default value.) Otherwise, it sets the field to > NULL. > > In order to have the Form Default used you should remove the element > completely from the soapUI payload > Missing <name> Name is not modified, or it is set to AR default. > (when minOccurs=0) > When an XML element is missing, AR System treats it the same way as a > missing field. Therefore, in a create operation, the field to which the XML > element is mapped assumes the AR System default value (or NULL if there is > no default). In a set operation and in consumption, the field remains > unchanged. > > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Joe D'Souza > Sent: Tuesday, January 22, 2013 9:03 PM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." while > consuming a AR System published web service.. <<<RESOLVED>> > > ** > > Hey Jason, > > Thanks. Tried it. > > Taking it off and setting the MinOccurs to 0 doesn't still pick up the > default from the AR Server but returns a 500 error. So I'm stuck with > having to define it as a DefaultValue in the WSDL or setting it in the > Request envelope. > > Joe > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Jason Miller > Sent: Tuesday, January 22, 2013 8:16 PM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." while > consuming a AR System published web service.. <<<RESOLVED>> > > ** > I have seen the same thing with soapUI. I just go through and remove > the question marks between the tags. > > Jason > > On Tue, Jan 22, 2013 at 4:51 PM, Joe D'Souza <[email protected]> wrote: > Yes I am using soapUI. I thought that ? indicates no value. > > If however you leave ? for drop lists, the WSDL plugin does use the field > default if it's a required field in the ARS. > > I tried the element with <element></element> and got the 500 error. Would > that error go away if I changed the minoccurs on required character fields > to 0 and define defaults to all those required character fields? > > I'm hoping it will.. > > I'll try that as a test to see.. > > Joe > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Grooms, Frederick W > Sent: Tuesday, January 22, 2013 5:49 PM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." While > consuming a AR System published web service.. <<<RESOLVED>> > > Required (In XML minOccurrs = "1") means it has to have a value. All > the MidTier does for required (I think) is validate that the element has > data. I think all type checking and actual data validation is from the AR > Server processes. > > For the ? issue, are you talking about what you see in soapUI? It is > soapUI that puts in the ? for each field not the MidTier server. If you > consume the WSDL with some other SOAP client you shouldn't see the ? in the > fields. If you pass in ? in the field then you are passing in a valid > character and the XML is satisfied. > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Joe D'Souza > Sent: Tuesday, January 22, 2013 4:09 PM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." While > consuming a AR System published web service.. <<<RESOLVED>> > > ** > > Fred! > > You were bang on your buck there! It did turn out that the WSDL plugin > barfed at the bad date and date time format. I didn't turn on any further > logging but went on to correct the date format as per the standards > documented at http://www.w3.org/TR/xmlschema-2/#dateTime. So I corrected > the regular Remedy like string of 01/22/2013 10:22:00 AM that I was sending > to confirm the WSDL standard => 2013-01-22T10:22:00-09:00 for the Alaskan > time zone, and the request went right through and created a Remedy record! > > I however do not like the way the WSDL plugin handles default values > defined to Character fields that are required. It saves "?" to the field if > you send <element>?</element> with the envelop. While it works perfect for > defaults on drop down fields if the value for the drop down fields is left > at <element>?</element>. Is that a known issue too? It should have treated > the question mark as null but it takes it literally and commits the "?" as > a value to that character field. Is this a possible bug?? > > I have tried <element></element> for required field and I get the 500 > error so obviously it either requires me to put a value or at least leave > the "?" in there. But leaving the "?" in there takes it as the literal > value and does not replace it with the default in case of Character fields. > I have not tried this with integer or real or decimal data types that are > required but I'm expecting that to work correctly as the drop downs (which > are integers) work correctly. > > Joe > > -----Original Message----- > From: Joe D'Souza [mailto:[email protected]] > Sent: Tuesday, January 22, 2013 4:59 AM > To: ARS Discussion List > Subject: RE: Possible reasons for "500 - Internal server error." While > consuming a AR System published web service.. > > > Fred, > > You might have something here, and if this turns out to be the cause, then > the error reporting is not accurate. I'll try this tomorrow. > > Joe > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Grooms, Frederick W > Sent: Monday, January 21, 2013 6:57 PM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." While > consuming a AR System published web service.. > > What is your Logging set for in the MidTier Web server? > > Log Level: Fine > Log Viewer: File > Log Format: Detailed Text > Categories: Set All On > > You may be encountering an old bug I had found where an invalid date > format will cause an internal error and a restart > > 1/18/2013 12:00:00 PM Should be invalid and error as it is not in the > valid XML DateTime format http://www.w3.org/TR/xmlschema-2/#dateTime > > Fred > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Joe D'Souza > Sent: Saturday, January 19, 2013 1:40 AM > To: [email protected] > Subject: Re: Possible reasons for "500 - Internal server error." While > consuming a AR System published web service.. > > ** > Yes I agree the date time format used in SOAP is a little different than > the one I sent with my request, but the error I'm getting is not because of > that. It's a communication error. Once I am past the communication error, > then I could go further. > > A colleague tried consuming a WS to see if we can at least consume, and > that we can with no problems. For some reason there is a problem > publishing. I will need to look at this on Monday when I get back, and may > use your def as a test to see if that works since you have already tested > it to be working. > > Thanks for your help. Appreciate you going out of your way to create a POC > (proof of concept) that I could borrow to test. Something tells me it might > possibly be a firewall issue although I did check to see if there is > anything there. I'm not a security expert so I must have missed something > when I checked the settings.. > > Joe > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
