cancel
Showing results for 
Search instead for 
Did you mean: 

WebService Portal Problem

Former Member
0 Kudos

I want to access a WebService from a Portal component. Easy I thought, just clicking through the wizard and voila. But it didn't work out that way. The generated type classes do not represent the wsdl structure correctly (response/request in wsdl defined with xsd). For example a sequence of strings happens to be just a plain string in the generated types structure.

The connection worked (axis TCPView did show me the correct soap request/response), but IPRTSOAPCall.invokeMethod returned null.

The generation process for the same wsdl worked out well with a DeployableProxy and a servlet. No problem with that.

1. How do I enable the soap.log file some docs talk about and where may I find it?

2. Can I access the DeployableProxy from a Portal component/service? Is the Portal JNDI different from the J2EE JNDI?

I can still switch to axis, but hope the portal is powerful enough to let me use its WS connectivity options.

Greetings,

Martin

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

1. Go to system administration->Monitoring->Logging console, select SOAPLogger click configuration mode and activate it.

2. You can do JNDI lookups from a portal service(see for example http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/accessin... ejb applications using jndi.pdf and there should be many threads about this)

AFAIK, there is not portal JNDI. Portal services are used diffrently (and I believe independently of the J2EE structure).

cheers

Dagfinn

Btw. which version are you on ?