[ http://issues.apache.org/jira/browse/FELIX-67?page=comments#action_12423322 ] Francesco Furfari commented on FELIX-67: ----------------------------------------
I've done some testing with Cyberlink library to verify that all the exceptions were managed correctly by the UPnP stack. The Cyberlink library does not validate the soap messages received by the action handler. Thus you can send the control message with a very strange envelop. The library only checks for the presence of the expected Action element. A patch to the library has been applied in order to raise INVALID_ARGS exception when the number of expected parameters does not match. The bridge correctly converts the fault messages in UPnPException and vice versa. In case of control request to exported devices, the Bridge automatically handles 401 -invalid Action 402 -invalid Args while every exception raised from the device is mapped to a 501 - internal error. error code 403 and 404 has to be tested yet > Implement UPnP Exception > ------------------------ > > Key: FELIX-67 > URL: http://issues.apache.org/jira/browse/FELIX-67 > Project: Felix > Issue Type: Sub-task > Components: UPnP Device Service > Reporter: Francesco Furfari > Assigned To: Stefano Lenzi > > We have to remove the reference to the class > "org.apache.felix.upnp.extra.util.UPnPException" in order to adopt the new R4 > class "org.osgi.service.upnp.UPnPException". > We should mange just the INVALID_ARGS - (402) Invalid argument and test that > lower layer (Cyberlink) send a valid exception descriptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
