Document based webservice failed

Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

Hello,
This error is unfamiliar and there is not enough information in your
post to ascertain the cause. Have you tried the examples of document
based webservices that Manoj has [1]? I think they would be helpful in
your efforts.
Regards,
Bruce
[1]
http://manojc.com/?sample13
http://manojc.com/?sample14
http://manojc.com/?sample31
http://manojc.com/?sample43
Boney Jose wrote:
>
Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

Similar Messages

How to develop Asynchronous Document Based WebServices?

Hi gurus,
The scenario is, We are developing an architecture where Asynchronous Document Based WebServices are desired.
As per my knowledge, This architecture includes some
work at JMS side.
Meaning,
Client -
> Calling [WebService] -
> Deletgate --
>JMQ (Java Message Queue)
Would appreciate ur thoughts here...
Regards,
Arvind Kugasia [[email protected]]

Hi Arvind,
this "pattern" - sending JMS message and performing some long asynchronous tasks in MDB is a standard J2EE way.
That should be supported by any j2ee server that at least covers J2EE 1.3 (where MDB-s are introduced). That includes the SAP Web AS as well and its JSM and EJB implementation as well.
The message can be sent from a servlet, web service, etc.
In fact the classic petstore application released from sun as a model for developing J2EE applications uses MDB-s for that purposes :
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/sample-app/sample-app1.3.1.html
Once you buy the parrot from the petstore, you will see the response page while the MDB will perform asynchonously the sending of the mail, charging of the account, etc.
It doesn't matter if the front end is a web service or a HTTP UI.
In addition you can google for any J2EE tutorial and MDB explanation.
However please note that I am speaking how your application will gather the parameters from the web service call, put them in a JMS message and send the message via several lines of java code.
Perhaps some other frameworks (Apache-Axis, etc.) are doing this automatically for you or are generating the code that sends the message via some wizard.
That up to my knowledge is not supported for SAP WebAS, but that is only a 10 lines of code inside the web service body, that can be easily created.
HTH
Peter

Document based Web Services

Can any one help me finding the example of document based web serives developed
using plain java classes.
I tried the way mentioned in documentation, if I use rpc style and pass xml as
string it is working fine. but if I use document base, it is not working.

The example dom.zip doesn't work properly.
I got following error when I was running the example on JDeveloper 9.0.3. Any
suggestion ?
C:\JDEV903\jdk\bin\javaw.exe -ojvm -classpath C:\MyStudy\java\WS3\classes;C:\JDEV903\jdev\lib\jdev-rt.jar;C:\MyStudy\java\1\dom\client.jar;D:\bea\weblogic700\server\lib\webserviceclient+ssl.jar;D:\bea\weblogic700\server\lib\weblogic.jar;C:\JDEV903\jdev\lib\jdev-rt.jar;C:\JDEV903\soap\lib\soap.jar;C:\JDEV903\lib\xmlparserv2.jar;C:\JDEV903\jlib\javax-ssl-1_2.jar;C:\JDEV903\jlib\jssl-1_2.jar;C:\JDEV903\j2ee\home\lib\activation.jar;C:\JDEV903\j2ee\home\lib\mail.jar;C:\JDEV903\j2ee\home\lib\http_client.jar;C:\JDEV903\lib\xmlparserv2.jar;C:\JDEV903\lib\xmlcomp.jar
-Dhttp.proxyHost=proxy.ouhk.edu.hk -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=localhost|ouhk-15msmdomah|sun17.ouhk.edu.hk|sun18.ouhk.edu.hk|www.ouhk.edu.hk|www4.ouhk.edu.hk
wl.client.wsServletClient
java.rmi.RemoteException: web service invoke failed; nested exception is:
 javax.xml.soap.SOAPException: failed to serialize xml:weblogic.xml.schema.binding.SerializationException:
