Migrating Dynpro Projects to DCs

Hi,
Asume that we've created lots Dynpro projects before NWDI. Now we've configured NWDI for general usage and we want to migrate our Dynpro Projects into DCs under NWDI.
1. Which one is preferred? NWDI or JDI?
2. Is it feasible to create a DC and move all the Applications and Components under it, so all projects are collected under a single DC? Or we must prefer to create seperate DCs for each Project?
Which approach is best?
Best Regards

Hallo Huseyin,
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/bd0e0401-0801-0010-aaab-d0e1742da383">designing Component-Based Web Dynpro Applications (38)</a> - Documentation: SAP TechEd '05 material on Web Dynpro Componentization - pages 10-14.
Best regards, Bertram

Similar Messages

Query related to Migrating non Dc Web dynpro project to DC.

Hi All,
I have the requirement to migrate a non DC Web dynpro project to DC.
I have a project which involves few models.The models are nothing but BAPIs released as web services. So, when I am trying to do what i intend to do, I am getting compile time errors and I am not able to deploy.
WHAT I AM DOING?
I am cerating an empty DC project. I am giving the Name and keeping the domain as basis which comes as the default one.
Later I am moving to the Navigator tab and trying to copy and paste the packages under src and the model folder.
Coming back to the web dynpro tab, i am trying to rebuild the newly created DC project. here i am getting thousands of compile time error.I have even tried changing the domain as enterprise portal while creating the DC project. But the result is same.
Kindly through some lime light on this.Its very urgent and I am still not very clear with componentization in web dynpros.
Looking forward to you.
Regards
DK

Hi DK,
Follow this procedure to Migrate Local Web Dynpro to DC Component.
Creating a New Development Component
1. Create a new Web Dynpro DC Project [Page 5].
You create an empty container for a Web Dynpro DC that does not have
functions. The new DC should include all relevant development objects
project.
Do not check the newly created DC into the DTR yet.
1.Copying Packages from the Local Project
2. In the Web Dynpro perspective, switch to the Navigator view.
3. Select the local Web Dynpro project to be migrated and expand the project
down to the source folder: <My_Local_Project> src packages.
4. Select all packages and choose Copy using the right mouse-click.
Inserting Packages into the New DC Project
5. Now choose the DC project that was just created and expand the project structure in
the Navigator view, again down to the source folder.
6. Select the Packages node and choose Paste.
The Add Files to DTR dialog box appears.
7. Choose OK to confirm your selection.
8. Assign a DTR activity either by creating a new activity or choosing an existing one.
Execute Reload
9. Switch to the Web Dynpro Explorer.
10. Choose the project node of the DC project and select the Reload function.
11. In the displayed dialog box, again choose Reload.
Reload now also reloads Web Dynpro metadata into the new project.
Building the Project
12. Execute a local rebuild for the entire DC project. Choose the function Rebuild
project.
13. If there are no errors in the task view, execute a DC-based build by choosing the
function Development Component Build.
This build is identical to the central build tool and is required to take dependencies of
DCs among each other into consideration.
Result
You have migrated your local Web Dynpro project into a DC project. You can now deploy the
new DC into your local environment and test it before you commence checking the assigned
activity into the DTR.
After all these steps, when you reload your project, if you happend to see errors in your project. Check few things.
- All the model classes has been genreated or not.
- Close the project and open it again, sometimes it works fine.
- Findout what is the reason for errors, any thing is missing.
Regards,
Sridhar
Message was edited by:
Sridhar kanchanapalli

Migrate Web Dynpro Project to NWDI through DC

Hi All,
I have a requirement which i need to migrate the local Web Dynpro projects to NWDI to make it in central location.
I have developed the Web Dynpro project which is local to my system (includes model creation - deprecated type).
I need to integrate/migrate these Web Dynpro projects into NWDI.
As i did copy & paste of src folder and did creating new model after deleting the existing model.
After these I am able to build the project however I am getting the below error message while deploying it to Sandbox system.
Error Message:-
Result
=> deployment aborted : file:/C:/DOCUME1/gssvkria/LOCALS1/Temp/temp8746sap.comhomecountry.ear
Aborted: development component 'home/country'/'sap.com'/'NWD_FASTPRJ_D'/'20111214124617'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application sap.com/homecountry.. Reason: Clusterwide exception: Failed to deploy application sap.com/homecountry. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/home~country. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Please someone help me to understand this deployment exception and to resolve as well.
Thanks in advance.
Rgs,
Vijay
<< moved by moderator - check out the list of other forums on top of portal forum >>
Links to other forums
Edited by: Anja Engelhardt on Dec 14, 2011 1:44 PM

