Callable object - Implementing a Web Dynpro Component

Hi,
I am trying out the tutorial for implementing Web Dynpro Callable object.
I think i have missed to add some library.
Can anybody guide me for importing the correct library?
It is not able to recognise the WebDynproResourceAccessor class.
Also mention what other library i need to import for this.
<b>WebDynproResourceAccessor resourceAccessor = new WebDynproResourceAccessor(textAccessor);
StructureInfo input = techDesc.getInputStructureInfo();</b>
Regards
Satya

Hi Satya,
You need to add the following DC's as used DC's to your WebDynpro DC:
caf/eu/gp/api
caf/eu/gp/api/wd
Then, you should be able to use the following code for accessing the message pool:
IWDTextAccessor textAccessor = wdComponentAPI.getTextAccessor();
GPWebDynproResourceAccessor resourceAccessor = new GPWebDynproResourceAccessor(textAccessor);
Johan

Similar Messages

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.

Dynamic insertion of MIME object into a web dynpro component

Hi,
I want to dynamically insert a MIME object of type JPEG or type GIF into my web dynpro component at runtime.
I was unable to find the database table which contains the list of MIME objects for a particular web dynpro component.
Can you please help me out with this?
Thanks in advance,
Adithya
Moderator message: wrong forum, please have a look in the "Web Dynpro ABAP" forum.
Edited by: Thomas Zloch on May 23, 2011 9:55 AM

Hi Muzammil Bichoo ,
when you copy the wda component, it will be copied and will be in active state, once all the components are activated means, windows, views, everything will be available.
now create application for your component, if you have more than one window(interface view) select the one which you need for the application.
Regards
Sarath

Web Dynpro Component cannot be found in list when Creating Callable Object

Hi All,
    I have created a web dynpro component and implemented the IGPWebDynproCO interface, after that I deployed it into the J2EE engine.
    But in the step of choosing the web dynpro component as a callable object, I cannot find the one I created.
    Any suggestion or idea?
    Thanks,
YiNing

Hi,
Check out these links :
-> Composite Application Framework Tutorial Center
SAP Composite Application Framework - CAF Tutorial Center [original link is broken]
->Creating a Callable Object: Composite Application Web Dynpro Component https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac4c81d1-0c01-0010-adb0-bb14220343c2
Regards,
Indu
Edited by: Indu Garg on Feb 28, 2008 12:33 PM

Errot at creation of callable object (Web Dynpro Component (GP Interface))

Hi,
I have made a Web Dynpro component and it has been built and deployed without problems.
However, when I go to the Design Time in the portal to create the callable object, it dumps with this message:
500 Internal server error
The initial exception that caused the request to fail was:
java.lang.UnsupportedClassVersionError: bad version number in .class file
Any ideas to what this is about ?

Hi Peter,
Check this link.It may be helpful.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/java/netweaver%252bdeveloper%252bstudio%252b(NWDS)
Regards,
Sumangala

Create Callable object of Web Dynpro Component (GP interface) giving error

Hi All,
We are facing a strange error in Guided Procedure.
While trying to create a new callable object of Web Dynpro Component (GP interface) after selecting the type and click on Next it is throwing below error.
*javax.xml.stream.FactoryConfigurationError: Requested factory com.ctc.wstx.stax.WstxInputFactory cannot be located. Classloader =com.sap.engine.services.deploy.server.ApplicationLoader 3995fdb9 sap.com/cafeugpuidt
    at javax.xml.stream.FactoryLocator.loadFactory(FactoryLocator.java:120)
    at javax.xml.stream.FactoryLocator.locate(FactoryLocator.java:109)
    at javax.xml.stream.FactoryLocator.locate(FactoryLocator.java:54)
    at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:41)
    at org.apache.axiom.om.util.StAXUtils$7.run(StAXUtils.java:311)*
Also while running the GP processses which are created in the past and working fine till few days back are also giving the same above error.
Please help us in resolving the issue.
Regards,
Satish

Hi Peter,
Check this link.It may be helpful.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/java/netweaver%252bdeveloper%252bstudio%252b(NWDS)
Regards,
Sumangala

"Unable to create web dynpro callable object implementation" - GP error

