We recently ran into this issue while doing process modelling with our NWDS version 7.3 SP07.
Error details:
We had developed few WD Java UI components with dependency to KM API's ( dependency with DC - tc/km/frwk). While assigning these UI's to our newly developed process, we were unable to do a search for UI components using the NWDS wizard.
Error Log:
BC-BMT-BPM-CMP#Exception while searching components.
[EXCEPTION]
- com.sap.sdi.SearchDiscoveryException: SEARCH_BROWSE: While searching for WD Components : Error while finding WD component {SC=KMC-CM, DC=tc/kmc/kmc.people.shared/wd_picker, COMPONENT_PACKAGE=com/sap/netweaver/kmc/people/wdpicker, REPOS=LocalDevelopment^LocalDevelopment, COMPONENT=PeoplePicker, DC_VENDOR=sap.com, SC_VENDOR=sap.com}
at com.sap.sdi.wd.search.WDSearchProvider.search(WDSearchProvider.java:173)
at com.sap.sdi.services.SearchBrowseService.search(SearchBrowseService.java:127)
at com.sap.sdi.services.SearchBrowseService.search(SearchBrowseService.java:113)
at com.sap.glx.ide.task.util.SearchUtil.search(SearchUtil.java:194)
at com.sap.glx.ide.task.util.SearchUtil.searchComponents(SearchUtil.java:129)
at com.sap.glx.ide.uui.wizard.UuiWizardPage1$8$1SearchComponentsRunnable.run(UuiWizardPage1.java:410)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.sap.sdi.SearchDiscoveryException: Error while finding WD component {SC=KMC-CM, DC=tc/kmc/kmc.people.shared/wd_picker, COMPONENT_PACKAGE=com/sap/netweaver/kmc/people/wdpicker, REPOS=LocalDevelopment^LocalDevelopment, COMPONENT=PeoplePicker, DC_VENDOR=sap.com, SC_VENDOR=sap.com}
at com.sap.sdi.wd.search.WDSearchProvider.createComponentIVResultNodes(WDSearchProvider.java:371)
at com.sap.sdi.wd.search.WDSearchProvider.search(WDSearchProvider.java:171)
... 6 more
[Error: com.sap.glx.ide.flow.util.logger.IDEAbstractDynamicParticipant$TRACEENTRIES Thread[ModalContext,6,main]]
We reached out to SAP support team with this issue and found that the issue is related to 2 Jars files in DC's - tc/km/kmc/people.shared/wd_picker and tc/km/km/wdui/dispatcher. Both the Jar's have a path which is more thatn 255 character and hence it works only in Windows Server.
Now since our landscape doesn't have a NWDI to manage this requirement, we found a workaround.
Workaround:
Delete all DC's under KMC-CM SCA except for tc/km/frwk using remove client option in Development Infrastructure perspective. Shutdown the NWDS and the delete the DC's from your workspace.
This way the UI wizard in process composer will search without any issues 