Web Service in Workflow not writing back

Hi,
Ive created a simple Web service that gets the supervisor Id from the form creator Id.
Ive tested the service on the SOAP services page and it works as expected.
But when I try to use this webservice in a workflow it doesnt write the values back into the from-variables.
Also, when you assign the formvariables to the WS-variables in the QPAC properties, the xpath boxes are not really always at the same place, ie. not filled with data or the like.
Is there a serious bug in the webservices QPAC?
Im using LC WF designer 7.0.
Id be thankful for any kind of advice how I can get webservices to run correctly in the designer.
Cheers
Gunther

Hi Gunther
I'm not sure why you're not getting return values.
I suggest you actually try using the external web services, and see whether they work.
One of the issues may be that the wsdl of the web service you're invoking is very complex, more complex than the parser that is built into the Adobe Web Service QPAC is capable of handling. So the web service may be executing correctly, but the data is not being extracted correctly. Perhaps! If this is the case, we do have another web service QPAC you may want to try. It's takes a simpler approach than the Adobe one - rather than trying to parse the schema and present variables to you, it simply allows you to provide a xml input document, and returns a xml output document. You can embed process variables into the input doc, and can assign the output do to an XML variable, where you can use XPath expressions to extract the data. This is currently in beta, if you'd like an early copy, please let me know.
Howard
http://www.avoka.com

Similar Messages

Qaaws "Web services url is not correct" while adding host.

Hello all,
            I am getting error "The web services Url is not correct" while adding the host name for Qaaws. The error is coming on the right side of the input text field of the Name showing by yellow warning icon.Please help me to resolve it.I was tried by keeping the host name instead of ip address.But is saying the same error.
regards
vishnu

To enable rest support there are some instructions below:
Before undertaking this process, I recommend backing up the file(s)
you are going to edit.
By default REST is disabled in Axis 2. We need to enable it. We
need to go to the following folder. Assuming D: is the installation drive:
1.     D:\Program
Files\Business Objects\Tomcat55\webapps\dswsbobje\WEB-INF\conf (for 32 Bit OS)
or D:\Program Files (x86)\Business Objects\Tomcat55\webapps\dswsbobje\WEB-INF\conf (for 64 Bit OS)
2.     There is a file with the name axis2.xml (This file is an XML File and contains many parameters as well as many other things).
3.     Make a backup copy of the filename you are about to edit.
4.     Open the axis2.xml file in Notepad or 'XML Editor' to edit
5.     Search for the word REST (Ctrl & F is probably easiest)
6.     You will see a line like this
<parameter name="disableREST" locked="true">true</parameter>
We need to replace' true' with 'false' to enable REST, and after the changing that line will look like following:
<parameter name="disableREST" locked="true">false</parameter>
7.     Save the file and restart the web server.

Error "web service destination is not configured" in CTS+

Hi experts,
during deployment with CTS+ I get the error "web service destination is not configured" (see below). In fact there is a web service to be deployed and a WebDynpro-DC using this web service as adaptive web service model. The model uses the destination DACC_PI_WS_METADATA_DEST and DACC_PI_WS_EXECUTION_DEST. I configured both destinations in the server with type "WSDL".
Any idea what goes wrong?
Regards,
Christoph
1 ETP199 ######################################
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "372.04.29" "700"
1 ETP198
2 EPU601X"CTS Deploy Service - Version 0.92" "06.03.2007" " " " "
2 EPU602 "==================================================""======================"" "" "
===="" "" "
2 EPU601 "Deploy web service destination =" " " " " " "
2 EPU601 "Directory =" "/usr/sap/trans/data" " " " "
2 EPU601 "SDM Deploy URL =" " " " " " "
2 EPU601 "SLD Deploy URL =" " " " " " "
2 EPU601 "XI Deploy URL =" " " " " " "
4 EPU607 Non-ABAP system "JAQ" (communication system "KSM")
4 EPU601X"Deploy for" "SDM" " " " "
4 EPU601 "Deploy File =" "karmann.comSC_DACCDIP_DACCD_C~20081001122205.sca" " " " "
4WEPU601 "Web service destination is not configured" " " ", deployment skipped" " "
4WEPU601 "Return Code =" "4" " " " "
4WEPU601 "Highest Return Code =" "4" " " " "