Good day.
I've created a GP process and transported it to the test system. But when I try to start the process I get an error on the screen: Error while processing the item; it cannot be displayed. When I look to the logs I can see the following exception:
Unable to create web dynpro callable object implementation.
java.lang.Exception
at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWD.execute(COExecWD.java:294)
at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWD.execute(InternalCOExecWD.java:171)
at com.sap.caf.eu.gp.ui.co.exec.wd.COExecWDInterface.execute(COExecWDInterface.java:122)
at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface.execute(InternalCOExecWDInterface.java:134)
at com.sap.caf.eu.gp.ui.co.exec.wd.wdp.InternalCOExecWDInterface$External.execute(InternalCOExecWDInterface.java:249)
at com.sap.caf.eu.gp.ui.act.container.VContainer.onPlugFromDispatcher(VContainer.java:391)
at com.sap.caf.eu.gp.ui.act.container.wdp.InternalVContainer.wdInvokeEventHandler(InternalVContainer.java:167)
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:881)
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:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:303)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:667)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:537)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
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: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(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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
It doesn't make any sense to me... I would appreciate for any help.

Hello
We are facing exact similar issue when we checked the logs.
Could you help us as we are new to GP.
What steps you followed to resolve this error.
Regards
aparna

Changes in standard e-rec web dynpro component

Hi ,
I need to make some changes in standard e-rec web dynpro component. Needed to know what approach needs to be followed for the same. Can I make changes in the standard itself or do I need to copy the standard component and make changes in the Z component.
Thanks in anticpation.
Regards
Nidhi Jain

Hi Nidhi,
Its better to make changes in the Enhancement Framework itself.It will be too complex to make it to Z applications since there will be lot of dependent objects involved. I was also in the state of dilema when i was about to make changes to the standard E-travel applications using ABAP webdynpro(EHP2) and finallly i was able to meet all the customer requirements using Enhancement Framework and yesterday the UAT ended successfully..:-).
I have also implemented the e-recruiting using BSP in my last project.So i am able to give the above suggestion to you.
Since E-rec applications will have lot of methods, you can be able to meet all the changes in the Pre and the Post exit methods itself.
All the Best.
Thanks,
Rajkumar.S

No executionContext attribute in Web Dynpro Component Controller

Hi All,
    I'm trying to write a Web Dynpro Component which can be used as a callable object by following the Link:[document|http://help.sap.com/saphelp_nw70/helpdata/en/43/e085d6421a4d9de10000000a155369/frameset.htm].
    I've successfully finished the getDescription method. In the execute method, I'm trying to get the executionContext attribute of the instance, but it always shows that no attribute name executionContext can be found here.
    Anyone can help me?
    Thanks,
YiNing

Hi,
You should get the executionContext attribute as an inout parameter of the execute() method. You can also declare a instance variable to hold this to be later refered in other methods of the controller.
Thanks,
Dipankar

No component usage created in enhanced web dynpro component

Hi experts,
I am facing the following problem:
I'd like to enhance a web dynpro component in order to add a popup window. The popup is triggered by the process_event method. So far everything works just fine.
But the popup needs to know some context attributes from the main component, and I cannot create a component usage in order to set the context mapping.
Does anybody know how to solve this issue?
Thanks and regards
Jan Phillip Höft

Hi!
Thanks for your answers first of all.
I need the popup to be a stand alone web dynpro component, so I guess the assistant class doesn't do the trick because I can not access it in the popup component.
The popup is called when the business object is saved. So that the user is asked to notify other users that the document has changed. In this popup the user should fill in the message and click a button to send it and close the popup.
So I tried the OBN approach as well but with two problems :
1. I cannot close the popup component by coding (button click) because it has no direct parent component
2. The save event is not run through properly so the document stays locked by the user. But I didn't look into this yet.
So it would be perfect to have an embedded popup component which is based on a stand alone web dynpro application so it can be closed properly but it need at least access to the guid of the main component.
Anybody got an idea for this?
Thanks and regards
Jan Phillip Höft

Calling session bean's business method through web dynpro component

Hi All,
Can anybody tell me how to call a session bean's methods through a web dynpro WITHOUT java-model or web service model ??
I have following scenario:-
1. Stateless Session bean having two business methods
2. Web Dynpro component
3.Now i want to call business methods without using any model. I have got following piece of code but I dont know how to go about it.
4.Where do i have to set JNDI name for session bean? which interface will be looked for?
5. Do I have to declare public part for EJB DC? If yes, how?
//This is inside web dynpro component
InitialContext context = new InitialContext();
o = context.lookup(JNDIName);
TestSessionbeanHome homeRef = (TestSessionbeanHome) PortableRemoteObject.narrow( o,
TestSessionbeanHome.class);
TestSessionbean beanRef = homeRef.create();
<returnValue> = beanRef.<ejb method name>
Please help to get a step-by-step approach to this case.
Thanks and regards,
Amey Mogare

