It can also happen that a producer administrator decided to change its requirement for registered
consumers. In this case, invoking operations on the producer will be failed with an
OperationFailedFault. GateIn will attempt to help you in this
situation. Let's walk through an example using the
self
producer. Let's assume that
registration is requiring a valid value for an
email
registration property (as we have seen so far). If you go to the configuration screen for this producer,
you should see:

Now suppose that the administrator of the producer also requires a value to be provided for a name registration property. We will actually see how to perform this operation in GateIn when we examine how to configure GateIn's producer in Section 6.7, “Configure GateIn's WSRP Producer”. Operations with this producer will now be failed. If you suspect that a registration modification is required, you should go to the configuration screen for this remote producer and refresh the information held by the consumer by pressing "Refresh & Save":

As you can see, the configuration screen now shows the currently held registration information and the expected information from the producer. Enter a value for the name property and then click "Modify registration". If all went on well and the producer accepted your new registration data, you should see something similar to:

As of WSRP 1, it is rather difficult to ascertain what caused an
OperationFailedFault
as it is the generic exception returned by
producers if something did not quite happen as expected during a method invocation. This means that
OperationFailedFault
can be caused by several different reasons, one
of them being a request to modify the registration data. Please take a look at the log files to see
if you can gather more information as to what happened. WSRP 2 introduces an exception that is
specific to a request to modify registrations, thus reducing the ambiguity that currently exists.