Versions in DTR

Hi Experts,
There are different versions of Development configuration on the track in the DTR. I am not sure, how to check the different versions.
Can any one please let me know how to access the different versions ?
or point me to any document where i can find it?
Thanks,
Raj

Hi raj,
If I have understood you clearly...my answers are below...
As far as I know there can be 2 development configurations for a track
1. Domain_TrackID_D(Dev)
2. Domain_TrackID_C(Cons)
Usually developers work with the dev configuration.
To access either of them you can just got to http://dtr:port/dtr and then you can click on ws when you will get to see various tracks stored in the DTR. And then if you further explore on each track you will the two configurations dev and cons both with the set of active and inactive DCs.
That's one point.
Now if you just want to look at the various versions of a file..YOu can check them via the developer studio using the version graph or revision history.
You question is little vague.What do you want to do exactly?
You can as well access the different versions of development configurations via the developer studio....
Akshatha

Similar Messages

How to get the latest version from DTR

Hi all,
I have all the latest code in my system 1 and i checkined the activites.Now i want all that code in my system 2.
Now i used sync from sources to get the lateset code.
But i am not able to get all the files and the build is getting failed.
Can any one plz help me out
Regards
Padma N

Hi,
Inorder to get the lateset version from DTR i used the procedure given by you.But at the second time if i want to get the lateset version from DTR wat to do??I didnt find the option of create project again because i already have to project in my workspace.
wat to do inorder to get the lateset source code from DTR 2nd time???
Regards
Padma N

Query Regarding DTR ?

Hi,
Can we maintain non java code (for ex: word documents, VB projects etc...) in DTR?
Is there a stand alone version of DTR which can be installed on client and used for check in and check out of the resources? ( not through Netweaver Developer Studio on Client Machines )
Thank You

Hi Reed,
Although a "slim" client would be ideal, the corporate users can also use only the DTR Perspective in NWDS to store their documents (or VB projects). The Eclipse architecture ensures that plugins are loaded on demand - so although NWDS contains many plugins, these will not be loaded so the memory footprint should not be so high.
To work with documents (or other projects), you need to proceed as follows:
1) Create a "Client" in DTR
2) Create a suitable hierarchy of "Workspace Folders","Workspaces" and "Folders"
3) Sync the empty folders to local machine, and under these folder place the files (and folders) you wish to add to DTR
4) Refresh the "Repository Browser", and you will see these "new" files and folders.
5) USe the context menu to "Add" these files/folders to an activity, and checkin the activity.
So you do not need a "project" in NWDS to store things in DTR - you can work purely from the DTR Perspective, and use it as a version control system to store your files of any kind.
Hope that helps.
Regards,
Manohar

DTR: How do I set an older version as active version

Hello,
Using the DTR I can sync to a specific Version of a File using "Sync to this version" from the context menu of the Version Graph.
Now I want to set the Version I synced to as the active version. Is there a possibility to do this?
Greets Johann

Hi
When I understand the question right, then the intension is to have an older version now as the current active version in the workspace on DTR.
Up to now DTR does not yet provide this functionality. But there is a workaround:
- please sync the file to the version that afterwards should get active (e.g. using context menu in version graph)
- and copy the synced file to a temporary location
- then sync the file again to the current active version
- and check-out for edit this version of the file
- then copy the older version from the temporary location over the checked-out version
- check-in
Please be aware that this changes the current active version in the workspace and that this change is visible to everyone accessing the workspace.
Regards, Uli

DTR a versioning system?

Hi,
as far as I know, DTR maintains DIFFERENCES, so there is IMHO not a real versioning, as for example compared with CVS, where you can go back to a certain version (number). In DTR you can, AFAIK only check out versions upto a certain date.
Is there any way to work, in DTR, with version numbers?

Hi Erik,
There is no revert command wherein you go back to a previous state of a workspace. However can you not propagate changes from another workspace to the current workspace.
I mean you already have the active and inactive workspaces. You can then propagate changes from the active workspace to the inactive one to restore to the last known active state.
I know this is not a direct way but then i feel this can be used effectively.
Please give your suggestions and lets try to compare DTR against other versioning tools.
Regards
Sidharth

Set older version as active in DTR

Hi community,
I'm struggling with this simple requirement. I want to to set an older version of a WD4J component as active. I can snych it to this version without any problem but when i try to edit and check in, it says that the source is out of synch and i can't do anything. What do i have to do to achieve this?
Many thanks,
Tobias

Actually i don't look for another "hack" and for web dynpro java this would be great pain to replace it all manually. So the NWDI does not provide this option? This is very very sad... but it fits perfect to some of the previous eyperiences i had with the SAP Java Development .
But thank you for your help Hamendra.
Regards,
Tobias

Reg: Open and Closed Activities in DTR

Hello Guru's,
I am confused with the Open and Closed Activities in DTR, What are the significance of these activities?
And when does an Open Activity changes to Closed Activity?
And why does an Empty Open Activity gets created?
How does the Open Activities effect the Performance of the system?
In NWDS what is the significance of the Public Part and the dcdef xml files?
Please explain and if possible send the links to better understand these? I tried searching for info but with no luck.
Appreciate the Help.
Thanks & Regards,
Pramod

