Menu
▾
▴
#2101 SfcbLocal method parameter type conversion and validation
In the SfcbLocal client library, we noticed the following problem:
(p1) For a method invoke operation, method parameters exist as string or reference type in Sfcc. Depending on the connection type, Sfcc loads a library belonging to Sfcb. We call this library as the back end component of Sfcc. The CIMXML backend in Sfcb provides conversion of the method parameters to the correct types as defined by the class. It also provides an option to validate the type through validateMethodParamTypes. This capability is absent in the LOCAL backend interface.
(p2) Debug logging in the back end Sfcc uses the Sfcb trace logging. Trace logging requires an init call from the application code. Since the back end library is loaded outside of Sfcb, the trace logging init is not called and hence debug log is not present.
The attached patch file (for sfcb-1.3.9) provides the proposed solution:
(s1) The conversion and type validation of method parameters are added to the LOCAL backend interface in Sfcb. Providers receiving requests through the LOCAL interface will now get the correct method parameter type instead of just strings and references. Similar to CIMXML, an invalid type will not reach the providers if validateMethodParamTypes is enabled.
(s2) Application loading the SfcbLocal library is not aware of Sfcb trace logging. Hence to enable logging, the trace log init is called within the library through the create api.
A portion of the fix is related to Bug 3001792. The fix here is current with additional fixes.
This is a stability fix to a provider crash accessing value of type other than string and reference. The proposed solution has been tested to work in our environment. Please integrate a solution so that Sfcb can continue to work in our environment with future releases. Thanks.
committed to CVS HEAD and git master
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 60 days (the time period specified by
the administrator of this Tracker).