JSP Dynpage Callable Object

Hi Experts,
If we want to use JSP Dynpage as Callable Object (CO), is this possible to for this CO to receive input parameters and export output parameters like WD CO do? Can anyone give me some advice on this? Sameple code would be better.
Best Regards

hi, Tom:
I think JSP Dynpage can be refer to portal object. Maybe this online help can give you some hint.
http://help.sap.com/saphelp_nw70/helpdata/EN/b0/588041a17e060de10000000a1550b0/frameset.htm
best regards, Nick.

Similar Messages

Hiding Label field in JSP dynPage

Hi all,
I am having an issue in Hiding/disabling label field in JSP Dynpage application
Works fine:
<hbj:label id="label_Input_US_Taxpayer_ID" text="<%= USTaxpayerID %>" required="FALSE" design="LABEL" labelFor="Input_US_Taxpayer_ID" />
but as soon as I use enabled="FALSE" the code will crash..
Gives ERROR
<hbj:label id="label_Input_US_Taxpayer_ID" text="<%= USTaxpayerID %>" required="FALSE" design="LABEL" labelFor="Input_US_Taxpayer_ID" enabled="FALSE" />
what is the way to implement this ?
Thanks !
Asif

@Nishant : label object does not have visibility property like input field
(http://help.sap.com/saphelp_nw73/helpdata/en/4a/3fcf2580551014e10000000a42189b/content.htm)
However we can enclose the lable field inside DIV object and use it's visibility property.for example
<div id="area_one" style="display:none">
<hbj:label id="label_Input_US_Taxpayer_ID" text="<%= USTaxpayerID %>" required="FALSE" design="LABEL" labelFor="Input_US_Taxpayer_ID" />
</div>
and then change the visibility in script function
if (obj.style.display == "none")
 obj.style.display = "block";
 else
 obj.style.display = "none";
Edited by: asif hirani on Mar 3, 2011 4:52 PM

WD4VC Callable Object: No parser configuration entry for the tag Invoke

I am trying to use a Visual Composer model as a callable object. I can deploy OK (as a Web Dynpro model, having checked the copmiler options "Deploy Model with PAR" and "Add Guided Procedure information").
When I try to test the Callable Object, I get the following error:
com.sap.tc.wd4vc.intapi.info.exception.WD4VCRuntimeException: No parser configuration entry for the tag Invoke.
No idea how to get around this.
Any help greatly appreciated.
Kind Regards,
Tony.

Hi Mario,
We have only three runtime in VC 7.0
1. XGraph
2. Flash
3. Webdynpro.
In your blog on wiki Flex runtime is mentioned as given below:
Webdynpro runtime is not fully supported in NW04s and some tags may not be supported as stated in the error. The reccomendation is to use the flex runtime.
Is Flex runtime and Flash runtime is same ,
I have tried to deploy the model in Flash runtime and Portal runtime error ocurs by diasply renderning JSP Component,
But when i deploy it in Webdynpro runtime , it works fine for displaying data in Table.But gives error :No parser configuration entry for the tag ChartView , when i used chart in place of table .
Thanks.

JSP Dynpage iView 'Open in New Window' losses session data

Hi All,
I have a JSP Dynpage that displays some position holder information based on a position id passed in by the URL query string. The problem that I am trying to solve is to allow the user to open the iView in its own window by using the 'Open in New Window' option from the button in the upper right of the iView title bar. When this happens the URL query string is no longer available so the iView has problems. My solution is to store the position id in the session object then read from that session object when the query string is not available - when opening in a new window.
But what is happening is that the position id saved in the session object is no longer there when the new window opens. I have looked else where on this site but all posts seem to deal with data transfer from JSP Dynpage to the JSP page. This issue is dealing with a page getting re-opened in a new page (browswer).
I can't seem to get the session object to work between JSP Dynpages at all, I would think that the data put into the session would stay there untill either cleared or the session ends. Am I missing some configuration settings? I have included some of the key code below.
// GET THE POSITION ID FROM THE URL QUERY STRING
String PosId;
PosId = request.getParameter("CKey");
if (PosId == null)
 myBean.testing = (String) request.getComponentSession().getValue("PosId");
else
 PosId = PosId.substring(6, 14);
 request.getComponentSession().putValue("PosId", PosId);
 myBean.testing = "POSID:" + PosId;
Thanks for all ideas and help.
Don

All of this logic is within the doProcessBeforeOutput event. Here is all my java code and JSP...
<%@ taglib uri="tagLib" prefix="hbj" %>
<hbj:content id="myContext" >
 <hbj:page title="PageTitle">
 <hbj:form id="myFormId" >
 <jsp:useBean id="myBean" scope="application" class="MSSBeanPackage.HolderDetailBean"></jsp:useBean>
 <% response.write(" xxxx-" + myBean.testing + "-zzzz "); %>
 <hbj:textView id="txtEname" text="<%=myBean.getEname()%>" design="HEADER2"/>
 <hbj:textView id="txtPernr" text="<%='(' + myBean.getPernr() + ')' %>" design="HEADER3"/>
 <hbj:gridLayout rowSize="1" columnSize="1" cellSpacing="2">
 <hbj:gridLayoutCell columnIndex="1" rowIndex="1" width="100%" verticalAlignment="TOP">
 <hbj:group id="grpContractData"
 design="SAPCOLOR"
 title="Contract Data"
 tooltip="Contract Data"
 width="100%">
 <hbj:groupBody>
 <hbj:formLayout id="myForm"
 marginTop="5px"
 marginRight="5px"
 marginBottom="5px"
 marginLeft="5px"
 width="300px" >
 <hbj:formLayoutRow id="Row1" paddingTop="1px" paddingBottom="1px" >
 <hbj:formLayoutCell id="Cell11" align="LEFT" width="40%" >
 <hbj:label
 id="label_WorkContract"
 text="Work Contract xx"
 design="LABEL"
 labelFor="WorkContract"></hbj:label>
 </hbj:formLayoutCell>
 <hbj:formLayoutCell id="Cell12" align="LEFT" width="40%" >
 <hbj:textView
 id="WorkContract"
 text="<%=myBean.getAnsvh_Text()%>"
 design="STANDARD"
 />
 </hbj:formLayoutCell>
 </hbj:formLayoutRow>
 <hbj:formLayoutRow id="Row2" paddingTop="1px" paddingBottom="1px" >
 <hbj:formLayoutCell id="Cell21" align="LEFT" width="40%" >
 <hbj:label
 id="label_HiringDate"
 text="Hiring Date"
 design="LABEL"
 labelFor="HiringDate"></hbj:label>
 </hbj:formLayoutCell>
 <hbj:formLayoutCell id="Cell22" align="LEFT" width="40%" >
 <hbj:textView
 id="HiringDate"
 text="<%=myBean.getEntry_Date()%>"
 design="STANDARD"
 />
 </hbj:formLayoutCell>
 </hbj:formLayoutRow>
 </hbj:formLayout>
 </hbj:groupBody>
 </hbj:group>
 </hbj:gridLayoutCell>
 </hbj:gridLayout>
 </hbj:form>
 </hbj:page>
</hbj:content>
******************* JAVA
package MSSPackage;
import MSSBeanPackage.HolderDetailBean;
import com.sapportals.htmlb.*;
import com.sapportals.htmlb.enum.*;
import com.sapportals.htmlb.event.*;
import com.sapportals.htmlb.page.DynPage;
import com.sapportals.htmlb.page.PageException;
import com.sapportals.portal.htmlb.page.JSPDynPage;
import com.sapportals.portal.htmlb.page.PageProcessorComponent;
import com.sapportals.portal.prt.component.IPortalComponentContext;
import com.sapportals.portal.prt.component.IPortalComponentProfile;
import com.sapportals.portal.prt.component.IPortalComponentRequest;
// SAP RFC Imports
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.JCO;
import com.sap.mw.jco.JCO.Table;
import com.sapportals.portal.prt.service.jco.IJCOClientPoolEntry;
import com.sapportals.portal.prt.service.jco.IJCOClientService;
import com.sapportals.portal.prt.runtime.PortalRuntime;
public class HolderDetail extends PageProcessorComponent {
public DynPage getPage(){
 return new HolderDetailDynPage();
public static class HolderDetailDynPage extends JSPDynPage{
 JCO.Repository mRepository;
 public void doInitialization(){
 // Define request, context and profile containers
 IPortalComponentRequest reqst = (IPortalComponentRequest) this.getRequest();
 IPortalComponentContext myContext = reqst.getComponentContext();
 IPortalComponentProfile myProfile = myContext.getProfile();
 // Define bean reference to bean
 HolderDetailBean myBean = new HolderDetailBean();
 // Place bean in user profile.
 myProfile.putValue("myBean", myBean);
 public void doProcessAfterInput() throws PageException {
 public void doProcessBeforeOutput() throws PageException {
 // Define request, context and profile containers
 IPortalComponentRequest request = (IPortalComponentRequest) this.getRequest();
 IPortalComponentContext myContext = request.getComponentContext();
 IPortalComponentProfile myProfile = myContext.getProfile();
 //Get Bean from Profile
 HolderDetailBean myBean = (HolderDetailBean) myProfile.getValue("myBean");
 String sapSystem = "SAP_R3_HumanResources";
 // GET THE POSITION ID FROM THE URL QUERY STRING
 String PosId;
 PosId = request.getParameter("CKey");
 //PosId = "60004790";
 if (PosId == null)
 myBean.testing = (String) request.getComponentSession().getValue("PosId");
 else
 PosId = PosId.substring(6, 14);
 request.getComponentSession().putValue("PosId", PosId);
 myBean.testing = "POSID:" + PosId;
 this.setJspName("HolderDetailJSP.jsp");
Thanks for your thoughts.

JSP Dynpage Deployment

I've created a JSP according to the help file
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/19/4554426dd13555e10000000a1550b0/frameset.htm">SAP Help JSP Dynpage Creation</a>
When I upload the sample, the iview is empty
Do I have to create the jsp-file manually? Where would it go in the NWDS-tree?
Where is it deployed in the portal?
Thanks - but I couldn't find any more detail beginners guide than the help file

Hi Holger,
>>Do I have to create the jsp-file manually? Where would it go in the NWDS-tree?
Ans: You need not create the jsp file seperately. Just create a JSPDynpage Page project from portal projects and you will get the jsp by itself. Go to:
Project_Name-> dist -> PORTAL_INF-> pagelet
(I am assuming that you are in the Navigator View)
there you will get the jsp file withthe name you must have given while creating the project.
>>Where is it deployed in the portal?
Ans: This is deployed at the portal Server as a .par file. And then you can create iViews from these pars later to create the business objects.
I hope this helps you and solves your problem.
Regards
Pravesh
PS: Please conside rewarding points if helpful and solved.

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.
Error 1
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
error 2
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
error 3
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

Portal Page Builder Error in Portal Callable Object

We have created a callable object in GP of type Portal Page or IView
When we try execute the action from UWL, the following error it shows,
The portal page builder required to execute this callable object is not available.
The same concept we tried in 2004s, its working fine.
Any idea about this error in ce. Highly urgent..

Not yet answered

Web Dynpro as Callable object in GP using PDF Forms

Hi All,
I somehow want to integrate a user filling out a pdf form within a Guided Procedure. So far I have created a local web dynpro DC and I want to make it a Web Dynpro Callable Object (GP Interface). The problem is, I want the user to be able to see the PDF form when filling out the form. For example, if they had a role in the portal where they can invoke the Web Dynpro application with the pdf form, then when they click submit on the pdf they invoke the guided procedure...is this possible? This is so, I can use the web dynpro to do some data validation and call some bapis to get info, then submit this all to the GP. Is this achievable? I know how to do most things, I just want to know things like when is the "execute" and "getDescription" methods called? I want my execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext ) method to call a bapi also. Is that possible? How do I automate a GP process when I click submit on the pdf form?
Thanks in advanced
TM

Hi,
You can integrate a PDF control in a Web Dynpro view. Refer the following links for that:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/dc/f1783fe3263042e10000000a114084/frameset.htm">Example of the Use of an Interactive PDF Form (SAP Library - Web Dynpro for Java)</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/60/6fc10c6748479392101e09c9e8d33a/frameset.htm">Interactive Forms in Web Dynpro for Java</a>
Also you can create Web Dynpro Java callable object in GP by implementing the IGPWebDynproCO interface. Refer the following links for that:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50d74ada-0c01-0010-07a8-8c118d408e59">Implementing a Web Dynpro Callable Object which Implements the GP Interface</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>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/fd/afb4429027da11e10000000a155106/frameset.htm">Implementing a Web Dynpro Component</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/de/8976417f2d5558e10000000a1550b0/frameset.htm">Implementing and Exposing a Web Dynpro as a Callable Object</a>
You can start a GP process using the public API:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/fcdf77fc6510b3e10000000a11466f/frameset.htm">Starting and Terminating Processes Using the GP API (SAP Library - Creating Composite Applications)</a><a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f27e290-0201-0010-ff82-c21557572da1">Creating Interactive Forms in Web Dynpro for Java</a>
Also you can start a GP process using Web Service:
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/44/44c59fd7c72e84e10000000a155369/frameset.htm">Starting a Process Using Web Services (SAP Library - Creating Composite Applications)</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/93/27dc108cfc407fbf6c726151840001/frameset.htm">Starting and Terminating Processes Within a Composite</a>
Refering the above links you'll get a fairly good idea how to integrate Adobe forms in WDP and how to start GP process programitically. My suggestion for your requirement would be if always you need to start the process after the user submits the Adobe form, then consider having the Adobe form as the first step for the process. In that case you don't need to start the process programitically. Whenever the user starts filling up the Adobe form the GP process will start. You can refer <a href="/people/dipankar.saha3/blog/2007/03/02/how-to-present-your-gp-processes-to-the-end-user">this blog</a> on how to start a GP process as an iview link in portal.
Otherwise if based on certain conditions you need to start the process then you can either use the Java API or the web service to start the process from Web Dynpro. You should have the Adobe form embedded in Web Dynpro and on submit event you can check the conditions and start the process if required.
Thanks,
Dipankar

Callable Objects-Write to System Log,Offline Approval

Hi,
I am new to Guided Procedures and I am trying out examples in all callable objects.
I have doubts in 2 callable object
1. Can you guide me how to use the callable object under Miscellaneous Type - Write to system Log
After we Enter the Log text where to go and view the text.
2.Callable object under Process control type - OfflineApproval
When I use this callable object I am not getting mail whether the action is approved or rejected.
Regards,
Bala Baskaran
Edited by: Bala Baskaran on Feb 27, 2008 12:45 PM
Edited by: Bala Baskaran on Feb 27, 2008 12:48 PM

Hi,
Which SRM version are you working??Always mention that in your post for appropriate solutions.
Pls see the foll notes:
Note 928320 - RBBP_OFFLINE_EVAL: Local purchase orders not selected
Note 980963 - RBBP_OFFLINE_EVAL: Some users not found
Note 1039869 - RBBP_OFFLINE_EVAL:Sometimes text contains no Object ID
1035114 - RBBP_OFFLINE_EVAL: Wrong messages , missing values there
BR,
Disha.
Pls reward points for useful answers.

I am not able to create a callable object of my web Dynpro application

Hi,
I have my Portal server installed with NW2004S and with other components as follows.
·WAS 7.0 SP9
·EP7.0 SP9
·CAF 7.0 SP9
·VC 7.0 SP9
But now my webdynpro application is not reflecting in web Dynpro Component(GP Interface) during the design time, when I am trying to create a callable object.
So please can you suggest what is the problem and how I will get it corrected.
Regards,
Paresh.

Hi Aliaksei,
I had created a complete CAF application which was working fine. Then the server got crashed and i lost everything.So then i again installed the server and upgraded it to SP7.But than i was not able to see my web dynpro application while creating callable object. So i created another instance in the server at the base level(SP4) and i was able to create callable object.
There is no problem in the webdynpro application.I have added runtime library referece to my project : sap.com/cafeugp~api and also implemented the Interface IGPWebDynproCO in my component.
So i dont know where i am going wrong while i am upgrading the server.
Regards,
Paresh.

Problem in creating a callable object of type Business Logic

Hi SDN,
I am trying to create a callable object of type Business Logic in CE.
When I give all information and click Next, I get this error message.
Error while loading configuration dialog: Failed to create delegate for component com.sap.caf.eu.gp.ui.co.CExpConfig. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
Can anybody help me out with this problem.
Regards,
Sumangala

Hi.
I'm having the same problem as Senthil in NW2004s SP15 with my application service and methods not showing up in the Callable Object wizard for Composite Application Services after I choose the Endpoint. The only application name that shows up in the wizard is caf.tc, and the only service names that show up for it are LDDataAccessor, Metadata, and PropPermissionService.
My IDE is on one machine and the application server I deploy to is located on a different machine. My endpoint to the remote application server looks to be correctly configured. The Composite Application Service seems to be deployed properly as I'm able to see it and test that it works in the Web Services Navigator <http://remotehost:50000/wsnavigator/>
My deployed application service is a remote enabled service and is also web services enabled as well.
I'm not sure if this is relevant, but I noticed that the generated Java code does not create any remote EJB interfaces (only home and local interfaces were generated).
Something else I noticed is that when I proceed to the External Service Configuration -> Business Entities screen <http://remotehost:50000/webdynpro/dispatcher/sap.com/cafUIconfiguration>, I only see three business entities displayed, and the following error message is displayed: "Corrupt metadata has been detected. This may prevent some objects from being displayed. Check the server log for more details." I was unable to find anything in the instance log files. Is the error message indicative of the problem?
I am developing locally without a NetWeaver Development Infrastructure (NWDI) in place.
I'm wondering if the credentials specified in the endpoint require any special roles or privileges.
Senthil, do any of these additional descriptions apply to you as well?
Edited by: Ric Leeds on Jun 20, 2008 4:37 PM

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 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.

Getting error while creating callable object

Hi,
I've created and deployed a DC using webdynpro.
Now I want to create a callable object from portal
I'm choosing the following options Guided Procedurers-->DesignTime>Create callable object-->userinterface>webdynprocomponent(GP interface)
On entering the required data on the displayed page, when I'm clicking 'next' option it is giving "500 internal server error".
Can somebody help how to resolve this.
Thanks
Piyush

your callable object component is missing. try to take preview of the iview and check.

JSP Dynpage Callable Object

Similar Messages

Maybe you are looking for