Error publishing plsql webservice - JDEV11

Hi guys,
I'm with a problem when publishing plsql webservices from JDeveloper 11.
The scenario is something like this:
1) I have a connection with a database 9i, and the objects (packages, object types, etc) are all in there.
2) In this case, i can publish the package spec using the option "Publish as JAX-RPC Web Service" normally.
3) A database 11g was created, and i compiled the objects in this environment.
4) Then i've created a new connection with a database 11g.
5) In this case, when i'll publish the webservice, the error occurs: "The following types used by the program unit do not have an XML Schema mapping and/or serializer specified: REC_DMP_REMESSA"
I have no idea in how to solve this case. Someone can help?
Thank in advance.
Best Regards,
Gustavo

Gustavo,
Wrong forum. This is SQL PL/SQL forum. May be you want to move this to Java or FM forums...
Fusion Applications
Fusion Middleware
Java
vr,
Sudhakar

Similar Messages

  • Error publishing plsql webservice (xml schema mapping and/or serializer)

    Hi guys,
    I'm with a problem when publishing plsql webservices from JDeveloper 11.
    The scenario is something like this:
    1) I have a connection with a database 9i, and the objects (packages, object types, etc) are all in there.
    2) In this case, i can publish the package spec using the option "Publish as JAX-RPC Web Service" normally.
    3) A database 11g was created, and i compiled the objects in this environment.
    4) Then i've created a new connection with a database 11g.
    5) In this case, when i'll publish the webservice, the error occurs: "The following types used by the program unit do not have an XML Schema mapping and/or serializer specified: REC_DMP_REMESSA"
    I have no idea in how to solve this case. Someone can help?
    Thank in advance.
    Best Regards,
    Gustavo

    Duplicate of https://forums.oracle.com/thread/2610823
    Timo

  • Error publishing plsql webservice

    Hi guys,
    I'm with a problem when publishing plsql webservices from JDeveloper 11.
    The scenario is something like this:
    1) I have a connection with a database 9i, and the objects (packages, object types, etc) are all in there.
    2) In this case, i can publish the package spec using the option "Publish as JAX-RPC Web Service" normally.
    3) A database 11g was created, and i compiled the objects in this environment.
    4) Then i've created a new connection with a database 11g.
    5) In this case, when i'll publish the webservice, the error occurs: "The following types used by the program unit do not have an XML Schema mapping and/or serializer specified: REC_DMP_REMESSA"
    I have no idea in how to solve this case. Someone can help?
    Thank in advance.
    Best Regards,
    Gustavo

    Gustavo, you better ask this in a pl/sql forum.
    Timo

  • Publish PLSQL as Web Service Fails

    Hi!
    I'm trying to publish PLSQL as a Web Service using the latest JDeveloper (JDeveloper 11g Release 2 (11.1.2.0.0)) and it fails on generating it.
    Is this a bug? Does anyone can do this? Or I'm doing something wrong?
    Database $version is:
    <?xml version="1.0" ?>
    <!DOCTYPE main [
    <!ELEMENT main (DATA_RECORD*)>
    <!ELEMENT DATA_RECORD (BANNER?)+>
    <!ELEMENT BANNER (#PCDATA)>
    ]>
    <main>
    <DATA_RECORD>
    <BANNER>Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi</BANNER>
    </DATA_RECORD>
    <DATA_RECORD>
    <BANNER>PL/SQL Release 10.2.0.4.0 - Production</BANNER>
    </DATA_RECORD>
    <DATA_RECORD>
    <BANNER>CORE&#9;10.2.0.4.0&#9;Production</BANNER>
    </DATA_RECORD>
    <DATA_RECORD>
    <BANNER>TNS for Solaris: Version 10.2.0.4.0 - Production</BANNER>
    </DATA_RECORD>
    <DATA_RECORD>
    <BANNER>NLSRTL Version 10.2.0.4.0 - Production</BANNER>
    </DATA_RECORD>
    </main>
    this is the error
    oracle.jdeveloper.webservices.tools.WsdlValidationException: oracle.j2ee.ws.common.tools.api.ValidationException: Error in database webservices assembly
    Error in database webservices assembly
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.newWsdlValidationException(WsaAdaptor.java:1116)
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.processDbEndpoint(WsaAdaptor.java:599)
         at oracle.jdeveloper.webservices.tools.WebServiceTools.processDbEndpoint(WebServiceTools.java:689)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.jdeveloper.webservices.tools.WebServiceTools$1.invoke(WebServiceTools.java:132)
         at $Proxy47.processDbEndpoint(Unknown Source)
         at oracle.jdeveloper.webservices.model.plsql.generator.PlsqlConfigureGenerator.createPortTypes(PlsqlConfigureGenerator.java:293)
         at oracle.jdeveloper.webservices.model.generator.ConfigureServiceGenerator.action(ConfigureServiceGenerator.java:66)
         at oracle.jdeveloper.webservices.model.plsql.generator.PlsqlConfigureGenerator.action(PlsqlConfigureGenerator.java:105)
         at oracle.jdeveloper.webservices.model.generator.GeneratorAction.run(GeneratorAction.java:142)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.j2ee.ws.common.tools.api.ValidationException: Error in database webservices assembly
         at oracle.j2ee.ws.tools.wsa.db.WSADBPlugin.processDBEndpoint(WSADBPlugin.java:207)
         at oracle.j2ee.ws.tools.wsa.Util.processDBEndpoint(Util.java:1221)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.jdevimpl.webservices.util.Debug.invoke(Debug.java:343)
         at oracle.jdevimpl.webservices.tools.wsa.Assembler$2$1.invoke(Assembler.java:217)
         at $Proxy48.processDBEndpoint(Unknown Source)
         at oracle.jdevimpl.webservices.tools.wsa.WsaAdaptor.processDbEndpoint(WsaAdaptor.java:588)
         ... 14 more
    Thanks in advance

    Hi! Sorry for the delay...
    I've checked the directory on the link that you mentioned, and it doesn't have any PLSQL package. Only jar's, namely runtime2.jar and translator.jar.. I've checked both jar's for the PLSQL package and I couldn't find it.
    I'll check out the version of the database. I'll get back to you as soon as I have more information...
    Thanks
    Edited by: Tiago Soares on May 10, 2010 4:26 PM

  • Error calling SAP webservice

    Hi,
    I have created a ZBAPI that is published as webservice via SE37 --> using the wizard, and I have created a flex web that invoke this webservice. When I runs the web in my local the call to webservice works perfect, but when I deploy the web in my Composite Environment and I execute the web I get the following error:
    [RPC Fault faultString="Security error accessing url" faultCode="Channel.Security.Error" faultDetail="Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL (http://xxxxxxxxxxxx:8000/sap/bc/srt/wsdl/bndg_4A02EE1AE83732C2E10000000AA51C62/wsdl11/allinone/standard/document?sap-client=330)"]
    I have been searching the solution and only I have found to deploy in the server (Composite Environmentt) the crossdomain.xml in the root, but it doesn't work.
    the crossdomain.xml content is:
    <?xml version="1.0"?>
    <!DOCTYPE cross-domain-policy SYSTEM
    "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
    <cross-domain-policy>
         <site-control permitted-cross-domain-policies="all"/>
         <allow-access-from domain="*" secure="false"/>
         <allow-http-request-headers-from domain="" headers="" secure="false"/>
    </cross-domain-policy>
    and the route where is deployed is:
    D:\usr\sap\XXXX\J00\j2ee\cluster\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root
    any idea?
    thanks in advance
    Jose Manuel

    Dear Vinay,
    Does your other FM are also using arrays.?
    Deserialization problem comes when xml parser is not able to convert XML schema or values to language specific elements.
    And this problem normally comes if you are using complex data types.
    Can you check once again and reply.
    Regards,
    Piyush

  • Generating plsql webservices, output different namespaces not consistent

    We've defined some database-packages which we want to publish as webservice. We use the option in jdeveloper to generate the plsql webservice.
    If we look in the generated wsdl generated by user A, the wsdl gives namespaces like :
    <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://someurl/AlgemeenWS.wsdl/types/"
         elementFormDefault="qualified" xmlns:tns="http://nl/fundeon/fundit/someurl/AlgemeenWS.wsdl/types/"if user B generates the same webservice it gives namespaces lile :
    <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://someurl/AlgemeenWS.wsdl"
         elementFormDefault="qualified" xmlns:tns="http://nl/fundeon/fundit/someurl/AlgemeenWS.wsdl"Any idea how we can control this generated result?
    update :
    when we generate the classes, etc for the first time after selecting the program units to publish...it generates the correct wsdl.
    when we repeat this step (second time of generation), we get the wrong namespace in the wsdl and the log gives us this warning :
    WARNING: Ignoring target namespace for schema: "http://someurl/relatieWS/RelatieWS.wsdl", WSDL target namespace is used for the value types in the same package as Service Endpoint: "nl.packagename.relatieWS.RelatieWSUser_getadviseur_Out"

    Hi Eric,
    I experience exactly the same problem.
    The first time the namespace contains 'types', regenerating the webservice afterwards omits the 'types' part.
    This has some very awkward effects as the webservice envelop and any proxies are affected by this bug.
    I have tried with both 10.1.3.1 & 10.1.3.2, both have the same problems.
    I am looking into regenerations of the webservice using ant tasks, there might be a bug in JDeveloper itself.. who knows...
    perhaps someone from oracle can comment / test this and open up a ticket for resolving....
    Fred Dullemond

  • Error while invoking webservice throu https

    Error while invoking webservice throu https://
    can any one help me on this topic please:
    CODE:
    SOAPConnection con = null;
              try{
                   String endpoint = "https://wks3089639:4565/Service.serviceagent/PortTypeEndpoint1";
                   //String endpoint = "http://wks3101999:5539/Service.serviceagent/PortTypeEndpoint1";
                   //String endpoint      = args[0];
                   //String soapAction      = args[1];
                   System.out.println("javax.net.ssl.keyStore-->"+System.getProperty("javax.net.ssl.trustStore"));
                   System.setProperty("javax.net.ssl.trustStore","C:/Documents and Settings/1067555/Desktop/certificates/cer.jks");
                   System.setProperty("javax.net.ssl.keyStore","C:/Documents and Settings/1067555/Desktop/certificates/server.keystore");
                   System.setProperty("javax.net.ssl.trustStorePassword","password");
                   System.setProperty("javax.net.ssl.keyStorePassword","password");
                   // use Sun's reference implementation of a URL handler for the     "https" URL protocol type.
                   //System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
                   // dynamically register sun's ssl provider
                   System.setProperty("security.provider","com.sun.net.ssl.internal.ssl.Provider");
                   //Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
                   System.out.println("javax.net.ssl.trustStore-->"+System.getProperty("javax.net.ssl.trustStore"));
                   System.setProperty("javax.net.debug","ssl,handshake");
                   SOAPConnectionFactory connectionFactory = SOAPConnectionFactory.newInstance();
                   con = connectionFactory.createConnection();
                   MessageFactory messageFactory      = MessageFactory.newInstance();
                   SOAPMessage message                = messageFactory.createMessage();
                   SOAPPart soapPart                     = message.getSOAPPart();
         SOAPEnvelope envelope                = soapPart.getEnvelope();
         SOAPBody body                          = envelope.getBody();
    //     MimeHeaders headers = message.getMimeHeaders();
    //     headers.addHeader("SOAPAction", soapAction);
    //     headers.addHeader("SOAPAction", "/Service.serviceagent/PortTypeEndpoint1/Operation");
    //     headers.addHeader("Content-Type","text/xml");
    //     headers.addHeader("charset","utf-8");
         MimeHeaders headers = message.getMimeHeaders();
         headers.addHeader("SOAPAction", "/Service.serviceagent/PortTypeEndpoint1/sampleOperation");
         headers.addHeader("Content-Type","text/xml");
         headers.addHeader("charset","utf-8");
         StreamSource inputmsg = new StreamSource(new FileInputStream("client.wsdl"));
         soapPart.setContent(inputmsg);
         System.out.println("REQUEST:\n");
         message.writeTo(System.out);
         System.out.println();
         message.saveChanges();
         SOAPMessage reply = con.call(message, new URL(endpoint));
         System.out.println("RESPONSE:\n"+reply.toString());
         System.out.println("Header:::"+reply.getSOAPHeader());
         System.out.println("Body:::"+reply.getSOAPBody());
         System.out.println("RESPONSE:\n");
         TransformerFactory transformerFactory      = TransformerFactory.newInstance();
         Transformer transformer                     = transformerFactory.newTransformer();
         //Extract the content of the reply
         Source responseContent                          = reply.getSOAPPart().getContent();
         //Set the output for the transformation
         StreamResult result = new StreamResult(System.out);
         transformer.transform(responseContent, result);
         System.out.println();
              }catch(Exception e){
                   e.printStackTrace();
              finally{
                   con.close();
    Exception:
    10-Nov-2008 11:55:04 com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection post
    SEVERE: SAAJ0009: Message send failed
    com.sun.xml.messaging.saaj.SOAPExceptionImpl: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:127)
         at com.Sample.main(Sample.java:91)
    Caused by: java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
         ... 1 more
    Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
         ... 3 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(Unknown Source)
         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
         at java.net.PlainSocketImpl.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at sun.net.NetworkClient.doConnect(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
         at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
         ... 4 more
    CAUSE:
    java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
         at com.Sample.main(Sample.java:91)
    Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
         ... 3 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(Unknown Source)
         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
         at java.net.PlainSocketImpl.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at sun.net.NetworkClient.doConnect(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
         at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
         ... 4 more
    CAUSE:
    java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:121)
         at com.Sample.main(Sample.java:91)
    Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Message send failed
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:325)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:150)
         ... 3 more
    Caused by: java.net.ConnectException: Connection refused: connect
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(Unknown Source)
         at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
         at java.net.PlainSocketImpl.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at java.net.Socket.connect(Unknown Source)
         at sun.net.NetworkClient.doConnect(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.http.HttpClient.openServer(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
         at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
         at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
         at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
         at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)
         at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:282)
         ... 4 more
    Edited by: javausers07 on Nov 10, 2008 11:58 AM

    I hope the sun forum can help for me. Lets see

  • Error while generating webservices using Date

    I am facing the following problem while generating a web service which is having Date as one its members.
    I have serialized a class with the following DataStructure
    private String rowId1;
    private Date created;
    private String name;
    private String quoteNum;
    private String revNum;
    private String curcyCd;
    private String activeFlg;
    private Number discntAmt;
    private Number discntPercent;
    When i tried to expose this as webservice, If I use the class oracle.jbo.domain.Date for Date type, the webservice is not generated properly. It is not including the method which contains this call. ie) This method is not present in the WSDL file as well as in the proxy.
    When I used java.util.Date instead of oracle.jbo.domain.Date, I am able to expose the method and webservice got generated properly. But When i tried to generate the proxy for the WSDL in the consumer, I go the following error.
    oracle.jdeveloper.webservices.model.GenerationException: Proxy generation failed for the following reason:
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.doGeneration(ProxyGenerator.java:608)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.generateImpl(ProxyGenerator.java:365)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.mav$generateImpl(ProxyGenerator.java:77)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator$1ThrowingRunnable.run(ProxyGenerator.java:206)
         at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.RuntimeException: generator error: no encoder for type "{http://www.w3.org/2001/XMLSchema}dateTime" and Java type "java.lang.String"
         at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:105)
         at oracle.j2ee.ws.tools.wsa.AssemblerTool.run(AssemblerTool.java:99)
         at oracle.j2ee.ws.tools.wsa.WsdlToJavaTool.createProxy(WsdlToJavaTool.java:354)
         at oracle.j2ee.ws.tools.wsa.Util.createProxy(Util.java:838)
         at oracle.jdeveloper.webservices.model.proxy.ProxyGenerator.doGeneration(ProxyGenerator.java:549)
         ... 6 more
    Caused by: generator error: no encoder for type "{http://www.w3.org/2001/XMLSchema}dateTime" and Java type "java.lang.String"
         at oracle.j2ee.ws.common.processor.generator.GeneratorBase.doGeneration(GeneratorBase.java:181)
         at oracle.j2ee.ws.common.processor.generator.GeneratorBase.perform(GeneratorBase.java:137)
         at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:97)
         ... 10 more
    I am referring to "Entity and view objects based on web service " in the following URL
    http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.html#93
    Thanks and Regards,
    James

    Hi all,
    I have applied the consolidated JRI fixes - patch 17191279 .
    Then, when generating Jar, received keypass is tampered error.
    re-generated the key using $ adjkey -initialize.
    Now, its working fine.
    Regards,
    Krish.

  • Error Publishing Podcast to ITunes using IWeb

    I am getting the following error publishing my podcast to Itunes using Iweb.
    We had difficulty reading this feed. Bad http result code: 500
    When I checked the rss.xml doc that iweb generates, it is very different from what itunes gives as an example. Do you guys plan on making your software match to the Itunes requirements so that it will post. I can edit and upload the xml file, but when iweb publishes again it will simply change it back to the wrong file.
    Is there an update coming? What should I do?

    Thanks for the suggestion. It seems that from GarageBand the only podcast option is to send it to iWeb. The option exists: "send song" to iTunes, but not "send podcast" directly to iTunes. I don't know if there's a meaningful difference between "song" and "podcast," but I've decided to wait.
    I contacted Apple (apparently I haven't yet exhausted my free tech-support options since the purchase of this MacBookPro) and was told that the problem is most likely with iTunes. We'll see what the iTunes team has to say...
    Further info I've learned: the audio podcast episode somehow got converted to a ".mov" file somewhere along it's path from being created in GarageBand to it's submission to iTunes. This is still a mystery to me as I specifically chose "MP3" when sending the episode from GarageBand to iWeb. Apple tech-support has passed me along the chain to the iTunes folks who only do tech support via email. So we'll see...

  • Error Publishing Policy

    Hi, I encountered an error when publishing a policy to the clients. The error message is displayed in a dialog box after clicking on "Publish".
    "The Management Console was unable to complete the policy assignment. The requested policy assignment has been queued and will be replicated to the Distribution Service during the next scheduled synchronization interval. To review your configured synchronization intervals open the configuration window from the Tools menu."
    Can anyone explain the cause and how to resolve it? Thanks.

    I never saw that error. Default values for infrastructure settings are fine for most implementations.
    Anyway, keep posting if you have problems.
    >>>
    From: KAJEREMY<[email protected]>
    To:novell.support.zenworks.endpoint-security-management
    Date: 20/2/2009 14:46
    Subject: Re: Error Publishing Policy
    I have 3 PCs, 1 running xp sp2 1 running win server 2008 and 1 running
    win server 2003. the xp box is the client machine, the server 2008 box
    is the AD machine, and the server 2003 box is a single server
    installation of ESM.
    I have been using the 2nd policy that I created with no issues. I
    actually ended up deleting the original policy yesterday afternoon
    because it was still giving me that message.
    I never did figure out what was causing it, but I needed to move on
    with the evaluation so I'm continuing with the 2nd policy and we'll see
    how that goes...
    Thanks for the reply!!
    dspinatto;1739430 Wrote:
    > Please describe your environment.
    >
    >
    > >>> From: KAJEREMY<[email protected]>
    >
    > To:novell.support.zenworks.endpoint-security-management
    > Date: 18/2/2009 15:26
    > Subject: Re: Error Publishing Policy
    >
    > chuacheehow;1474402 Wrote:
    >
    > > After some trying, it seems that the problem has to do with the
    > > synchronization intervals as indicated in the message.
    > >
    > > When I shut down the machines for a long time, say, a day, the next
    > > time I turn the machines on, the policies get updated. So it seems
    > that
    > > the problem has to do with the synchronization interval but this
    > > interval cannot be set to zero - it has to be a minimum of 15
    > minutes
    > > for "Distribution Service" and "Policy Data and Activity".
    > >
    > > I'm now going to set the values at 15 minutes and wait for 15
    > minutes
    > > to see if the policy can get updated on the clients' end. But I'd
    > > appreciate if anyone can shed some light on how to get the policy
    > sent
    > > to the workstations immediately as I need to do demos to potential
    > > customers.
    >
    >
    > I'm having the same issue. It was working fine while testing the
    > first
    > day, but the 2nd day of testing I get the same error. I've waited 15
    > minutes (the specified refresh time) but nothing seems to happen...
    > I then created a 2nd test policy and have been able to publish that
    > several times in a minute...
    > Trying to publish the first policy still gives the same error.
    > I've rebooted both server and client, same result. I'll wait a while
    > longer and post back if I find anything
    >
    >
    > --
    > KAJEREMY
    > ------------------------------------------------------------------------
    > KAJEREMY's Profile: 'NOVELL FORUMS - View Profile: KAJEREMY'
    > (http://forums.novell.com/member.php?userid=9979)
    > View this thread: 'Error Publishing Policy - NOVELL FORUMS'
    > (http://forums.novell.com/showthread.php?t=312762)
    KAJEREMY
    KAJEREMY's Profile: http://forums.novell.com/member.php?userid=9979
    View this thread: http://forums.novell.com/showthread.php?t=312762

  • Errors while invoking webservice

    I am getting below error while invoking webservice in jdev:
    <env:Envelope
      xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
      <env:Fault>
       <faultcode>env:Server</faultcode>
       <faultstring>Failure in SDOSerializer.deserialize.</faultstring>
      </env:Fault>
    </env:Body>
    </env:Envelope>
    I can see only below log in jdev server log :
    <oracle.adf.model> <SDOHelper> <findHelperContext> <SDOHelperContext identified by {http://xmlns.oracle.com/apps/projects/projectManagement/common/projectServiceV2/}ProjectService has not been defined yet!>
    <oracle.adf.model> <SDOHelper> <findHelperContext> <SDOHelperContext identified by {http://xmlns.oracle.com/apps/projects/projectManagement/common/projectServiceV2/}ProjectService has not been defined yet!>
    could anybody help me to understand what gone wrong ?

    This thread might help you:
    Problems invoke Web Service

  • Error while publishing a service with WSPUBLISH: Error publishing Endpoint

    Hallo,
    I've a problem while publishing a service which a had created via proxy. I configured the service and one endpoint (binding) in SOAMANAGER. When I publish the service in WSPUBLISH I get the error:
    'Error publishing Endpoint for SD : <Proxy>, Service : <Service>, EP : <Endpoint>.
    with details:
    '10160A save request exceeded the quantity limits for a given structure type .#Number of BusinessEntities exceeds your limit of 1 (2)'
    In the Service Registry I can find the service but without endpoints.
    Does anybody know what happend ?
    We use a SAP NetWeaver 7.10 with SP05 (SAPKB71005) but the same error happens if I publish a service from a CRM 5.0 with SP15 (SAPKB70015) to the Service Registry of the 7.10
    Christoph

    This is my steps to publish ES to SR:
    1. Create RFC destination in SM59
    2. Create ES Parameter in WSPARAM
    3. Create logical port for SR in LPCONFIG
    4. Release Web Service for SOA Runtime in WSCONFIG
    5. Publish ES in WSPUBLISH.
    When i was using SOAMANAGER to manually create the endpoint, the endpoint in the SR doesnt works though.
    eg,  Business Administration -> WS Administration -> Search for CRM_BPBASICDATABYIDQR -> Apply selection -> Configuration -> Create Service -> enter new service name and new binding name -> user id/password  for HTTP Authentication -> save.
    It works after i released it in WSCONFIG (ya, i know it's old way) and re-publish.
    -julius

  • InvalidSecurity Error while accessing Webservice

    Hi,
    I am getting an "*InvalidSecurity*" error while accessing webservice.
    Below is the error, which I got while invoking the webservice :
    <env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header/>
    <env:Body>
    <env:Fault
    xmlns:ns0="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <faultcode>ns0:InvalidSecurity</faultcode>
    <faultstring>InvalidSecurity : error in processing the WS-Security security header</faultstring>
    <faultactor/>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    Thanks
    Abheek
    Edited by: 1005832 on May 14, 2013 6:16 AM

    The error was generated on the endpoint and indicates that the SOAP request message had incorrect WS-Security information in its headers. The SOAP response message you included doesn't contain specific information about what is wrong (we wouldn't want to reveal too much to hackers, of course!).
    Without seeing the SOAP request message and the WS-SecurityPolicy that the endpoint requires, it's impossible to tell what's wrong.
    Other important information:
    - what version of WLS are you running?
    - is the endpoint a WLS JAX-WS or a WLS JAX-RPC web service?
    - is WS-Security configured using native WLS WS-Security (e.g. @Policy) or using OWSM WS-Security (i.e. @SecurityPolicy)?
    - what specific policy is being used to enforce security at the endpoint (the advertised WSDL for the endpoint should contain this)

  • ORA-01403: no data found Error in PLSQL code raised during plug-in processing.

    Hello OTN community,
    We are having the access to APEX problem. a New user was setup to access the APEX application. When I test to login as a new user, I get the message "ORA-01403: no data found Error in PLSQL code raised during plug-in processing.". When click OK to the disply message, the application will take me out of the sstem. I need help to even understand what is happening. I didn't develop the application, there is no documentation for this application, I am just supporting the application whenever there is a problem and I am new to APEX. As you can see I need help to figure this thing out. Your help is dearly appreciated.
    Thank you OTN

    Try to check the query that is executed and check if there is data or not

  • How to publish a  webservice

    Hai experts,
    I have created one  java webservice using NWDS and it is working fine in all environments it is deployed. I want to publish this webservice. Can anyone explain the way for publish this webserice as like a third party webservice.
    Advance thanks.
    Kind Regards,
    Hariprasath.R

    Hello,
    I assume you mean publishing to the Services Registry - check [this|http://help.sap.com/saphelp_nwce10/helpdata/en/46/7f3d32ba796be3e10000000a155369/frameset.htm] out.
    HTH!
    \-- Vladimir

Maybe you are looking for