Re map wsdl file

Hi to all!
I am a newbie to Web Services and I was trying to resolve the following thing:
I am trying to expose as a WS a Java method which returns an array of strings. In the wsdl file this return is mapped like this:
*<sequence>*
*<element name="return" type="string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>*
*</sequence>*
The problem is that I want to map every element of the array as a separate element. For example let say the array contains personal data, like Name, Surname, Birthplace, Social ID etc, I would like the WSDL file to be smth like the following:
*<sequence>*
*<element name="Firstname" type="string" nillable="true"/>*
*<element name="Lastname" type="string" nillable="true"/>*
*<element name="Birthplace" type="string" nillable="true"/>*
*</sequence>*
Can someone help me how to accomplish that.
Regards
Drini!

Hi,
You can run the adgendbc.sh script to recreate the DBC files -- See (Troubleshooting Login [ID 178437.1]) for details.
However, I would suggest you run AutoConfig and it should recreate the DBC files for you. If you get any errors when running AutoConfig please post the error here.
Thanks,
Hussein

Similar Messages

  • Mapping WSDL file to a URL

    Hi,
    I have successfully deployed the webservice examples included with S1AS7. I would now like to test the interoperability with .NET clients but I have noticed that I have no way of accessing the wsdl file through a URL such as : http://localhost/jaxrpc-simple/HelloWorld?wsdl
    The wsdl file exists because I have used the -keep option with xrpcc.
    I have even tried placing it in the WEB-INF folder but it doesn't seem to work.
    How can I map the wsdl to a URL and is there a way of not having to do it manually each time.
    Thanks,
    Tom

    Hi Thomas,
    I was expecting http://localhost/jaxrpc-simple/HelloWorld?wsdl for generating the wsdl file too.
    In order to work with .NET, I did the following
    1. create wsdl file using -keep option
    2. run wsdl command to generate webservice a proxy classe
    c:\> wsdl HelloWorld.wsdl
    This will create HelloWorldService.cs. You can review the source code and change URL if you need to.
    HellowWorldService ws = new HelloWorldService();
    ws.Url = ... // set to your webservice url
    or optionally you can deploy wsdl file in war file (i.e. copy HelloWorld.wsdl to your root context)
    index.html
    HelloWorld.wsdl
    WEB-INF/web.xml
    etc.
    Assuming the context name is jaxrpc-simple
    c:\> wsdl http://localhost/jaxrpc-simple/HelloWorld.wsdl
    But you still have to manually update the server information in wsdl file. I prefer ?wsdl approach (like WebLogic or Apache AXIS). I hope SUN remedy this problem.
    Andy

  • Mapping wsdl - custom vs generic

    Would there ever be a difference in the custom and generic mapping wsdl files?
    Thanks!
    -Kevin

    Hi, It depends on the kind of application you develop. If you are developing something that dumps all the data from OnDemand using WS or building some app that can work across multiple instances, it is better to use generic wsdl otherwise custom is good. The problem with generic is it contains whole lot of fields and any integration tag changes for custom created fields would not be reflected in custom wsdl so it is going to be time confusion and tough to manage using generic WSDL. If the application is simple it may not worth to handle that complexity. Hope it helps
    -- Venky CRMIT

  • Problem in Creating .wsdl file and mapping.xml with ant

    hi
    i am created my .wsdl file and mapping.xml file with wscompile tool but when i run this by ant tool it show a problem.
    the command runs on command prompt but when run throught ant file it shows a following error :-
    Execute failed: java.io.IOException: CreateProces: wscompile -define -mapping build\classes\META-INF\mapping.xml -d . -nd build\.................and so on
    so if anybody have any idea then plz help me asap
    thanx

    The following Ant snippet is the way I've defined my wscompile task. I'm creating a web application and it looks like yours might be an EJB endpoint, but you can adjust where necessary:
    <taskdef name="wscompile" classname="com.sun.xml.rpc.tools.ant.Wscompile">
         <classpath refid="compile.classpath" />
    </taskdef>
    <target name="init">
         <echo message="-------- ${appname} --------" />
    </target>
    <!-- This target compiles the server components using an existing WSDL as the driving document.
           The configuration file must use the <wsdl> element giving the location (local file system
           or URL) of the WSDL document.
           Note: the fork argument is needed to over come a bug when using the mapping argument. See
           http://forum.java.sun.com/thread.jspa?threadID=592994&tstart=0
      -->
         <target name="generate-server-from-WSDL" depends="init">
              <wscompile fork="yes"
                           keep="true"
                           base="${basedir}/WebContent/WEB-INF/classes"
                           import="true"
                           features="wsi"
                           xPrintStackTrace="true"
                           verbose="true"
                           mapping="${basedir}/WebContent/WEB-INF/jaxrpc-mapping.xml"
                           sourcebase="${basedir}/src"
                           config="${config.server.doclit.file}">
                   <classpath>
                        <path refid="compile.classpath" />
                   </classpath>
              </wscompile>
         </target>
         <target name="compile-server-from-WSDL" depends="generate-server-from-WSDL">
              <javac srcdir="${basedir}/src" destdir="${basedir}/WebContent/WEB-INF/classes" debug="${compile.debug}">
                   <classpath refid="compile.classpath" />
              </javac>
         </target>Just make sure that the named destination directories exist before you run the script.
    If you'd like more details on the wscompile Ant task, I found the following pages invaluable:
    https://jax-rpc.dev.java.net/whitepaper/1.1/index-part1.html

  • Java.io.IOException: unable to find the type mapping resource file

    Hi,
    I am using weblogic7.0 to deploy my applications. I wrote a web service and
    was able to deploy it sucessfully. I am trying to access the web service through
    a jsp page. I am the error posted below on my server and " error:505 internal
    server error" on the browser. Can any one please help me out with the problem.
    My jsp page just displays the float value i am returing from the session bean
    method.
    Thanks,
    Ramya.
    <Apr 14, 2003 4:32:51 PM PDT> <Error> <HTTP> <101019> <[ServletContext(id=64204
    55,name=bankwebapp,context-path=/bankwebapp)] Servlet failed with IOException
    java.io.IOException: unable to find the type mapping resource file for:bank.Ban
    kService
    at weblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegi
    stry.java:62)
    at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:72)
    at bank.BankService_Impl.<init>(BankService_Impl.java:23)
    at jsp_servlet.__getbal._jspService(__getbal.java:106)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.ru
    n(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:445)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActi
    on.run(WebAppServletContext.java:5412)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:744)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppS
    ervletContext.java:3086)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestI
    mpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >
    <Apr 14, 2003 4:40:59 PM PDT> <Notice> <Application Poller> <149400> <Activatin
    g application: appsdirbankwebapp_war>
    <Apr 14, 2003 4:40:59 PM PDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbankwebapp_war on myserver - Running>
    <Apr 14, 2003 4:41:01 PM PDT> <Notice> <Application Poller> <149404> <Activate
    application appsdirbankwebapp_war on myserver - Completed>
    The url value from the jsp page ishttp://localhost:7001
    The wsdl value from the jsp page ishttp://localhost:7001/web_services/BankServi
    ce
    <Apr 14, 2003 4:41:06 PM PDT> <Error> <HTTP> <101019> <[ServletContext(id=72463
    20,name=bankwebapp,context-path=/bankwebapp)] Servlet failed with IOException
    java.io.IOException: unable to find the type mapping resource file for:bank.Ban
    kService
    at weblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegi
    stry.java:62)
    at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:72)
    at bank.BankService_Impl.<init>(BankService_Impl.java:23)
    at jsp_servlet.__getbal._jspService(__getbal.java:106)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.ru
    n(ServletStubImpl.java:1058)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:401)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:445)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActi
    on.run(WebAppServletContext.java:5412)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:744)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppS
    ervletContext.java:3086)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestI
    mpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >

    Hi Manoj,
    Thanks a lot for your hepl. I tried as you said and its working now.
    Ramya
    "manoj cheenath" <[email protected]> wrote:
    Make sure that you put the client jar file generated by
    clientgen in the lib directory of the jsp web app.
    It looks like the runtime is unable to load
    <service>.xml type mapping file. This xml file
    should be in the classpath (web-inf/lib or
    web-inf/classes).
    -manoj
    "Ramya" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am using weblogic7.0 to deploy my applications. I wrote a web serviceand
    was able to deploy it sucessfully. I am trying to access the web servicethrough
    a jsp page. I am the error posted below on my server and " error:505internal
    server error" on the browser. Can any one please help me out with theproblem.
    My jsp page just displays the float value i am returing from the sessionbean
    method.
    Thanks,
    Ramya.
    <Apr 14, 2003 4:32:51 PM PDT> <Error> <HTTP> <101019><[ServletContext(id=64204
    55,name=bankwebapp,context-path=/bankwebapp)] Servlet failed withIOException
    java.io.IOException: unable to find the type mapping resource filefor:bank.Ban
    kService
    atweblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegi
    stry.java:62)
    atweblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:72)
    at bank.BankService_Impl.<init>(BankService_Impl.java:23)
    at jsp_servlet.__getbal._jspService(__getbal.java:106)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.ru
    n(ServletStubImpl.java:1058)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:401)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:445)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:306)
    atweblogic.servlet.internal.WebAppServletContext$ServletInvocationActi
    on.run(WebAppServletContext.java:5412)
    atweblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:744)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppS
    ervletContext.java:3086)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestI
    mpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >
    <Apr 14, 2003 4:40:59 PM PDT> <Notice> <Application Poller> <149400><Activatin
    g application: appsdirbankwebapp_war>
    <Apr 14, 2003 4:40:59 PM PDT> <Notice> <Application Poller> <149404><Activate
    application appsdirbankwebapp_war on myserver - Running>
    <Apr 14, 2003 4:41:01 PM PDT> <Notice> <Application Poller> <149404><Activate
    application appsdirbankwebapp_war on myserver - Completed>
    The url value from the jsp page ishttp://localhost:7001
    The wsdl value from the jsp page
    ishttp://localhost:7001/web_services/BankServi
    ce
    <Apr 14, 2003 4:41:06 PM PDT> <Error> <HTTP> <101019><[ServletContext(id=72463
    20,name=bankwebapp,context-path=/bankwebapp)] Servlet failed withIOException
    java.io.IOException: unable to find the type mapping resource filefor:bank.Ban
    kService
    atweblogic.webservice.core.encoding.DefaultRegistry.<init>(DefaultRegi
    stry.java:62)
    atweblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:72)
    at bank.BankService_Impl.<init>(BankService_Impl.java:23)
    at jsp_servlet.__getbal._jspService(__getbal.java:106)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.ru
    n(ServletStubImpl.java:1058)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:401)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:445)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubI
    mpl.java:306)
    atweblogic.servlet.internal.WebAppServletContext$ServletInvocationActi
    on.run(WebAppServletContext.java:5412)
    atweblogic.security.service.SecurityServiceManager.runAs(SecurityServi
    ceManager.java:744)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppS
    ervletContext.java:3086)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestI
    mpl.java:2544)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
    >

  • How to combine multiple webservices into one WSDL file

    Gurus,
    I have 4 four webservices(ws1,ws2,ws3 & ws4) defined in XI. Normally in XI when we define webservice ,WSDL file will be generated for each interface. Now I have 4 related interfaces, so 4 WSDL files will generated. Suppose if I have 100 webservices then 100 WSDL files need to be generated & need to send to other party to consume our services, which is very tedious task & to track also. So is it possible to combine related webservices into one WSDL file? Your inputs will be highly appreciated.
    Regards,
    Santhosh

    Hi,
             Instead of trying to combine the interfaces, you can try to define your interface mapping with 4 sender interfaces with in one interface mapping . I think this may give you the result you are expecting.
                      If you want entire content to be in one interface , then, define single interface which can accomadate, all message ocntent of all 4 interfaces.Means your sender message to contain the 4 datatypes internally.
    Regards,
    Reyaz

  • Xsl schema import from within a wsdl file

    I have a namespace conflict issue validating a bpel process.
    The message error is as follow:
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
    // Here the BPEL file (SMSMulticast2.bpel)
    <pre>
    <!-- SMSMulticast2 BPEL Process [Generated by the Oracle BPEL Designer] -->
    <process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
         <!-- ================================================================= -->
         <!-- PARTNERLINKS -->
         <!-- List of services participating in this BPEL process -->
         <!-- ================================================================= -->
         <partnerLinks>
              <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
              <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
              <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
              <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
         </partnerLinks>
         <!-- ================================================================= -->
         <!-- VARIABLES -->
         <!-- List of messages and XML documents used within this BPEL process -->
         <!-- ================================================================= -->
         <variables>
              <!-- Reference to the message passed as input during initiation -->
              <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
              <!-- Reference to the message that will be sent back to the
    requester during callback
    -->
              <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
              <variable name="count" type="xsd:integer"/>
              <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
              <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
              <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
              <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
         </variables>
         <!-- ================================================================= -->
         <!-- ORCHESTRATION LOGIC -->
         <!-- Set of activities coordinating the flow of messages across the -->
         <!-- services integrated within this business process -->
         <!-- ================================================================= -->
         <sequence name="main">
              <!-- Receive input from requestor.
    Note: This maps to operation defined in SMSMulticast2.wsdl
    -->
              <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
              <!-- Asynchronous callback to the requester.
    Note: the callback location and correlation id is transparently handled
    using WS-addressing.
    -->
              <assign name="setProperties">
                   <copy>
                        <from expression="5"></from>
                        <to variable="count"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
                   </copy>
              </assign>
              <while name="foreach" condition="bpws:getVariableData('count') &gt; 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                        <assign name="decrease"><copy>
                                  <from expression="bpws:getVariableData('count') - 1"></from>
                                  <to variable="count"/>
                             </copy>
                        </assign>
                   </sequence>
              </while>
              <!--invoke name="callbackClient" partnerLink="client" portType="tns:SMSMulticast2Callback" operation="onResult" inputVariable="output"/-->
              <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
         </sequence>
    </process>
    // Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
         name="SMSSenderEnablerSEI"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
         <xsd:schema
              elementFormDefault="qualified"
              targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
              xmlns="http://www.w3.org/2001/XMLSchema"
              xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
              <xsd:complexType name="InvocationContext">
              <xsd:sequence>
              <xsd:element
              maxOccurs="unbounded"
              name="properties"
              nillable="true"
              type="xsd:string"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:complexType name="EnablerException">
              <xsd:sequence>
              <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
              <xsd:element name="errorCode" type="xsd:int"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
              </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
    <xsd:element name="sendSMS">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotification">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element
    name="sendSMSWithNotificationToAliasReturn"
    nillable="true"
    type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
                   <xsd:complexType name="SMSMessageETO">
    <xsd:sequence>
    <xsd:element name="content" nillable="true" type="xsd:string"/>
    <xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="priority" nillable="true" type="xsd:string"/>
    <xsd:element name="recipient" nillable="true" type="xsd:string"/>
    <xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
    <xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
    <xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
    <xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <xsd:complexType name="SMSException">
    <xsd:sequence>
    <xsd:element name="errorCode" type="xsd:int"/>
    <xsd:element name="message" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="sendSMSRequest">
    <wsdl:part element="impl:sendSMS" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasResponse">
    <wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="EnablerException">
    <wsdl:part element="tns2:EnablerException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasRequest">
    <wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasRequest">
    <wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasResponse">
    <wsdl:part
    element="impl:sendSMSWithNotificationToAliasResponse"
    name="parameters"/>
    </wsdl:message>
    <wsdl:message name="SMSException">
    <wsdl:part element="tns4:SMSException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationResponse">
    <wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationRequest">
    <wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSResponse">
    <wsdl:part element="impl:sendSMSResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="SMSSenderEnablerRemote">
    <wsdl:operation name="sendSMS">
    <wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
    <wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdl:input
    message="impl:sendSMSWithNotificationRequest"
    name="sendSMSWithNotificationRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationResponse"
    name="sendSMSWithNotificationResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSToAliasResponse"
    name="sendSMSToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdl:input
    message="impl:sendSMSWithNotificationToAliasRequest"
    name="sendSMSWithNotificationToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationToAliasResponse"
    name="sendSMSWithNotificationToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding
    name="SMSSenderEnablerRemoteSoapBinding"
    type="impl:SMSSenderEnablerRemote">
    <wsdlsoap:binding
    style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendSMS">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="SMSSenderEnablerRemoteService">
    <wsdl:port
    binding="impl:SMSSenderEnablerRemoteSoapBinding"
    name="SMSSenderEnablerRemote">
    <wsdlsoap:address
    location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
    </wsdl:port>
    </wsdl:service>
    <plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
    <plnk:role name="SMSSenderEnablerRemoteProvider">
    <plnk:portType name="impl:SMSSenderEnablerRemote"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </wsdl:definitions>
    Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
    Many Thanks
    Guillaume

    You need to use the XSLT before you do assignment to achieve this, to
    change the message to the correct namespace.
    Please refer to sample at
    "orabpel\samples\tutorials\114.XSLTTransformations" which talks about
    how to use XSLT transformation.
    And please refer to
    "orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
    especially "InvToPo.xslt" which talks about doing transformations
    between 2 structures pointing to different namespaces.

  • Element tag in the WSDL file.

    I have the following interface for the webservice:
    public interface DocumentProvider extends Remote {
    public void deleteDocument(String documentId) throws
    RemoteException;
    I use the wscompile command to generate the wsdl file and it creates a complex type like this:
    <complexType name="deleteDocument">
    <sequence>
    <element name="String_1" type="string" nillable="true"/>
    </sequence>
    </complextType>
    Is there an option in the wscompile command to change "String_1" to "Document" as it is called in the interface.
    I have run out of idea, pls. help if you know how.
    TIA

    I suggest, if possible, that you switch from JAX-RPC to JAX-WS. JAX-WS is the latest APIs for doing Web Services. JAX-RPC is no longer actively developed. The JAX-WS RI is an open source project on java.net (http://jax-ws.dev.java.net) that is widely used, actively developed, much faster than JAX-RPC. With JAX-WS you have much more control of the mapping Java <-> WSDL. For example, your interface below could be written like the following to achieve what you want.
    @WebService
    public class DocumentProvider {
    public void deleteDocument(@WebParam(name="Document")String documentId) { ... }
    Notice that an interface is no longer needed, you can use a POJO directly as long as you annotate it with @WebService. Also, you no longer need to extend Remote or throw RemoteExceptions. Check it out, I think you will really like it.

  • Workshop 10.0.1 - Generating service control from a WSDL file

    Hi!
    I've been familiarising myself with Workshop (version 10.0.1).
    There is a feature that allows the generation of a web service control by right-clicking a WSDL file (Web Services > Generate Service Control).
    This process creates a jar file containing the WSDL's complex type.
    My only problem with this is that the jar uses the namespaces as package names (for example: www.openuri.org will be converted into an org.openuri package).
    I've been searching for a way to customize the package names, but I've been unable to find it. We previously used Axis to generate a web service client, and we ran an Ant task that could map namespaces to packages.
    Would there be a way to achieve this in Workshop?
    Thank you!

    Hi
    This is a known issue and a limitation. Service controls doesn't honor xsdconfig files when generated from wsdl file.
    We have an enhancement request CR307698 pending to address this issue. It looks like it's a big change in code to get this working so it is being looked at in the next release.
    Also, you can call BEA support / create a case in future and request status on this CR anytime.
    Vimala-

  • Import WSDL file along with XSD

    Hi,
    I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
    If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
    How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
    Could you please help me out…?

    first i will tell how my wsdl file is defined
    <xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
    and in my xsd file for xx:AuthInfo
    <xs:complexType name="AuthInfo">
              <xs:sequence>
                   <xs:element name="acctName" type="tns:CustName">
                        <xs:annotation>
                             <xs:documentation xml:lang="en">
                             account name.
                        </xs:documentation>
                        </xs:annotation>
                   </xs:element>
                   <xs:element name="password" type="tns:AcctPswd">
                        <xs:annotation>
                             <xs:documentation xml:lang="en">
                            Specify the password                    </xs:documentation>
                        </xs:annotation>
                   </xs:element>
              </xs:sequence>
         </xs:complexType>
    when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
    but "AuthInfo" has two inputs.
    this is how my Target Message Look like
    Tree          Occurences          Type
    authInfo     1..1                      xx:AuthInfo
    i hope i have cleared u..

  • How to assosciate webservice to a WSDL file

    Hi
    I tried developing webservice(EJB as RPC) in weblogic server and installed and its working fine if i call it from client.
    I am using java2WSDL(axis) tool to create a WSDL file and WSDL2Java to create stubs for client to call.I am struck in linking webservice to use the wsdl file which i have created.
    I manually tried to add my WSDL file to the WAR file of my application and also Updated the web.xml file of the Web application adding a mime-mapping.
    I am able to access the WSDL file in browser as http://bt885094:7001/webservice/user.wsdl
    But my client tries to access the service "http://bt885094:7001/webservice/C2PUserService" which has an associated WSDL file defined as http://bt885094:7001/webservice/C2PUserService?WSDL which needs to be checking for http://bt885094:7001/webservice/user.wsdl
    Could anyone tell me how to assosciate webservice to a WSDL file.
    thanks in advance

    Thank you everyone for your help. As a complete newbie I found this nice walkthrough tutorial in onjava(i dont mean to spam).
    1. View: Take a peek at the existing Fibonacci code.
    2. Java2WSDL: Generate the WSDL file for the given Fibonacci interface.
    3. WSDL2Java: Generate the server side wrapper code, and stubs for easy client access.
    4. FibonacciSoapBindingImpl: Fill in wrapper to call the existing Fibonacci code.
    5. Deploy: Deploy the service to Apache Axis.
    6. Client: Write a client that uses the generated stubs, to easily access the Web service.
    Given the webservice endpoint and the method name, I think I can now consume the web service using steps 3,4, and 6.

  • All I want for my birthday is my jaxrpc-mapping.xml file.........;-)

    I am using JWSDP 2.0 with JDK 1.5. I have developed an ant script for building my web service files. When the script runs, the command line arguments are passed to the wscompile:
    wscompile -d C:\WorkSpaceForMyEclipse\WebService\WebContent\WEB-INF\classes "-features:rpcliteral, wsi" -g -import -keep -nd C:\WorkSpaceForMyEclipse\WebService\descriptors -s C:\WorkSpaceForMyEclipse\WebService\JavaSource -verbose -Xprintstacktrace -Xserializable C:\WorkSpaceForMyEclipse\WebService\WebContent\WEB-INF\wsdl\webservice-config.xml -classpath  <all the jar files from jwsdp project> <project jars>This all works well and good.
    My problem is I am not seeing a jaxrpc-mapping.xml file being created.
    When I add the mapping=${path}/jaxrpc-mapping.xml to the ant task, the builds break saying -mapping is not an option for wscompile....
    Am I doing something wrong? Can some guide me in the right direction for creating the mapping file? When I try axis, the mapping file is created, but it is not populated with any mappings. All I want for Christ is my jaxrpc-mapping.xml file. :-)
    Thanks in advance for reading my post. Any suggestions would be greatly appreciated.
    Russ

    If you are using rpc/literal and jdk 1.5, you would be better off using JAX-WS which does not require a mapping file. JAX-WS is the next generation Web services API that replaces JAX-RPC. Check out http://jax-ws.dev.java.net.

  • Issues using WSDL file

    Hi,
    I have the following issue:
    created a Web Service
    Got the WSDL file
    Created a new data connection in the Adobe form
    Pulled the interface elements from the data view and designed the form
    Now when I input data to the form the data is mapped to web service interface and its passed to the RFC function module
    *But when I have a table I add rows to the table dynamically using addInstance method*
    Now when I submit back the data to the webservice only the last record of the table is passed to the web service can u guide me hw to get all the records of the table passed back to the web service
    Thank & Regards
    Nancy

    Hi Nancy,
    You can check these threads:
    Re: dynamic table data not transfered to context WD4ABAP
    Tables
    I have not worked on WSDL, but there should be some way to call method written in WD Java or ABAP. You have to write code of creating instance of the Table in that method.
    We are still working on it, we are using WD java and facing same issue. Will keep you updated if i solved this problem.
    With Regards,
    Amit

  • To Import XSD file along with WSDL file in ED

    Dear All,
    I am doing a scenario web service1 —XI—RFC—web service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.
    My client (web service2) has given me the web service (WSDL) file along with XSD file.
    In the wsdl file there are number of elements and complex types.
    <xs:element name="GetCustomer">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="authentication" type="xx:AuthInfo"/>
                   <xs:element name="CompanyName" type=" xx:AuthInfo "/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.
    My questions are
    1)     Do I have to import the XSD file in ED or not.
    2)     How do I map this XSD
    3)     As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    4)     Can some one help with any docs please..
    Thanks in advance

    Hi,
    >>Do I have to import the XSD file in ED or not
    If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.
    >>How do I map this XSD
    XSD are same as Message Types. So create a MM and choose your XSD.
    >>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.
    Yes you have to because you are taking the responce from RFC and going to give it to WS2.
    BPM steps:
    1) receive (open sync bridge)
    2) transformation 1
    3) send (snyc)
    4)transformation 2
    3) send (close sync bridge)
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    Regards
    Suraj

  • Java2WSDL hooks to modify generated WSDL file

    I need to programmatically modify the contents of the WSDL file generated by the Java2WSDL command.
    How is this done, or is it possible?
    The class that I�m using to generates the WSDL from works fine, although a portion of it is missing due to the fact that the class uses meta-data to construct/create this section. (which is what I would have expected anyway).
    That�s why I would like to insert the missing piece during the construction of the WSDL.
    Basically Java2WSDL hooks

    I guess the original name in PL/SQL looks like p_ojr, p_ritid, etc.. If you are using 10.1.3 assembler (wsa.jar), I can give you a recipe on how to customize the name mapping. It would help if you can post the PL/SQL declaration part. I can less sure about wheter JDeveloper allows such customization.

Maybe you are looking for