Importing EJBs into web dynpros

I have created EJBS and I would like to use these EJBs in
web dynpros. How do I do it.
I think I can create a jar file for the EJBS and reference them in my Web Dynpro project but I think that is not the right way to do it.
Thanks,
PKK.

Hi Simon + Praveen,
I will try to walk you through how to do it but I think you may need a bit of experience with EJB's, Web Dynpro and NWDS to understand it right away. The following assumes you have created a session and entity bean.
First you need to make sure your table is deployed in the database that you created(dictionary perspective).
Second deploy your EJB (.ear file) to the J2EE engine (J2EE development perspective)
Third switch to Web Dynpro perspective and goto your project properties (right click on the project and click properties)
Now goto Java Build Path - libraries - add external jars and add the EJB-Jar file. then choose the tab called "order and export" and move the jar file to the top.
THIS IS A LITTLE TRICKY. Next you need to add the sharing reference. In the same properties wizard where you add the java build path select Web Dynpro References and then select the Sharing references tab. Click on Add and enter the vendor name and name of the ear file like this <vendor name>/<name of the ear file>, This is how your web dynpro knows where the ear file is on the j2ee engine. IF YOU ARE NOT SURE WHAT IT IS you need to access the J2EE visual administrator. and goto SERVER 0/Services/Deploy then select the "runtime" tab then look under Server 0/EJBContainer save all your meta data. your WD application now accesses your EJB logic.
Good luck!!
-wael
*plz dont forget the rewards?

Similar Messages

Couldn't complete tutorial u0091Integrating EJB 3.0 into Web Dynpro ... '

Hi All,
I am trying to complete the Integrating EJB 3.0 into Web Dynpro Using the EJB Model Importer tutorial that goes with SAP NetWeaver Composition Environment 7.1 SP3 Developer Studio.
Does anyone ever completed this tutorial because I have problems completing it. The result is very important for me because I need to use this technology for my essay.
In this tutorial you create a button that calls the method StudsBean.getStudent(String). In this method the object student is created and it will be returned. In several labels the information of the returned student should be displayed. But that doesnt happen, when I push the button no error occurs but the labels are still empty. When I try to debug the Enterprise Bean and Web Dynpro application I see that the method StudsBean.getStudent(String) is called and the propertys are set and the student object is returned, but still it isnt displayed.
After discussing this with a colleague I tried to search for a solution on the SDN and of course Google. First I thought I would be a bug but I only found 2 people with the same problem. I found it remarkable because its one of the key subjects of Java EE 5 and its a tutorial displayed in the welcome page of the Developer Studio.
So do you people think its a bug in WebDynpro? Because I am sure that I followed all the steps mentioned (a colleague checked it even).
Regards,
Sander