type mapping lookup failure on class=class weblogic.apache.xerces.dom.DocumentImpl
TypeMapping=TYPEMAPPING SIZE=0
javax.xml.soap.SOAPException: failed to serialize xml:weblogic.xml.schema.binding.SerializationException:
type mapping lookup failure on class=class weblogic.apache.xerces.dom.DocumentImpl
TypeMapping=TYPEMAPPING SIZE=0
 void weblogic.webservice.core.DefaultPart.toXML(javax.xml.soap.SOAPElement, java.lang.Object,
weblogic.xml.schema.binding.SerializationContext, boolean, javax.xml.rpc.encoding.TypeMapping)
 DefaultPart.java:260
 void weblogic.webservice.core.DefaultMessage.toXML(javax.xml.soap.SOAPMessage,
java.lang.Object[])
 DefaultMessage.java:455
 java.lang.Object weblogic.webservice.core.DefaultOperation.invoke(java.util.Map,
java.lang.Object[], java.io.PrintStream)
 DefaultOperation.java:403
 java.lang.Object weblogic.webservice.core.DefaultOperation.invoke(java.util.Map,
java.lang.Object[])
 DefaultOperation.java:359
 java.lang.Object weblogic.webservice.core.rpc.StubImpl._invoke(java.lang.String,
java.util.Map)
 StubImpl.java:225
 java.lang.Object examples.dom.EchoDomServicePort_Stub.echoDom(java.lang.Object)
 EchoDomServicePort_Stub.java:33
 void wl.client.wsServletClient.main(java.lang.String[])
 wsServletClient.java:76
Process exited with exit code 0.
Rajesh Mirchandani <[email protected]> wrote:
See if this helps
http://dev2dev.bea.com/direct/webservice/index.html
kaushik wrote:
Can any one help me finding the example of document based web serivesdeveloped
using plain java classes.
I tried the way mentioned in documentation, if I use rpc style andpass xml as
string it is working fine. but if I use document base, it is not working.--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

JPS-06514: Opening of file based keystore failed.

I have a fresh install of JDeveloper 11.1.2.3.0 (Build JDEVADF_11.1.2.3.0_GENERIC_120914.0223.6276.1). When I try to start the integrated WebLogic Server from the Application Servers explorer tab, it fails and crashes with "JPS-06514: Opening of file based keystore failed." The entire output console content is pasted below for your reference. I am under time pressure, so the sooner somebody can help, the better. Thanks in advance!
*** Using HTTP port 7101 ***
*** Using SSL port 7102 ***
C:\Users\userP\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe101\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~3\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_12.1.1.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\xqrl.jar;.;c:\oracle\middleware\wlserver_10.3\server\lib;M:\dommgr\DomainManager\classes;M:\3rdparty\wls_10.3\weblogic.jar;M:\3rdparty\wls_10.3\wlfullclient.jar;M:\3rdparty\wls_10.3\wljmxclient.jar;M:\3rdparty\wls_10.3\wlclient.jar;
PATH=C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\native;C:\Oracle\MIDDLE~1\patch_oepe101\profiles\default\native;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~3\jre\bin;C:\Oracle\MIDDLE~1\JDK160~3\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\IBM\RationalSDLC\ClearCase\bin;C:\Program Files\IBM\RationalSDLC\common;M:\etc;C:\Oracle\MIDDLE~1\WLSERV~1.1\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~3\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.1\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Users\FCOCA~1.COR\AppData\Local\Temp\trustStore7654511046496503013.jks -Ddmsc_config_file=M:\etc\dommgr.properties -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -Djava.endorsed.dirs=C:\Oracle\MIDDLE~1\JDK160~3/jre/lib/endorsed;C:\Oracle\MIDDLE~1\WLSERV~1.1/endorsed -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.1 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.1\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\FCOCA~1.COR\AppData\Roaming\JDEVEL~1\SYSTEM~1.1\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1211\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe101\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath weblogic.Server
<19-Dec-2012 2:37:23 o'clock PM EST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<19-Dec-2012 2:37:23 o'clock PM EST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<19-Dec-2012 2:37:24 o'clock PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>
<19-Dec-2012 2:37:24 o'clock PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 13340309 Thu Feb 16 18:30:21 IST 2012
WebLogic Server Temporary Patch for 13019800 Mon Jan 16 16:53:54 IST 2012
WebLogic Server Temporary Patch for BUG13391585 Thu Feb 02 10:18:36 IST 2012
WebLogic Server Temporary Patch for 13516712 Mon Jan 30 15:09:33 IST 2012
WebLogic Server Temporary Patch for BUG13641115 Tue Jan 31 11:19:13 IST 2012
WebLogic Server Temporary Patch for BUG13603813 Wed Feb 15 19:34:13 IST 2012
WebLogic Server Temporary Patch for 13424251 Mon Jan 30 14:32:34 IST 2012
WebLogic Server Temporary Patch for 13361720 Mon Jan 30 15:24:05 IST 2012
WebLogic Server Temporary Patch for BUG13421471 Wed Feb 01 11:24:18 IST 2012
WebLogic Server Temporary Patch for BUG13657792 Thu Feb 23 12:57:33 IST 2012
WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925
WebLogic Server 10.3 Tue Nov 15 08:52:36 PST 2011 1441050
WebLogic Server 10.3 Tue Nov 15 08:52:36 PST 2011 1441050 >
<19-Dec-2012 2:37:25 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<19-Dec-2012 2:37:25 o'clock PM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<19-Dec-2012 2:37:25 o'clock PM EST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\userP\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
<19-Dec-2012 2:37:25 o'clock PM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\userP\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00003. Log messages will continue to be logged in C:\Users\userP\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<19-Dec-2012 2:37:25 o'clock PM EST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\userP\AppData\Roaming\JDeveloper\system11.1.2.3.39.62.76.1\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
19-Dec-2012 2:37:26 PM oracle.security.jps.internal.keystore.file.FileKeyStoreManager openKeyStore
WARNING: Opening of file based keystore failed.
<19-Dec-2012 2:37:26 o'clock PM EST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.>
<19-Dec-2012 2:37:26 o'clock PM EST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-06514: Opening of file based keystore failed.
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
 at weblogic.security.SecurityService.start(SecurityService.java:148)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-06514: Opening of file based keystore failed.
 at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
 at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based keystore failed.
 at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
 at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3097)
 at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
 at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06514: Opening of file based keystore failed.
 at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:374)
 at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:104)
 at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:76)
 at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:66)
 at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)
 Truncated. see log file for complete stacktrace