Dear Pramod,
Activity in general can be considered as the wrapper of your changes.
While working in NWDI, any modification that you perform on your source code must be associated with an Activity.
Some Definitions:
Client DTR: Represents the Local Track file system present on you local machine, where Checked-out a desired code from Server DTR
Server DTR: Represents the Central Repository present on the server, where your source code is checked-in.
Open Activities
These are the activities that are not yet checked-in to Server-DTR, and they represent the Open Version.
Exmple:
1) Suppose you have made some modification in "File A" which is associated in Activity-1
2) When you open the DTR Perspective in your Developer studio, you will be able to see all the changes that you have associated in the Activity-1, this DTR-perspective of your NWDS is also termed as Client-DTR.
3) But, when you open the Server-DTR in DTR Web interface, you will not be able to see the same file structure that is present in your client DTR, it will not contain the changes that you have incorporated in Activity-1.
4) The changes present in Activity-A are not available to any other developers, even if you try to use the same developer ID and load the same track, the activities are still said to be purely Local.
Closed Activities
These are the activities that are already Checked-in to Server-DTR and they represent Closed Version.
Example:
1) In the same example explained above assume that we now Check-in the Activity-1.
2) Now, if you open the Server-DTR in DTR Web Interface, you will be able to see the same file structure that is present in your Client-DTR.
3) Now the changes that were present in Activity-A are also available to other developers too.
Open Activity and Performance
1) Open Activities create a temporary entry point reference on the Server DTR you can serach for open activities in Secer DTR web interface, every single activity occupies space on your local machine. So it may affect the performance only if the activity count is very high.
2) In the local file system, the meta data is stored in the .dcdef file in the _comp
subfolder.
3) The meta data is stored in the .dcdef file, every public part has its own meta data file. They are located in the def subfolder of the component and have the fileextension pp.
Every component (DC) is defined by a set of files, stored and versioned together with the
component in the repository.
u2022 A file with the reserved name .dcdef stores the basic attributes such as name,
description and component type, the parent component (if there is one), a list
of child components (if there are any), a list of dependencies, links to the component
sources, and the access control list. The .dcdef file must be stored directly
in the _comp folder.
u2022 The folder _comp/def contains one file for each public part of the component,
which carries the name of the public part with the extension .pp. This file contains a list
of the development objects belonging to the public part and an access control list for
this public part.
Both .dcdef and .pp files are stored in an XML-based format; you can display them in the
content display of the Repository Browser or with any text editor. However, this is
not necessary. To create and edit these files, use the component tools of the SAP NetWeaver
Developer Studio.
In exceptions, you can manually repair the .dcdef or a .pp file of a component.
Note that direct manipulations are dangerous and can render a component
unusable.
I hope you will get a clear picture now.
Regards,
Shreyas Pandya

Error when starting DTR Console on NWDI 7.31

Hi Guys
When starting DTR console from command line on a Windows 2008 OS, im getting the following error
S:\usr\sap\NDI\SYS\global\com.sap.dtr.console>run
S:\usr\sap\NDI\SYS\global\com.sap.dtr.console>java -Dhttp.readtimeout=0 -cp S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\sap.com~tc~dtr~console~all.jar;S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\sap.com~tc~dtr~cmdlineappfwk~all.jar;S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\antlr-runtime-3.0.1.jar com.sap.dtr.console.DTRConsoleApplication
Exception in thread "main" java.lang.RuntimeException: com.sap.dtr.cmdlinefwk.CommandLineException: Validation of the examples for the command "Discard" failed.
The example "discard -col -cip/collision/dce6250e4fd911dc81e400199905d653_3_b4c044e04fd511dccef000199905d653_b4c044d84fd511dca33b00199905d653_open_PredSucc" contains a command that is not valid against its specification.
        at com.sap.dtr.console.DTRConsoleApplication.registerCommandSpecs(DTRConsoleApplication.java:207)
        at com.sap.dtr.console.DTRConsoleApplication.initialize(DTRConsoleApplication.java:156)
        at com.sap.dtr.console.DTRConsoleApplication.<init>(DTRConsoleApplication.java:137)
        at com.sap.dtr.console.DTRConsoleApplication.main(DTRConsoleApplication.
java:311)
Caused by: com.sap.dtr.cmdlinefwk.CommandLineException: Validation of the examples for the command "Discard" failed.
The example "discard -col -cip /collision/dce6250e4fd911dc81e400199905d653_3_b4c044e04fd511dccef000199905d653_b4c044d84fd511dca33b00199905d653_open_PredSucc" contains a command that is not valid against its specification.
        at com.sap.dtr.cmdlinefwk.CommandLineApplication.addCommandLineSpec(CommandLineApplication.java:115)
        at com.sap.dtr.console.DTRConsoleApplication.registerCommandSpecs(DTRConsoleApplication.java:204)
        ... 3 more
Caused by: com.sap.dtr.cmdlinefwk.CommandNotSupportedException: Command 'discard' is not supported
        at com.sap.dtr.cmdlinefwk.support.parser.DefaultCommandLineParser.parse(DefaultCommandLineParser.java:57)
        at com.sap.dtr.cmdlinefwk.CommandLineApplication.addCommandLineSpec(CommandLineApplication.java:107)
        ... 4 more
Any idea what is missing? Im seeing the command line its showing S:\usr\sap\NDI\SYS\global\com.sap.dtr.console\antlr-runtime-3.0.1.jar, but this file is not present
Thesefiles are at OS level
Regards!

