Does the WebService return `null`? #1

Closed
FreakyBytes opened this Issue Jan 30, 2017 · 0 comments

Comments

Projects
None yet
1 participant
Owner

FreakyBytes commented Jan 30, 2017

Trac Ticket #1

component: code
owner: martin
reporter: martin
created: 2014-01-31 13:27:43
milestone:
type: defect
version:
keywords: bives-ws, null

last meeting we saw a ''bives web service returned null'' message. did bivesws:wiki really return null without any error report?

comment 1

time: 2014-02-12 10:04:43
author: martinP

comment 2

time: 2014-02-12 10:04:43
author: martinP

Updated status to accepted

comment 3

time: 2014-02-12 10:12:13
author: martinP

approved. When requesting COMMAND_REPORT_HTML and COMMAND_COMPONENT_HIERARCHY_JSON the hierarchy will be calculated, but there is no html report. Instead an "Error: null" is returned.

Test Models were:

I will attache a slightly modified version of the response json.

comment 4

time: 2014-02-12 10:12:50
author: martinP

Updated attachment to bives-ws-out.json

comment 5

time: 2014-02-12 10:12:50
author: martinP

component_hierarchy_json and report_html

comment 6

time: 2014-02-12 13:31:06
author: martin

indeed a bug. not sure whether it's still there, but not ready to build web service against new bives, yet... will see to it: bives-cellml:#10

comment 7

time: 2014-02-12 13:31:06
author: martin

Updated owner to martin

comment 8

time: 2014-02-12 13:31:06
author: martin

Updated priority to critical

comment 9

time: 2014-02-12 13:31:06
author: martin

Updated status to assigned

comment 10

time: 2014-02-12 13:31:06
author: martin

Updated type to defect

comment 11

time: 2014-03-09 17:15:30
author: martin

fixed in http://sems.uni-rostock.de/trac/bives-cellml/wiki//27a795aac6efdfe4b6253a8337a516d53aaaac9f, web services updated in http://sems.uni-rostock.de/trac/bivesws/wiki//51ab959

comment 12

time: 2014-03-09 17:15:30
author: martin

Updated resolution to fixed

comment 13

time: 2014-03-09 17:15:30
author: martin

Updated status to closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment