APAR status
Closed as fixed if next.
Error description
Symptom/Description: When we execute runNamed Query method in Soap UI in 3.6.1.1 with Mail as module and Notification as BO and run a query, it is throwing ObjectTypeDoesNotExist Exception even though Notification BO is present. Steps to Reproduce (If Any): 1) Open Soap UI. 2) Create new SOAP project in SOAP UI 3) Provide the Wsdl url in Initial WSDL 4) Provide a Project Name 5) Click on OK button 6) After that it opens a popup for user and credential details 7) Provide Username ,Password and click on OK button 8) Run the following code in runNamed Query by clicking on new request: <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:ws="http://ws.tririga.com" xmlns:dto="http://dto.ws.tririga.com"> <soap:Header/> <soap:Body> <ws:runNamedQuery> <!--Optional:--> <ws:projectName></ws:projectName> <!--Optional:--> <ws:moduleName>Mail</ws:moduleName> <!--Optional:--> <ws:objectTypeName>Notification</ws:objectTypeName> <!--Optional:--> <ws:queryName>Notifications - Report - Over 180 days old</ws:queryName> <ws:start>1</ws:start> <ws:maximumResultCount>99999</ws:maximumResultCount> </ws:runNamedQuery> </soap:Body> </soap:Envelope> 9) You will get a response stating ObjectTypeDoesNotExistException <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Body> <soap:Fault> <soap:Code> <soap:Value>soap:Receiver</soap:Value> </soap:Code> <soap:Reason> <soap:Text xml:lang="en">Unable to find objectType named Notification for moduleName: Mail</soap:Text> </soap:Reason> <soap:Detail> <ns1:ObjectTypeDoesNotExistException xmlns:ns1="http://ws.tririga.com"/> </soap:Detail> </soap:Fault> </soap:Body> </soap:Envelope> Expected fix in version: Reported in 3Q2020. We are still working on the target date of the release. Expected Fix Description: Fix will be done so that we wonâ t get ObjectTypeDoesNotExist Exception when we call runNamed Query method. Key Words: Platform, Soap UI, runNamed Query
Local fix
Problem summary
When executing runNameQuery against some BO's in the Mail module, a trailing space deep in the meta-data was causing an error. This issue has been resolved by trimming the whitespace off the meta-data in the database. This issue has been resolved in our next major release version, which is tentatively planned for 2H 2020.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IJ26454
Reported component name
TRI APP PLTFM R
Reported component ID
5725F26RE
Reported release
353
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-07-23
Closed date
2020-09-18
Last modified date
2020-09-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"353"}]
Document Information
Modified date:
19 September 2020