Hi,
i have also problem with launching DTR console. I followed this article for enabling it:
Starting Command Line Tools - Using the Development and Production Infrastructure - SAP Library
But when I try to start the console via Run, I receive this error:
eclipse.buildId=unknown
java.version=1.6.0_38
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Framework arguments: -application com.sap.di.cltools.dtrshell
Command-line arguments: -application com.sap.di.cltools.dtrshell -data D:\IDE\IDE7.31SP12\eclipse\workspace/../runtime-New_configuration(2) -dev file:D:/IDE/IDE7.31SP12/eclipse/workspace/.metadata/.plugins/org.eclipse.pde.core/CBS Command Line Tool/dev.properties -os win32 -ws win32 -arch x86
Error
Wed Oct 29 15:53:05 EET 2014
Application error
java.lang.NullPointerException
at com.tssap.dtr.client.commandline.DTRShell.main(DTRShell.java:86)
at com.sap.di.cltools.internal.DtrShell.start(DtrShell.java:32)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
If you have solution to this problem, please give me advice.
Thanks!

Getting a DC broken on importing the track into DTR

Hi,
I am getting an DC broken on importing and creating a DC-dp_logstatus .I am currently using NWDS CE7.1 EHP1 and NWDI as 7.0 SP16 for deployment on PI 7.1 EHP1.Please see build log is as below and suggest.
Build Plugin 'WebdynproPlugin', Version 7.11 SP 5 (NW711_05_REL, built on 2010-05-02 22:28:40 +0200, CL89977)
   development component: dp_logstatus (primavera.com)
      software component: INSPIRE_GUI_71 (primavera.com)
                location: HNI_IG71-604_D
                    type: Web Dynpro
           build variant: default
         source location: http://HOSEC6:50000/dtr/ws/IG71-604/primavera.com_INSPIRE_GUI_71/dev/inactive/
         output location: E:\NWDS_711_workspace.jdi\0\t2\D18E04A8BC5750E06188A9036E7F0DAA\default
       generation folder: E:\NWDS_711_workspace.jdi\0\t\D18E04A8BC5750E06188A9036E7F0DAA
       plugin start time: 2010-06-28 16:00:11 GMT+05:30 (IST)
                 Java VM: Java HotSpot(TM) Client VM, 1.5.0_18-b02 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Source folder "META-INF" does not exist and will be ignored.
Warning: Source folder "src/configuration" does not exist and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.016 seconds
Preparing data context..
sap.com"), public part "runtime", using legacy mode.
No public part descriptor found for component "tc/je/webservices/api" (vendor "sap.com"), public part "api", using legacy mode.
No public part descriptor found for component "tc/je/webservices/lib" (vendor "sap.com"), public part "api", using legacy mode.
Data context preparation finished in 0.343 seconds
[cmgen] [Info]       sap.comtcwdwslibapi~gci.jar - E:/NWDS_711_workspace.jdi/0/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/gci/lib/java
     [cmgen] [Info]    Optional property i18npath is empty
     [cmgen] [Info]    Initialize generation templates from configuration jar:file:/E:/NWDS_711_workspace.jdi/0/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/generation/lib/java/sap.comtcwdwslibapi~generation.jar!/AWSModelGenerationConfigurationCompiled.xml
     [cmgen] [Info]    Using DocumentBuilder com.sap.engine.lib.jaxp.DocumentBuilderImpl
[cmgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:81)
     [cmgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:56)
     [cmgen]      at com.sap.ide.generationfwk.pp.PublicParts.parsePublicParts(PublicParts.java:62)
     [cmgen]      ... 62 more
     [cmgen] [Warning] Generation of PublicPartFileList.xml failed: null
     [cmgen] [Info]    Common model generation finished (0 seconds)
     [cmgen]
     [timer] Common model generator finished in 0.484 seconds
     [wdgen] [Info]       sap.comtcwdwslibapi~gci.jar - E:/NWDS_711_workspace.jdi/0/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/gci/lib/java
     [wdgen] [Info]    Optional property i18npath is empty
     [wdgen] [Info]    Catching throwable null
     [wdgen] [Info]    java.lang.Exception
     [wdgen]      at com.sap.ide.generationfwk.pp.PublicParts.parsePublicParts(PublicParts.java:66)
     [wdgen]      at com.sap.ide.webdynpro.generation.Generation.getPublicPartsForCheckContext(Generation.java:2801)
     [wdgen]      at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:191)
     [wdgen]      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
     [wdgen] Caused by: java.lang.IllegalArgumentException
     [wdgen]      at com.sap.engine.lib.jaxp.DocumentBuilderImpl.setErrorHandler(DocumentBuilderImpl.java:107)
     [wdgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:81)
     [wdgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:56)
     [wdgen]      at com.sap.ide.generationfwk.pp.PublicParts.parsePublicParts(PublicParts.java:62)
     [wdgen]      ... 63 more
     [wdgen] [Warning] Could not get PublicPart[] for CheckContext: null
     [wdgen] [Info]    Initialize generation templates from configuration jar:file:/E:/NWDS_711_workspace.jdi/0/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/webdynpro_generation_core_api.jar!/WebDynproGenerationConfigurationCompiled.xml
     [wdgen] [Info]    Using DocumentBuilder com.sap.engine.lib.jaxp.DocumentBuilderImpl
     [wdgen] [Warning] Component 'SyncStatusComp': Cycle in component usage definitions: SyncStatusComp
     [wdgen] [Warning] NavigationTargetReference 'com.primavera.inspire.dp.LogStatusViewUsage1_ToConfirmation_1': Target Inbound Plug ConfirmationViewWinInterfaceView.Default of Link has Type startup. Do not navigate to Inbound Plugs with type startup. The behaviour of this plug type will change.
     [wdgen] [Warning] Controller 'ConfirmationViewWinInterfaceView': Cycle in required controller definitions.
    [wdgen] [Warning] Controller 'LogStatusWinInterfaceView': Cycle in required controller definitions. There is a controller usage (possibly indirectly via further controllers) to 'SyncStatusComp' which defines a usage back to 'LogStatusWinInterfaceView' Hint: This warning can be ignored as long as there are no cyclic dependencies between context attributes as well
     [wdgen] [Warning] Controller 'SyncStatusComp': Cycle in required controller definitions. There is a controller usage (possibly indirectly via further controllers) to 'ConfirmationViewWinInterfaceView' which defines a usage back to 'SyncStatusComp' Hint: This warning can be ignored as long as there are no cyclic dependencies between context attributes as well
     [wdgen] [Warning] Controller 'SyncStatusComp': Cycle in required controller definitions. There is a controller usage (possibly indirectly via further controllers) to 'LogStatusWinInterfaceView' which defines a usage back to 'SyncStatusComp' Hint: This warning can be ignored as long as there are no cyclic dependencies between context attributes as well
     [wdgen] [Info]    Image 'imgPrimavera.alt': Property 'alt' is deprecated. Hint: Instead of the imageAlt text the tool tip is displayed if the image isn't available.
     [wdgen] [Info]    Table 'tblSapPv': 'Columns' is deprecated. Hint: Functionality is covered in "groupedColumns". Use "groupedColumns" aggregation instead. Use the 'Migrate Columns' functionality to remove this deprecation.
     [wdgen] [Info]    Table 'tblSapPv': No elements in 'GroupedColumns'.
     [wdgen] [Info]    ScrollContainer 'scr_logstatus.scrollingMode': ScrollingMode is 'auto' or 'both' and height is not set.
     [wdgen] [Info]    FlowData 'txvDesc1_2_layoutdata_19_15.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'txvDesc1_2_layoutdata_19.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'txvSAPId1_6_layoutdata_23.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData_25.paddingLeft': Property 'paddingLeft' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'txvPvId1_10_layoutdata_27.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingLeft': Property 'paddingLeft' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingLeft': Property 'paddingLeft' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingLeft': Property 'paddingLeft' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'LayoutData.paddingRight': Property 'paddingRight' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    FlowData 'TextView1_layoutdata_32.paddingLeft': Property 'paddingLeft' is deprecated. Hint: Use cellDesign instead.
     [wdgen] [Info]    Table 'tblLogStatus': 'Columns' is deprecated. Hint: Functionality is covered in "groupedColumns". Use "groupedColumns" aggregation instead. Use the 'Migrate Columns' functionality to remove this deprecation.
     [wdgen] [Info]    Table 'tblLogStatus': No elements in 'GroupedColumns'.
     [wdgen] [Info]    Table 'tbl_LogDetails': 'Columns' is deprecated. Hint: Functionality is covered in "groupedColumns". Use "groupedColumns" aggregation instead. Use the 'Migrate Columns' functionality to remove this deprecation.
     [wdgen] [Info]    Table 'tbl_LogDetails': No elements in 'GroupedColumns'.
     [wdgen] [Info]    Generating packages/com/primavera/inspire/dp/wdp/IPrivateConfirmationPopupView.java
     [wdgen] [Info]    Generating packages/com/primavera/inspire/dp/ConfirmationPopupView.java
     [wdgen] [Info]    Generating packages/com/primavera/inspire/dp/wdp/InternalConfirmationPopupView.java
     [wdgen] [Info]    Searching view element definition for TransparentContainer RootUIElementContainer[Info]    Generating configuration/Applications/com.primavera.inspire.logstatusapp.Logstatusapp/wdrr_en.properties
     [wdgen] [Info]    Creating file configuration/Applications/com.primavera.inspire.logstatusapp.Logstatusapp/wdrr_en.properties not necesseary
     [wdgen] [Info]    Generating E:/NWDS_711_workspace.jdi/0/t/D18E04A8BC5750E06188A9036E7F0DAA/S2XFileList.txt
     [wdgen] [Info]    Catching throwable null
     [wdgen] [Info]    java.lang.Exception
     [wdgen]      at com.sap.ide.mmservices.generation.dc.DCDependencyInfo.parseDCDependencyInfo(DCDependencyInfo.java:81)
     [wdgen]      at com.sap.ide.mmservices.generation.dc.DCDependencyInfo.<init>(DCDependencyInfo.java:57)
     [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1578)
     [wdgen]      at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:190)
     [wdgen]      at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:69)
     [wdgen]      at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:191)
     [wdgen]      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
     [wdgen] Caused by: java.lang.IllegalArgumentException
     [wdgen]      at com.sap.engine.lib.jaxp.DocumentBuilderImpl.setErrorHandler(DocumentBuilderImpl.java:107)
     [wdgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:81)
     [wdgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:56)
     [wdgen]      at com.sap.ide.mmservices.generation.dc.DCDependencyInfo.parseDCDependencyInfo(DCDependencyInfo.java:77)
     [wdgen]      ... 61 more
[wdgen] [Error]   generatePersistentArchive: DCDependencyInfo.xml could not be read (null)
     [wdgen] [Error]   Generation failed due to errors (4 seconds)