>
<19-Dec-2012 2:37:26 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<19-Dec-2012 2:37:26 o'clock PM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<19-Dec-2012 2:37:26 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
<19-Dec-2012 2:37:26 o'clock PM EST> <Warning> <Security> <BEA-090922> <Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by attribute SSLMBean.JSSEEnabled, either explicitly or by default.>
Process exited.

I believe you can chmod back to your app user and correct the issue.
-ryan

SOURCING10: Passing parameters to a Query Based webservice using JAVA

Hi Experts,
I have been working on consuming a Query based webservice published in Souricng10 in a simple JAVA class. The query has a filter parameter which is not mandatory. I am able to consume the webservice using the GET method and display the content of the webservice. But when i try to POST a value to the filter parameter of the query i am getting the following error:
java.io.IOException : Server returned HTTP response code: 415 for URL: http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Following is the code which i have used:
   URL url = new URL("http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/");
   HttpURLConnection connection = (HttpURLConnection)url.openConnection();
   connection.setRequestProperty("Authorization", "Basic " + authStringEnc);
   connection.setRequestProperty("Content-Type","application/x-www-form-urlencoded; charset=UTF-8");
   connection.setRequestProperty("Content-Length", "" +Integer.toString(urlParameters.getBytes().length));
   connection.setRequestProperty("Content-Language", "en-US");
   connection.setUseCaches (false);
   connection.setDoInput(true);
   connection.setDoOutput(true);
   connection.setAllowUserInteraction(true);
   connection.setInstanceFollowRedirects(false);
   connection.setRequestMethod("POST");
   connection.connect();
   //Send request
   OutputStream out = connection.getOutputStream();
   OutputStreamWriter wr= new OutputStreamWriter(out, "UTF-8");
   wr.write("EXTERNAL_ID");
   wr.write("=");
   wr.write(URLEncoder.encode("temp","UTF-8"));
   wr.close();
   out.close();
   is = connection.getInputStream();
   isr =new InputStreamReader(is);
   BufferedReader bufferReader = new BufferedReader(isr);
   String str; StringBuffer stringBuffer = new StringBuffer();
   while ((str = bufferReader.readLine()) != null) {
   stringBuffer.append(str);
   stringBuffer.append("\n");
   System.out.println(stringBuffer.toString());
   connection.disconnect();
   is.close();
Please Advise how to proceed on this isssue?
Thanks in advance.
Srikanth Emani

Hi Gael,
your URL is made up of :
[ProcedureName]?[parameter1]=[value1]&[parameter2]=[value2]
creating URLs like this can have problems especially with spaces and punctuation.
the answer is a FORM
the following will create a hidden form :
FORM ACTION="[ProcedureName]" METHOD="POST" name="F1"
INPUT type="HIDDEN" name="[parameter1]" value="[value1]"
INPUT type="HIDDEN" name="[parameter2]" value="[value2]"
/FORM
you can set the values in the form using:
document.F1.[parameter1].value="abc123%%&&$$!";
document.F1.submit();
will submit the form and the PL/SQL procedure should receive the text as it was contained in the form.
the only characters that can now cause problems are :
" as it delimits the field.
' as it may cause problems in PL/SQL.
\ as it is a special character.
Regards Michael

Issue when Converting RPC styled Webservice to Document Styled Webservice

Hi All,
My requirement is to create a Document style WS using Jdev10.1.2 and deploy it in the OAS server 10.1.2 which follows J2EE1.3 standards.
since jdev10.1.2 does not have inherit option of developing Doc'Style WS,
I created a RPC Styled Webservice using Jdeveloper10.1.2 and converted it into Document styled webservice by changing the WEB.xml file in the WS project.
The link from which i learned the changes is given below
http://radio-weblogs.com/0132036/2003/12/07.html
PFB the changes made in my WEB.xml file.
<servlet-class>oracle.j2ee.ws.StatelessJavaRPCWebService</servlet-class> to <servlet-class>oracle.j2ee.ws.StatelessJavaDocWebService</servlet-class>.
I deployed the WS in the OAS10.1.2 server successfully.
Now the ISSUE is when im invoking the webservice. It is failing with the following error.
Error parsing the WSDL for this endpoint.
javax.servlet.ServletException: WSDL Generation exception: Error: method HelloWorld -- cannot use document style binding when output requires encoding
how to solve this error ?
If any one came across this error.
pls help.

What does the registry key you installed ?
If you want to get rid of the save dialog box, you can try to use the VBA code.
Private Sub Workbook_BeforeClose(Cancel As Boolean)
Me.Close savechanges:=True "close and save changes, don't ask".
Me.Close savechanges:=False "close and don't save changes, don't ask".
End Sub
Wind Zhang
TechNet Community Support

Dynamic client for document styled webservice

Hi ,
I created a document styled webservice when I try to run it using DII client I am getting the following problem
Exception in thread "Main Thread" javax.xml.rpc.JAXRPCException: failed to invoke operation 'testOperation' due to an error in the soap layer (SAAJ); nested exception is: Message[ failed to serialize interface javax.xml.soap.SOAPElementweblogic.xml.schema.binding.SerializationException: mapping lookup failure. class=interface javax.xml.soap.SOAPElement class context=TypedClassContext{schemaType=['http://www.examples.com/types']:testOperation}]StackTrace[
Can anybody give me a simple example of creating document styled webservice and DII client using weblogic workshop 9.2
Thanks
Sksrinu

What's the question about??

WSDL Parser [Is anyone else testing WCF-based webservices?]

I'm encountering the following message when attempting to force the use of the .NET parser when interrogating the WSDL of a new webservice:
Parsing specified wsdl...
Connecting to https://BLAH-BLAH/MobileTerminated.svc?wsdl
Validating https://BLAH-BLAH/MobileTerminated.svc?wsdl
.NET Parser could not parse https://BLAH-BLAH/MobileTerminated.svc?wsdl
Warning:Selected .NET Parser is invalid.
Must installed the .net sdk Framework.
Failed to parse https://BLAH-BLAH/MobileTerminated.svc?wsdl
Am I correct in interpreting this as "you need the .NET SDK installed in order to use the .NET Parser within OATS"?
I already have .NET framework 3.5(SP1) but not the SDK.
[UPDATE] It is probably significant that the webservice I need to test is WCF-based.
Edited by: IHodgetts on May 21, 2010 5:45 PM
Edited by: IHodgetts on Jun 21, 2010 12:07 PM

I know I'm answering my own post here, but a lot of work has gone into this and someone else may as well benefit from my findings...
It would appear that OATSv9.10 does NOT support WCF-based webservices. The problem is apparently down to OpenScript not supporting WS-Addressing (part of Windows Communication Foundation) and this isn't currently scheduled for inclusion in v9.20 (much to my disappointment).
However, I have in the meantime found a workaround. Basically IGNORE what OpenScript populates the request with!
1) Use the OpenScript parser (the .NET parser will not work) to parse the WSDL.
2) Add the method(s) you require to the script.
3) The script will at this stage have two problems but can be used as a starting point.
Problem #1 - The content-type will need to be manually changed from "text/xml;charset=UTF-8" to "application/soap+xml; charset=utf-8". Edit this by right-clicking on the request and selecting "Headers" then "Content-Type".
Problem #2 - The contents of the request will not include the WS-Addressing information. One workaround is to obtain a working packet to replace this e.g. from a test harness for your WCF-webservice. Edit this by right-clicking on the request and selecting "Post Data". Replace the WHOLE string with a valid packet from your test harness.
Hopefully this will assist anyone else trying to get this working :-)