Hi Vesselin,
Thank you for the quick replay, this is the code I'm using:
public void onActionGetStudent(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionGetStudent(ServerEvent)
          try {
              // executes the corresponding method on the session facade
              wdContext.currentRequest_StudsLocal_getStudentElement().
              modelObject().execute();
              // forces Web Dynpro to re-create the Request model object
              // in order to clear the InputField
             wdContext.nodeRequest_StudsLocal_getStudent().invalidate();
              // updates the UI elements bound to the Response node
              wdContext.nodeResponse().invalidate();
              //Code for trying something out
              //wdContext.nodeReturn().invalidate();
              //wdContext.nodeAddress().invalidate();
           } catch (Exception e) {
              throw new RuntimeException(e);
Have you tried this example yourself, or is replay based on experience?
Kind Regards,
Sander

Couldn't complete tutorial 'Integrating EJB 3.0 into Web Dynpro ...'

Hi All,
I am trying to complete the Integrating EJB 3.0 into Web Dynpro Using the EJB Model Importer tutorial that goes with SAP NetWeaver Composition Environment 7.1 SP3 Developer Studio.
Does anyone ever completed this tutorial because I have problems completing it. The result is very important for me because I need to use this technology for my essay.
In this tutorial you create a button that calls the method StudsBean.getStudent(String). In this method the object student is created and it will be returned. In several labels the information of the returned student should be displayed. But that doesnt happen, when I push the button no error occurs but the labels are still empty. When I try to debug the Enterprise Bean and Web Dynpro application I see that the method StudsBean.getStudent(String) is called and the propertys are set and the student object is returned, but still it isnt displayed.
After discussing this with a colleague I tried to search for a solution on the SDN and of course Google. First I thought I would be a bug but I only found 2 people with the same problem. I found it remarkable because its one of the key subjects of Java EE 5 and its a tutorial displayed in the welcome page of the Developer Studio.
So do you people think its a bug in WebDynpro? Because I am sure that I followed all the steps mentioned (a colleague checked it even).
Regards,
Sander

Hi Sander,
I guess, it's not a bug in Web Dynpro, maybe it's a bug in the tutorial
I tried something similar, but not following the tutorial and it works. I wasn't able to call the model from the view controller and I guess that's the problem. Take the code from the init-method of the view controller and put it to the component controller's init -method and the code inside the onActionGetStudent and put it into a method you create in the component controller, too. From onActionGetStudent just call this method in the component controller with some code like this:
wdThis.wdGet<your component controller's name>.<your method's name>;
Hope this helps
Kind regards
Stefanie

Import web service from service registry into web dynpro

HI, when i import web service into web dynpro model, it asks me to create service group or if i choose no service group configure, it ask me the destionation for metadata and excution. i import service from service registry. what does the service configuration mean? and if i choose no service group, where should i configure the destination?thanks

Hi Lei,
The metadata and execution destinations are relevant for runtime. On runtime you web dynpro application will access the web services you imported via these two destinations.
You can configure the metadata and execution destinations in the following location:
login on the CE system Netweaver Administrator: http://hostname:portnumber/nwa
On NWA navigate to SOA Management --> Technical Configuration --> Destination Template Management.
In this section of NWA you can define the Metadata and Execution destinations for your web services.
Please check the following blog for more information:
How to Consume an Enterprise Service from the ES Workplace in Web Dynpro in the new SAP NetWeaver Composition Environment 7.1
Regards,
Yasar

Using EJBs in Web Dynpro

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Thanks for your reply and your suggestion. I have posted in the Web Dynpro Java forum... and suggest those wishing to participate in this thread to refer to the Web Dynpro Java forum.
As for your answer, I'm afraid it doesn't satisfy me.
Reuse is hardly an issue, since the CommandBean is specifically tailor-made for the Web Dynpro application that needs to use it. I could hardly imagine building another application that would just happen to have the exact same needs as far as data structure and processing is concerned...
As for the right Eclipse environment... the CommandBean is not an EJB artifact - it is an EJB client. The aforementioned tutorial in fact suggests creating it in the Java perspective.
But thanks anyway for your time and suggestion

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Can a PDF be imported in a Web Dynpro Application

Can a PDF be imported in a Web Dynpro Application than deployed into a New Archive and be able to displayed in the browser? Instead of creating the PDF from scratch.

I am sorry, I did find the tool menu.
I did import it and created the datasources for the form.
And I get this error messege when I deploy:
Error stacktrace:
java.lang.ClassCastException
     at com.acc.demo.salestaxreturn.wdp.IPrivateSalesTaxReturnCompView$IContextElement.wdSetObject(IPrivateSalesTaxReturnCompView.java:201)
     at com.sap.tc.webdynpro.progmodel.context.AttributePointer.setObject(AttributePointer.java:222)
     at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:106)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1085)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:393)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     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:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Debugging into web dynpro

Hi there,
How can I step into web dynpro component while debugging a process?
Regards,
Ricardo Giacomin

Hi
1.Enable remote debugging(external breakpoint) on function module
2. Use same UserID that enables debugging and used in JCo Connection.
3. Run your application, it will take you to SAP GUI screen when breakpoint found.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0e9a9d90-0201-0010-478e-991dbea73a30

How to call a method of a zclass into web dynpro application

How to call a method of a zclass into web dynpro application

Hi,
if the method is of type static then u can access it directly as below.
call method class_name=>method_name
If the method is instance method then U need to create the object of that class. then through this object u can access the method.
CALL METHOD Obj_name->method_name

How to inject external configuration into web dynpro application

Hi colleagues,
I've a web dynpro application, which has some hard coded hostnames in the source code.
All hard coded hostnames should be moved to some else place, either engine parameters or external configuration file.
Searching over the project, hard coded hostnames were found in following file types:
- wdmodel files
- properties files
- java files
How to inject external configured hostnames into web dynpro applications, especially wdmodel and property files? Are threre best practices?
Thanks for any hint!
Best regards
Daniel

property file is supposed to do that job, you can configure the value at nwa after the application is deployed.
Configuring a Web Dynpro Application (Java) - IT Scenarios at a Glance - SAP Library

How to import an image icon into Web Dynpro for Java project

Dear Experts,
I would like to have a "select all" button which has an image of a standard "Select ALL" icon in SAP R/3. Where do I store the icon in my Web Dynpro for Java Project?
Any help would be very appreciated.
regards,
Shoira

Hi Shoira! 
 