Error: E:\NWDS_711_workspace.jdi\0\t2\D18E04A8BC5750E06188A9036E7F0DAA\default\logs\build.xml:210: [Error]   Generation failed!
     at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:275)
     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     at org.apache.tools.ant.Task.perform(Task.java:364)
     at org.apache.tools.ant.Target.execute(Target.java:341)
     at org.apache.tools.ant.Target.performTasks(Target.java:369)
     at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:114)
     at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:57)
     at com.sap.ide.dii05.lib.internal.commands.dc.BasicCreateProjectJob.triggerBuildIfNecessary(BasicCreateProjectJob.java:318)
     at com.sap.ide.dii05.lib.internal.commands.dc.BasicCreateProjectJob.access$000(BasicCreateProjectJob.java:53)
     at com.sap.ide.dii05.lib.internal.commands.dc.BasicCreateProjectJob$1.doInWorkerThread(BasicCreateProjectJob.java:233)
     at com.sap.ide.dii05.util.api.job.JdiJob$1.doInWorkerThread(JdiJob.java:77)
     at com.sap.ide.dii05.util.internal.job.InternalJdiJob$3$1.run(InternalJdiJob.java:198)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797)
     at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1779)
          at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runInternal(InternalDiiJob.java:305)
     at com.sap.ide.dii05.util.internal.job.InternalDiiJob.runR(InternalDiiJob.java:203)
     at com.sap.ide.dii05.util.internal.job.InternalDiiJob.run(InternalDiiJob.java:191)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Ant runtime 5.746 seconds
Ant build finished with ERRORS
[Error]   Generation failed!
Error: Build stopped due to an error: [Error]   Generation failed!
Build plugin finished at 2010-06-28 16:00:18 GMT+05:30 (IST)
Total build plugin runtime: 6.87 seconds
Build finished with ERROR

