You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NullPointerException is thrown when trying to integrate kinetic laws into model while the node "kinetic law" is selected in the right tree in the GUI
#16
Open
eikept opened this issue
Jan 12, 2021
· 0 comments
When trying to integrate newly kinetic laws after the creation with squeezer or the search in SABIO-RK a NullPointerException is thrown if the node "Kinetic Law" is selected in the right tree in the GUI. The source of this issue is that this node has no parent node (here reaction) if selected directly from the path (via getLastPathComponent() or manually). Currently there is a workaround implemented which selects the second to last node of the path instead and then searches the children of this node for a node with the same name as the last node and then selecting the node which was found. If selected this way, the node actually contains the parent node but obviously this is not a very nice way to select the last node. Therefore the goal would be to identify the reason as for why the node has no parent when selected directly in this special case and then fix it.
The text was updated successfully, but these errors were encountered:
When trying to integrate newly kinetic laws after the creation with squeezer or the search in SABIO-RK a
NullPointerException
is thrown if the node "Kinetic Law" is selected in the right tree in the GUI. The source of this issue is that this node has no parent node (here reaction) if selected directly from the path (viagetLastPathComponent()
or manually). Currently there is a workaround implemented which selects the second to last node of the path instead and then searches the children of this node for a node with the same name as the last node and then selecting the node which was found. If selected this way, the node actually contains the parent node but obviously this is not a very nice way to select the last node. Therefore the goal would be to identify the reason as for why the node has no parent when selected directly in this special case and then fix it.The text was updated successfully, but these errors were encountered: