LS remote adapter

patrykgalwa

I have a question regarding ls-adapter-remote MetadataProvider methods. In the in-process version we have data adapter parameter, in the remote not. Do you have plans to add this parameter in next version?

public String[] getItems(String user, @NonNull String session, @NonNull String groupName, @NonNull String dataAdapter)

patrykgalwa

I would like to have single Metadata adapter and choose factory based on DataAdapter name

Giuseppe Corti

Yes, you're right: the interfaces of the in-process adapter library have a few more evolutionary steps compared to the remote adapter libraries.
We do have the goal of unifying the interfaces in our roadmap, but at the moment we don't have a precise date for this update — and it's not planned for the short term.

If possible — that is, if the sets of item names handled by your data adapters are disjoint — you could distinguish them directly based on the item name.
Alternatively, you could have the client add a prefix or suffix that identifies the data adapter, and then strip it out in your getItems code.

Let us know if you need any further clarifications about one of these approaches.

patrykgalwa

Hi @giuseppe.corti, thanks for quick reply. What about other methods like

public void customizeUpdate(String user, @NonNull String itemName, @NonNull CustomizableItemEvent event)
public boolean enableUpdateCustomization(String user, @NonNull String itemName)

Is there any replacement?

Dario Crivelli

Hello. Regarding update customizers, they are not exposed at all on the remote interfaces by design.
In fact, the customizer should be invoke for every update of an item and for every client subscription of the item which requires the customizer.
For this reason, we invoke the interface synchronously and, as a consequence, we only support the Java In-Process interface. Extending this to remote interface could be too risky.
So, there is no replacement, but you can resort to a Java In-Process Adapter.