It seems you are using some DC references in your local DC which are missing on server...
Please refer :
http://help.sap.com/saphelp_nw70/helpdata/en/42/c8204dd57f136fe10000000a1553f7/content.htm
specifically look for "Reload" in above link..
also refer :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4032dae5-b951-2b10-d380-f4f6bedbbf37?QuickLink=index&overridelayout=true

Migrating Local Web Dynpro Projects to the JDI -- labels missing

Hi all
I am trying to Migrating Local Web Dynpro Projects to the JDI .But the labels are missing..?.
The runtime output is coming well. Any suggestions.Do any of you come accross this problem before?.help appreciated and I promise to award full points for best solution
Thank you
Regards
Maruti

Hi Maruthi,
Please look at this link,
Re: How to modify ESS ii views code which are imported from NWDI to NWDS
Thanks,
Raj.

Using External JARs in a Web Dynpro Project

Hi,
I'm having some difficulties building and deploying a Web Dynpro application that uses the Apache JaxMe libraries. We're using SP11 of Developer Studio and WebAS and we're using JDI Scenario 2+ for building and deployment. Thus far here's the procedure I followed:
1) Created a DC of type "External Library"
2) Added the necessary jars to the "libraries" folder of the External Library DC project (the jars that I added were jaxme2-rt.jar, jaxme2.jar, jaxmeapi.jar, jaxmejs.jar, jaxmepm.jar, jaxmexs.jar, xercesImpl.jar, xml-apis.jar all of which were pulled from the Apache JaxMe implementation download)
3) For each of the jars in the libraries folder I right-clicked, selected Develoment Component then clicked "Add to public part"
Then after reading this note:
https://websmp206.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000038152005
I created a J2EE Library Component DC following these steps:
1) Created a new DC of type J2EE Server Component / Library
2) Added the External Library DC that I had just created as a "Used DC"
3) Edited the DC so that it is used a Build Time and Run Time
Finally I went to the Web Dynpro application and included the J2EE Library Component DC as a Used DC at build time and run time.
I was able to build all of the project successfully (doing a DC build for each) then I was able to succesfully deploy the applications to my local development WebAs (by doing a DC deploy for both the J2EE Server Component and the Web Dynpro application) The problem is that at runtime the Web Dynpro application cannot find the external libraries. For example, I receive the following error when running the application:
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
The "missing" class is included in one of the jars but for some reason these jars are not accessible to Web Dynpro at runtime.
Any help you can provide on this problem is very much appreciated.
Thanks in advance!
Jason

