After getting useful pointers to deployment issues for the web service deployable proxy (Unable to deploy Web Service Deployable Proxy DC) here, I am now having a different issue with the deployed proxy.
1. I have non DC versions of the Web service deployable proxy and the client EJB code for which the lookup code from the EJB client code works absolutely fine.
Ref section Implement the session bean on page 40 of the PDF Providing and Consuming Web Serviceson this URL : https://www.sdn.sap.com/irj/go/km/docs/library/nw/netweaverdevelopersguide2004s/sap%20netweaver%20developer's%20Guide%202004s/UsingJava_00_PDFsList.ca
2. For the dc version of the two i.e. Deployable proxy and the Client EJB , my code
fails giving a class cast exception at the statement
CreditLimitCheck obj = (CreditLimitCheck) ctx.lookup("java:comp/env/CreditLimitCheckProxy");
the JNDI registry of the server shows following
<DEPLOYABLE PROXY APPLICATION NAME> [Context]
+ <FULLY QULIFIED CLASS NAME OF THE WS PROXY>
+ [Class Name] : <FULLY QULIFIED CLASS NAME OF THE WS PROXY><b>Impl</b>
Note the Class name is appended with Impl which is not a class available at compile time.
I can see the DC & NON DC version of deployable proxy having the same kind of JNDI registry entries , only difference being the Vendor name getting changed from sap.com to the one for my SWC setup.
The question here being, same code in NON DC setup works fine , but the same put inside DC gives me a class cast exception. Has anybody faced similar situation with deployable proxy DCs?