Hi,
If I comment out the part that is using session bean's business method, DC is building fine.
And if I uncomment, then compiler is unabl eto resolve business method(s).
And i would like to mention that my EJB + J2EE App DC is building properly, but it havent yet deployed properly as I am waiting for data-source-alias name prefix to be configured by ERP team. So will this be a reason why Web Dynpro DC is not able to resolve business methods ??
Because Web Dynpro DC is able to resolved all interfaces of Session bean and entity bean. But when it comes to business method, its not able to resolve.
Any more ideas why it is not happening?
Pls help.
Now i went through some forum posts regarding this and found that we also need to add EJB DC to Java Build Path for WebDynproDC>Properties>Java Build Path.
I did this and now it is able to resolve business methods and DTOs as well. So to summarize I did following:-
1. Added EJB DC (complete DC) as a Used DC to Web Dynpro DC with Buid-n-Deploy-n-Run time dependency
2. Added Sharing reference of J2EE application DC to Web Dynpro DC -->Properties
This reference I constructed as follows:-
<vendorname>/<name of j2ee application as appearing under display name tag in application.xml (replacing '/' with '~')>
So my Sharing Reference becomes:- <vendorname>/reqpstapscreqpstapja_reqid
3. Added EJB DC to Java Build Path in Web Dynpro DC's properties
4. Then I added following piece of code to get object of SessionBean class
InitialContext context = new InitialContext();
Object o = context.lookup("java:comp/env/ejb/SessionRequestIDBean");
SessionRequestIDHome homeRef = (SessionRequestIDHome) PortableRemoteObject.narrow(o, SessionRequestIDHome.class);
SessionRequestID beanRef = homeRef.create();
beanRef.<business method>
But After doing this I am facing another problem :-
The build fails saying it is not able find the package for DTOs. But when I see the Component Controller's code it is not showing any red or yellow marks.
Can anybody pls help me out here?
Thanks and regards,
Amey Mogare

Transport issue when copying a web dynpro component

Hello All.
I have a web dynpro component lets say ZTest and now I want to copy this, I gave the new one a different name i.e. ZFINAL, now when I copied, it asked me for the trasnport and when I asked to create a new transport I got this message "Class ZIWCI_ZFINAL does not exist" and then I clicked the green arrow again and it created a transport for me. After this process I activated my web dynpro component successfully, my web dynpro component has 3 views and 3 windows. When I looked at my new transport (for ZFinal), I only saw three tasks attached to teh transport i.e. 1. Interface 2. Info Object from the MIME Repository and 3. Web Dynpro Component but I didn't see Controller (Web Dynpro), Definition (Web Dynpro) and View (Web Dynpro) attached to my transport. Now I wonder when I release my transport to Q I may have issues.
Note: My old trasnport (which has Ztest)has all the missing objects: (Web Dynpro), Definition (Web Dynpro) and View (Web Dynpro)

I resolved it myself.. I had to write the transport entry manually for the views and windows and even the component controller definition.

Is it possible to serialize a web dynpro component controller?

Hi,
Is it possible to serialize a web dynpro component controller and deserialize it for use?
I have one web dynpro application WDA1 for web dynpro component WDC1. And another web dynpro application WDA2 for WDC2 will be opened in a new window triggered by a button action in WDC1.
Iu2019d like to pass the object reference of WDC1 component controller to WDC2.
I first tried to use a static member of a class object but found out that even the static member is initialized and set in WDC1, itu2019s still initial when I access it in WDC2.
Then I searched the forum and found one article Passing Object ref to Webdynpro Application while calling from BSP screen .
The recommended way is to serialize the object reference and store in a DB table, later on read it out and deserialize it for use.
I tried serialization using the following code, but when itu2019s deserialized, the result is initial.
Can anyone share some ideas on this?
Serialize
data: ostream type string,
           xslt_err type ref to cx_xslt_exception.
***** serialize model class
try.
      call transformation id
      source model = wd_comp_controller
      result xml ostream.
    catch cx_xslt_exception into xslt_err.