I created the JAR with the following class (structure):
com.sap.tc.webdynpro.tests.utils.TableSorter.class
I have followed the steps that was suggested in the forum:
==========================================================
1) creating an Extneral library DC
2) import the JAR "com.sap.tc.webdynpro.tests.util.jar" to the libraries folder of the External Library DC project
3) Right-click on the JAR imported to the project and add them to the public part.
This DC is now ready to be used as a build-time reference that will allow CBS to build the "main" Web Dynpro application that will use the external libraries. Next, we have to create a new Web Dynpro DC to hold the class files here are the steps:
1) Create a new Web Dynpro DC
2) Create a new public part, selecting the "Can be packaged into other build results" option
3) Rename the JARs as Zip files and extrct the full content (folders and class files) to your root folder
4) Import the folders and files to the src/packages folder
5) Expand the public part node that was created and select the "Entities" node, right-click it and choose Edit
6) In the Entity Type list select the "Folder" option then in the selected entities tree pick each of the folders that you imported in step 5 (above)
7) Now do a DC build and a DC deploy of the project
Then check-in, activate, and release any activities you have associated with creating these two projects. In the DC perspective, refresh the Active DCs and Inactive DCs to ensure that both new DCs appear in the Active list. Now we have to setup the references to these DCs in our main Web Dynpro application. To do this, follow these steps:
1) Open the Web Dynpro perspective and right click the Used DCs node then choose "Add Used DC.."
2) Pick the public part of the External Library DC that we created (first) and set it to have a Build Time dependency
3) Again, right click the Used DCs node and choose "Add Used DC.." then choose the public part of the Web Dynpro DC that we created and give it a Run Time dependecy (weak) and click finish.
4) Now, due to what I think is a bug. You must right click on the Web Dynpro "used DC" that you just added in the previous step, and set the run time dependency again (it seems to revert to the default values for some reason)
5) Now do a DC build and a DC deploy on the "main" web dynpro application.
6) Check-in, activate, and release any activities associated with adding these references and then others on your team may use the classes in the external libraries within the Web Dynpro project.
However, when I executed, the following exception occurred:
===========================================================
Error stacktrace:
java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/tests/utils/TableSorter
at br.com.embraer.materiais.zdplmm001.view.Zdplmm001_0500View.wdDoModifyView(Zdplmm001_0500View.java:138)
What's missing????
Thanks
Robson Lima
Sao Paulo - Brazil

Error in web dynpro project build

Hi All,
My web dynpro project which was running absolutely fine earlier is now facing certain build and deployment problem.
The build log is as follows:
Jun 25, 2007 2:16:28 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: sox_p3v1: Build failed for sap.com/sox_p3v1(MyComponents) in variant "default":
The Build terminated with errors
Build log -
Build Plugin Version: 1.6.3 (630_REL) from 03 November 2004 12:47:57
Start: 25.06.2007 02:16:23
Temp dir: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F
prepare:
 [mkdir] Created dir: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\DCs\sap.com\sox_p3v1\_comp\gen\default\deploy
 [mkdir] Created dir: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\gwd\packages
