Callable object context question

HI All.
1)If i make web dynpro as a callable object then - i have 2 types of context - 1 is the web dynpro context as always and one is the calleble object context (GP Context)
What is the difference between the two contexts?
2)What is achieved when i map the webdynpro context attribute's value  to the attribute of GP Context -ie - what purpose does it serve?
3)Whati if i do not set any attributes in the technical description of the GP Context
Please help me in the above things
Points assured for help

Hi,
1) By GP context I think you mean the input/ouput parameter of the GP CO context. These are defined in the getdescription() method of the Web Dynpro callable object which are exposed in GP as Callable object's parameters. In WDP there is no context node available as GP context. This is defined and operated by code using GP API.
2) The GP context of a WDP CO is what available in GP design time from the callable object as input and output parameters. In the WDP application you may not have any physical context as GP context. Because anyway you have to write code to define, read and write the GP context in the getDescription(), execute() and complete() methods. So you may or may not keep a specific context node in WDP for the GP context. You can read any relevant context node of the WDP and populate the GP context by coding. So no question of mapping physically.
3) if you don't set any attributes in the getDescription() method no input or output parameter will be available in GP from that callable object.
Thanks,
Dipankar

Similar Messages

  • Understandng the callable object within GP

    Hi All,
    I have basic question on callable objects in GP.
    I would like to know how the Adobe form content gets persisted with in GP .
    Example : We have 4 steps in a GP process , one requestor and two approvers. Each step is a webDynpro callable object.
    Requestor fills a Adobe form and this request goes through two approvers and then to complete state.
    Consider we have two fields in adobe form. For my understanding , we need to take care of the business logic within the webDynpro callable object which takes care of storing the two field data into a database(Maxdb or SQl).Is that correct ? Or GP will take care of storing the content also ?
    2. Another scenario
      Assume that the application context stored with in GP process
      The system restarted/down after the requestor submits his request. In that case will that request gets lost or GP will take care of storing......???
      Please correct me if my understanding is not correct.
    Regards, Anil
    Edited by: Anilkumar Vippagunta on Jun 18, 2008 1:46 AM

    Hi Sumangala,
    Thanks for your response.
    Lets consider I have 2 webDynpro callable objects..One is for requestor another for approver.
    Requestor filled the adobe form in callableobject1 and submitted the request.For some reason j2ee got restarted or went down.
    When requestor submits his request , GP will send the notification to the approver.So a task will be added to approver inbox.
    So GP will take care of storing the process related information but not the content within Adobe or webDynpro application ...Am I right ??
    I am just trying to analyze the overall behaviour of GP in all aspects.
    Thanks, Anil

  • GP: Info Callable Object working?

    Hi all,
    I have tried to implement an info CO in one of my processes. That Callable Object takes a string as input parameter and launches a search website to find the results. It worked well in the test environment in design time. But wenn I added that CO as Info Callable Object to an action of my process. It's not displayed in the runtime on the navigation bar at all, where it was supposed to be according to the RKT. I also set a category to it without any effect. And I have also tried to add the info CO to the Block and even the process level but neither way worked. Is that a possible bug?
    I'm using GP 7.0 with F37 milestone J2ee
    Another related question:
    I need a kind of summary at each of my process steps. My idea is to implement it as an info callable object. Now as I understood, it's possible to pass parameter values to info Callable Objects at runtime as well. Does such a parameter have to be available in GP-Context already or is it possible to get that parameter value from the displayed webdynpro DC at the same step? The idea is, I would like to have a webdynpro table displayed and have the info callable object show the detail of each table entries when I`m performing the selection. In other words, would it be possible to pass the selected item to the info callable object at runtime? My guess is that it's not possible, as I haven`t finished my Webdynpro step at the time I make the selection, so the parameter value of the selected table item is not yet available in the GP context. Are my considerations correct? 
    Most appreciated.
    Xiaopeng

    Hi Xiaopeng,
    Please make sure that you defined the correct run time view - otherwise the Info CO will not be displayed. You can find some documentation on that here: http://help.sap.com/saphelp_nw04s/helpdata/en/33/198141f906040de10000000a1550b0/frameset.htm and then CAF-GP:Business Expert Guide -> Process Modeling -> Info Callable Objects, there you find at the end of text the link to 'Defining Runtime Views'.
    The parameters for the Info Callable Object must be available already in the GP context so I believe it's too late if they are available at runtime first. However your idea is really clever.
    Regards,
      Jan

  • Object context

    Hi,
    what is context object, and where do we use it?.
    if possible provide with an example.
    Regards
    Ajay.

    Hi,
    1) By GP context I think you mean the input/ouput parameter of the GP CO context. These are defined in the getdescription() method of the Web Dynpro callable object which are exposed in GP as Callable object's parameters. In WDP there is no context node available as GP context. This is defined and operated by code using GP API.
    2) The GP context of a WDP CO is what available in GP design time from the callable object as input and output parameters. In the WDP application you may not have any physical context as GP context. Because anyway you have to write code to define, read and write the GP context in the getDescription(), execute() and complete() methods. So you may or may not keep a specific context node in WDP for the GP context. You can read any relevant context node of the WDP and populate the GP context by coding. So no question of mapping physically.
    3) if you don't set any attributes in the getDescription() method no input or output parameter will be available in GP from that callable object.
    Thanks,
    Dipankar

  • Difference between Callable Object for execution and Display

    Hi,
             I am new to Guided Procedures.When i am creating a callable object under an Action ,i find callable object for execution and callable object for display in the dropdown.What is the difference between the two types of callable objects.
    Thanks,
    Bala

    Hi Bala,
    GP comes with a set of registered callable object types that define which applications you can directly expose as callable objects and enable their handling in the context of GP processes.
    So the different COs can handle your specific application requirements or process flow requirements appropriately at runtime.
    You refer those COs in actions. To make the action functional, you attach at least one callable object to it. In addition to the object that is executed when the action is called, you can attach a callable object that is displayed after the execution. The first one is mandatory. You must attach a callable object for execution. It can be either a callable object with a visible part, such as a Web Dynpro or BSP callable object, or one for background execution.
    Optionally, you can attach a callable object for display. It is required to have a visible part – for example, you cannot select a callable object for background execution.
    At runtime, this object is displayed if the processor wants to open the process step after it has been completed, or if a process contributor has view permissions on the action.
    To make it easier, I will give you an example with submitting and approving a composite form. Say, the employee fills in an order for something, submits it and the manager then approves or rejects it.
    First, in order for the employee to view the form, you can use a Form Display callable object as a display callable object for actions where the execution object is a form. It displays the name and description of the form and provides a link for download. If the user has view permissions on the step, he or she can view the display object and download the form itself. So, this CO is connected basically with the user experience and what he/she sees displayed on the screen, no matter what happens in the background (e.g. you can have a pre-filling service in the background that prefills some fields of the form, but what the user sees is only the form fields with certain info already prefilled in them).
    Next, for the manager to approve or reject the form of the employee, you need a CO that is only for execution, for example a Process Control CO for File Approval For forms, you can use it in a process in which a form is sent by e-mail. As soon as the form is submitted back to the system, the receiver can view it, save a copy of the form, and depending on his or her decision, can approve or reject it.
    This really is a very simplified example, but I hope it helped a little in some way or another
    Here is a link to the Callable Objects in GP documenatation, hope it also clears up some questions:
    http://help.sap.com/saphelp_nw70/helpdata/en/d2/d174413aff5458e10000000a1550b0/frameset.htm
    Also, a link to the documentation for exposing COs:
    http://help.sap.com/saphelp_nw70/helpdata/en/08/d88041a17e060de10000000a1550b0/frameset.htm
    HTH:)
    Greets,
    Petra

  • 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

  • Error building/creating WD Callable Object

    Hello guys,
    Pardon for reposting - I did post on the WD Java thread - and I think this is the more appropriate area to ask this question since its GP Callable Objects related.
    While creating a WD Callable Object: I
    I added Used DC: caf/eu/gp/api/wd to the WD DC. And added IGPWebdynproCO on the Implemented Interface. Afterwards, after building the DC, I got the following errors:
    This compilation unit indirectly references the missing type com.sap.caf.eu.gp.co.api.IGPTechnicalDescription (typically some required class file is referencing a type outside the classpath)
    The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.caf.eu.gp.co.api.IGPTechnicalDescription. Fix the classpath then try rebuilding this project.
    I tried repair and rebuild - and restared NWDS (and even restarted my PC).
    Issue not resolved.
    What else should I do?
    Thanks!
    Regards,
    Jan

    I solve this including DC from caf/eu/gp/api (external public part) as show
    http://help.sap.com/saphelp_nw70/helpdata/en/43/e085d6421a4d9de10000000a155369/content.htm
    Later the method getDescription throws error because not return anything, while I return null
    Regards,

  • Error testing Web Dynpro Callable Object (GP Interface)

    With reference to thread:
    Interactive form as  Callable object error on testing the object.
    FYI, I'm running NW04s, EP 7.0 SPS 13, JDK 1.4.2_14, Unix OS
    Hi All,
    I have created a Web Dynpro App with a Adobe Form as the frontend. I have included the caf/eu/gp/api as a DC and implemented the IGPWebDynproCO interface. Next I created a Web Dynpro Callable object in GP and ran a test and received the following error:
    Result: Technical Exception
    Details: Could not create web dynpro callable object component
    Output Parameters
    Callable object implementation did not return  output parameters
    Can anyone help me resolve this? Do I have to make a manual entry in the HOST file? If so, what is that entry? Are there alternatives?
    Thanks
    Kunal.

    Hi,
    For creating WD callable object you need to add following three DC in your WD DC project.
    In the Web Dynpro Explorer of the Web Dynpro Perspective, expand the node DC MetaData -> DC Definition, and select Used DCs.
    a.      To create a DC dependency, open the context menu and choose Add Used DC.
      b.      Select Local Development  -> SAP-EU  -> caf/eu/gp/api/wd  -> DC MetaData  -> Public Parts  -> GPWebDynproCO. For Dependency Type, select Build Time, Design Time, and Run Time. Choose weak from the dropdown list.
      c.      Repeat the previous step to define a dependency to DCs SAP-EU-> caf/eu/gp/api (public part external) and SAP-JEE -> com.sap.security.api.sda (public part default).
    You need to do one more thing like bellow.
    Select your Web Dynpro project and open its context menu. Choose Properties.
    1. Choose Web Dynpro References -> Library References.
    2.  Add a reference for library caf/eu/gp/api.
    I think this will help you.
    Thanks
    Chandan

  • GP, callable object Web Dynpro Application (bespoke) not appearing in list

    Hey y'all
    We're developing our first GP, and we would like to call an existing bespoke Web Dynpro. When creating the callable object, we're selecting type Web Dynpro Application, but our Web Dynpro screen is not appearing in the drop down list on the next page. We think that this is because the application has been deployed to a different server (i.e. it has not been deployed onto the portal server).
    So the question is, has anyone faced this problem before, and is there a solution?
    Kind regards
    Jon

    Hi John,
    Please have a look at this Exception on creating GP Action
    This will solve your issue definitively. Do not take care of a given SDA, just redeploy everything and make sure that everything is overwritten by selecting the right option.
    Best regards,
    David

  • 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

  • Problem with Input out put parametes of IViews in callable objects

    Dear Friends,
    I have designed model which contains 2 IViews
    Apply leave IViews
    Approve leave Iviews
    In both the cases i have exposed the in & out parameters using start & end point.
    Finally deployed in portal successfully
    Guided procedures ->Design Time
    I have created folder
    when i create callable objects using this IViews , i dont see the input & out put parameters exposed in context parameters tab for this IView.
    Any step i missed.
    Regards
    shekar Chandra

    HI Nishi
                struck up with minor problem,
    We have a application designed in VC.It contains
    Create request
    Approve Request(approve or reject buttons)
    IF approved then
    a.Book Request IView
    b.Summary Iview
    If Rejected then
    a.rejected IView.
    When i am designing Process with Sequential block,
    all the actions namely
    create request
    appprove request
    reject
    book
    summary
    are processingone one by as action mentioned in sequential block irrespective of approved or rejected.
    I cannot go for alternative block, since the result state buttons are desinged in IView only namely(Approve/reject).
    How to overcome this probelm any suitable solution?
    regards
    shekar chandra

  • Webdynpro Development Component Callable Object Escalation

    Hi,
    In gp sequential block workflow  using webdynpro development component callable objects  When the initiator intiates a workflow ,it is assigned to the first approver.Now if the approver does not take any action within 2 days i want to escalate the task to the second approver.How can i do this escalation?
    There is a standard parameter call <b>due date</b>...in action.How can I set this value dynamically from my application..
    During escalation , the next approver has to be taken by executing an rfc in the background
    Please help....
    Thanks,
    Shamila

    Hi,
    You can define a CAF Core application service (implemented in the CAF Core layer) or a background CO (implemented by a J2EE class interface) which can call a RFC to get the next approver and return the next approver's user id as an output parameter. You can use dynamic user assignment in the next action (approval), by selecting the processor as "Filled From Context Parameter" (at the Roles tab in block level) and select the user id output parameter of the background CO/CAF app service CO.
    You can get more details on different types of CO at the CAF Tutorial Center @SDN
    Thanks,
    Dipankar

  • Sending my callable object as interactive form thru workflow for approval

    hai
            I have created a sales order form as per the requirement given by sales head.Also i ve created a role in portal and have deployed my application implementing the rfc s required. i need to send my callable object(component1) to the saleshead with approve and reject button where when he approves notification mail should be sent to the required persons and if he rejects it should come back to me.(order initiator).i need to complete this soon and i dont have any idea about _+sending my callable object as interactive form thru workflow+_ .plz guide me with the steps(step bye step process) to be followed which ll help me to complete this project.

    Can we know the reason why do you need to extract the Interactive Form from Workflow.When you are calling the workflow try to save the form in a shared folder and save the url of the shared folder in a field and try to acces it by using SAP Activity.You can create a button for that create an SAP activity and when you click on the button the Interactive Form can be opened.
    Iam not sure weather i have answered your question or not?

  • Cannot display Adobe form as Callable object in GP

    Hi all,
    I'm trying to display an adobe form as an Interactive Form Callable object.
    I've created a process -> block -> action -> callable object. But the form doesnt display. When I launch the GP runtime and initiate the process, I get the message "The next activity is not yet available: try again later using the "Refresh" button " nothing happens when I hit the refresh button.
    Can someone advise me what I might be doing wrong? I've also tried things like consolidating parameters with other callable objects just to see if anything display, but no luck so far.
    Thanks
    TM

    Hi Som,
    I'm using NW04s, EP 7.0 SPS 10
    OS is Unix(server) Windows 2000 Pro (client)
    Browser version is IE 6.0.
    I just realised the system is sending out an email to the initiator, and the initiator is able to open the Adobe form. But who does the initiator send the email back to? I'm quite a newbie to this stuff so please bear with me. Also another question is, if the form is offline, then how do we know which workflow (GP) it will tie to once the form is submitted back to the system? In other words, does the person who receives the email with a filled adobe form have to manually initiate the workflow or is there a mechanism to automate this?
    Thanks in advance
    TM

  • 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

Maybe you are looking for

  • GR/IR account master change

    Hi Gurus, I have forgot to check open item managed check box in the master and some of the transactions are already posted. I have cleared the transactions and made it the balance to zero. Now if I try to check the "open item managed" check box syste

  • ADOBE ACROBAT 8 Pro Upgrdade / WIN 7 Pro INSTALLING

    I'm replacing my computer, moving from Windows XP pro to Windows 7 pro. To install Acrobat 8 Pro (this this an upgrade license) I should install step by step the following software: Adobe Acrobat 6 Std > Adobe 7 Pro > Adobe 8 Pro. This will work with

  • HT203175 How can I copy my Word document and my films which I already have in my computer into my itouch?

    How can I copy my Word documents and my films which I already have in my computer into my itouch?

  • Call procedure from ADF

    Hi, I have implemented a prtototype in JHeadStart/ADF. In my database there is a package with procedures and functions i want to call from my application. As i read in Dev.guide and blogs i could use StoredProcedureCall. But it is a part of the TopLi

  • PDF output adjustments

    Using a iphone on windows version 7.1.2 how do I correct alignment for business card stock edges.