You have to use the following path: 
<your workspace>\LocalDevelopment\DCs\demo.sap.com\<your UI component>\_comp\src\mimes\Components\<your component> 
 
Best regards, 
 
Christoph

Problem in Importing DC in Web dynpro

Hi All,
I am not able to import a DC project in web dynpro.
I followed the help guide according to which i opened the development configuration perspective and local view inside that.
Problem is that the DC folder which is to be imported is not visible in the MyComponent tree. I have copied the folder in .dtc/local development.
Please help me out. Purpose is to integrate 3 modules into 1 which have been developed at 3 different systems.
Thanks in advance!

Anubha
If you are using NWDI you must login and then you will see active , inactive and local tabs.You have to open the local tab and then if you open the Mycomponents tree you will find your DC for importing.
Award points if useful !!!

Using EJBs in Web Dynpro and others model tecnology patterns

I'm having difficults in order to implement the business logic in Java.
I did a simple application and I put all business rules inside de controller in the web dynpro. Everything is ok to users, but I know that this isn't indicate.
I tried to encapsulate de business rules and dao in a session bea, but I'm not sucessfull. I'd like to receive advices/tutorial about model, I found some treads in the forum, but almost all links in the sdn are browke. I was thinking in using hibernate and spring, but I don't know with it's a good choive to sap world.

Hi,
try these tutorials:
(ejb) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c
(hibernate) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/14f55178-0801-0010-0bac-974ed17e51d3
Regards
Ladislav
PS. Consider rewarding helpful answers

"Unable to log URL" error when importing WSDL into Web Service connection

Hello Experts
I'm using Xcelsius Engage and I'd like to use Web Service connection.
I've developed my own Web service (that is using 2 other web service inside it).
and now I'm trying to import it into the Xcelsius (connection --> Web service connection).
And I get the follwoing error:
"Unable to log URL"
When I browse to my wsdl file in IE the file is loaded with no problem.
When trying to import other URLs it also works fine (for example: http://www.xignite.com/xFinancials.asmx?wsdl)
Any idea?
Thanks,
Miki

Hi Matt
Thanks a lot!!!
Indeed the solution was in the follwoing thread:
VB.net code to create XML
Parsing the query result fixed the problem.
For others who might have the same problem:
Here's a working web service (C# code, for vb code follow the link to the thread above):
public Service () {
 public struct QueryResult
 public string SlpName;
 public string Commission;
 [WebMethod]
public QueryResult[] RunQuery()
 // Open Connection - Query Data from DB table - Close connection
 SqlConnection connection = new SqlConnection("Data Source=(local);Integrated Security=SSPI;Initial Catalog=SBODemoUS");
 SqlDataAdapter adapter = new SqlDataAdapter(
 "SELECT SlpName, Commission FROM OSLP", connection);
 DataTable DT_QryResult = new DataTable();
 adapter.Fill(DT_QryResult);
 connection.Close();
 // Parse data to be forward to Xcelsius
 QueryResult[] QryRes = null;
 QryRes = new QueryResult[DT_QryResult.Rows.Count];
 int i=0;
 foreach (DataRow row in DT_QryResult.Rows)
 QryRes.SlpName = row["SlpName"].ToString();
 QryRes.Commission = row["commission"].ToString();
 i++;
 return QryRes;
Best regards,
Miki

Error when importing an old web dynpro project

Hi all,
I've have upgraded my Sap Netweaver Developer Studio from 2.0.13 to 7.0 .
Now when i try to compile my old WD project it returs the seguent errors:
1)The project was not built since its classpath is incomplete. Cannot find the class file for java.lang.Object. Fix the classpath then try rebuilding this project
2)This compilation unit indirectly references the missing type java.lang.Object (typically some required class file is referencing a type outside the classpath) PackagePointer.java Project/gen_ddic/datatypes/com/sap/function/model/types line 1
Where can i find the java.lang.Object?
thanks, Daniele

Hi all,
maybe is too late.. but I wish to share my humble experience with you.
I encounter in a similar problem...
When I'm working with Web Dynpro (Messagge Pool) suddenly the NWDS seems to be crazy and give me the error "this compilation unit indirectly references the missing type java.lang.Object "
I read many post, this one too, but still got the problem.
Compare the current WD project with another one I found that my project didn't have rt.jar ibrary in its library list.
So I add in WD project - properties - Java build Path - Libraries the rt.jar library.
In my case it was in C:\j2sdk_dir\jre\lib\rt.jar.
So I build project and the problem desappear.
I hope this experience will be usefull.
Cristian

Importing EJBs into web dynpros

Similar Messages

Maybe you are looking for