gen:
 [ddgen]
 [ddgen] [Info] Property deployment is true: Deployment information is provided!
 [ddgen] [Info] Property sourcepath: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\DCs\sap.com\sox_p3v1\_comp\src/packages
 [ddgen] [Info] Property targetpath: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F/gdd
 [ddgen] [Info] Property archivename: sap.com~sox_p3v1
 [ddgen] [Info] Property vendor: sap.com
 [ddgen] [Info] Property dcname: sox_p3v1
 [ddgen] [Info] Property language: Available languages are automatically determined!
 [ddgen] [Info] Property addpaths ...
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_JTECHS/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] Destination directory C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\gdd does not exist
 [ddgen] [Info] Destination directory C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\gdd is created
 [ddgen] [Info] Initialize generation templates from configuration jar:file:/E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/dict/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/severity.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/PackagePointer.java
 [ddgen] [Info] Generating datatypes/com/sap/hcl/tree/parant.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/tree/PackagePointer.java
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/noanswer.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/PackagePointer.java
 [ddgen] [Warning] Simple type com.sap.hcl.assessmemt.noanswer is generated with warnings
 [ddgen] [Warning] mdoTexts: The text consists only of special characters and/or numbers. ;
 [ddgen] [Info] Generating datatypes/com/sap/hcl/tree/iconproc.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/risk/impact.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/risk/PackagePointer.java
 [ddgen] [Warning] Simple type com.sap.hcl.risk.impact is generated with warnings
 [ddgen] [Warning] mdoTexts: The text consists only of special characters and/or numbers. ;
 [ddgen] [Info] Generating datatypes/com/sap/hcl/control/effectiveness.gsimpletype
 [ddgen] [Info] Generating datatypes/com/sap/hcl/control/PackagePointer.java
 [ddgen] [Warning] Simple type com.sap.hcl.control.effectiveness is generated with warnings
 [ddgen] [Warning] mdoTexts: The text consists only of special characters and/or numbers. ;
 [ddgen] [Info] Generating datatypes/com/sap/hcl/risk/likelihood.gsimpletype
 [ddgen] [Warning] Simple type com.sap.hcl.risk.likelihood is generated with warnings
 [ddgen] [Warning] mdoTexts: The text consists only of special characters and/or numbers. ;
 [ddgen] [Info] Generating datatypes/com/sap/hcl/risk/structRisk.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/control/structControl.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/issue/structIssue.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/issue/PackagePointer.java
 [ddgen] [Info] Generating datatypes/com/sap/hcl/tree/structTree.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/structAnswer.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/structAuditInfo.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/structAudit.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/structAuditee.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/QuestionnaireInfo.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/task/structTask.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/task/PackagePointer.java
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/structQuestionnaire.gstructure
 [ddgen] [Info] Generating datatypes/com/sap/hcl/tree/simpleTypesResource.properties
 [ddgen] [Info] Generating datatypes/com/sap/hcl/control/simpleTypesResource.properties
 [ddgen] [Info] Generating datatypes/com/sap/hcl/assessmemt/simpleTypesResource.properties
 [ddgen] [Info] Generating datatypes/com/sap/hcl/audit/simpleTypesResource.properties
 [ddgen] [Info] Generating datatypes/com/sap/hcl/risk/simpleTypesResource.properties
 [ddgen] [Info] Generating dbtables/sdmDeployDd.xml
 [ddgen] [Info] Generation finished (3 seconds)
 [ddgen]
 [wdgen]
 [wdgen] [Info] Property deployment is true: Deployment information is provided!
 [wdgen] [Info] Property sourcepath: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\DCs\sap.com\sox_p3v1\_comp\src/packages
 [wdgen] [Info] Property targetpath: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\gwd
 [wdgen] [Info] Property archivename: sap.com~sox_p3v1
 [wdgen] [Info] Property vendor: sap.com
 [wdgen] [Info] Property dcname: sox_p3v1
 [wdgen] [Info] Property language: Available languages are automatically determined!
 [wdgen] [Info] Property addpaths ...
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_JTECHS/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_JTECHS/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] Initialize generation templates from configuration jar:file:/E:/Program Files/SAP/JDT/eclipse/plugins/com.sap.tc.ap/comp/SAP_BUILDT/DCs/sap.com/tc/bi/wd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
 [wdgen] [Info] Generating portalapp.xml
 [wdgen] [Info] Generating wd.xml
 [wdgen] [Info] Generating application.xml
 [wdgen] [Info] Generating application-j2ee-engine.xml
 [wdgen] [Info] Generating PublicPartFileList.properties
 [wdgen] [Info] Generating PublicPartFileList.xml
 [wdgen] [Info] Generation finished (0 seconds)
 [wdgen]
 [mkdir] Created dir: C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\classes
 [javac] Compiling 7 source files to C:\Documents and Settings\anubha.pandey\.dtc\LocalDevelopment\t\FD7EA53918BB25A337D8FEA68F2A940F\classes
Build with ERRORS
java.lang.UnsupportedClassVersionError: com/sun/tools/javac/Main (Unsupported major.minor version 48.0)
 at java.lang.ClassLoader.defineClass0(Native Method)
 at java.lang.ClassLoader.defineClass(Unknown Source)
 at java.lang.ClassLoader.defineClass(Unknown Source)
 at com.sapmarkets.technology.classloader.ExtendedClassLoader.access$001(ExtendedClassLoader.java:21)
 at com.sapmarkets.technology.classloader.ExtendedClassLoader$1.run(ExtendedClassLoader.java:702)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapmarkets.technology.classloader.ExtendedClassLoader.findClass(ExtendedClassLoader.java:688)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClass(Unknown Source)
 at java.lang.ClassLoader.loadClassInternal(Unknown Source)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Unknown Source)
 at org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.doesModernCompilerExist(CompilerAdapterFactory.java:173)
 at org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:131)
 at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:835)
 at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
 at org.apache.tools.ant.Task.perform(Task.java:341)
 at org.apache.tools.ant.Target.execute(Target.java:309)
 at org.apache.tools.ant.Target.performTasks(Target.java:336)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
 at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:130)
 at com.sap.tc.buildplugin.techdev.webdynpro.BuildAction.execute(BuildAction.java:79)
 at com.sap.tc.buildtool.PluginHandler.handlePluginCommunication(PluginHandler.java:616)
 at com.sap.tc.buildtool.PluginHandler.execute(PluginHandler.java:220)
 at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1131)
 at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:4713)
 at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:301)
 at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
 at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:206)
 at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