contiued--
[cmgen]      at com.sap.ide.generationfwk.pp.PublicParts.parsePublicParts(PublicParts.java:66)
     [cmgen]      at com.sap.ide.cmi.generation.Generation.doPersistentGenerationForArchivePublicPartFileList(Generation.java:217)
     [cmgen]      at com.sap.ide.cmi.generation.Generation.doPersistentGenerationForArchivePublicPartFileList(Generation.java:255)
     [cmgen]      at com.sap.ide.cmi.generation.Generation.generatePersistentArchive(Generation.java:400)
     [cmgen]      at com.sap.ide.cmi.generation.console.GenerationConsole.generate(GenerationConsole.java:158)
     [cmgen]      at com.sap.ide.cmi.generation.ant.GenerationAnt.main(GenerationAnt.java:52)
     [cmgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     [cmgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     [cmgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     [cmgen]      at java.lang.reflect.Method.invoke(Method.java:585)
     [cmgen]      at com.sap.ide.cmi.generation.ant.CMGenAntTask.execute(CMGenAntTask.java:211)
     [cmgen]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
     [cmgen]      at org.apache.tools.ant.Task.perform(Task.java:364)
     [cmgen]      at org.apache.tools.ant.Target.execute(Target.java:341)
     [cmgen]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
     [cmgen]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
     [cmgen]      at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
     [cmgen]      at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:114)
     [cmgen]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:57)
     [cmgen]      at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
     [cmgen]      at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
     [cmgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
     [cmgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
     [cmgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     [cmgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     [cmgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     [cmgen]      at java.lang.reflect.Method.invoke(Method.java:585)
     [cmgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
     [cmgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
     [cmgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
     [cmgen]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
     [cmgen]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
     [cmgen]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1515)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:761)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:527)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:452)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:324)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:262)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:217)
     [cmgen]      at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:178)
     [cmgen] Caused by: java.lang.IllegalArgumentException
     [cmgen]      at com.sap.engine.lib.jaxp.DocumentBuilderImpl.setErrorHandler(DocumentBuilderImpl.java:107)
     [cmgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:81)
     [cmgen]      at com.sap.ide.generationfwk.util.xml.DOMParser.<init>(DOMParser.java:56)
     [cmgen]      at com.sap.ide.generationfwk.pp.PublicParts.parsePublicParts(PublicParts.java:62)
     [cmgen]      ... 39 more
     [cmgen] [Warning] Generation of PublicPartFileList.xml failed: null
     [cmgen] [Info]    Common model generation finished (1 seconds)
     [cmgen]
     [timer] Common model generator finished in 1.453 seconds
      [echo] Starting WebDynpro generator
     [wdgen]
     [wdgen] [Info]    Property deployment is true: Deployment information is provided!
     [wdgen] [Info]    Property sourcepath ...
     [wdgen] [Info]       D:\usr\sap\HN2\JC20\j2ee\cluster\server0\temp\CBS\35\.B\1982\DCs\primavera.com\dp_logstatus\_comp\src\packages
     [wdgen] [Info]    Property targetpath: D:\usr\sap\HN2\JC20\j2ee\cluster\server0\temp\CBS\35\.B\1982\t\D18E04A8BC5750E06188A9036E7F0DAA\gen_wdp
     [wdgen] [Info]    Property archivename: primavera.com~dp_logstatus
     [wdgen] [Info]    Property vendor: primavera.com
     [wdgen] [Info]    Property dcname: dp_logstatus
     [wdgen] [Info]    Property metadatapath: D:\usr\sap\HN2\JC20\j2ee\cluster\server0\temp\CBS\35\.B\1982\t\D18E04A8BC5750E06188A9036E7F0DAA
     [wdgen] [Info]    Property generates2x is false: S2X files will not be generated
     [wdgen] [Info]    Property projectlanguage: en
     [wdgen] [Info]    Property language: Available languages are automatically determined!
     [wdgen] [Info]    Property addpaths ...
     [wdgen] [Info]       jxl.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/elib_xls/_comp/gen/default/public/elib_xlsapi/lib/java
     [wdgen] [Info]       primavera.comjv_confirmationcommandjv_confirmationcommandAPI.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_confirmationcommand/_comp/gen/default/public/jv_confirmationcommandAPI/lib/java
     [wdgen] [Info]       primavera.comjv_sync_commandbeanjv_sync_commandbeanAPI.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_sync_commandbean/_comp/gen/default/public/jv_sync_commandbeanAPI/lib/java
     [wdgen] [Info]       primavera.cominspiresc001~jv_sync_ejb_client.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_sync_ejb/_comp/gen/default/public/client/lib/java
     [wdgen] [Info]       primavera.comjv_sync_wrapperjv_sync_wrapperAPI.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_sync_wrapper/_comp/gen/default/public/jv_sync_wrapperAPI/lib/java
     [wdgen] [Info]       primavera.comjv_synchlogcommandjv_synchlogcommandapi.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_synchlogcommand/_comp/gen/default/public/jv_synchlogcommandapi/lib/java
     [wdgen] [Info]       primavera.cominspiresc001~jv_synchlogejb_client.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_synchlogejb/_comp/gen/default/public/client/lib/java
     [wdgen] [Info]       primavera.comjv_synchlogwrappersynchlogwrapperapi.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_synchlogwrapper/_comp/gen/default/public/synchlogwrapperapi/lib/java
     [wdgen] [Info]       primavera.comjv_xiconf_commandbeanjv_xiconf_commandbeanAPI.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_xiconf_commandbean/_comp/gen/default/public/jv_xiconf_commandbeanAPI/lib/java
     [wdgen] [Info]       primavera.cominspiresc001~jv_xiconf_ejb_client.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_xiconf_ejb/_comp/gen/default/public/client/lib/java
     [wdgen] [Info]       primavera.comjv_xiconf_wrapperjv_xiconf_wrapperAPI.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/jv_xiconf_wrapper/_comp/gen/default/public/jv_xiconf_wrapperAPI/lib/java
     [wdgen] [Info]       primavera.com~logejb_client.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/primavera.com/logejb/_comp/gen/default/public/client/lib/java
     [wdgen] [Info]       engine.j2ee14.facade.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/engine.j2ee14.facade/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       ecjavajsf~api.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/engine.jee5.facade/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       engine.jee5.facade.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/engine.jee5.facade/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       tcaiibaseofflinefacade.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/aii/base/offline/facade/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       SapMetamodelDictionaryContent.zip - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
     [wdgen] [Info]       tcbiwstech_public.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bi/wstech/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       core.exception.lib.api.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/exception/lib/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       tcbljrfc~api.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/jrfc/api/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       tcblloggingapidefaultttt.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/logging/api/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       sap.comtcbl~base_webservices_lib.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/wsproxy/standalone/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcsapxmltoolkit.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/wsproxy/standalone/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcsecwssecclient~api.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/wsproxy/standalone/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       tcwsstandalone~proxy.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/bl/wsproxy/standalone/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       com.sap.tc.cmi.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       tc~cmi.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       SapMetamodelDictionaryContent.zip - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/ddic/runtime/facade/_comp/gen/default/public/runtime/lib/java
     [wdgen] [Info]       dictionary.rtcontainer.facade.filter.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/ddic/runtime/facade/_comp/gen/default/public/runtime/lib/java
     [wdgen] [Info]       dictionary.runtime.facade.filter.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/ddic/runtime/facade/_comp/gen/default/public/runtime/lib/java
     [wdgen] [Info]       dictionary.services.facade.filter.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/ddic/runtime/facade/_comp/gen/default/public/runtime/lib/java
     [wdgen] [Info]       tcddicruntime~facade.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/ddic/runtime/facade/_comp/gen/default/public/runtime/lib/java
     [wdgen] [Info]       tcjewebservices~api.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/je/webservices/api/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       tcjewebservices~lib.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/je/webservices/lib/_comp/gen/default/public/api/lib/java
     [wdgen] [Info]       SapMetamodelWebdynproContent.zip - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/api/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       SapMetamodelWebdynproResources.zip - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/api/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcwdapidefault.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/api/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcwdapigci.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/api/_comp/gen/default/public/gci/lib/java
     [wdgen] [Info]       com.sap.tc.aws.modeltype.content.zip - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcwdwslibapi~default.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/default/lib/java
     [wdgen] [Info]       sap.comtcwdwslibapi~gci.jar - D:/usr/sap/HN2/JC20/j2ee/cluster/server0/temp/CBS/35/.B/1982/DCs/sap.com/tc/wd/wslib/api/_comp/gen/default/public/gci/lib/java
     [wdgen] [Info]    Optional property i18npath is empty
     [wdgen] [Info]    Catching throwable null
     [wdgen] [Info]    java.lang.Exception

Error while creating a project from DTR.

When i am creating a dc locally from DTR,
It is giving an error message as follows;-
generic VFS error
com.sap.tc.devconf.SyncException: Unable to sync file or folder.: Sync request not
at com.sap.tc.devconf.impl.DTRClientErrorMapper.toSyncException(DTRClientErrorMapper.java:73)
at com.sap.tc.devconf.impl.VFSHandler.syncLocalPath(VFSHandler.java:359)
at com.sap.tc.devconf.impl.DCProxy.syncSources(DCProxy.java:579)
at com.sap.tc.devconf.impl.DCProxy.syncAsSources(DCProxy.java:461)
at com.sap.tc.devconf.impl.DevelopmentConfiguration.syncAsSources(DevelopmentConfiguration.java:4895) at com.sap.tc.devconf.impl.DevelopmentComponentNode.syncAsSources(DevelopmentComponentNode.java:903) at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.syncSelectedDCs(DcCreateProjectAction.java:441) at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:235) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101) Caused by: com.tssap.dtr.client.lib.vfs.VfsException: Sync request not
at com.tssap.dtr.client.lib.vfs.impl.SyncRemoveFeatureMget.syncMountedFolder(SyncRemoveFeatureMget.java:213)
     at com.tssap.dtr.client.lib.vfs.impl.SyncRemoveFeature.sync(SyncRemoveFeature.java:530)
     at com.tssap.dtr.client.lib.vfs.impl.VfsFolder.sync(VfsFolder.java:1290)
     at com.sap.tc.devconf.impl.VFSHandler.syncLocalPath(VFSHandler.java:349)
     ... 10 more
