Web Service as Web Dynpro tableView Model

Hi people!
I´ve developed a WebService with a findAllClients method which brings out all the rows from a MaxDB table. Everything works fine when I test it from de WebServices perspective, but when I create a model for my Web Dynpro tableView importing the mentioned WS, I get the following error message:
The Java type of the cmp-field that is stored in column ID, table DB_CLIENTES does not fit to the JDBC type INTEGER of the column. The expected JDBC type is VARCHAR.
I´ve set the built-in type of the column ID in my Java Dictionary project to integer. The corresponding CMP-Field in the entity EJB is java.lang.Integer. I´ve deleted the column from the tableView.
What´s wrong? Any idea please? Where could I find some documentation about this mapping requirements topic?
Thanks very much in advance.

Is this the only way?
Anyways, thanks a lot. I haven't been working with ODI yet, I just have to find out, if it is possible to use it for our project. So I just read through the user's guide...

Similar Messages

  • How to addRecord in Web Dynpro to Model node (Entity Service ref)

    Hi,
    1) I create Entity Service in CAF and try to write web dynpro Table UI for it.
    2) is it possible with using Model Node? or I MUST use Value Node - Table must have possibilities for Add, Edit and Delete records.
    Now I can edit, and delete records, but I can't add records with AddRecord method
    Code below
      public void NewTS( )
         //@@begin NewTS()
       IServiceFacade serviceFacade;
    // Add new Model object TS
       ATS ts = TSServiceProxy.create();
       ts.setDate( new Date(System.currentTimeMillis()));
       ts.getAspect().sendChanges();
       serviceFacade = CAFServiceFactory.getServiceFacade(tsDefinition.class);
    // try to addRecord to Controller context     
       IWDNodeElement n = wdContext.nodeTS().createElement(ts);
       wdContext.nodeTS().addElement(n);
    The error is: com.sap.caf.rt.exception.CAFBaseRuntimeException:
    Aspect row is invalid for aspect:   <Aspect name="TS" >
    Thx for any help

    Hi Nikolai,
    implement it in the following way:
    wdInit()
         IAspect originalAspect = TSServiceProxy.FindByName(employee) ;
         wdContext.nodeTS().bind(originalAspect)
         //just create new attribute this java native type IAspect
         wdContext.currentContextElement().setOriginalAspect() ;
    public void NewTS( )
    //@@begin NewTS()
         IAspect originalAspect = wdContext.currentContextElement().getOriginalAspect() ;
            IAspectRow newTS = originalAspect.createAspectRow() ;
            newTS.setAttributeValue("date", new Date(System.currentTimeMillis())) ;
    or
    public void NewTS( )
         IAspect originalAspect = wdContext.currentContextElement().getOriginalAspect() ;
            IAspectRow newTS = originalAspect.createAspectRow() ;
         ITSElement tsElem = wdContext.nodeTS().getTSElementAt(originalAspect.indexOf(newTS)) ;
            tsElem.setAttributeValue("date", new Date(System.currentTimeMillis())) ;
    Best regards,
    Aliaksei

  • Problem with Complex Web Dynpro Webservice Model

    Hi all,
    in my Web Dynpro application I am using a Webservice which seems to be too complex for the Web Dynpro Model. I think I am getting the same kind of problems like:
    HELP for WebDynpro web service model with complex structure
    But I dont have a complex structure in my input parameters (like in this thread), <b>I have a complex structure in my output.</b>
    This is the structure of my WSDL. I have a customer (KUNDE) which has an array of contracts (Vertrag).
    <wsdl:types>
      <schema targetNamespace="urn:Rentenkonto" xmlns="http://www.w3.org/2001/XMLSchema">
       <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
       <complexType name="Vertrag">
        <sequence>
         <element name="aufschubfrist" type="xsd:int"/>
         <element name="brutto" type="xsd:double"/>
         <element name="eintrittsalter" type="xsd:int"/>
         <element name="endalter" type="xsd:int"/>
         <element name="laufzeit" type="xsd:int"/>
         <element name="renteKapital" type="xsd:double"/>
         <element name="rentenbeginn" nillable="true" type="xsd:dateTime"/>
         <element name="rentenbeginnAlter" type="xsd:int"/>
         <element name="versichererName" nillable="true" type="xsd:string"/>
         <element name="vertragsablauf" nillable="true" type="xsd:dateTime"/>
         <element name="vertragsartTx" nillable="true" type="xsd:string"/>
         <element name="vertragsbeginn" nillable="true" type="xsd:dateTime"/>
         <element name="vertragsnummer" nillable="true" type="xsd:string"/>
         <element name="zahlungsweise" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <complexType name="ArrayOfVertrag">
        <complexContent>
         <restriction base="soapenc:Array">
          <attribute ref="soapenc:arrayType" wsdl:arrayType="impl:Vertrag[]"/>
         </restriction>
        </complexContent>
       </complexType>
       <complexType name="Kunde">
        <sequence>
         <element name="geburtsdatum" nillable="true" type="xsd:dateTime"/>
         <element name="kundenkennzeichen" nillable="true" type="xsd:string"/>
         <element name="pkNummer" nillable="true" type="xsd:string"/>
         <element name="vertraegeDcKapital" nillable="true" type="impl:ArrayOfVertrag"/>
         <element name="vertraegeDcRente" nillable="true" type="impl:ArrayOfVertrag"/>
         <element name="vertraegeDv" nillable="true" type="impl:ArrayOfVertrag"/>
         <element name="vertraegePk" nillable="true" type="impl:ArrayOfVertrag"/>
         <element name="vertraegeRdv" nillable="true" type="impl:ArrayOfVertrag"/>
        </sequence>
       </complexType>
      </schema>
    </wsdl:types>
    When I execute the Webservice basically I get an empty response. I think this is because the WSModel isnt fully mapped to the WS proxy. This should be done via coding.
    Can someone give me some hints on this?
    Kind regards
    Christoph

    Hi Christoph,
    First test the webservice itself. Maybe it is required to give some input parameter in the request and then get some output parameters in the Response. But therefore you should test the webservice yourself and take a look.
    Give more detail about ur case.
    Greetings, Sandhya

  • Web dynpro rfc  model reference

    Is there a way to change the  jCOclient reference
    of  rfc model after creating the model for example from WD_RFC_MODELDATA_DEST to WD_R3_RFC_MODELDATA_DEST

    Yes Natti.
    You can change the reference to the model by changing the Application /Message server settings of the
    MODELDATADEST and METADATADEST.
    Open the cotent administrator and click the "edit" button of the destination that you want to change. Then change the Application / Message server setting from the client1 (current client) to say client 2 (the required client).
    Please reward appropriate points.
    Bala

  • Display data in Web DynPro table from database via EJB

    I have a JavaBeans model which has a method populateDataToTable()to retrieve data from database via Session bean (calling entity bean, returning ArrayList of data) and the data needed to be display in the Web DynPro table.
    User Interface (Web DynPro) <-> JavaBeans Model <-> Busineess Logic (session bean) <-> Persistence (Entity Bean)<-> DB table.
    The context bindiing and table part is ok. How do i load the data to the table ? what the coding to put in wdDoInit() ?
    Any help would be appreciated.

    in wdinit(),
    Collection col = new ArrayList();
    try{                    
      MyCommandBean bean = new MyCommandBean();
      col = bean.getDataFromDbViaEJB();
      wdContext.nodeMyCommandBean().bind(col);
    } catch (Exception ex) {
       ex.printStackTrace(ex); 
    in your JavaBean model class, MyCommandBean getDatafromDbViaEJB() method:
    Collection col = new ArrayList();
    Collection newcol = new ArrayList();
    //include your own context initialization etc...
    col = local.getDataViaSessionBean(param);
    // if your returned result also a bean class, reassigned it to current MyCommandBean
    for (Iterator iterator = col.iterator(); iterator.hasNext();) {
        MyOtherBean otherBean=(MyOtherBean)iterator.next();
        MyCommmandBean bean = new MyCommandBean();
        bean.attribute1 = outBean.getAttirbute1();
        // get other attibutes
        newcol.add(bean);
    return newcol;

  • URGENT: Illegal Argument Exception for  RAW data type in Web Dynpro

    I am getting this error in the following scenario.
    I want to save the text fields from an interactive form to SAP through RFC enabled function module. The type in the model and controller is byte[]. I have converted the string attribute from view to save to the model. But the model dictionary in Web Dynpro project (model) has this type as Binary (meta data model through EFC). The type in SAP is RAW. I am going nuts since a week to solve this.
    IS this a bug? I am using NW04s - SP12. and NWDS 7.0.9
    Exception Details:
    The initial exception that caused the request to fail, was:
    java.lang.IllegalArgumentException
    at com.sap.dictionary.runtime.DdTypeBinary.format(DdTypeBinary.java:60)
    at com.sap.dictionary.runtime.DdTypeBinary.toString(DdTypeBinary.java:64)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.doFormat(DataContainer.java:1405)
    at com.sap.tc.webdynpro.clientserver.data.DataContainer.getAndFormat(DataContainer.java:1098)
    at com.sap.tc.webdynpro.clientimpl.xdp.renderer.data.XfdRenderer.renderAttributes(XfdRenderer.java:370)
    ... 41 more

    Issue with the RAW data types is resolved now. I have changed the data type of the field into String in the dictionary (web dynpro).. I have changed the corresponding getters and setter functions from byte[] to string. And everything working fine now. I got the Illegal Argument exception initially because I was trying to display the binary data type fields on the adobe form or view which I am not supposed to do.
    Also it is better to create separate view attributes in the context to get the values rather than mapping the model attributes directly in the form or view.
    Thank you one and all.
    Regards
    Vasu

  • Best place to begin design of old HTML pages with Web Dynpro

    I am new to web dynpro (and the Netweaver environment).  I just took the EP150 course so I have an idea of how to create pages with both Visual Composer (although I doubt I'll use that much) and in java projects in NWDS. 
    My first application is to be an online purchase requisition application to replace one written in Lotus Domino (this will NOT be integrated with R/3- we will have a seperate DB for these documents outside of R/3).  I have taken the HTML main page from that application and coded it as a JSP but I am getting the impression that the overall design/coding may be simpler if I do the project as a web dynpro.  I want to find some sort of a primer that describes the various controls that go on the web dynpro view in order to figure out how I can take my HTML design and bring it into a web dynpro project.  Can anyone point me to a resource that does this?  I've checked the help and SDN and not found anything that is too helpful yet.
    Can anyone tell me if it would be worthwhile for me to attend the JA310 Web Dynpro course?  I have done a couple of the tutorials posted on SDN for web dynpro but haven't done much else with it as of yet.
    Thanks.
    Dana

    I don't know such a migration guide, but here are some general remarks:
    The Web Dynpro programming model does not use tag-libs, markup, scripting etc. as you might have used in JSP or BSP applications.
    Instead, you create your view layout using the NWDS view designer (or the runtime API) and place UI elements like tables, input fields etc. inside containers.
    Containers have layouts (e.g. MatrixLayout, RowLayout, FlowLayout) and UI elements placed inside a container have layout data for setting individual layout constraints. This is similar to programming in non-Web frameworks like Java Foundation Classes (Swing).
    The UI elements get their data from the view controller context by data binding. There is a hierarchy of controllers (view, custom, component) and the corresponding controllers may be mapped, giving an automatic data flow through the controller hierarchy.
    The complete details of markup (e.g. HTML), client-side scripting, CSS etc. is provided by the client-specific framework part and the application is completely shielded from these technical details.
    This has the additional benefit that a Web Dynpro application can be run on completely different clients without change.
    Example: If tomorrow it will be hip to run your business application inside some other UI technology, e.g. Adobe Flex, SAP will provide a new Web Dynpro client and all Web Dynpro applications will run without change inside this  environment. (Replace Adobe Flex by any other relevant framework).
    Compare this to a programming model, that directly uses HTML, Javascript etc. Good luck rewriting several thousand user interfaces!
    So in your concrete use case, look at your UIs from such a perspective and identify the Web Dynpro concepts. This should help in the migration process.
    Armin

  • Create adaptive web service model for a web dynpro project

    I have been trying to create a new new adaptive web service model for a web dynpro project.I am using the URL of the wsdl file to create the model. I have copied the url link of the wsdl from the overview tab of the web services navigator. The web service works fine when tested through the Netweaver Navigator. This web service has also been used successfully through the Visual Composer. But when I try to create a model for this web service URL, when I click the Next button after entering the URL in the model creation wizard  step 4 , I get "Error loading wsdl file. Check error log for details" Given below is the exception recorded in the error log: (Infact, I get this for all wsdl URLs)
    !MESSAGE Jun 6, 2007 9:44:59 AM           com.sap.ide.webdynpro.ui.service.ServicesUI          [Thread[main,5,main]] Error: Internal error
       Plugin name: Web Dynpro Model Editor
       Plugin ID  : com.sap.ide.webdynpro.modeleditor
       Class      : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
       Method     : loadNameSpacesAndModelClasses
       Message    : Cannot load NameSpaces and ModelClasses
    Class Path: C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
    java.home: C:\java\j2sdk1.4.2_09
    proxyHost:
    proxyPort:
    nonProxyHosts:
    Temporary Directory: C:\DOCUME1\E51914\LOCALS1\Temp\
    WSDL URL: http://etcvpcod108:50100/UserService/Config5?wsdl
       Exception  : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://etcvpcod108:50100/UserService/Config5?wsdl and service factory configuration {DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}
    !STACK 0
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://etcvpcod108:50100/UserService/Config5?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:413)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:371)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:341)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:305)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:315)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
         at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
         at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
         at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
         at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
         at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
         at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
         at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
         at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
         at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:149)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:49)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:411)
         ... 53 more

    Hi Srikanth,
    My version was
    Version: 7.0.09
    Build id: 200608262203
    I was able to successfully import the model after I did the following
    1. Re intsall Studion (same version , same build)
    2. Reset the proxy settings to not use Proxy server
    Thanks for looking into it though...
    -Lakshmi

  • Web Dynpro Import Web Service Model - not a valid NCName

    Hi people,
    We are having a problem while importing a WSDL as an Adaptive Web Service Model in Web Dynpro (CE 7.2 SP03).
    The error is the following:
    "Definition of qualified base /schema/element[5]/complexType/sequence/element[4] is not correct. The value of property is not a valid NCName."
    We tried importing the same WSDL in other tools (XML Spy and SOAP UI). With these tools it could be read without errors and were able to successfully call the service.
    The point is, why the import fails in Web Dynpro if the WSDL can be read in other tools ? Can we do something in WD to import the WSDL that is supposed to be "not correct" ?
    Thanks in advance for your comments,
    Daniel

    Hi Pranav,
    I was facing this issue sometime back and i figured out that the ABAP proxy namespace in my case had a '/' in it, because of which the internal name of the service had a '/' character too.
    And this was unacceptable for the endpoint binding name in my case.
    Since it is occuring for you in case of the service name (i figured it out from attribute definations/services@name), check if the proxy name have a special character like '/'.
    Regards,
    Vivek

  • Error when Creating Web Dynpro Model in CAF-Service

    Hi All,
    I reaaly need help. AFter updating to SPS 9, it was necessary to redeploy my Entity Service. That contains to "Create a Web Dynpro Model" in the Service Explorer,
    to get an interface of the Service in my Web Dynpro Application.
    Before I update to SPS 9, the Application works fine.
    But now, when I want to "Create a Web Dynpro Model" in the NWDS I get the following Error-Message (its not a useful Error-Message):
    <i>Error cannot create Web Dynpro Model:
    Creation of  Web Dynpro model failed. Reason: null </i>
    Thanks for helping me
    Steve

    Hi Aliaksei,
    the problem in the thread is the same I got.
    When I use only 7 letters for the operation name, the creation work. When I use more then 7 letters the creation doesnt work.
    But its hard to find a methodname with only 7 letters.
    In SPS 8 I didnt have problems with the length of method names. Why is it so?
    The workspace log:
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.577
    !MESSAGE Oct 10, 2006 3:12:45 PM         com.sap.ip.mmr.foundation.AssociationsOfObject        [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:45.592
    !MESSAGE Oct 10, 2006 3:12:45 PM         com.sap.ip.mmr.foundation.AssociationsOfObject        [Thread[main,5,main]] Error: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 35, 3c, 3f(:main:, row:1, col:3)
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
    !MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO:
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
    !MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.core.service.FileSystemService.comp... [Thread[main,5,main]] Error: absolute path too long (253) for MDO:
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
    !MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)
    !ENTRY com.tssap.util 4 0 Okt 10, 2006 15:12:48.705
    !MESSAGE Oct 10, 2006 3:12:48 PM  com.sap.ide.metamodel.webdynpro.implementation.ModelProxy... [Thread[main,5,main]] Error: could not get a valid path for ModelClass "cas.conti.com.sap.cd.database.services.cd_database.changedescriptiontableservice.QChangeDescriptionTableServiceFindByTitle" (path too long?)
    Thanks
    Steve

  • Creating web dynpro model from XMII web service

    Hi All,
    need some help, after creating model in Web Dynpro from XMII WSDL file everything is fine but when i execute the service. I'm getting the following error:
    <b><i>Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML is not valid. Element [http://www.sap.com/xMII]<OutTxRecordSetXML> is required in <OutTxExecutionMsg> but can not be found.</i></b>
    Please help!
    Regards,
    Raj

    Hi Sam,
    i am providing login details, if i dont i see the authorization error message. I'm using runner to access the BLS transaction now to get the xml data. I'm wondering if there's something wrong on the XMII side, some config?
    Regards,
    Raj

  • Problem Importing Web Service as model in Web Dynpro

    Hi experts,
    I want to import a new adaptive web service model into web dynpro. As when I open Data Model to create the model, it prompt me login to DTR as the feature required logon to DTR.  After I logon to DTR, there is nothing happen.
    Any idea what is done wrong ?
    help help.
    thanks

    Hi,
    Just found out that there is error and it is as followed:
    com.sap.cms.util.exception.client.CMSClientVersionConflictException: Version conflict: to call method "readSystemMessages" the minimum server version is "Release6.40 SP16 Patch level 00" but the used server has only version "Release 6.40 SP15 Patch level 00"
    at com.sap.cms.client.organizerAPI.CMSTransportOrganizerAPI.versionCheck(CMSTransportOrganizerAPI.java:1232)
    at com.sap.cms.client.organizerAPI.CMSTransportOrganizerAPI.readSystemMessages(CMSTransportOrganizerAPI.java:1164)
    at com.sap.cms.client.ideAPI.CmsConfiguration.readSystemMessagesMap(CmsConfiguration.java:445)
    at com.sap.ide.eclipse.component.devconf.DevConfManager.getSystemMessages(DevConfManager.java:809)
    at com.sap.ide.eclipse.component.provider.listener.DevConfLoginListener.showSystemMessages(DevConfLoginListener.java:97)
    at com.sap.ide.eclipse.component.provider.listener.DevConfLoginListener.loginPerformed(DevConfLoginListener.java:91)
    at com.sap.ide.login.UserValidator$1.run(UserValidator.java:161)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:98)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1999)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1733)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:136)
    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:261)
    at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:357)
    at com.sap.ide.login.UserValidator.getData(UserValidator.java:411)
    at com.sap.ide.login.UserValidator.getDefaultServerData(UserValidator.java:131)
    at com.sap.ide.login.UserValidator.getDefaultServerData(UserValidator.java:116)
    at com.sap.ide.metamodel.core.plugin.DtrHelper.logon(DtrHelper.java:401)
    at com.sap.ide.metamodel.core.repository.RepositoryServices.showReadonlyRepositoryObjectsAndCheckout(RepositoryServices.java:345)
    at com.sap.ide.metamodel.core.repository.RepositoryServices.checkWriteability(RepositoryServices.java:279)
    at com.sap.ide.webdynpro.service.controllereditor.ServiceWithUI.createModelUsages(ServiceWithUI.java:727)
    at com.sap.ide.webdynpro.tsmodel.application.provider.ModelUsageNodeProvider.createUniqueName(ModelUsageNodeProvider.java:63)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
    at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
    at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
    at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
    at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
    at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
    Help Help

  • About import web service model in web dynpro dc

    Hi all,when i import a web service model in web dynpro dc, an error occurs.
    java.lang.Exception: com.sap.tc.webdynpro.model.webservice.modeltype.core.implementation.AWSModelImporter$FatalImportException: Model setting definition 'considerNillable' not defined for Adaptive Web Service model type
         at com.sap.tc.webdynpro.model.webservice.modeltype.service.AWSModelImporterService.createModel(AWSModelImporterService.java:67)
         at com.sap.tc.webdynpro.model.webservice.modeltype.ui.wizard.AWSModelCreationWizard.createModel(AWSModelCreationWizard.java:238)
         at com.sap.ide.cmi.core.model.importer.CMIWizard$3.run(CMIWizard.java:246)
         at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
    Caused by: com.sap.tc.webdynpro.model.webservice.modeltype.core.implementation.AWSModelImporter$FatalImportException: Model setting definition 'considerNillable' not defined for Adaptive Web Service model type
         at com.sap.tc.webdynpro.model.webservice.modeltype.core.implementation.AWSModelImporter.setModelSetting(AWSModelImporter.java:174)
         at com.sap.tc.webdynpro.model.webservice.modeltype.core.implementation.AWSModelImporter.importModel(AWSModelImporter.java:632)
         at com.sap.tc.webdynpro.model.webservice.modeltype.core.implementation.AWSModelImporter.doImport(AWSModelImporter.java:351)
         at com.sap.tc.webdynpro.model.webservice.modeltype.service.AWSModelImporterService.createModel(AWSModelImporterService.java:65)
         ... 3 more
    please tell me

    1.Create New Model.
    2.Select the type of model as Adaptive web service model and click next.
    3.Give Model name and Model Package .Select Available WSDL sources.
       a.If u get wsdl from local system,select Remote Location/File system.
       b.If u get wsdl from Sap location ,u have to configure with esr reposirtry.
    4.Select Remote Location/File System and click next.Get WSDL URL from services repositry and click next.
    5.Click finish.

  • Generate web service model in web dynpro

    Hi,
    I have a web service which I generated a model in web dynpro and working fine.
    But the problem is that when I update my web service(change in method prototype, number of parameters, data type changes) I need to regenerate the model again and need to map to context elements.
    So, is there any way so that I can update my model instead of regenerating entire model to reflect to new changes in web service.
    Thanks for your time and effort.
    Regards,
    Shiva.

    Hi Shiva,
    Please look at this weblog for reimporting web service model.
    /people/bertram.ganz/blog/2005/10/10/how-to-reimport-web-service-models-in-web-dynpro-for-java
    There is no direct method available for that. But u can do by following this method.
    Regards,
    Bhavik

  • Web Dynpro Model Generation for Application Services

    Hi Experts,
    I'm currently experimenting with the new functionality provided by CE, but there is one thing that I can't seem to figure out. How does the new Web Dynpro model generation work with regards to CAF Application Services? I'm trying to call an application service from a web dynpro application, but it seems as if models are completely different from Netweaver 7.0. What type of model do I need to create? Do I have to expose the application services as web services?
    I've tried creating an EJB model and then binding the model to the context, but I kept receiving null pointer exceptions when doing this and I'm not sure if this is the correct way to do this. Can anybody point me to some good documentation on Web Dynpro/CAF interaction in CE?
    Thank you,
    JP

    Hi JP,
    You are right, the CAF models are completely different in NW CE 7.1 compared to NW 7.0.
    CAF Application Services in CE 7.1 are in fact EJBs. So the EJB model importer is the way to go. You can find <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/dd45e4bc295595e10000000a1553f7/frameset.htm">documentation</a> and some <a href="http://help.sap.com/saphelp_nwce10/helpdata/en/45/f7f744aea471fae10000000a1553f6/frameset.htm">tutorials</a> on help.sap.com. If you still have troubles after you go thru these, please post your concrete issues and I'm sure we'll be able to figure out what's been going wrong.
    HTH!
    -- Vladimir

Maybe you are looking for