End: 25.06.2007 02:16:28 (Duration: 4 seconds)

hi Anubha:
This isnt a web dynpro error. This is an error regarding the java installtion of your machine. I guess there is a mis match between the JDK and the JRE verions installed. Kindly uninstall the jre and jdk and freshly install jdk 1.4.2_10 and let me know what happens.
P.S: Kindly assign points if your query is resolved, also close the question to assist other users narrow the search and find solutions

DC Build Error with Web Dynpro Project

Hi,
I have created a DC Project and migrated all the local Web Dynpro project to the DC project which is connected to NWDI.
When I performed a Development Component Build, I am getting tons of errors like this :
C:\Documents and Settings\mlee20\.dtc\1\t\E9C452A69844E0F9849D478F81878AB9\gwd\packages\com\bhpb\totalcomp\TestConnect.java:26: package com.sap.ip.bi.sdk.dac.result.model does not exist
import com.sap.ip.bi.sdk.dac.result.model.BITableItem;
                                          ^
C:\Documents and Settings\mlee20\.dtc\1\t\E9C452A69844E0F9849D478F81878AB9\gwd\packages\com\bhpb\totalcomp\TestConnect.java:27: package com.sapportals.connector.connection does not exist
import com.sapportals.connector.connection.IConnectionFactory;
                                           ^
C:\Documents and Settings\mlee20\.dtc\1\t\E9C452A69844E0F9849D478F81878AB9\gwd\packages\com\bhpb\totalcomp\TestConnect.java:28: package com.sapportals.connector.connection does not exist
import com.sapportals.connector.connection.IConnectionSpec;
                                           ^
C:\Documents and Settings\mlee20\.dtc\1\t\E9C452A69844E0F9849D478F81878AB9\gwd\packages\com\bhpb\totalcomp\WealthView.java:25: package com.sap.security.api does not exist
import com.sap.security.api.;*
^
C:\Documents and Settings\mlee20\.dtc\1\t\E9C452A69844E0F9849D478F81878AB9\gwd\packages\com\bhpb\totalcomp\WealthView.java:29: package com.bhpb.bi does not exist
import com.bhpb.bi.BITable;
                   ^
I have included a jar file BIWrapper.jar in the lib folder....
Does it mean that some of the dependencies jar files is needed in the NWDI?
For anyone help please.
Thanks.

Hi,
Create an Dc of type external library which contains the BI Wrapper
and refer this dc from your WD.
This blog will help you in creating external /people/valery.silaev/blog/2005/09/14/a-bit-of-impractical-scripting-for-web-dynpro
Regards
Ayyapparaj

Creating Web Dynpro Project in JDI

Hi,
I'm having difficulty creating a simple Web Dynpro project in a DC in JDI. I'm trying use Scenario 2+. When I try to build the DC containing the WDP project in the DC View, I get the following error:
Apr 25, 2005 6:15:48 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: hello: Build failed for meridium.com/hello(meridium.com_APPLICATION_1) in variant "default": Used component not found: sap.com/tc/bi/bp/webDynpro
In the Web Dynpro perspective of the same project, the project cannot be built until I modify the .classpath file to modify the build path to include all of the jars reference in a WDP project.
How do I identify the components that are to be used for a Web Dynpro application? Is this done in the SLD? If so, which dependencies should I assign? Are there any step-by-step examples of creating a WDP application in JDI scenario 2+?
Thanks.
Rob