Caused by:
[VFS version: 6.40 630_VAL_REL 0010 (2005-05-08 21:54:38 CEST)] com.tssap.dtr.client.lib.vfs.VfsException: Sync request not
    at com.tssap.dtr.client.lib.vfs.impl.SyncRemoveFeatureMget.syncMountedFolder(SyncRemoveFeatureMget.java:213)
    at com.tssap.dtr.client.lib.vfs.impl.SyncRemoveFeature.sync(SyncRemoveFeature.java:530)
    at com.tssap.dtr.client.lib.vfs.impl.VfsFolder.sync(VfsFolder.java:1290)
    at com.sap.tc.devconf.impl.VFSHandler.syncLocalPath(VFSHandler.java:349)
    at com.sap.tc.devconf.impl.DCProxy.syncSources(DCProxy.java:579)
    at com.sap.tc.devconf.impl.DCProxy.syncAsSources(DCProxy.java:461)
    at com.sap.tc.devconf.impl.DevelopmentConfiguration.syncAsSources(DevelopmentConfiguration.java:4895)
    at com.sap.tc.devconf.impl.DevelopmentComponentNode.syncAsSources(DevelopmentComponentNode.java:903)
    at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.syncSelectedDCs(DcCreateProjectAction.java:441)
    at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:235)
    at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
what will be the reason. how to get rid of this?
helpful answer will be rewarded.Its urgent.

Hi,
   You can try the following:
1. Give the fully qualified domain name of the DTR server host in NWDS Preferences->Development Configuration.
2. Check if your WAS and JDI are on a higher SP level. If yes then use the corresponding NWDS.
Regards,
Satyajit.

Error while creating project in NWDS from DTR

Hi Experts,
I have installed NWDS 7.0.11 and Imported the configuration from NWDI
After importing I created a project .
I am getting the following error.
Development Component Build (2010-06-08 22:43:39)
Component name: vendordisplay
Component vendor: weyerhaeuser.com
SC compartment: domtar.com_DOMTAR_VENDOR_DISPLAY_1
Configuration: NW3_DMTRWAS_D
Location: NW3_DMTRWAS_D
Source code location: http://cinw3.domtar.com:50300/dtr/ws/DMTRWAS/domtar.com_DOMTAR_VENDOR_DISPLAY/dev/inactive/DCs/weyerhaeuser.com/vendordisplay/_comp/
DC root folder: D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\weyerhaeuser.com\vendordisplay\_comp\
DC type: Web Dynpro
Host: D--113000920
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
   validating dependency to public part "default" of DC "sap.com/tc/col/api"
   validating dependency to public part "default" of DC "sap.com/tc/cmi"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
   validating dependency to public part "default" of DC "sap.com/tc/logging"
   validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
   validating dependency to public part "default" of DC "sap.com/com.sap.exception"
   validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
   validating dependency to public part "default" of DC "weyerhaeuser.com/connection_service"
   validating dependency to public part "default" of DC "weyerhaeuser.com/custom_types"
   validating dependency to public part "default" of DC "weyerhaeuser.com/information_service"
   validating dependency to public part "SearchHelp" of DC "weyerhaeuser.com/search_help_service"
   validating dependency to public part "default" of DC "weyerhaeuser.com/navigation_service"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/webDynpro
   starting build plugin from : D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 11 (645_VAL_REL, built on 2007-01-31 22:47:10 CET, CL51454)
   development component: vendordisplay (weyerhaeuser.com)
      software component: DOMTAR_VENDOR_DISPLAY (domtar.com)
                location: NW3_DMTRWAS_D
                    type: Web Dynpro
           build variant: default
         source location: prasanna@D--113000920
         output location: D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\weyerhaeuser.com\vendordisplay\_comp\gen\default
       plugin start time: 2010-06-08 22:43:40 GMT+05:30 (IST)
                 Java VM: Java HotSpot(TM) Client VM, 1.4.2_14-b05 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Checking path lengths for sources