Hello,
I am getting an identical error per below. I have checked Web deploy service, CTSDEPLOY setup in SM59 etc and looks OK, yet the issue still occurs:
   Deployment
   Transport request   : BWDK903389
   System              : BWQ
   tp path             : tp
   Version and release: 372.04.36 700
   CTS Deploy Service - Version 0.92 06.03.2007
   ========================================================================
   Deploy web service destination =
   Directory =
   SDM Deploy URL =
   SLD Deploy URL =
   XI Deploy URL =
   Double-stack system BWQ
   Deploy for SDM
   Deploy File = CTSTEST_20081008_123719.epa
   Web service destination is not configured   , deployment skipped
   Return Code = 4
   Highest Return Code = 4
   Deployment
   End date and time : 20081015162015
   Ended with return code: ===> 4 <===
Anyone have any ideas on this one?
Thanks & Regards,
Michael

Web Service security is not set up on this component

Hi Friends,
In RWB, when I click on component monitoring->Integration Engine, I got "Web Service security is not set up on this component"
I want to send message using soap adapter by encrypting and signing it. for this purpose I need to configure the Web Service Security.
Can someone please provide some documentation or link on how to set up this Web Service Security?
thankx

Hi,
there is a chapter - Security Configuration at Message Level
in XI config guide which specifies everything you need - this is what you need
so I hope no further explanations are necessary
Regards,
Michal Krawczyk

Can universe connect to restful web service which is not soap based

Can universe connect to restful webservice? I know it is allowed to connect to SOAP webservice. Currently is using WSDL1.1.
How about restful web service which does not have any wsdl file?

Hi,
there is a chapter - Security Configuration at Message Level
in XI config guide which specifies everything you need - this is what you need
so I hope no further explanations are necessary
Regards,
Michal Krawczyk

Web Service session manager not found.

I'm trying to understand how to use the HTTP utilities, and I'm having trouble just creating a session. I get a Web Service session manager not found error. I've read where the client has to support cookies. My eventual client will be a labview VI that talks to a web server. I llooked at the Toolsptions, but don't see anything related to cookies. Not sure if that's what's causing this anyway, but I'm just digging. Also, I want to eventually send http messages across TCP/IP. Do I need to use the TCP/IP VIs (i.e. open connection, etc) or do I use the http utilities alone. If both are needed, how does the httpRequestID and the TCP/IP connection ID correlate.
Attachments:
htttGetSession.vi ‏9 KB
WebServerError.PNG ‏13 KB

Hi can you please let me know how you resolved this issue?

11G - invoking an asynchronous Web service that is not a BPEL process

Hi all,
Is there an 11G example of implementing and invoking an asynchronous Web service that is not a BPEL process ? . In 10g there is an example for Axis web service (Oracle_Home\integration\orabpel\samples\interop\axis\BPELCallingAsyncAXIS ) but I can't find anything related to 11G so far.
Thanks in advance,
sasha

Hey Chris.
I am just starting to write a jcd that calls an external web service but cannot find any sample code nor instructions on how to do it in the supplied documentation. Could you send me a code sample from your one?
Cheers
Matt

Web Services Demo (OTNMobileWrapper) not works

I tested in my own database environment and also at my account on htmldb.oracle.com.
- Wheather service works fine
- Amazon works fine
- OTNMobileWrapper did not
I believe the URL and the Action are wrong!
(the Urls in Wheather and Amazon I can call in the browser directly, the Url from OTNMobileWrapper was not found).

yeah, i see what you mean regarding that "OTN Message Service" option in our web services demo. further inspection by a teammate reveals that more than a few of these OTN Live Web Services appear to not be working. i'm currently checking around to see what the deal is with that, but from an html db perspective, though, you should already know what you need to know: it is possible to call web services from within your html db applications. this particular one in our example appears to currently be unavailable (if you do feel it's our "URL and action", btw, please do send that info to [email protected]), but calls to the more stable ones like amazon, for instance, always work.
hope this helps,
raj

Qaaws web services URL is not correct

Hi,
When i am trying to login in Qaaws its showing warning "Web service URL is not correct" for BO server with a yellow icon and in Authorization dropdown its showing nothing.It was working fine in the past, the same problem with Live office also.
Please help.

No,is is saying on browser the following error:
HTTP Status 404 - /dswsbobje
type Status report
message /dswsbobje
description The requested resource (/dswsbobje) is not available.
Apache Tomcat/6.0.24
Regards
vishnu

Web service handler could not called in client web service