Thanks for your response.
I took a look at the .dcdef file and it looks like it defines the proper DCs for a WDP project (see below). The problem seems to be that the files defined in these dependencies can't be located. The build error says "Used component not found: sap.com/tc/bi/bp/webDynpro" which is defined in the .dcdef file below. How do I specify where to find the dependent files?
<?xml version="1.0" encoding="UTF-8"?>
<development-component
 xmlns="http://xml.sap.com/2002/11/DevelopmentComponent"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://xml.sap.com/2002/11/DevelopmentComponent dcdef.xsd"
 version="1.0.2"
 xmlns:IDX="urn:sap.com:DevelopmentComponent:1.0">
 <name>hello</name>
 <vendor>meridium.com</vendor>
 <caption>Hello </caption>
 <component-type>
 <vendor>sap.com</vendor>
 <type>Web Dynpro</type>
 </component-type>
 <properties>
 <ns0:localization xmlns:ns0="http://xml.sap.com/2003/06/Localization">
 <ns0:domain>CA</ns0:domain>
 <ns0:originalLocale>en</ns0:originalLocale>
 </ns0:localization>
 </properties>
 <build-plugin>
 <dc-ref>
 <name>tc/bi/bp/webDynpro</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>webDynpro</pp-ref>
 </build-plugin>
 <dependencies>
 <dependency>
 <dc-ref>
 <name>tc/cmi</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>tc/ddic/ddicruntime</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>tc/ddic/metamodel/content</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>tc/wd/webdynpro</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>tc/logging</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>tc/wdp/metamodel/content</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>com.sap.aii.proxy.framework</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>com.sap.aii.util.misc</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>com.sap.exception</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 <dependency>
 <dc-ref>
 <name>com.sap.mw.jco</name>
 <vendor>sap.com</vendor>
 </dc-ref>
 <pp-ref>default</pp-ref>
 <at-build-time/>
 </dependency>
 </dependencies>
 <folders>
 <source-folder>META-INF</source-folder>
 <source-folder>src/mimes</source-folder>
 <source-folder>src/configuration</source-folder>
 <package-folder>src/packages</package-folder>
 </folders>
</development-component>
-r

Migrating WebDynpro Projects for 6.40 based developments

Hi,
We have a lot of webdynpro projects developed as standalone projects. The version of developer studio used 2.0.X. The Web AS server version is 6.40.
Are there any tools or standard options available for migration of this projects to DCs. ?
In CE , there are some tools available for the same. But we want to do this migration of Web AS 6 40.
Any sugggestions would be very helpful.
Thanks and Regards
Bharathwaj

Hi,
You can create a DC from existing proejct. Follow the steps given below:
File->New->Development Component Project ->Local Development ->My Components->Click on Next->Give some Name to DC->select Type as WenDYnpro->Click on Next
->Now check the check box "Import content from existing local project ->Now select the project you want convert to DC->click on finish.
New DC will be created.
Thanks & Regards,
Jhansi Miryala

Got reading error when deploying a web Dynpro project

Hi everyone,
I'm working on NWDS 7.1 CE. After I synchronized a project (using the "Create Project" option), then Build and Deploy it under the Development Infrastructure perspective, I can run it by choosing the "Run" option of the web Dynpro project's application. But once I chose "Deploy new arcihve and run", I got the following error message:
[ERROR CODE DPL.DC.3095] A reading error occurred while loading the SDU 'D:/usr/sap/DW1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/3888/dow.comgcacmpprofitcenterui.ear'.; nested exception is:
     com.sap.engine.services.dc.util.readers.sdu_reader.SduReaderException: [ERROR CODE DPL.DC.3388]
The specified file D:/usr/sap/DW1/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/3888/dow.com~gca~cmp~profitcenter~ui.ear is not a valid SAP deployable unit. In case it is Java Enterprise application, please convert it to SAP compatible deloyable unit first.
Additional information: 'The information about the development component found in the manifest is either missing or incomplete!
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Does anyone know what happens here? What's the difference of the Build/Deploy commands under Web Dynpro perspective and under Development Infrastructure perspective? After I made changes to the project, can I just deploy it under the Development Infrastructure perspective?
Thanks,
James

Hi Nilesh,
       Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
       Deploy now...Other wise see this thread same error solved:
Re: An Deploy Problem about Credentials.
Regards
Suresh

Import/export issue to migrate the project

Hi,
I am trying to migrate a project from 1 server to another server.
I exported the project and model from my current server, and imported them to the new server. the thing is, the senario can be run successfully, but when I open the interface in designer, the source table cannot get any definition, all the columns in the source table won't show up. it looks like to me is that the interface lost the connection of the data store in the model.
Anybody has any idea how to fix it?
Thx

