Model Execute Exception in a WD Callable Object

Hello,
I've been having some trouble making queries to a database through a Web Dynpro Development Component (GP Interface). I imported a Web Service and the calls are being made through there. I know that the Web Service works just fine as I've tested it through the WS Navigator. The problem occurs when I create the Callable Object and try to test it. The following message shows up:
WDWSModelExecuteException: Exception on execution of web service with WSDL URL 'http://server:50000/LetterStep34WS/letter34?wsdl' with operation 'getLetterById' in interface 'LetterStep34WSVi_Document'
I've tried redeploying the project, re-importing the web service model, and changing the package name where the model is imported but nothing seems to be working. Does anyone have any ideas? It´s becoming a pressing matter.
Thanks,
Luis T.

Felipe,
Check name of component used in Component Usage or in code: com.polar.excel.WDC_ExcelExport.
Seems that you mistyped the name.
Valery Silaev
SaM Solutions
http://www.sam-solutions.net

Similar Messages

  • GP callable object (Visual Composer FLASH)u2013 update input/output parameters

    Dear Sirs,
    I have a callable object which is based on a Visual Composer Flash iview. In this iview I have two input parameters and two output parameters, and these can been seen in the callable object.
    However, if I add another input or output parameter deploy the model  and change and active the callable object the new changes are not picked up.
    Has anyone else encountered the same problem?
    best regards,
    Jørgen

    Hello Nick,
    You gave me the answer I did not want :=), however I think you are right.
    This is not a very good solution by SAP and I think I will open an OSS to get a final answer from SAP on they are going to solve this.
    You can not delete all the callable objects in a process whenever you need a new parameter.
    mvh
    Jørgen

  • Backgroung Callable Object

    I am trying to create a Background CO that calls an EJB. I have the client libraries/classes for the EJB but at runtime I get the following error: 
    java.lang.ClassCastException: com.sap.engine.interfaces.cross.ObjectReferenceImpl incompatible with <myHomeInterface>
    Has anyone seen this or knows how to correct the error?
    Thanks,
    SV
    Message was edited by:
            Sunil Vishnubhotla

    Hi,
    Check your build dependencies of the DC included. Or,
    Code the EJB method in the execute method in the Background Callable Object and include all the references (Used DCs). You can also create the web service callable object(EJB) .
    Correct me if I am wrong.
    hope it helps.
    Avinash.

  • Exception in executing External Service type Callable Object

    Hi
    I was trying to test a callable object of type external service. I have used the bapi BAPI_FLIGHT_GETDETAIL. But while executing I was getting exception like
    java.lang.IndexOutOfBoundsException: Index: 5, Size: 3
    at java.util.ArrayList.add(ArrayList.java:371)at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.addElementSilently(Node.java:1991)at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.addElement(Node.java:2003)at com.sap.tc.webdynpro.progmodel.context.Node.doAddElement(Node.java:676)at com.sap.tc.webdynpro.progmodel.context.Node.addElement(Node.java:644)
    Anybody knows the reason?
    Cheers
    Sudip

    Hii
            I forgot to mention that if the RFC has a structure as output parameter it doesnt get displayed but if the parameter in RFC is string value it works fine.Please Help Urgently
    Regards
    Ishita

  • Unable to use bean model in a Callable Object

    Hello,
      I'm trying to use a bean model in a callable object but at runtime I'm allways getting null pointer exception.
      If I test it in a WebDynpro application everything goes right (I only have to add a sharing reference to my EJB Application). But if I Implement a Callable Object and I try to use a EJB bean model it doesn't works.
    (I have added the sharing reference in the callable object DC)
    I have made somes test and the command bean class never finds the EJB using home interface.
    At the moment I would like to use a bean model instead Web Service model because of testing propouses.
    Please, Do you know If I'm missing something? Do I have to add more reference or use DC?
    Is possible to use bean models in Callable Objects?
    Thanks in advance,
    Regards

    Hi,
    Not sure if it will work.
    Try creating the view object with a single query, and once after creating it, edit the view object, and change the SQL query in the source.
    Something like
      <SQLQuery>
        <![CDATA[select * from emp]]>
      </SQLQuery>to
      <SQLQuery>
        <![CDATA[select * from emp where deptno=10 union all select * from emp where deptno=20]]>
      </SQLQuery>-Arun
    P.S : I am able to create the view object with union declaratively in JDev 11g. Probably you can upgrade to 11g ;) .

  • Model in Background callable object

    Hi Gurus,
    Currently we have an application where a Scheduled background callable object is used , that does some table updation to SAP R/3 backend. Now all the connection parameters are maintained in property files and JCO connection is created through java coding and with JCO API. Is there any possiblity to used Model in Background callable object so that , we could have used our common jco destionations and connections . Please suggest.
    Thanks in Advance.
    Tony Isaac.

    Couldn't find a solution, in this case a new solution was developed which then had nothing to do with the callable object.

  • Implementing a Web Dynpro Java Callable Object in GP using a R/3 Model

    Hi to all,
    my scenario is that I have to Implement a WD Java Callable Object (as descripted in this example https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814) but I want to get datas from an R/3 system with a RFC Model.
    I tried but I have some problems how to use the model itself. Can someone help me, please?
    I'm using NWDS 7.0.
    Thank you very much,
    Antonio

    Hi Antonio,
    Go through this link https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=externalservicesusing+RFC&adv=false&sortby=cm_rnd_rankvalue  and find "Consuming RFC Function Module Using Guided Procedures" Application
    Thanks,
    Nataraju

  • Implementing a Web Dynpro Java Callable Object in GP using a Model

    Hi to all,
    my scenario is that I have to Implement a WD Java Callable Object (as descripted in this example https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814) but I want to get datas from an R/3 system with a RFC Model.
    I tried but I have some problems how to use the model itself. Can someone help me, please?
    Thank you very much,
    Antonio

    Hi,
        I thin k u have imported the RFC Model into the Workspace .
      Declare the usage of model in the component .
    then do model binding between the component controller and the Model Nodes.and finally the model binding with the component Controller and the View .
    in the Doinit method of the component Controller ,
    create the instance of the model and excecute the model.
    and finally invalidate the Response node of the Model.
    For further pleasde verify the link.
    [http://help.sap.com/saphelp_nw04/helpdata/en/d5/1558bfa6aa80499113983e738b1b21/frameset.htm]
    thanks and regards
    Fistae

  • Problem to execute a Callable Object (SAP R/3 transaction)  in UWL

    Hi,
    I have developed a callable object which calls a SAP R/3 transaction. It runs perfectly in design time , when I run it in UWL I am getting the Error “"An error occurred while displaying the callable object, which uses the page builder. Check that the page builder is installed, and the transaction iView is available “.
    Please let me know your thoughts and suggestions.
    Regards
    Wesley Solomon

    Hi Wesley
    According to me, it is because of some missing package that this problem is encountered coz even i have faced this problem w.r.t the UWL and then i imported the required packages and it worked.
    Regards
    Navneet

  • Error while creating a callable object - User Interface

    Hello,
    When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
    Is there any body who allready had somthing like this.
    Greetings
    Kurt

    Hi Raja Akella,
    I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
    I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
    In the visual administrator i get the following  errors.
    <b>Error 1</b>
    Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 2</b>
    Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
         at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
         at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
         at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
         at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
         at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
         at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
         at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
         at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
         at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
         at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
         ... 39 more
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
         at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
         ... 52 more
    Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
         at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         ... 53 more
    <b>error 3</b>
    Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
    Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
    thanks in advance
    Kurt

  • About callable object-send notification

    Hi expertise,
    when i create a callable object-send notification,when i test it,an exception occurs:
    java.lang.NoClassDefFoundError: javax/activation/DataHandler
        at com.sap.caf.eu.gp.model.fnd.mail.MailFactory.createBodyPart(MailFactory.java:468)
        at com.sap.caf.eu.gp.model.fnd.mail.MailFactory.sendMail(MailFactory.java:396)
        at com.sap.caf.eu.gp.callobj.mail.NotificationCO.onExecute(NotificationCO.java:331)
        at com.sap.caf.eu.gp.callobj.bckgd.base.AbstractBackgroundCallableObject.execute(AbstractBackgroundCallableObject.java:102)
        at com.sap.caf.eu.gp.callobj.container.BackgroundCallableObjectsContainer.execute(BackgroundCallableObjectsContainer.java:81)
    why?thanks

    Hi Jorgen,
    This behavior is completely normal. It can seem awkward but what you described is somehow logical.
    Let's say you have three actions, the second one is the email notification. When completing the first action, the second action is triggered. As it is a background callable object, it is put into the queue and wait for processing. As the refresh of the screen is faster than the processing of the callable object, the next action (the third) is not yet active/ready to be processed.
    When the email is sent (i.e. the background callable object executed), a callback takes place and the next activity is triggered. Then, the 3 action is active and can be shown.
    Due to technical restriction of Web Dynpro, it is not possible to refresh the screen when the action is ready to be processed. The user has to refresh it explictly.
    With SP12, the processing of the queue has been improved and it's much more faster than before. The "problem" you noticed shouldn't be there anymore.
    Hope this helps.
    David

  • Error Interactive Form(.xdp) as a callable object

    I am running on EP 7.0 SPS13. We are testing GP by including an Interactive Form (.xdp) as a callable object. The form is just a test form and have only two fields: Name and EmpNo.
    I have testing this form using ObjectDefinition>Instantiate Form.
    when form opens up in new window  the below error is thrown up. Please let me know if I have to do any configuration on server side.
    Execution ended in an unrecognized state
    com.sap.caf.eu.gp.base.exception.EngineException: Execution ended in an unrecognized state
    at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorImpl.executeBackground(CallableObjectExecutorImpl.java:242)
    at com.sap.caf.eu.gp.model.co.execute.impl.CallableObjectExecutorImpl.execute(CallableObjectExecutorImpl.java:294)
    at com.sap.caf.eu.gp.model.co.CallableObjectExecutor.doGet(CallableObjectExecutor.java:256)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    Thanks a Lot
    Madhan

    Hi again,
    To inlcude adobe form as callable object in GP you need to
    create a callable object of type Composite form.In the template of composite form you need to include the adobe form.
    In the adobe form create a button.Specify the control type as Submit.Submit format as- PDF and we need to provide the url.
    I am not sure of what url(might be the process url).Check it out.
    Also refer to these documents.
    http://help.sap.com/saphelp_nw04s/helpdata/en/1c/f967cadb004963817d7c9bfbfe421c/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0769d60a-0801-0010-cfbf-9fcb27c851e8
    Hope this helps you.
    Thanks and regards,
    Sumangala

  • GP Background callable object. Error while making a Callable object

    Hi,
    I have implemented a Background callable object and deployed it to the server.
    When I try to make a Callable object of this from the Design Time tab in GP, i get the following error msg.
    *Class does not correctly implement the required interface*
    The detailed error msg is as follows
    Full Message Text
    Unable to load the required classes. Check all the references to other modules, especially the GP API
    com.sap.caf.eu.gp.base.exception.EngineException: Unable to load the required classes. Check all the references to other modules, especially the GP API
    at com.sap.caf.eu.gp.model.svc.impl.EngineClassloaderImpl.isClassAvailable(EngineClassloaderImpl.java:101)
    at com.sap.caf.eu.gp.ui.co.config.bkgd.COCfgSelect.OnCanLeaveScreen(COCfgSelect.java:293)
    Pls help.
    Tx in advance

    The problem was resolved after retrying many times. Code was checked again and redeployed. Server restarted as well. GP objects deleted and steps repeated. It worked in the end.

  • Web Dynpro Callable Object : use of RFCs

    Hi All,
    I've to create a callable object using Web dynpro.
    In this web dynpro to display a table data populated by calling RFC and we need to select one row of the table and sent it as output parameter.
    My question is how we gonna set the getDescription Method in this case for creating the Callable Object?
    How we define the execute Method in the Interface Controller.
    Where I should bind the Model to Controller (Component Controller / Interface Controller)
    Can someone explain how we gonna use RFC in Web dynpro while calling it as Callable Object.
    Thanks
    Srikant

    Hi,
    You need to have the SCs for local development of Web Dynpro callable object.
    Refer the following documents for more details:
    <a href="/people/andre.truong/blog/2006/06/26/working-with-the-apis-of-caf-guided-procedures-nwdi-or-local-development with the APIs of CAF Guided Procedures: NWDI or Local Development?</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f7be53bb-0b01-0010-1c96-be3cb6799c1b">How to Get NW04s SP7 Guided Procedure APIs for Local Development</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814">Implementing a Web Dynpro Callable Object</a>
    Let me know if this solves your issue.
    Thanks,
    Dipankar

  • Date type attribute in web dynpro callable object

    Hi all,
    I am creating a callable object with date type attribute as input parameter in a web dynpro callable object.
    date type I have used is java.sql.date.
    But when I am exposing that callable object in GP its giving an error:
    Technical Exception:
    Web dynpro Component cannot be created.
    And when i am changing date type as java.util.date then I am not able to asssign that date attribute in my view layout.
    Can anyone plese help me.

    Hi Ritu ,
               u have to convert the util date to sql date in the execute method .
    do it as showm below in Execute method in the component Controller :
    let the Attribute be planEndDate in the Context:
    public void execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext )  {
    java.util.Date planEndDate = null;
    planEndDate = (java.util.Date) inputStructure.getAttributeAsDate(IContextElement.PLAN_ENDDATE);
    java.sql.Date sqlDate = new java.sql.Date(planEndDate.getTime());
                        wdContext.currentContextElement().setPlanEnddate(sqlDate);
    Thanks and Regards

Maybe you are looking for