Hi All,
I have two web service ServiceA & ServiceB and both implemented in weblogic.
The ServiceA is SSL enable and protocol is https which is not published by me.
The ServieB is my web service(wls8.1) and act as client for ServiceA.
My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
My service file:
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import weblogic.webservice.client.SSLAdapterFactory;
import weblogic.webservice.client.WLSSLAdapter;
public class HelloService {
String wsdl = "https://188.122.123.23/RemoetService?WSDL";
static {
SSLAdapterFactory factory = SSLAdapterFactory.getDefaultFactory();
WLSSLAdapter adapter = (WLSSLAdapter) factory.getSSLAdapter();
adapter.setTrustedCertificatesFile("D:\\lib\\certs
cacerts");
factory.setDefaultAdapter(adapter);
System.setProperty("weblogic.xml.encryption.verbose","true");
System.setProperty("weblogic.xml.signature.verbose","true");
System.setProperty("weblogic.webservice.verbose","true");
public String sayHello(String user) {
RemoteService_Impl service = new RemoteService_Impl(wsdl);
RemotePortType port = service.getRemoteServicePort1();
String namespace = service.getServiceName()
.getNamespaceURI();
QName portName = new QName(namespace,
"RemoteServicePortType");
HandlerRegistry reg = service.getHandlerRegistry();
List handlerList = new ArrayList();
Map map = new HashMap();
map.put("Username", "user1");
map.put("Password", "pwd1");
HandlerInfo info = new HandlerInfo();
info.setHandlerClass(WSClientHandler .class);
info.setHandlerConfig(map);
handlerList.add(info);
reg.setHandlerChain(portName,(List)handlerList);
RemoteServiceResponse = port.callMe(name);
My Handler file:
package com.test;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.Handler;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.Name;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPHeaderElement;
public class WSClientHandler implements Handler {
private HandlerInfo handlerInfo;
public WSClientAuthenticateHandler(){}
public void init(HandlerInfo hi) {
System.out.println("Handler init");
handlerInfo = hi;
public void destroy() {
System.out.println("Handler destroy method called");
handlerInfo = null;
public QName[] getHeaders() {
System.out.println("Handler Header method called");
try {
Map map = handlerInfo.getHandlerConfig();
QName[] headers = handlerInfo.getHeaders();
System.out.println(" Config :"+map);
for(int i=0;i<headers.length;i++) {
System.out.println(headers.getLocalPart()+" "+
headers.toString()+" "+headers.getNamespaceURI());
}catch(Exception e) {
e.printStackTrace();
return handlerInfo.getHeaders();
public boolean handleRequest(MessageContext mc) {
SOAPMessageContext smc = (SOAPMessageContext) mc;
System.out.println("Calling handler class.....................");
try {
SOAPEnvelope se = smc.getMessage().getSOAPPart().getEnvelope();
System.out.println("Calling handler class.....................");
SOAPHeader soapHeader = se.getHeader();
Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
System.out.println("Calling handler class.....................");
System.out.println("** Request: \n "se.toString()"\n");
}catch(SOAPException e) {
e.printStackTrace();
return true;
/** * Specifies that the SOAP response message be logged to a
* log file before the
* * message is sent back to the client application
* that invoked the Web service.
public boolean handleResponse(MessageContext mc) {
System.out.println("Handler Response method called");
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
System.out.println("** Response: \n"messageContext.getMessage().toString()"\n");
return true;
/** * Specifies that a message be logged to the log file if a SOAP fault is
* * thrown by the Handler instance.
public boolean handleFault(MessageContext mc) {
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
System.out.println("** Fault: \n"messageContext.getMessage().toString()"\n");
return true;
Please need help here.
Thanks in Advance,
pps

I have tested static client calling using handler simple above service and found the issues.
QName portName = new QName(namespace,
"*RemoteServicePortType*");
The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="SayHelloRequest">
<part name="firstName" type="xsd:string"/>
</message>
<message name="SayHelloResponse">
<part name="greeting" type="xsd:string"/>
</message>
*<portType name="RemoteServicePortType">*
<operation name="sayHello">
<input message="tns:SayHelloRequest"/>
<output message="tns:SayHelloResponse"/>
</operation>
</portType>
<binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation soapAction="sayHello"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="Hello_Service">
<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">
<soap:address
location="http://host1:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">
<soap:address
location="http://host2:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">
<soap:address
location="http://host3:8080/soap/servlet/rpcrouter"/>
</port>
<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">
<soap:address
location="http://host4:8080/soap/servlet/rpcrouter"/>
</port>
</service>
</definitions>
From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
Please guide me here how i specify correct portname which can call Handler class also.
Thanks in advance,
pps

Web service handler could not registered/called in client web service

Hi Expert,
I have two web service ServiceA & ServiceB and both implemented in weblogic.
The ServiceA is SSL enable and protocol is https which is not published by me.
The ServieB is my web service(wls8.1) and act as client for ServiceA.
My problem is when i hit my service, its not able set the handler when it call ServiceA but it is invoking the service and giving application exception like authentication error.
My service file:
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import weblogic.webservice.client.SSLAdapterFactory;
import weblogic.webservice.client.WLSSLAdapter;
public class HelloService {
String wsdl = "https://188.122.123.23/RemoetService?WSDL";
static     {
          SSLAdapterFactory factory =                SSLAdapterFactory.getDefaultFactory();
          WLSSLAdapter adapter = (WLSSLAdapter)     factory.getSSLAdapter();
          adapter.setTrustedCertificatesFile("D:\\lib\\certs\\cacerts");
          factory.setDefaultAdapter(adapter);
          System.setProperty("weblogic.xml.encryption.verbose","true");
          System.setProperty("weblogic.xml.signature.verbose","true");
          System.setProperty("weblogic.webservice.verbose","true");
     public String sayHello(String user) {
          RemoteService_Impl service = new RemoteService_Impl(wsdl);
          RemotePortType port = service.getRemoteServicePort1();
          String namespace = service.getServiceName()
                    .getNamespaceURI();
          QName portName = new QName(namespace,
                    "RemoteServicePortType");
          HandlerRegistry reg = service.getHandlerRegistry();
          List handlerList = new ArrayList();
          Map map = new HashMap();
          map.put("Username", "user1");
          map.put("Password", "pwd1");
          HandlerInfo info = new HandlerInfo();
          info.setHandlerClass(WSClientHandler .class);
          info.setHandlerConfig(map);
          handlerList.add(info);
          reg.setHandlerChain(portName,(List)handlerList);
          RemoteServiceResponse = port.callMe(name);
My Handler Class:
package com.test;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.Handler;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.Name;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPException;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPHeaderElement;
public class WSClientHandler implements Handler {
     private HandlerInfo handlerInfo;
     public WSClientAuthenticateHandler(){}
     public void init(HandlerInfo hi) {
          System.out.println("Handler init");
          handlerInfo = hi;
     public void destroy() {
          System.out.println("Handler destroy method called");
          handlerInfo = null;
     public QName[] getHeaders() {
          System.out.println("Handler Header method called");
          try     {
               Map map = handlerInfo.getHandlerConfig();
               QName[] headers = handlerInfo.getHeaders();
               System.out.println(" Config :"+map);
               for(int i=0;i<headers.length;i++)     {
                    System.out.println(headers.getLocalPart()+" "+
                    headers[i].toString()+" "+headers[i].getNamespaceURI());
          }catch(Exception e)     {
               e.printStackTrace();
          return handlerInfo.getHeaders();
     public boolean handleRequest(MessageContext mc) {
          SOAPMessageContext smc = (SOAPMessageContext) mc;
          System.out.println("Calling handler class.....................");
          try     {
          SOAPEnvelope se =      smc.getMessage().getSOAPPart().getEnvelope();
          System.out.println("Calling handler class.....................");
     SOAPHeader soapHeader = se.getHeader();
     Name headerName = se.createName("Security","wsse","http://schemas.xmlsoap.org/ws/2002/07/secext");
     SOAPHeaderElement headerElement = soapHeader.addHeaderElement(headerName);
     SOAPElement element = headerElement.addChildElement(se.createName("UsernameToken", "wsse", "http://schemas.xmlsoap.org/ws/2002/07/secext"));
     element.addChildElement(se.createName("Username", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testuser");
     element.addChildElement(se.createName("Password", "wsse","http://schemas.xmlsoap.org/ws/2002/07/secext")).addTextNode("testpwd");
     System.out.println("Calling handler class.....................");
               System.out.println("** Request: \n "+se.toString()+"\n");
          }catch(SOAPException e)     {
               e.printStackTrace();
          return true;
     /** * Specifies that the SOAP response message be logged to a
     * log file before the
     * * message is sent back to the client application
     * that invoked the Web service.
     public boolean handleResponse(MessageContext mc) {
          System.out.println("Handler Response method called");
          SOAPMessageContext messageContext = (SOAPMessageContext) mc;
          System.out.println("** Response: \n"+messageContext.getMessage().toString()+"\n");
          return true;
     /** * Specifies that a message be logged to the log file if a SOAP fault is
     * * thrown by the Handler instance.
     public boolean handleFault(MessageContext mc) {
          SOAPMessageContext messageContext = (SOAPMessageContext) mc;
          System.out.println("** Fault: \n"+messageContext.getMessage().toString()+"\n");
          return true;
Please need help here.
Thanks in Advance,
pps

I have tested static client calling using handler simple above service and found the issues.
QName portName = new QName(namespace,
*"RemoteServicePortType");*
The above line code has created the issues,becuase in wsdl file ( given similar wsdl file).
<?xml version="1.0"; encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://www.ecerami.com/wsdl/HelloService.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="SayHelloRequest">
<part name="firstName" type="xsd:string"/>
</message>
<message name="SayHelloResponse">
<part name="greeting" type="xsd:string"/>
</message>
<portType name="*RemoteServicePortType*">
<operation name="sayHello">
<input message="tns:SayHelloRequest"/>
<output message="tns:SayHelloResponse"/>
</operation>
</portType>
<binding name="Hello_Binding" type="tns:*RemoteServicePortType*">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="sayHello">
<soap:operation soapAction="sayHello"/>
<input>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</input>
<output>
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="urn:examples:helloservice"
use="encoded"/>
</output>
</operation>
</binding>
<service name="Hello_Service">
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType1*">+
+<soap:address+
location="http://host1:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType2*">+
+<soap:address+
location="http://host2:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType3*">+
+<soap:address+
location="http://host3:8080/soap/servlet/rpcrouter"/>
+</port>+
+<port binding="tns:Hello_Binding" name="*RemoteServicePortType4*">+
+<soap:address+
location="http://host4:8080/soap/servlet/rpcrouter"/>
+</port>+
</service>
</definitions>
From the above WSDL, I have four port name (port binding="tns:Hello_Binding" name="*RemoteServicePortType1*) which is not matching with PortType (portType name="*RemoteServicePortType*")
even i have iterated from getPorts() method and used to invoke the service.But handler was not calling when i invoke.
Please guide me here how i specify correct portname which can call Handler class also.
Thanks in advance,
pps

Web Service Testing Does Not Work In IE

I am using WLS 7.0SP4 with a webservice generated from an EJB. I have been
testing it using the web service home page, and I have noticed this strange
behavior: when I press the "Invoke" button in Internet Explorer 6, I am sent
back to the web services home page; when I do the same in Mozilla Firebird,
I get the page indicating what transpired as the web service was invoked.
Simple print statements in the EJB indicate that with Internet Explorer the
EJB is definitely not being called when I press the Invoke button.
Furthermore, the same print statements are executed when using Mozilla
Firebird and pressing the Invoke button.
Any ideas?
Jimmy
James "Jimmy" Wilson
[email protected]

Yes this is an issue with IE. I think, there is a max
size for HTTP GET in IE. If the get request is larger
than the max size, it simply cuts off the extera data
(without any error message). When this happens,
server things that you are requesting home page, instead
of invoking a method.
You can either use a different browser, or try to reduce
the size of data in the method invoke form.
Regards,
-manoj
http://manojc.com
"James Wilson" <[email protected]> wrote in message
news:[email protected]..
I am using WLS 7.0SP4 with a webservice generated from an EJB. I havebeen
testing it using the web service home page, and I have noticed thisstrange
behavior: when I press the "Invoke" button in Internet Explorer 6, I amsent
back to the web services home page; when I do the same in MozillaFirebird,
I get the page indicating what transpired as the web service was invoked.
Simple print statements in the EJB indicate that with Internet Explorerthe
EJB is definitely not being called when I press the Invoke button.
Furthermore, the same print statements are executed when using Mozilla
Firebird and pressing the Invoke button.
Any ideas?
Jimmy
James "Jimmy" Wilson
[email protected]

Web services and JPA - not a good mix?

Hi!
Sorry if this question isn't web services specific, but this forum is the closest I've found here at SDN.
I'm having a bad time trying to figure out how to use JPA and web services in the same application.
Problems is, some of my entities contains binary data, and instances of those entities are members of other entities. If I'm correct, that is an enormous waste of memory on the server side, and worse, I need to transmit some of those entities via web services so the resulting SOAP message will be really huge. See the example below:
@Entity
public class A {
@Id
private Integer id;
private byte[] data;
@Entity
public class B {
@Id
private Integer id;
@ManyToOne
private A a1;
@ManyToOne
private A a2;
public static void main(String[] args) {
A a = new A("huge_data.avi");
B b = new B();
b.a1 = a;
b.a2 = a;
WebService.send( b ); //TWO identical "huge_data.avi" sent down the wire
}From what I've read from other forums, setting the fetch type to "LAZY" in the binary data is problematic since the entities will be dettached and serialized into SOAP messages.
Is JPA the right choice in this case? I could drop JPA and begin to use JDBC (and use "id"s instead of full object references) but some of the benefits of JPA would be wasted. See how it would become:
@Entity
public class A {
@Id
private Integer id;
private byte[] data;
@Entity
public class B {
@Id
private Integer id;
private Integer a1Id;
private Integer a2Id;
public static void main(String[] args) {
A a = new A("huge_data.avi");
B b = new B();
b.a1Id = a.id;
b.a2Id = a.id;
WebService.send( a, b ); //Fine now, but all "A" objects would need to be sent as a separated list.
}Sadly, almost every example out there on the web about JPA+web services is very simplified to be of any real usage.
Please, help me. Thanks a lot.

This will get rid or your ant problem. This stuff really works. You put a few drops of the liquid on a little piece of paper and you will see TONS of them come and eat it. They take it back to their colony and it kills them all. The next day they are all gone. It's that quick.
http://www.terro.com/
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
 An Apple User Group 
MacOSG Podcast >>
Note: I receive no compensation for product endorsements.

Tutorial - Web Services - 405 Method Not Allowed

Hi,
I am going thru the tutorial "Building and Using Web Services with JDeveloper" from Oracle JDeveloper 11g Release 2 (11.1.2.0.0) Tutorials. I am using Studio Edition Version 11.1.2.1.0. At the end of the first section on POJO Annotation-Driven Service when I press the "Send Request" button, nothing comes back or is displayed. The HTTP Analyzer shows "405 Method Not Allowed" for every HEAD request. GET and POST are fine. I don't get a response and the logs don't show any errors.
Does anyone know what is causing the 405 error?
Thanks.

Hi Frank,
I have not written any code. I am following the JDeveloper Tutorial step-by-step. The tutorial is called "Building and Using Web Services with JDeveloper", "Part 1: Building a POJO Annotation-Driven Service ". Near the end of the tutorial, you are instructed to run "Test Web Service" from the menu on MyCompany.java. When JDeveloper runs the test, a new tab opens with the HTTP Analyzer. You are then instructed to enter a '20' as arg(0) in the parameters section of the HTTP request header panel and press the 'Send Request' button. After pressing the button, JDeveloper starts the integrated server and issues the request. The right hand side of the analyzer tab shows the results of the test as HTTP Response Headers. The tutorial shows data from getDeptInfo(int id). The result on my screen shows nothing - blank.
In the logs frame at the bottom, there is a tab that shows the output logs of the HTTP Analyzer. It shows that 15 calls were made: 6 GET methods, 8 HEAD methods and 1 POST method. The status of each call is '200 OK' except for the HEAD method calls which show '405 Method Not Allowed'.
The tutorial is at [http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_52/jdtut_11r2_52_1.html] I wonder if maybe there is a parameter in the integrated Weblogic server that prevents the method call because of policy or security settings.
If you have any ideas, please let me know.
Thanks, Rick

Attn Grant Ronald : Web Services How To : Not valid anymore

Hi Grant
The how to integrate web services with Forms uses Jdeveloper 10g to create a stub for the web services which can be called in from Forms 10g. The step by step instructions are based on version 9i. Jdeveloper 10g does not have the same deployment options as 9i version. The instructions have to change.
Rgds
Arvind Balaraman

Web Services are not supported on apex.oracle.com at this time. This is a fairly recent change - just after our upgrade a few weeks back.
I just added a note to our ShowCase app that demonstrated this a few days ago because our Web Services Showcase pages no longer work (but you can download the packaged version of the application and install it locally to see it work).
-- Sharon

Web Service in Workflow not writing back

Similar Messages

Maybe you are looking for