Hi
If its a fresh imploementation then its fine.
Say yu migrated the ODI objects to prod and you face an issue.
you have fixed it in development and want to move it to prod.
How do you handle this scenario.
Please let us know the process that you are following

How to add a javabean Model to a web dynpro Project

Hi all,
I have been following the tutorial "Using EJBs in Web Dynpro Applications" for creating a customized LOCAL webdynpro application, based in javabean Model. It was made by just exporting the JAR file from a java project, as it is explained in the tutorial. OK.
The problem comes when I want to duplicate the development but using a DC Web Dynpro Project. I have re-develop every step of the tutorial but using DC projects:
DC diccionary project, DC ejb project, DC enterprise application project & DC java project.
But now I DO NOT KNOW the steps for importing the development into a model for DC Web Dynpro.
Anyhelp will be very appreciated, thanks in advance-

Thanks Jhansi,
Yes, you are right. I had already followed those steps. The error comes when I have to select between the JavaBean Source:
1. project (source folder) (checkbox)
2. public parts of used DC's (combobox)
I have been trying both, the second one by copying first the JAR called CommandBean.jar of my DC Java Project with dependencies to EJB project into the web dynpro "lib" folder, and then selecting the new entry CommandBean.jar from that combobox.
then i get de following error: "Invalid JAR - No JavaBeans available for import"
So I do not know how to use any of these two options for java source.
Thanks.

How to add new class to existing DC (Web Dynpro project)

Hi,
How can I add new class to an existing DC (Web Dynpro project)?
I tried adding it using File - New - Other - Java - Class, but after a build of the DC the new class (and its contents ) was completely removed.
Then I created a new DC (java project) and created a new class in that DC. This went fine, but I got into problems because of circular referencing between the new & the old DC, so no build was possible.
This can't be difficult, does somebody knows how to do it?
My temporary solution is to add the classdefinition to an exisiting .java file. Very ugly.
Thanks,
Jeroen

Hi Jeroen,
where did you create the class? If the *.java file is placed in the src/packages folder it should not be deleted by a build. (I suspect you created it in the gen_wdp folder?)
Regards,
Marc

Create adaptive web service model for a web dynpro project

I have been trying to create a new new adaptive web service model for a web dynpro project.I am using the URL of the wsdl file to create the model. I have copied the url link of the wsdl from the overview tab of the web services navigator. The web service works fine when tested through the Netweaver Navigator. This web service has also been used successfully through the Visual Composer. But when I try to create a model for this web service URL, when I click the Next button after entering the URL in the model creation wizard step 4 , I get "Error loading wsdl file. Check error log for details" Given below is the exception recorded in the error log: (Infact, I get this for all wsdl URLs)
!MESSAGE Jun 6, 2007 9:44:59 AM com.sap.ide.webdynpro.ui.service.ServicesUI [Thread[main,5,main]] Error: Internal error
 Plugin name: Web Dynpro Model Editor
 Plugin ID : com.sap.ide.webdynpro.modeleditor
 Class : com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS
 Method : loadNameSpacesAndModelClasses
 Message : Cannot load NameSpaces and ModelClasses
Class Path: C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;
java.home: C:\java\j2sdk1.4.2_09
proxyHost:
proxyPort:
nonProxyHosts:
Temporary Directory: C:\DOCUME1\E51914\LOCALS1\Temp\
WSDL URL: http://etcvpcod108:50100/UserService/Config5?wsdl
 Exception : com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL http://etcvpcod108:50100/UserService/Config5?wsdl and service factory configuration {DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}