endtry.
Deserialize
    data: istream type string,
          xslt_err type ref to cx_xslt_exception.
    istream = ls_db_sel-obj.
    data lr_wdc type REF TO ZIWCI_BY_WDC_SERIALIZE.
    try.
        call transformation id
        source xml istream
        result model = lr_wdc.
      catch cx_xslt_exception into xslt_err.
    endtry.

When you say new window, I assume you mean new browser window. This is a separate user session then. This is why the singleton pattern doesn't work. Have you considered using a new dialog window instead of a new browser window. It will be modal, but will share the same user session as the parent window.
>Why do you choose this approach over cross-component usage ? component usage is the way webdynpro components are >to be reused.
>You can also consider using Singleton OO pattern class to share data between these two components.
Neither of these approaches will work if you are using separate browser windows. Such an approach results in two separate user sessions (perhaps even running on different application servers depending upon how you have load balancing setup) and therefore can't share data using either of these approaches.
In general the idea of serialization and then writing the string ito a server cookie or other database table is sound. I don't think you should try and serialize the component controller, however. Serialization only saves and restores public attributes - not protected or private ones. So in general a class has to be designed for serialization. The component controller is much too complex and wasn't designed for such an operation.
I would suggest instead extracting the data you want to share out of component controller or context and serializing it into a custom class and passing that to the other component.

Nwdi-managed access of pcd-objects from java web dynpro

Hi,
im am trying to access portal pcd-objects from a java web dynpro component (namely getting and setting personalized iview properties). for locally managed web dynpro components this works fine with the code below.
when i try the same with a nwdi managed web dynpro component i run into problems regarding references to used dcs. for instance, i need to reference used dc SAP_JTECHS/tc/epbc/pcm/adminapi/java because the build needs tcepbcpcmadminapijava.jar which is inside the mentioned dc. but access permissions of this dc don't allow the dependency. when i try to "add used dc ..." in nwds i get the error message: illegal dependency: access list does not allow use of ...
has someone any solution for this problem? are there other ways of accessing pcd-objects from java web dynpro (nwdi managed!)?
thanks
heiko
private static void savePersonalizationData(String value) {
     try {
          IAttributeSet attributeSet = (IAttributeSet) getIview(IVIEW);
          attributeSet.putAttribute(ATTRIBUTE, value);
          attributeSet.save();
     } catch (Exception e) {
private static Object getIview(String pcdPath) throws Exception {
     Hashtable env = new Hashtable();
     env.put(
          com.sap.portal.directory.Constants.REQUESTED_ASPECT,
          com.sap.portal.pcm.admin.PcmConstants.ASPECT_SEMANTICS);
     env.put(
          Context.SECURITY_PRINCIPAL,
          WDClientUser.getCurrentUser().getSAPUser());
     env.put(
          IPcdContext.PCD_PERSONALIZATION_PRINCIPAL,
          WDClientUser.getCurrentUser().getSAPUser());
     InitialContext iCtx = new InitialContext(env);
     return iCtx.lookup(pcdPath);

Hi Kust,
To access the PCD objects the code you used looks ok for me but your main issues is related to the dc access permissions. This thread discussed about the similar issue. Please review this below thread.
/message/979328#979328 [original link is broken]
Regards
Krishna Reddy

Context from Web-Dynpro-Component-Interface & Customer Extention Fields

Hello all,
A main component uses a Web-Dynpro-Component-Interface and defines an external maping to it. Web-Dynpro-Component-Interface has a context and a window. At runtime implementaion of Web-Dynpro-Component-Interface is provided.
All works fine, but how can i create an implementation with view which contains customer extention fields? Unfortunately only fields from context of Web-Dynpro-Component-Interface are visible. I can not even extend the context of Web-Dynpro-Component-Interface via enchancement framework.
I assume, it is possible with dynamic programming, but why is it not possible in declarative way?
thanks
regards
Paul

Hello,
I found this documentation:
Implementation of Interfaces for Customer Developments
Using interfaces in a Web Dynpro component benefits customers by giving them a clean basis for their own further developments. When creating a local development, you can implement a used interface in a separate component and add your own aspects to an application delivered by SAP.
http://help.sap.com/saphelp_nw70/helpdata/en/a9/19eebc1e2943dbb2d443095d017ae9/content.htm.
I think it must be a correct way to extend SAP programms with customer fields. Please reply, issue is very important.
Regards
Paul

Callable object - Implementing a Web Dynpro Component

Similar Messages

Maybe you are looking for