Document-based web services - WebLogic 8.1

Hi all, 
I'm exposing a stateless session bean method as a web service. The in/out parameters are XML documents so my method signature looks as follows:
 
public Document collectMessages( Document request )
 
Accordingly I want to use document-based web services. I use servicegen to create all server-side classes required for the web service.
 
I'm testing the service from the WebLogic provided test page. For document-based services, the text-area is initially populated with the following content
 
<pre>
<['http://www.revenue.ie/webservices/ris/rcm/webservices']:RcmCollectRequest/></pre>
 
When I invoke the service I get the following error:
 
<pre>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Body>
<env:Fault>
<faultcode>Client</faultcode>
<faultstring>Unable to find a matching Operation for this remote invocation <RcmCollectRequest>
</RcmCollectRequest>. Please check your operation name. </faultstring>
</env:Fault>
</env:Body>
</env:Envelope></pre>
 
I've searched for this error and seen it in the forum only a number of times. It seems as though some manual manipulation of the web-services.xml document can solve it. Does anyone have an example? My web-services.xml document looks as follows:
 
<pre><?xml version="1.0" encoding="UTF-8"?>
<web-services>
 <web-service useSOAP12="false" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices" name="rcmmessageservices" style="document" uri="/">
 <types>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="http://www.revenue.ie/webservices/ris/rcm/webservices" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="http://www.revenue.ie/webservices/ris/rcm/webservices">
 <xsd:element type="xsd:anyType" name="RcmCollectRequest" nillable="true">
