Re: [Nsi-wg] Issue 23 in ogf-nsi-project: "NsiExceptionType" change to "serviceException"
Updates: Status: Fixed Labels: FixedWithUpdateR5 Comment #4 on issue 23 by jmacau...@gmail.com: "NsiExceptionType" change to "serviceException" http://code.google.com/p/ogf-nsi-project/issues/detail?id=23 Renamed NsiExceptionType to ServiceExceptionType as per issue #23. Closing issue #23. ------------------------------------------------------------------------ r5 | jmacauley@gmail.com | 2011-10-14 16:30:54 -0400 (Fri, 14 Oct 2011) | 1 line Renamed NsiExceptionType to ServiceExceptionType as per issue #23. Renamed messageId to errorId in ServiceExceptionType as per Issue 24. Renamed ServiceException element to ServiceException as per issue #27. Closing issues #23 and #27. Updating issue 24 ------------------------------------------------------------------------
Updates: Status: Accepted Comment #5 on issue 23 by thost...@gmail.com: "NsiExceptionType" change to "serviceException" http://code.google.com/p/ogf-nsi-project/issues/detail?id=23 This was originally a reference to the generic protocol _Document_ using the term "NsiExceptionType", where it should have been serviceException. I'm okay, with the change in the WSDL, but that wasn't what the original issue was about. It seems, we are forgoing updates to the document, which isn't very good. Is there a person responsible for the protocol document?
Updates: Status: Done Comment #6 on issue 23 by guy.robe...@gmail.com: "NsiExceptionType" change to "serviceException" http://code.google.com/p/ogf-nsi-project/issues/detail?id=23 NSI connection service protocol document v1.1 has been updated and issue closed
participants (1)
-
ogf-nsi-project＠googlecode.com