JNDI lookup for JAX-WS web services

[former_member190457]

Hi all,

When a JAX-Ws consumer proxy is deployed in its own EAR and is not consumed by means of an @WebServiceRef by an EE5 component, the proxy itself is not processed and not bound in the global JNDI context.

See:

A Java consumer proxy is not displayed in SAP NetWeaver Adm

SAP Note Number: 1396556

This means that in order to lookup the proxy via JNDI (InitialContext.lookup(...))from an arbitrary code location (i.e. a different EAR) you MUST create and deploy a dummy EJB whose only purpose is to have an instance variable with @WebServiceRef

This way JNDI proxy binding is performed at deploy time.

This seems a bit awkward.

Is there any plan to fix this and have the proxy processed and bound to JNDI at deploy time irrespective of whether it is used or not with @WebServiceRef?

thanks

regards

Vincenzo

[former_member190457]

appearently no way