</xsd:element>
 <xsd:element type="xsd:anyType" name="RcmCollectResponse" nillable="true">
</xsd:element>
 </xsd:schema>
 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stns="java:ie.revenue.rcm.ejb.session" elementFormDefault="qualified" attributeFormDefault="qualified" targetNamespace="java:ie.revenue.rcm.ejb.session">
 <xsd:element type="stns:InvalidRequestException" name="InvalidRequestException">
</xsd:element>
 <xsd:element type="stns:SystemUnavailableException" name="SystemUnavailableException">
</xsd:element>
 <xsd:complexType name="InvalidRequestException">
</xsd:complexType>
 <xsd:complexType name="SystemUnavailableException">
</xsd:complexType>
 </xsd:schema>
 </types>
 <type-mapping>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" serializer="ie.revenue.rcm.ejb.session.SystemUnavailableExceptionCodec" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException">
</type-mapping-entry>
 <type-mapping-entry deserializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" serializer="ie.revenue.rcm.ejb.session.InvalidRequestExceptionCodec" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException">
</type-mapping-entry>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:anyType" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 <type-mapping-entry deserializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" serializer="weblogic.xml.schema.binding.internal.builtin.DocumentCodec" class-name="org.w3c.dom.Document">
</type-mapping-entry>
 </type-mapping>
 <components>
 <stateless-ejb name="ejbcomp0">
 <ejb-link path="rcm-ejb-1.0.jar#CustomerMessageController">
</ejb-link>
 </stateless-ejb>
 </components>
 <operations>
 <operation name="collectMessages" method="collectMessages(org.w3c.dom.Document)" component="ejbcomp0">
 <params>
 <param style="in" xmlns:p1="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p1:RcmCollectRequest" location="body" name="document" class-name="org.w3c.dom.Document">
</param>
 <return-param xmlns:p2="http://www.revenue.ie/webservices/ris/rcm/webservices" type="p2:RcmCollectResponse" location="body" name="result" class-name="org.w3c.dom.Document">
</return-param>
 <fault xmlns:p3="java:ie.revenue.rcm.ejb.session" type="p3:SystemUnavailableException" class-name="ie.revenue.rcm.ejb.session.SystemUnavailableException" name="SystemUnavailableException">
</fault>
 <fault xmlns:p4="java:ie.revenue.rcm.ejb.session" type="p4:InvalidRequestException" class-name="ie.revenue.rcm.ejb.session.InvalidRequestException" name="InvalidRequestException">
</fault>
 </params>
 </operation>
 </operations>
 </web-service>
</web-services>
</pre>
 
Thanks in advance, 
Eoin