!STACK 0
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://etcvpcod108:50100/UserService/Config5?wsdl' and service factory configuration '{DynamicProxy.ClassPath=C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.cmi_1.0.0/_cmi_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.exception_2.0.0/lib/exception.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/boot.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/iq-lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/util.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/webservices_api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.engine.webservices_2.0.0/lib/tc_sec_wssec_lib.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.runtime_2.0.0/lib/SapDictionaryTypesRuntime.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.dictionary.services_2.0.0/lib/SapDictionaryTypeServices.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/logging.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/loggingStandard.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.logging_2.0.0/lib/jARM.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.tssap.sap.libs.xmltoolkit_2.0.0/lib/sapxmltoolkit.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/activation.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxm-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/saaj-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jaxrpc-api.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jnet.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/jsse.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ext.libs.webservices_2.0.0/lib/mail.jar;C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.tc.webdynpro.model.webservice_2.0.0/lib/_webdynpro_model_webservice.jar;, DynamicProxy.INetProxy.Bypass=, DynamicProxy.INetProxy.Port=, DynamicProxy.Javac.path=C:\java\j2sdk1.4.2_09, DynamicProxy.TempDir=C:\DOCUME1\E51914\LOCALS1\Temp\, DynamicProxy.INetProxy.Host=}'
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:413)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:371)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:341)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:305)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:315)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.PageRenameWS.loadNameSpacesAndModelClasses(PageRenameWS.java:435)
 at com.sap.ide.webdynpro.modeleditor.wizards.model.creation.ModelDialog.nextPressed(ModelDialog.java:105)
 at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
 at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
 at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
 at org.eclipse.jface.window.Window.open(Window.java:563)
 at com.sap.ide.webdynpro.modeleditor.ModelEditorCallback.createModel(ModelEditorCallback.java:52)
 at com.sap.ide.webdynpro.service.modeleditor.ModelService.createModelWithUI(ModelService.java:70)
 at com.sap.ide.webdynpro.service.modeleditor.ServiceWithUI.createModel(ServiceWithUI.java:49)
 at com.sap.ide.webdynpro.tsmodel.application.provider.ModelNodeProvider.createUniqueName(ModelNodeProvider.java:55)
 at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntityUin(EntityImpl.java:936)
 at com.tssap.selena.impl.model.elements.EntityImpl.createChildEntity(EntityImpl.java:502)
 at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.runInternal(CreationAction.java:76)
 at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.access$000(CreationAction.java:24)
 at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction$1.run(CreationAction.java:51)
 at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
 at com.sap.ide.webdynpro.tsmodel.application.actions.CreationAction.run(CreationAction.java:57)
 at com.sap.ide.webdynpro.projectbrowser.actions.PBCreateModelAction.run(PBCreateModelAction.java:95)
 at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:224)
 at com.tssap.util.ui.menu.MenuFactory$MuSiAction.saveRunAction(MenuFactory.java:1425)
 at com.tssap.util.ui.menu.MenuFactory$MuSiAction.run(MenuFactory.java:1407)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:616)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:586)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:716)
 at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
 at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:610)
 at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
 at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
 at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
 at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
 at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
 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.ide.eclipse.startup.Main.basicRun(Main.java:291)
 at com.sap.ide.eclipse.startup.Main.run(Main.java:789)
 at com.sap.ide.eclipse.startup.Main.main(Main.java:607)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
 at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:149)
 at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:49)
 at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
 at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:411)
 ... 53 more

Hi Srikanth,
My version was
Version: 7.0.09
Build id: 200608262203
I was able to successfully import the model after I did the following
1. Re intsall Studion (same version , same build)
2. Reset the proxy settings to not use Proxy server
Thanks for looking into it though...
-Lakshmi

Accessing portal dictionary tables from Web Dynpro project

Hi
Am a new to whole portal and webdynpro thing, and I hope that you can help here
I created a new dictionary project through NWDS and created a table with columns and I successfully deployed it
I also created a web dynpro project and I added a TABEL UI to the layout
how can I connect or access the table I created in the dictionary project from the Web dynpro project so I can query all data to fill the TABEL UI in the web dynpro ?
is there a driver that I can use like JDBC where I can just write regular SQL queries ?
regards

Hi swathi
See the persistence API--Adv and Disadvantages what ever you mentioned come under the persistence API
Relational Persistence
=================
SQL-based coding: expressive!
SQLJ: for static SQL, checked at design time,
recommended
JDBC: for dynamic SQL, can be combined with SQLJ
=======================
Object-relational Persistence
======================
SQL-free! Portable!
JDO: light-weight object persistence, Java-like dynamic
query language
EJB CMP: part of J2EE standard, relatively heavy-weight,SQL-like static query language
Regards,
Venkata Kalyan Karanam

Migrating Dynpro Projects to DCs

Similar Messages

Maybe you are looking for