Path length checks finished in 0.093 seconds
Preparing data context..
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\col\api\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\cmi\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\ddic\ddicruntime\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\ddic\metamodel\content\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\wd\webdynpro\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\logging\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\wdp\metamodel\content\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\com.sap.aii.proxy.framework\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\com.sap.aii.util.misc\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\com.sap.exception\_comp\gen\default\public\default, using legacy mode.
No public part descriptor found in D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\com.sap.mw.jco\_comp\gen\default\public\default, using legacy mode.
No 'default' JDK defined, will use running VM.
Data context prepared in 0.344 seconds
Creating Ant build file..
Creating output file: D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\weyerhaeuser.com\vendordisplay\_comp\gen\default\logs\build.xml
Using macro file:     D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
Build file created in 0.266 seconds
Starting Ant..
Using build file:     D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\weyerhaeuser.com\vendordisplay\_comp\gen\default\logs\build.xml
Using build target:   build
Generation folder:    D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\t\F5F315E03624A8A9DCE52475ABD38A2D
Error: D:\Back Up 26-May 2010\Prasanna\NWDS\.dtc\0\DCs\weyerhaeuser.com\vendordisplay\_comp\gen\default\logs\build.xml:15: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Bad comment content(file:///D:/Back%20Up%2026-May%202010/Prasanna/NWDS/.dtc/0/DCs/weyerhaeuser.com/vendordisplay/_comp/gen/default/logs/build.xml, row:15, col:40)
     at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:222)
     at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:131)
     at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:108)
     at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
     at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
     at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
     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.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:347)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
     at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5633)
     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
     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:212)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Caused by: com.sap.engine.lib.xml.parser.ParserException: Bad comment content(file:///D:/Back%20Up%2026-May%202010/Prasanna/NWDS/.dtc/0/DCs/weyerhaeuser.com/vendordisplay/_comp/gen/default/logs/build.xml, row:15, col:40)
     at com.sap.engine.lib.xml.parser.XMLParser.scanComment(XMLParser.java:2186)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2779)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
     at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:208)
     ... 21 more
--- Nested Exception ---
com.sap.engine.lib.xml.parser.ParserException: Bad comment content(file:///D:/Back%20Up%2026-May%202010/Prasanna/NWDS/.dtc/0/DCs/weyerhaeuser.com/vendordisplay/_comp/gen/default/logs/build.xml, row:15, col:40)
     at com.sap.engine.lib.xml.parser.XMLParser.scanComment(XMLParser.java:2186)
     at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2779)
     at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
     at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:208)
     at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:131)
     at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:108)
     at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
     at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
     at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
     at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
     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.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:347)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
     at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
     at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
     at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5633)
     at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
     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:212)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Ant runtime 0.062 seconds
Ant build finished with ERRORS
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Bad comment content(file:///D:/Back%20Up%2026-May%202010/Prasanna/NWDS/.dtc/0/DCs/weyerhaeuser.com/vendordisplay/_comp/gen/default/logs/build.xml, row:15, col:40)
Error: Build stopped due to an error: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Bad comment content(file:///D:/Back%20Up%2026-May%202010/Prasanna/NWDS/.dtc/0/DCs/weyerhaeuser.com/vendordisplay/_comp/gen/default/logs/build.xml, row:15, col:40)
Build plugin finished at 2010-06-08 22:43:41 GMT+05:30 (IST)
Total build plugin runtime: 1.172 seconds
Build finished with ERROR
Steps tried but no use .
Set the Java Home
Reload and Rebuild the project
Synced the DC
Added the ips in host files
After all this still when I try to DC build I am getting the same error . ,
Dont know how to proceed
Edited by: Prasanna Kumar on Jun 9, 2010 11:48 AM

Try to syncronize DC dependencies (in Development Configuration perspective: "Sync Used DCs")... after, rebuild your project.
regards,
Angelo

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Trial version has expired, and i need backup.

Hello Experts,
I had installed a trial version of SAP Netweaver AS Java 7.1 ehp1 sp03, then it expired.
I forgot to make some backup before the expired time, and i lost some important things.
I really need this things, and if i need to make all the this things again, i will get a lot of time.
I ask for you, if there is some way to recuperate the objects that i have lost.
The objects that i lost are some enterprise services, one track of nwdi with my project in dtr, and some destinations.
Please, could someone help me?
Regards
Marcos

I solved.

Why do we need to create DTR client

Can any one give me some info why DTR client are needed when working with JDI. Because, In NWDI we dont need them...But, now I am workign on older version JDI.. So, can anyone let me know.

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/83/74c4ce0ed93b4abc6144aafaa1130f/content.htm">This</a> might give you some help you require.
Regards,
Shubhadip

ABAP Code in End Routine - reverts back to previous version

Team:
Currently, we are in upgrading from 7.01 to 7.4. The new development environment is only used to built the new development work until the mirror image client is upgraded.
In one customised dataflow, we place some code and the transformation is activated. No issues at all, then the next day, the code reverts back a previous version. Consequently, we are losing the code. We already have a sign off of a piece of work and we checked the code again. We were puzzled as to why the code has gone back to a previous version.
SAP is asking to replicate the issue. Unfortunately, we cannot replicate accurately this issue. Now, we have two more developers reporting the same case. Yet again, the issue comes and goes. We reboot the server with some success. Then days later, the issue pops up with a developer. The Basis guys have not found anything related to this case.
Any idea is welcome.

Sync to Date is currently the only option offered by the DTR.
You can only edit the active version of a resource in a workspace, because the DTR does not support branching within a workspace: There is no mechanism in place to merge an older version of a resource into the same workspace.
If you want to do this, you must make a copy of the workspace (a "maintenance" workspace) and make your changes in that workspace. You can integrate the related activity/activities into the "ongoing development" workspace afterwards, if you want to of course.
Why don't you want your bugfixes to be forwarded by the way? Those bugs are also in your enhancement tracks...

Versions in DTR

Similar Messages

Maybe you are looking for