Hi Eoin,
I had the exact problem. Struggled a lot and still couldn't figure out. I think its a problem in 8.1. Not sure. Might want to check with the support guys. If you are struck with 8.1 and still couldn't figure out, AXIS would be a option for you. Just an FYI. Thats what we are doing now.
Luckily for us we are migrating to 9.1 and I just completed a POC for doc oriented webservices in 9.1. It works like a charm.
Thanks and good luck
- Aspert

Payroll to FI posting error message - Document Transfer has Failed

Hello experts,
We recently received the following error message when posting Payroll results to FI. This was not done using any process models.
'Document Transfer has Failed'
Does anyone know why it's coming up and more importantly, how to correct it? I looked and found an SNote: 1240870 but that seems to apply to 3PR issues not FI posting.
Anyone else had this error before? How do I correct this? Please help as this error needs to be corrected as soon as possible since FI will be closing the month of November soon.
Thanks,
Suparna

Hi,
http://help.sap.com/saphelp_dimp50/helpdata/en/81/42b1884a3711d189490000e8323c4f/content.htm
The posting run has the status Document transfer has failed. Posting to Accounting did not take place.
Depending on the error that occurred, it may be a good idea to start posting this posting run once again. If the error still occurs and it is not possible to post the posting run, you must delete the posting run and create a new one.
Thanks
Umakanth

Material documents based on Sales order

Dear Experts,
We are developing a report where I need to extract the list of material documents with movement type 411E and 412E based on the sales order. This data is available in MSEG but after designing the report, Its performance was very poor hence we could not move the report to production.
As MSEG is a cluster table it is taking to much time. I checked other tables MKPF MSSA but nothing is working out. Is there any way out to improve the performance of the report by taking the list of material documents based on sales order and movement types 411E and 412E .
Please suggest me with suitable solution.
I will reward the points immediately.
With Regards
Uday

Hope you are not trying to join MKPF and MSEG currently:
821722 - Performance of the join on MSEG and MKPF
If you are below release 606 in your system, this note will have to be implemented in your system to bring redundant fields of MKPF into MSEG for performance improvement:
1516684 - MKPF fields added to MSEG - Performance optimization
The blog shared by Jurgen is pretty well explained. In addition have a look at these notes:
1638997 - Performance: CKMDUVMAT selection with new fields in MSEG
1558298 - MB5B: Redesign of selection for performance optimization
1550000 - MB51: Redesign of selection for performance optimization

Document Store Operation Failed due to missing authorisations.

Hi
I am using BW 3.5, One of the user is getting the following error message while accessing one of the report:
Document Store Operation Failed due to missing authorisations.
The user has previously accessed this report many times. But when I tied to access the report, there was no problem.
Could any one of you advise me how to rectify this error?
Many Thanks in advanc
Regards
Ishi

Hi Suresh
Thanks for the response; I have checked authorizations and user is authorised to access all the existing reports in BW. Checks were successful.
What might be the reason then?
Thanks

'Document store operation failed due to missing authorization'

Hi all,
I am getting the error message 'Document store operation failed due to missing authorization' when trying to save the workbook as the existing Workbook after changing the structure for it. We are using the Authorization Hierarchies.
What is the problem and how can I fix it, PLEASE ???
Thanks.
Message was edited by: Venkat Kodi

check out the related thread:
What is this error

Document "Check In" fails

Hi All,
I need your help.
My use case is to edit a document locally which fails.
In detail:
   After pressing Edit locally the file opens in the right application.
   Then I change some entries in the document, save it and want to check in the doc.
   After a while the checkin fails and I get the error message:
   "A communication error occurred. "QAlerts.xls" could not be uploaded"
I must say its not an typically document, its an Excel file with more than 50 MB.
In the error log you can read about timeout.
So checked the configuration for example the Http Provider Service, but in my mind all looks good.
Im glad for any other ideas.
Many thanks
Steve

Closed because get no answers

Create a document based on specific document template using JavaScript (ECMA Script/REST API/SP Services)

Hi,
I have requirement to create a new document based on specific document template available in document library. Able to set the specific content type but the respective document template not being applied. I am trying with ECMAScript, REST API and SPServices
but no luck for now. Please help me.
Thanks,
JP

Hello,
I have already tried your solution, however in that case I get the error - "UncaughtSys.ArgumentNullException: Sys.ArgumentNullException:
Value cannot be null.Parameter name: context"...
Also, I tried removing SP.SOD.executeFunc
from my code, but no success :(
Kindly suggest !!!
Vipul Jain

Document based webservice failed

Similar Messages

Maybe you are looking for