Create Web Services in WebLogic Workshop

I'm new to WebLogic. Basically I need to create a web service to grab data from
database, then to convert the data to XML, then to call a transformation control
to map to another XML schema, then to build the XML into a web service and send
out to client.
All the web service examples are not using Workshop, thus I have no idea how to
invoke a control (transformation control) within the code. Also, what are the
differences to implement web services in ANT and in Workshop?
Thanks,

Hi Henry,
Try taking a look at:
http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
For using Ant with WLW, see:
http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/howdoi/HowUseCustomAntBuild.html?skipReload=true
Bruce
Henry Niu wrote:
>
I'm new to WebLogic. Basically I need to create a web service to grab data from
database, then to convert the data to XML, then to call a transformation control
to map to another XML schema, then to build the XML into a web service and send
out to client.
All the web service examples are not using Workshop, thus I have no idea how to
invoke a control (transformation control) within the code. Also, what are the
differences to implement web services in ANT and in Workshop?
Thanks,

Similar Messages

  • Invoking web service using Weblogic Workshop (JCX)

    Invoking web service using Weblogic Workshop
    Posted: 5 Jan 2005 23:31 PM Reply
    Hi,
    I have WSDL from which I have generated a web service control (.jcx) using Weblogic Workshop.
    I need to write a client which will invoke the web service using the control.
    Can someone help me on how to go about this ?
    BTW .. I also tried the clientgen route and tried to generated the proxy jar from the WSDL but wasn't successful because of a existing clientgen bug.
    Refer bug

    Hi,
    if the consumer of the webservice is a control-aware consumer ( pageflow, control, process ) simply drag the control to this consumer and the control variable is ready for use.
    if the consumer is not control-aware, try to generate a proxy using eg. the axis tool, or handcode your proxy class.
    links :
    how to use webservice control
    http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/conGettingStartedWithJavaControls.html
    axis
    http://ws.apache.org/axis/
    - Anders M.
    - Anders M.

  • Deploying a web service to WebLogic 7 - error with RemoteDispatcherBean

    Hi there,
    I have just created a web service through WebLogic Workshop. The web service can be tested through the workshop and it works fine
    I am trying now to deploy it to a development server, and I am having the following error:
    preparing application <appName> on mope
    Exception caught for task Activate application <appName> on mope: Prepare failed. Task Id = 1
    Module, AP_NotificationEJB.jar, reported error: Exception preparing module: EJBModule(AP_NotificationEJB.jar,status=NEW)
    Unable to deploy EJB: C:\bea\<deploymentPath>\.wlnotdelete\<appName>\AP_NotificationEJB.jar from AP_NotificationEJB.jar:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: weblogic.knex.bean.RemoteDispatcherBean
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:440)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfo(EJBDeployer.java:965)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1276)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:235)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1742)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:745)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:559)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1116)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:784)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
    Looking inside the EAR I generated (using jwsCompile), I can find several classes RemoteDispatchBean_bu6zup_....class but no RemoteDispatchBean.class file anywhere
    Am I doing anything wrong to generate the EAR file? Anything fancy I need to include to my jws file or any descriptor?
    Any idea or suggestion would be much appreciated
    Thank you,
    Miguel

    We have found a work around for that specific problem.
    We have included the whole knex library within our libs folder. Now we can deploy the Web services as a web application to the webLogic, The deployment returns successful, but any time we initiate the server, there is another ClassNotFoundException. This time the missing class is weblogic.knex.bean.DeploymentListener.
    The strange thing is that that specific class is part of the knex.jar library we have included within our libs folder ...
    It seems that the folder is not read from the server when starting, but it is read when executing the application.
    Any suggestion to this nonsense?
    Thanks,
    Miguel

  • Unable to create web service from wsdl that contains xsd as import

    I have written a WSDL and tried to create the web services by weblogic workshop.
    Prior to that I have created the war file and able to deploy them properly. Also able to access any wsdl by hitting the server.
    But when I am trying to create the web services by weblogic workshop its throwing error as "URL is not well formed" for those XSDs which I have imported in my WSDL. I have kept all my XSDs and WSDLs in the same folder.
    The WSDL has given below :
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:intf="http://soapheader.ibm.com" xmlns:impl="http://soapheader.ibm.com" xmlns:MessageContext="MessageContext" xmlns:AlertUpdateRequest="AlertUpdateRequest" xmlns:AlertFetchResponse="AlertFetchResponse" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapheader.ibm.com">
         <import namespace="MessageContext" location="http://localhost:7001/WebApplicationWeb/gss/xsd/MessageContext.xsd"/>
         <import namespace="AlertUpdateRequest" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertUpdateRequest.xsd"/>
         <import namespace="AlertFetchResponse" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertFetchResponse.xsd"/>
         <wsdl:types>
              <schema elementFormDefault="qualified" targetNamespace="http://ggg.com" xmlns="http://www.w3.org/2001/XMLSchema">
              </schema>
         </wsdl:types>
         <wsdl:message name="alertUpdateRequest">
              <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertUpdateResponse">
              <wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertFetchRequest">
              <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:message name="alertFetchResponse">
              <wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
              <wsdl:part name="request_header" element="MessageContext:MessageContext"/>
         </wsdl:message>
         <wsdl:portType name="AlertUpdateService">
              <wsdl:operation name="getAlertUpdate">
                   <wsdl:input name="alertUpdateRequest" message="intf:alertUpdateRequest"/>
                   <wsdl:output name="alertUpdateResponse" message="intf:alertUpdateResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:portType name="AlertFetchService">
              <wsdl:operation name="getAlert">
                   <wsdl:input name="alertUpdateRequest" message="intf:alertFetchRequest"/>
                   <wsdl:output name="alertUpdateResponse" message="intf:alertFetchResponse"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="AlertUpdateServiceSoapBinding" type="intf:AlertUpdateService">
              <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="getAlertUpdate">
                   <wsdlsoap:operation/>
                   <wsdl:input>
                        <wsdlsoap:header message="intf:alertUpdateRequest" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <wsdlsoap:header message="intf:alertUpdateResponse" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:binding name="AlertFetchServiceSoapBinding" type="intf:AlertFetchService">
              <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="getAlert">
                   <wsdlsoap:operation/>
                   <wsdl:input>
                        <wsdlsoap:header message="intf:alertFetchRequest" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <wsdlsoap:header message="intf:alertFetchResponse" part="request_header" use="literal"/>
                        <wsdlsoap:body parts="parameters" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="AlertUpdateServiceService">
              <wsdl:port name="AlertUpdateService" binding="intf:AlertUpdateServiceSoapBinding">
                   <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertUpdateService"/>
              </wsdl:port>
         </wsdl:service>
         <wsdl:service name="AlertFetchServiceService">
              <wsdl:port name="AlertFetchService" binding="intf:AlertFetchServiceSoapBinding">
                   <wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertFetchService"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>

    Hi,
    From your description I am assuming that you are using JAX-WS, if not get back to me as I might have another bug to look at.
    The problem is that the annotation @Oneway needs to be added to the methods in java files for this to work correctly. You can either do this manually or use the PI in the code editor. I have raised bug 6266513 to track the fact this annotation is not written out properly. I have logged bug 6266556 to track the nillable=true and extranious elements you will see when you do add @Oneway.
    Thanks for the quality of your bug report, and we would of course welcome any other feedback good or bad you would like to give us.
    Gerard Davison
    JDeveloper Web Services Team

  • Problem creating portal web project in weblogic workshop 9.2

    hello All,
    I am facing a problem when i create portal web project in weblogic workshop 9.2 it gives some problems
    The library module reference :
    p13n-app-lib
    wlp-framework-full-app-lib
    wlp-services-app-lib
    wlp-tools-support-app-lib
    is on the classpath of this project, but it is not contained in the weblogic.xml descriptor of this WEB project : portalproject.     weblogic.xml     portalproject/WebContent/WEB-INF     
    so plz help me how we provide these library .
    Diwakar Gupta

    Those are application libraries that should be listed under the portal enterprise app under meta-inf/weblogic-application.xml.

  • Web service client in Workshop 10.1

    Anybody have any advice on the best way to create a Web service CLIENT in Workshop 10.1 ?
    I've been looking around for a couple of days. I understand how to run clientgen from the command line. That works fine.
    I have looked at the tutorial for using 'Web service controls' also. As far as I can tell, though, in Workshop 10.1 I can only generate such a control nside another Web service, as in the tutorial. In other types of classes, the Insert option is not available on the menu I pull up by right-clicking in the source. I hope I am missing something obvious.
    My goal is to call Web services from other applications inside Workshop. The other applications may be Web applications or they may not. Most of the time they will not be other Web services.
    Thanks in advance for any help !!

    Thanks Vimala.
    I am able to create the JAR using clientgen, and I can call the Web service after that from the command line. All of that depends upon various environment variables being set with setDomainEnv.cmd and it works fine.
    I would like to create a Java project in Workshop 10.1 and use that JAR created with clientgen, but that does not work - I get an Exception wqhen I try to run, although it all compiles :
    Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/descriptor/BasicDescriptorManager
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClass(Unknown Source)
         at java.security.SecureClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.defineClass(Unknown Source)
         at java.net.URLClassLoader.access$100(Unknown Source)
         at java.net.URLClassLoader$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
         at com.kohls.example.client.SimpleClient.main(SimpleClient.java:29)
    The classes are al lthere, or it would not compile, so I assume I am missing some of the scaffolding around calling the Web service. I just created a normal Java project - maybe that's wrong ?
    Edited by ethan_kohls at 01/18/2008 12:44 PM
    Edited by ethan_kohls at 01/18/2008 12:44 PM

  • How to create Web Service based on PI WSDL message

    Hi all,
    we have following scenario:
    Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
    Unfortunately, I have problems creating the Web Service.
    For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
    What I tried so far is:
    - I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
    - I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
    I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
    Can you please advice me how to create a Web Service in such an environment?
    regards
    René Jurmann

    Hi Tahir,
    sorry that you needed to wait this long - but this is how I created the web service:
    The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
    Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
    Prerequisites:
    Add Java Perspective and J2EE Development Perspective to the open perspectives.
    Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
    The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
    Create a Development Component (DC) with type "J2EE -> EJB Module"
    The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
         Choose "File -> New -> Other"
         In opening PopUp choose "Development Component -> Development Component Project"
         Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
         Choose now vendor, name and type:
              vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
              name is an alpha-numeric string starting with a letter - all in lower case
              vendor and name concatenated must not be longer then 40 characters
              the name can be separated into different part using "/" as separator
              each part of the name must not be longer than 8 characters
              the type is "J2EE - EJB Module"
              you can specify a Caption as general description for the web service
    Create new EJB
    To create the EJB itself:
         In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
         Choose "New - EJB" with following details:
              EJB Name: <name as for PI service Interface to be created - starting in upper case>
              EJB Project: <pre selected>
              Bean Type: Stateless Session Bean
              Default EJB Package: <corresponds to namespace in PI>
              generate default interfaces: Checked
    Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
    Example:
    Namespace in PI is:  http://company.net/pi/SOFTWARE_COMP/Application
    The corresponding package then is: net.company.pi.software_comp.application
    Implement coding for web service
    As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
    Data Type
    net.company.pi.software_comp.application.types.MessageProcessingInformation
    Structure:
         Element name          Element type
         sendingSystemID          String
         interfaceID               String
         businessProcessVariantCode     String
         testIndicator               Boolean
    For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
    package net.company.pi.software_comp.application.types;
    import java.io.Serializable;
    public class MessageProcessingInformation implements Serializable {
         protected String sendingSystemID;
         protected String interfaceID;
         protected String businessProcessVariantCode;
         protected Boolean testIndicator;
         public String getSendingSystemID() {
              return sendingSystemID;
         public void setSendingSystemID(String value) {
              this.sendingSystemID = value;
         public boolean hasSendingSystemID() {
              if(sendingSystemID != null && !sendingSystemID.equals("")){
                   return true;
              return false;
    All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
    As soon as all data types are declared the real business logic can be implemented:
         In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
         In detail view select folder "Business Methods" and click "Add"
         choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
         return type should be "void"
         add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
         you can mark certain parameters as array if necessary
    Remark:
    It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
    It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
    Within the newly created business method within the bean class you can now implement the business logic.
    Create a DC with type "J2EE -> Enterprise Application"
    In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
    After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
    Create web service for EJB
    As soon as you implemented the business logic you can create the "real" web service. Therefore:
         Right click on the EJB name below "ejb-jar.xml"
         Choose "New - Web Service"
         Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
         Copy the URL of the web service - you'll need it later for PI configuration
         on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
         the "EAR Project" should be preselected
    Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
    Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
    Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
    If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
    As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
    For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
    If all this is done you can deploy the web service to the J2EE:
         right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
         right click on "Enterprise Application" DC and choose "Development Component - Deploy"
    Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
    Create PI interface
    After the web service is created successfully the PI integration can be started.
    Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
    Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
    In case you need to include arrays following applies:
    The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
    Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
    Create PI mappings and routings
    How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
         When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
              <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
         The soap action is the name of the web service business method.
         Most likely the web service needs authentication to be executed.

  • Error creating web service from WSDL in 11.1.2.0.0

    Hello,
    I have just installed JDeveloper 11.1.2.0.0. I tried to test a web service created (and successfully tested) in 11.1.1.5.0. The service is deployed to internal WebLogic server but when I call "Test Web Service" this is the error I get:
    The Web Service Tester cannot be invoked, because the WSDL document of the selected service cannot be read.
    java.lang.IllegalStateException: SSLContextImpl is not initialized
         at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
         at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
         at java.lang.ThreadLocal.get(ThreadLocal.java:131)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLDirect(CachedWSDLReader.java:471)
         at oracle.jdevimpl.webservices.tcpmonitor.ServiceTester$3.run(ServiceTester.java:262)
         at java.lang.Thread.run(Thread.java:662)
    Then I tried to create a new project and Java web service from WSDL, but on the second step of the "Java Web Service from WSDL" wizard when I select WSDL file from the disk and click "Next" I get
    java.lang.IllegalStateException: SSLContextImpl is not initialized
    java.lang.IllegalStateException: SSLContextImpl is not initialized
         at com.sun.net.ssl.internal.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:145)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdevimpl.credential.LazySSLContextSpi.engineGetSocketFactory(LazySSLContextSpi.java:67)
         at javax.net.ssl.SSLContext.getSocketFactory(SSLContext.java:260)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getNewReaderInstance(CachedWSDLReader.java:398)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:298)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader$1.initialValue(CachedWSDLReader.java:294)
         at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:141)
         at java.lang.ThreadLocal.get(ThreadLocal.java:131)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.getReaderImpl(CachedWSDLReader.java:308)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDLInternal(CachedWSDLReader.java:531)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:484)
         at oracle.jdeveloper.webservices.wsdl.CachedWSDLReader.readWSDL(CachedWSDLReader.java:455)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel.fetchWSDL(SpecifyWsdlPanel.java:1050)
         at oracle.jdevimpl.webservices.wizard.jaxrpc.common.SpecifyWsdlPanel$1.run(SpecifyWsdlPanel.java:364)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:655)
         at java.lang.Thread.run(Thread.java:662)
    I performed fresh install of this new JDeveloper version in new Middleware home with all the default options and this is the first thing I tried.
    Any hints?
    Thanks,
    Bruno

    Hi Vishal,
    no, I don't see any HTTPS security settings defined. The thing is that this worked just fine in 11.1.1.5.0 version. I installed 11.1.2.0.0 and the first thing I tried was testing this web service. Right away I get this error. I also tried creating Web Service Client Proxy for this web service and I get the same exception. I looks to me that this happens when wizard tries parsing WSDL...
    But, I got another error when I opened "Java Web Service Editor" for this web service and selected "Methods":
    NPE in o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel:702
    Performing action (35) Project Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService.jpr, VegaService.jpr, DMSVegaAdapter.jws ) ]
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:02 AM IndexFacade runQuery
    INFO: Having to guess workspace
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:05:28 AM IndexFacade runQuery
    INFO: Having to guess workspace
    Performing action (23) Find... [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (25) Find Next [ from CodeEditor ] [ for ( VegaService.wsdl, VegaService.jpr, DMSVegaAdapter.jws ) ]
    Performing action (56) Properties... [ from ProjectNavigatorWindow ] [ for ( VegaService, VegaService.jpr, DMSVegaAdapter.jws ) ]
    oracle.jdevimpl.webservices.index:Jun 9, 2011 9:09:32 AM IndexFacade runQuery
    INFO: Having to guess workspace
    java.lang.NullPointerException
    java.lang.NullPointerException
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.populateListImpl(SelectMethodsPanel.java:702)
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel.access$600(SelectMethodsPanel.java:82)
    o.ji.webservices.wizard.jaxrpc.bottomup.SelectMethodsPanel$4$1.run(SelectMethodsPanel.java:603)
    j.a.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    j.a.EventQueue.dispatchEventImpl(EventQueue.java:642)
    j.a.EventQueue.access$000(EventQueue.java:85)
    j.a.EventQueue$1.run(EventQueue.java:603)
    j.a.EventQueue$1.run(EventQueue.java:601)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.a.EventQueue.dispatchEvent(EventQueue.java:612)
    o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
    o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
    j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:178)
    j.a.Dialog$1.run(Dialog.java:1046)
    j.a.Dialog$3.run(Dialog.java:1098)
    j.security.AccessController.doPrivileged(Native Method)
    j.a.Dialog.show(Dialog.java:1096)
    j.a.Component.show(Component.java:1585)
    j.a.Component.setVisible(Component.java:1537)
    j.a.Window.setVisible(Window.java:842)
    j.a.Dialog.setVisible(Dialog.java:986)
    o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:395)
    o.bali.ewt.dialog.JEWTDialog.runDialog(JEWTDialog.java:356)
    o.i.dialogs.WizardLauncher.runDialog(WizardLauncher.java:55)
    o.i.panels.TDialogLauncher.showDialog(TDialogLauncher.java:225)
    o.ji.webservices.wizard.jaxrpc.WebServicesEditor.showDialog(WebServicesEditor.java:313)
    o.ji.webservices.WebServicesAddin.findAndInvokeWizard(WebServicesAddin.java:1672)
    o.ji.webservices.WebServicesAddin.handleEvent(WebServicesAddin.java:870)
    o.i.controller.IdeAction$ControllerDelegatingController.handleEvent(IdeAction.java:1469)
    o.i.controller.IdeAction.performAction(IdeAction.java:662)
    o.i.controller.IdeAction.actionPerformedImpl(IdeAction.java:1140)
    o.i.controller.IdeAction.actionPerformed(IdeAction.java:617)
    jx.s.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
    jx.s.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
    jx.s.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
    jx.s.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
    jx.s.AbstractButton.doClick(AbstractButton.java:357)
    jx.s.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:809)
    jx.s.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:850)
    j.a.Component.processMouseEvent(Component.java:6289)
    jx.s.JComponent.processMouseEvent(JComponent.java:3267)
    j.a.Component.processEvent(Component.java:6054)
    j.a.Container.processEvent(Container.java:2041)
    j.a.Component.dispatchEventImpl(Component.java:4652)
    j.a.Container.dispatchEventImpl(Container.java:2099)
    j.a.Component.dispatchEvent(Component.java:4482)
    j.a.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
    j.a.LightweightDispatcher.processMouseEvent(Container.java:4238)
    j.a.LightweightDispatcher.dispatchEvent(Container.java:4168)
    j.a.Container.dispatchEventImpl(Container.java:2085)
    j.a.Window.dispatchEventImpl(Window.java:2478)
    j.a.Component.dispatchEvent(Component.java:4482)
    j.a.EventQueue.dispatchEventImpl(EventQueue.java:644)
    j.a.EventQueue.access$000(EventQueue.java:85)
    j.a.EventQueue$1.run(EventQueue.java:603)
    j.a.EventQueue$1.run(EventQueue.java:601)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
    j.a.EventQueue$2.run(EventQueue.java:617)
    j.a.EventQueue$2.run(EventQueue.java:615)
    j.security.AccessController.doPrivileged(Native Method)
    j.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
    j.a.EventQueue.dispatchEvent(EventQueue.java:614)
    o.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
    o.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
    j.a.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
    j.a.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
    j.a.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
    j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
    j.a.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
    j.a.EventDispatchThread.run(EventDispatchThread.java:122)
    Regards,
    Bruno

  • Issue in creating web service for a ABAP Function Module

    Hi,
    now i'm learning how to create web service for a ABAP Function Module. I used the following steps.
    1. select the Function Module, named "zws_test".
    2. in the context menu, select "create->proxy object". so we enter into wizard.
    3. in the wizard, press the radio button "Service Provider".
    4. in the next page, press the radio button "Existing ABAP Objects(Inside Out)".
    5. In the next page, Enter the "zws_test_prvider" as Service Definition and select "Function Module" as Endpoint Type.
    6. in the next page, enter "zws_test" as Function Module and mark the "Mapping der Namen" button
    7. in the next page,select "PRF_DT_IF_SEC_LOW" as Profile and mark "Deploy Service".
    8. Save in the local package.
    9. then it will pop up a window with title "WSDL Source". i selected "URL/HTTP Destination" and press "OK".
    10.in the next page, i enter the URL as "http://hostname:portnumber/", and press "OK".
    11. then it will pop up a window with title "Display logs". A record with error message "HTTP error(return code 404, message "Not found")" appears.
    12. i press "ok" and a service provider with name "zws_test_prvider" appears in my local package.
    13. i use "zws_test_prvider"'s URL to create a service consumer "ZCO_WS_TEST_CONSUMER" and logic portal "LP1".
    14. But when i test my service consumer "ZCO_WS_TEST_CONSUMER", it will throw an exception "cx_ai_system_fault" with errortext "SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/".
    15. I use t-code SM59 to test connection  and get the following info.
          Status HTTP Response     200
          Status Text                      OK
          Duration Test Call             328 ms.
    who can give me the reasons about item 11 and 14, and explain me how to create service provider and service consumer for a Function Module.
    Thanks in advance
    Johnney

    have you seen this weblog
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices

  • How to create Web Service & Web Service Client on OCMS

    Hi all,
    Is anybody can show me how to create Web Service on OCMS?
    I only know how to do it on WebLogic Server.
    It has many differences between OCMS and WLS.
    Thanks & Regards,
    Jack.

    Jack,
    This tutorial can help:
    http://www.oracle.com/technology/products/ocms/pdf/parlayxjdeveloper.pdf
    Regards,
    Adam

  • Create web service from java code in Jdeveloper 11.1.1.5

    I am try to create web service from java code by default it is connected to Integrated web logic server and generate a
    WSDL like this.
    http://localhost:7101/javaexcel-project1-context-root/MyWebService1Soap12HttpPort.
    please tell me how we can change this local host to our needed Host and how to deploy this web service to web logic server.

    Hi,
    Just right click on your project and deploy it to your application server (Weblogic Server (Not the Integrated server)). {Before that, you have create your Application server connection in the Jdeveloper).
    After deployment open the Admin console of the weblogic server and find your ear of the project.Click on that (Go to the "Testing tab") and you will get the "WSDL" (Concreate wsdl)  and "Test Client" of the Project.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Deployment of JSR-109 Web Services on Weblogic 11g (OAS migration)

    Hi.
    I'm being part of an ongoing migration effort from Oracle Application Server 10.1.3.5 to WebLogic 11g (10.3.6). Some of the OAS applications use old JSR-109 Web Services, where each service has the following components:
    - A SEI interface that extends java.rmi.Remote and declares the service methods, which throw java.rmi.RemoteException (e.g. ServiceSEI)
    - A service implementation POJO that implements the SEI interface (e.g. ServiceImpl)
    - A [Service]-config.xml file that declares the service and relates name, namespaces, packages, interface and implementation (e.g. Service-config.xml)
    - A declaration of the service implementation POJO as a servlet (with mapping) in web.xml (docs says it doesn't have to be technically a servlet)
    - A webservices.xml file that defines the service and references the mapping file.
    - A [Service]-mapping.xml file that defines the WS-Java mappings.
    All the artifacts look right according the old documentation:
    - Programming Web Services for WebLogic Server, Creating a J2EE Web Service Manually: http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html
    - Web Services for J2EE 1.0 Final Release Spec: http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    The Web Services work OK in OAS. When I try to deploy any of the application that contain one of that services to WebLogic, I get the following Exception:
    <BEA-101216> <Servlet: "WSServlet_Procesos" failed to preload on startup in Web application: "/webapp".
    java.lang.IllegalStateException: ClassNotFound co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:601)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:273)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:171)
    at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
    at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:705)
    at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201)
    at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54)
    at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:91)
    at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:372)
    at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:83)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    I obviously though the EAR package given to me was incomplete, lacking the ClassNotFound related class, but the package was OK, and is exactly the same that deploys without problems in OAS.
    The ClassNotFound related class is referenced in the <java-xml-type-mapping> element of the [Service]-mapping.xml file, e.g.:
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_ResponseStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperationResponse</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>result</java-variable-name>
    <xml-element-name>result</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I searched the OAs installation deployment dirs looking for the missing class and found it was present in a Jar called deployment-cache.jar. According OC4J related documentation, this Jar es auto-generated at deployment time.
    Weblogic 11g documentation says that kind of Web Services will continue to run, without any changes, on version 10.3.x of WebLogic Server because the associated Web services run time is still supported in this release, although it is deprecated and will be removed from the product in future releases (http://docs.oracle.com/cd/E21764_01/web.1111/e13760/upgrade.htm). I know the right estrategy is migrate the Web Services, but right now my client needs to deploy and use them as they are. I think WL recognizes my service since internally is calling a "Deploytime109MappingHelper" class.
    ¿Is there any way I can deploy that kind of services to Weblogic 11g? ¿I'm I missing some required step?
    As a workaround, I included the OAS generated deployment-cache.jar into the EAR to deploy in Weblogic 11g and the app deploys without errors, but I see this is not a nice solution.
    Any help would be much appreciated.
    Thanks,
    Esteban
    Edited by: salzo on Oct 30, 2012 9:54 AM
    Edited by: salzo on Oct 30, 2012 9:56 AM

    Hi. The [Service]-mapping.xml file is a standard "JAX-RPC mapping file" according the JSR-109 spec and WebLogic 9.2 doc ([1],[2]). That's the file that references the class. Here's a fragment:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Service/types</namespaceURI>
    </package-mapping>
    <package-mapping>
    <package-type>co.com.acme.services</package-type>
    <namespaceURI>urn:Services/wsdl</namespaceURI>
    </package-mapping>
    <java-xml-type-mapping>
    <java-type>co.com.acme.services.ServiceSEI_serviceOperation_RequestStruct</java-type>
    <root-type-qname xmlns:typeNS="urn:Service/types">typeNS:serviceOperation</root-type-qname>
    <qname-scope>complexType</qname-scope>
    <variable-mapping>
    <java-variable-name>String_1</java-variable-name>
    <xml-element-name>String_1</xml-element-name>
    </variable-mapping>
    </java-xml-type-mapping>
    I'll take a look at the ant task.
    Thank you very much.
    [1]http://download.oracle.com/otndocs/jcp/websvcs-1.0-fr-spec-oth-JSpec/
    [2]http://otndnld.oracle.co.jp/document/products/wls/docs92/webserv/jsr109.html

  • How to create web service for a Java class in SAP NetWeaver Studio

    hi all,
    i am using SAP Netweaver Developer Studio.have created a normal java project and i want to create web service for one of the classes in this project. i used the  Web Service Creation Wizard to create a web service for this class. but it says there's no methods available for VI. all my methods in this class are public, what should i do?

    Hi,
    I guess there are other ways. But this is an easy way, if you find the right wizards.
    Besides this it is good practise to define interface methods so that session bean implement these interface methods, and thus seperate the interface from the implementation.
    In this approach you will need 3 projects:
    An enterprise application project (will contain EJB Module)
    An EJB Module project (will contain session bean)
    A Java project (contains code that implements the session bean methods)
    In my previous post I suggested to use a J2EE web mudule project. This was a mistake, it should be EJB module.
    But it should be possible to do it in another way. It is up to you.
    Good luck, Roelof

  • Error while creating web service reference

    Hi,
    I have very limited knowledge of web services. we have a BPEL implementation and I have been handed location to 3 wsdl files for which I am trying to create a web service reference(under shared component->logic) in apex(3.1.1). I am successfully able to create for 1 wsdl but for other two i get the below error.
    "1 error has occurred
    The WSDL document contains multiple SOAP bindings. Application Express only supports WSDL's with one SOAP binding. Click Create Web Service Reference Manually to continue creating a reference for this service."
    looking at the working and not working wsdls, i see the following difference. i collapsed all the xml tags in the wsdl file and found that the one that is not working and giving above error has the below two tags twice with data in it.
    <wsdl:portType name=
    <wsdl:binding name=
    any help to parse this wsdl in APEX be greatly appreciated.
    thanks,
    khan

    I have just read that " APEX does not support multiple binding web services currently" at http://oraclebizint.wordpress.com/category/apex/
    ..still reading it. though the post is dated back in 2008, I wonder why this functionality wasn't added to Apex.

  • XML Parser Error while creating Web service Client using JAX RPC

    hello evryone,
    Im facing XML Parser Error while creating web service client using JAX RPC. Im using Net Beans IDE for development purpose. I have wrote configuration file for client. Now i want to create Client stub. However i dont know how to do this in Net Beans. So i tried to do it from Command promt using command :
    wscompile -gen:client -d build -classpath build config-wsdl.xml
    here im getting Error:
    error parsing configuration file: XML parsing error: com.sun.xml.rpc.sp.ParseException:10: XML declaration may only begin entities
    Please help me out.
    Many thanks in advance,
    Kacee

    Can i use the client generated using jdeveloper 11g to import into the oracle forms 10g, i.e., form builder 10g. Currently this is the version we have in our office.

Maybe you are looking for