Property Metadata in Web Dynpro

Hi Experts,
I created a KM custom property with a csv list of allowed values. Now I'm looking for some java coding that will read the allowed values for this property from the portal. Can anybody help me with some example java code for doing this?
Thanks in advance,
Edwin van der Palen

Hi,
go through this links,
/thread/192920 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/69e7e490-0201-0010-848e-88d9f707952d
Regards
Anil..

Similar Messages

How to get user language in property renderer without web dynpro (java)

Hi all,
how can I get the language of the current user?
Normally I got it with:
IWDClientUser wdClientUser = WDClientUser.getCurrentUser();
com.sap.security.api.IUser sapUser = wdClientUser.getSAPUser();
IUser ep5User = WPUMFactory.getUserFactory().getEP5User(sapUser);
IResourceContext resourceContext = new ResourceContext(ep5User);
String strUserLanguage = resourceContext.getLocale().getLanguage();
But this only works in web dynpro applications. Now I need to get the language in my own property renderer. The code throws:
com.sap.tc.webdynpro.services.sal.um.api.WDUMException: No client user defined for the current request (no regular Web Dynpro request as ITask is null.
Thanks a lot
Steffi

Hi,
If you are in a property renderer you always have a IResource which inturn has a ResourceContext and ResourceContext has the Users object.
So the code should be:
IResourceContext resourceContext = IResource.getContext();
IUser user = resourceContext.getUser();
user.getLocale().getLanguage();
Regards,
Praveen Gudapati
Edited by: Praveen Gudapati on May 16, 2008 2:54 PM

Displaying KM Property structure in Web Dynpro

Hi All,
From SAP Help:
<...>
A property structure displays properties of a resource (folder, document, or link) in a fixed order.
A property structure can be displayed in the following places in the system:
· In the Details dialog box for a document or folder under Settings ® Properties.
· When creating or editing a document or folder, using the link Show Properties.
<...>
How to proceed when I want the property structure to be displayed as a Web Dynpro.
Do we have to build a "WebDynpro-PropertyStructureRenderer" or are there short-cuts possible??
Kind regards,
Maarten

Hi Maarten,
There are commands to allow you to open the Details page to the Properties page.
See the UI commands called "details_properties" and "details_properties_ex"
These generate links directly to that page for a resource. You can see similar
examples of how these are formulated using the "Status Explorer" Layout set.
You can do this by opening a KM iView in a new window and adding
"&rndLayoutSet=ConsumerTreeStatusList" to the end of the URL.
The parameters allow opening the page with or without the rest of the details page
navigation. The effective parameters will look something like this (for permissions,
but properties is similar):
&Standalone=true&command=permissions&isp=permissions&StartUri=/documents&StartPage=StandaloneDetailsPage
You would have to generate the corresponding URL in WD.
Regards,
Darin

How to create a custom property for web dynpro iView - please respond

Hi,
I have to create a custom iView property for a web dynpro Java Application. I am searching forums and sap help and not able to find any documentation on this. Please post your thoughts here...
Thanks
Srini
Edited by: Srinibapati on Sep 5, 2009 3:56 PM

No One replied and closing this thread...........I still don't have answer for this.
Thanks.
Srini

How to integrate backend web dynpro abap application in Portal 7.3?

Hello,
before Portal 7.3 I was able to integrate a web dynpro abap application as iView in the portal. Now I don't get the point on how to do it. I cannot find a "normal" iview that enables me to give the backend and the application name. The possibilty to create iView based on remote source looks strange because I don't want to upload the application I just want to do my normal user/pass mapping and show the applicaton via iView.
Somehow I don't get the point with the new version. Could someone give me a hint where to find more information regardings this problem`?
Thanks a lot,
Vanessa

Hi Vanessa,
Could someone tell me if I should see the SAP Web Dynpro for ABAP iView template in the long list of available templates when I create a new iView?
You will 'SAP Web Dynpro iView' option in the list while creating iview from template.Create and change the property platform to 'Web Dynpro for ABAP'.
Is it correct not to use the remote source option? I think yes because otherwise he would upload the app to the portal, if I am not wrong.
If i understood your question correct,then You can use this option as well to create iview.Atlast it wil create only iview for the application not the application itself in the portal.
Naga

Access KM predefined property values from a Web Dynpro application

Hi,
I am trying to build a custom search interface in Web Dynpro which leverages the KMC Indexing and Search services.
In this interface I would like to display value lists of predefined properties in KM (created using the Property Metadata Service) and bind each predefined property's value list to a checkbox group UI element.
Which KM API should I use to retrieve the values of a specific predefined property ?
When using the standard flexible user interface in the portal this can easily be achieved through configuration, but now I would like to know how to achieve this in Java code.
Thanks in advance for your input.
I have some idea on how to get the propertymap from a resource, but how can I access the metadata of a predefined property in KM directly ?

Hi Theo, i'm working on something like this, i have a WD application that is accessing Km through a Webservice, on the webservice ejb i have this problem:
IResourceFactory resFactory = ResourceFactory.getInstance();
IRepositoryServiceFactory serFactory = resFactory.getServiceFactory();
IPropertyConfigurationService propConfigService = (IPropertyConfigurationService) serFactory.getService("PropertyConfigurationService");
IMetaNameListIterator i = propConfigService.getMetaModel().nameIterator();
     while (i.hasNext()) {
     IMetaName metaname = i.next();
     if ( metaname.getDocumentPatterns()!= null){
     propertyData.setId(metaname.getName());
     propertyData.setName(metaname.getLabel(locale));
     propertyData.setNamespace(metaname.getNamespace());
     propertyData.setDescription(metaname.getDescription(locale));
                propertyList.add(propertyData);
On this line serFactory.getService("PropertyConfigurationService") i get the following error on the trace:
#System.err#sap.com/KmmsListEAR#System.err#Guest#2####30a27fa0cbfa11dbace30018de0545f1#SAPEngine_Application_Thread[impl:3]#Error##Plain###Configuration Framework error: unable to create an IConfigClientContext instance from an EP5 userInitialConfigException: The configuration service locator could not be initialized for any of the environments. The configuration framework is not available.#
#System.err#sap.com/KmmsListEAR#System.err#Guest#2####30a27fa0cbfa11dbace30018de0545f1#SAPEngine_Application_Thread[impl:3]#Error##Plain###InitialConfigException: The configuration service locator could not be initialized for any of the environments. The configuration framework is not available.
Do you have any idea of how to solve this? or if you accomplished in a different way, can you guide me a little bit.
Thanks in advance Theo

ClassName property missing in file for Web Dynpro for ABAPSSO layer

We are trying to create an ABAP webdynpro iview using XML content creation in EP7.3. Below link points to the XML used to create the iview. After importing this xml, iview is being created in specified PCD location.
http://www.freeimagehosting.net/26365
But when we preview the iview, we are getting an exception which says
com.sapportals.portal.appintegrator.ApplicationIntegratorException: Missing Property 'ClassName' in property file for layer'WebDynpro/Web Dynpro for ABAPSSOLayer'.
We checked by creating another abap dynpro iview for the same application using iview template and that is working fine.
Details of the error log is mentioned below.
Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.WebDynpro',
Context Name (iView): 'pcd:portal_content/com.bat.folder.Sudip/com.bat.folder.xmlcontent/com.bat.folder.iview.abap.wd.Z_WD_COMPONENT',
Top Layer:            'WebDynpro/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'SAP_ECC',
Exception ID:01:50_02/01/12_0076_15632350
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Application name : com.sap.portal.appintegrator.sap
Component : pcd:portal_content/com.bat.folder.Sudip/com.bat.folder.xmlcontent/com.bat.folder.iview.abap.wd.Z_WD_COMPONENT
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : 98909242
at com.sap.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:765)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Missing Property 'ClassName' in property file for layer'WebDynpro/Web Dynpro for ABAPSSOLayer'.
... 54 more
Caused by: com.sapportals.portal.appintegrator.ApplicationIntegratorException: Missing Property 'ClassName' in property file for layer'WebDynpro/Web Dynpro for ABAPSSOLayer'.
01:50_02/01/12_0076_15632350
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: Missing Property 'ClassName' in property file for layer'WebDynpro/Web Dynpro for ABAPSSOLayer'.
at com.sapportals.portal.appintegrator.LayerProcessor.createLayer(LayerProcessor.java:361)
at com.sapportals.portal.appintegrator.LayerProcessor.getNextLayer(LayerProcessor.java:303)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:183)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:390)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:203)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Can anyone please suggest how to solve this error ?
Regards
Kaushik

Hi,
Please check the system object 'SAP_ECC' connection test whether it is fine or not.
Producer ID (FPN): 'null', System Alias: 'SAP_ECC',
This message clearly states that the system object with alias SAP_SRM is missed or improperly configured.
Hope this helps u.
Best Regards
Vijay K

How to disable/enable image property in Web Dynpro?

Hi,
I was trying to find a help about "How to disable/enable property of an image in Web Dynpro?" but never find it. Let me explain what I'm trying to do:
I need to show three different status (Released, Rejected and Approved) each one is an image ... How do I do to disable images property before a process and enable them after it?
Thanks in Advance, and waiting an answer As Soon As Possible !!!
Tokio

Your question is not completely clear to me. An image cannot trigger an event, so disabling it has no effect.
To display different images in a Image element depending on some condition, you can use a calculated context attribute imageSource of type "string" that returns the URL of the image, something like
public String getImageSource(IWDNodeElement element)
if (...)
 return "image_for_status1";
else if (...)
 return "image_for_status2";
else if (...)
 return "image_for_status3";
return ""; /* no image will appear */
Bind property Image.source to attribute imageSource.
If you put the three image files inside folder src/mimes/components/<componentName>, your method can simply return the file name without calculating an URL.
Armin

Web Dynpro Metadata

Hi,
i'am computer science student and i'am interested in model-driven-architecture.
thats why i'am interested in the web dynpro metadata. is it possible to extract/view
the metadata of a web dynpro comp.?
are there any technical documents about the metamodel (i found none)?
thanks
tobias

Hi Tobias,
so this post is in the WD for ABAP forum, your are looking for information about web dynpro for ABAP or for JAVA?
Because you use different development tools.
WD4A -> Development Workbench (SE80)
WD4J -> SAP NetWeaver Developer Studio
Within the SAP NetWeaver Developer Studio there is a tool for comparing the metadata
http://help.sap.com/saphelp_nw04/helpdata/en/6e/0e184188b4f16fe10000000a1550b0/content.htm
What I know, in the development workbench, there is nothing similar to this
I'm not sure, but I think there is a solution - presented on the SAP Teched 08 (Demo jam?!) - integrating a WD4A application into the SAP NetWeaver developer studio and than you can maybe use the tools integrated in NWDS for the WD4A application...
Regards,
Andreas

Code Web Dynpro Save All Metadata

Hi Experts!!
I have a problem with SAP Netweaver when I go programming in web Dynpro.
When I go insert a code in tab "Implementation", for example:
Insert this code:
String headerText = "Congratulations ";
       headerText +=   wdThis.wdGetCadastroPessoaController().wdGetContext().currentContextElement().getNome();
       headerText += "!";
       wdContext.currentContextElement().setNome(headerText);
Into to method:
public void onPlugFromCadastroPessoaView(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
When I go Save All Metadata the code disappearing. Then I try click again in Save All Metadata Button, but the code don't stay there.
Anyone know why this happen?
Thanks in advance!
Marcelo

Hi Marcelo,
In webdynpro programming u need to write ur code between the default comments given .
//@@begin
     ***code******
//@@end
you cannot just delete the comments or write the code above or below the comments, if u do so your code just dissappears once u save all ur metadata.
Regards,
Tilak.

Web Dynpro metadata API

Hi,
I'm currently working with web dynpro for java metadata api to create a simple web dynpro application consisting
of one component defining a model, component controller and a view. I found an example how to create controllers
and views, but I don't find any examples of building a model metadata. Are there any resources available, e.g.: javadoc api, sample appplications covering metadata api details ?
Thanks in advance,
Ilya.

Hi
What do you mean by Model Metadata api. If you are using Webdynpro then you can import the model using the Create Model Wizard of NDS.
Do you want to create a Model at runtime. If you can tell me what you would like to do i would be able to help you further.
Anyway See if this example helps you.
http://help.sap.com/saphelp_nw04/helpdata/en/d5/1558bfa6aa80499113983e738b1b21/frameset.htm
regards
ravi

What is mean by word "metadata" in terms of Web Dynpro ABAP

Hi All,
I am new to Web DynproI searched the old posts but not able to find the answer.
..I need clarification regarding word "metadata" in terms of Web Dynpor ABAP.
There is a concept called "Web Dynpro MetaModel" in this what exactly "MetaModel" means.
Regards
CB

hi, channappa.
Very sorry that cann't get what you want?
Anyway, Metadata is the "data" describing the "data".The most easly understanding example is the "Table": "data" is the real records saved in the table, the "meta data" is the data describing the table,i.e the attribute,fields,etc..
In WD, for example, the Context..The value which is saved in the memory by Context node/attribute, we can call them "Data", yet the data which we can get runtime(for example, the context node or attribute), maybe we can call them Meta data to some extent.
I don't this can fit your confusion.
Very glad to discuss with you.
Best wishes.

Web Dynpro NullPointerException while saving all metadata

Web Dynpro is consitently generating an exception when I click Save All Metadata. Here is the exception text:
Plugin name: Metamodel Core
Plugin ID: com.sap.ide.metamodel.core
Method: saveAllMetaData
Message: postSave failed. projectName = IssueLoan
Exception: java.lang.NullPointerException: null
It looks like it has something to do with re-importation of the model. The sequence is not clear for me.
Did anybody get this error before?

Hi
This seems strange. When do u get this error. Do you get it when you change something to a Webdynpro component and click on Save all metadata or what.
Well if that is the case revert back the changes and try doing them again. This happens when the automatic generation of WebDynpro fails. In most cases you may have to restart your machine and then come in again.
Let me know if it is something other than the problem mentioned above. Maybe some of us would have already encountered it
regards
Ravi

In web dynpro i want explanation/definition for the following things

Hi dudes,
I want explanation *** definition for the following
(1) web dynpro
(2) Cardinality
(3) methods
(4) Nodes
(5) Attributes
(6) Interface
(7) Views
(8) Windows
(9) Mapping
(10)Binding
(11)Model
(12)Controller

Hi,
Here are the defintions for the terms you hav requested-
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms
Extensive platform independence of interfaces
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
A Web Dynpro component is a reusable entity. It summarizes all components that are
required as part of this programming unit for an executable Web Dynpro application.
The Web Dynpro component concept offers a number of advantages:
Structuring of the programming
Creation of easily manageable application blocks
Reusability of whole components
Decoupling of software projects in both time and space
The Web Dynpro component contains any number of windows and views and their
corresponding controllers. Additional Web Dynpro components can also be referenced.
View
A view describes the layout and behavior of a rectangular area of a user interface.
Every Web Dynpro application has at least one view. The layout of a view is made up of
different user interface elements, which can be nested in each other. The positioning of
interface elements in one view is supported by the supplied layout variants.
In addition to the visible part, the layout, a view also contains a controller and a context. The
data to which the elements of the view can be bound are stored and managed in the view
context, enabling them to be represented or used on the screen. The view controller can
contain methods for data retrieval or for processing user input.
Window
A window is used to combine several Views and View Sets (the concept of view sets is only
offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
embedded in a window. A window always contains one or more views, which are connected
by navigation links. One of these views, or a view set, is specified as the start view and is
displayed the first time the window is called.
Windows have inbound and outbound plugs.
Inbound Plugs and Outbound Plugs
A window has one or several inbound or outbound plugs. Using these plugs, a window can be
included into a navigation chain. The concept of these plugs corresponds to the concept of
the plug for a view. Each plug of a window is visible within the entire window and can be used
for navigating within this window. In addition, one or several plugs can be made accessible to
the component interface so that they are visible even beyond the limits of the component in
question. They thus belong to the interface view of the relevant window.
They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
Controller
Controllers are the active parts of a Web Dynpro application. They define how the user can
interact with the Web Dynpro application. The data that a controller can access is defined in
the corresponding context. Different instances of controllers and contexts exist within a Web
Dynpro application.
View Controller
Each view has exactly one view controller, which processes the actions performed by the user in the view.
A view also has exactly one view context, which contains the data required for the view.
Interface Controller
Each Web Dynpro component contains exactly one component controller. This controller is a
global controller that is visible also outside the component. It is thus part of the interface of a
Web Dynpro component.
Context
Definition
The data used in the component or in the view are stored in the context. Read-write access to
this data is available using the controllers as a starting point.
Structure
The data from the contexts is managed in a hierarchical structure. Each context has a root
node, underneath which the individual data fields (attributes) are stored in a tree structure.
You create this tree structure according to the structure of your application.
CONTEXT is generally called as a ROOT Node.
Each context has nodes and attributes also.
Cardinatlity
Each node contains data fields that represent one of the following:
u2022
An individual instance of an object type
u2022
A table of instances.
This property of a node is known as its cardinality. The following table summarizes the
possible cardinalities for a node:
Cardinality Description
1:1 The node contains only one element instance, which is instantiated automatically.
0:1 The node contains only one element instance, which must not be instantiated.
1:n The node can contain multiple element instances, of which at least one must always be
instantiated (and is instantiated automatically).
0:n The node can contain multiple element instances, of which none have to be instantiated.
Further information about this and other properties of context nodes is available in the section
Context-Nodes: Properties.
Recursion Nodes
Dynamic node nesting is possible within a context, creating what is called a recursion node.
The node that is used for recursion is always a predecessor of the new node. The newly
created recursion node is a reference to a predecessor node and therefore cannot be
processed separately. Instead it takes on the structure of the node to be repeated.
Data Binding and Mapping
Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
different ways:
u2022
A UI element of the user interface of the view can be linked with an element of the view
context.
u2022
A mapping can be defined between two global controller contexts, or from a view
context to a global controller context.
The context of a global controller can be linked to a Web Dynpro Model.
Defining Mapping Between Two Contexts
The elements of a view context can be locally defined. In this case (represented in the graphic
below as a "Local Node"), all the contained attributes are only visible within the relevant view.
When the view disappears, the attribute values are deleted.
Event
The component controller allows you to create events.
Events are used to communicate between controllers and enable one controller to trigger
event handlers in a different controller.
Cross-component communication can be implemented using the interface controlleru2019s events.
Events that were created in the component controller are visible within the component only.
Inbound Plugs
Inbound plugs in a view also react like an event. Therefore, when a view is called using an
inbound plug, the event handler that is optionally available for the inbound plug is always
called first. In this case event handling takes place within the current view controller.
UI Element Events
Some UI elements, such as the Button element have special events that are linked with user
actions. These events are predefined and have to be linked with an action at design time.
Actions for UI Element Events
Some UI elements such as the button element can react to a useru2019s interaction: clicking on
the corresponding pushbutton can trigger a handling method to be called within the view
controller. Such UI elements are equipped with one or several general events, which can be
linked with a specific action at design time (switching to a subsequent view, for example). If
such an action is created, an event handler method for this action is created automatically. In
this way, you can equip a UI element event (which has been inserted several times into a
view) with different actions as necessary. The event is then processed by the corresponding
event handler depending on the action that is linked.
Interfaces of Web Dynpro Components
Each component has an interface in order to enable communication between Web Dynpro
components and to enable a component to be called up by a user. This interface consists of
two parts:
Interface View of a Window Contained in a Component
The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
application that can be called by the user.
Reward if helpful.
Best Wishes,
Chandralekha

Activating Web Dynpro DC fails

Hi Experts,
I try to activate my activities. But they fail with an error message. In the error message there is printed that the component and the startup plug is missing. But that's not true. They exist and when i deploy the application to a portal directly the application works. What could be wrong?
Here the build log:
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/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"
 DC model check OK
Start build plugin:
 using build plugin: sap.com/tc/bi/bp/webDynpro
 starting build plugin from : F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 9 (645_VAL_REL, built on 2006-08-26 18:15:25 CEST)
 development component: dc2test (com.chiron.test)
 software component: NWDIDEMO (nwdi)
 location: DI1_DEMO_D
 type: Web Dynpro
 build variant: default
 source location: http://cwte0066:50000/dtr/ws/DEMO/nwdi_NWDIDEMO/dev/active/
 plugin start time: 2007-11-13 12:54:28 GMT+01:00 (CET)
 Java VM: Java HotSpot(TM) 64-Bit Server VM, 1.4.2_12-b03 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Source folder META-INF exists but is empty.
Source folder src/mimes exists but is empty.
Source folder src/configuration exists but is empty.Plugin initialized in 1.219 seconds
Preparing data context..
No 'default' JDK defined, will use running VM.
Data context prepared in 0.078 seconds
Executing macro file..
Using macro file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\macros\build.vm
Creating output file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\gen\default\logs\build.xml
Macro file executed in 0.969 seconds
Starting Ant..
Using build file: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\gen\default\logs\build.xml
Using build target: build
Generation folder: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60
Using Ant version: 1.6.2
compile:
 [echo] Starting dictionary generator
 [ddgen]
 [ddgen] [Info] Property deployment is true: Deployment information is provided!
 [ddgen] [Info] Property sourcepath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\src\packages
 [ddgen] [Info] Property targetpath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_ddic
 [ddgen] [Info] Property archivename: com.chiron.test~dc2test
 [ddgen] [Info] Property vendor: com.chiron.test
 [ddgen] [Info] Property dcname: dc2test
 [ddgen] [Info] Property projectlanguage: de
 [ddgen] [Info] Property language: Available languages are automatically determined!
 [ddgen] [Info] Property addpaths ...
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
 [ddgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] jrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] cmiapi.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproadmin.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynprobasesrvc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproclientserver.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpromodelimpl.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpromodel_dynamicrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynpropdfobject.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproportal.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproprogmodel.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_designtime_coupling.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_designtime_coupling_api.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_repository.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproruntime_repository_pmr.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] webdynproservices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] exception.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] aii_util_misc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] aii_proxy_rt.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] logging.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] logging.perf.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapDictionaryTypeServices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] SapDictionaryTypesRuntime.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [ddgen] [Info] Initialize generation templates from configuration jar:file:/F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
 [ddgen] [Info] Generating dbtables/sdmDeployDd.xml
 [ddgen] [Info] Generation finished (4 seconds)
 [ddgen]
 [timer] Dictionary generator finished in 4.625 seconds
 [mkdir] Created dir: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_ddic\datatypes
 [echo] Starting WebDynpro generator
 [wdgen]
 [wdgen] [Info] Property deployment is true: Deployment information is provided!
 [wdgen] [Info] Property sourcepath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\DCs\com.chiron.test\dc2test\_comp\src\packages
 [wdgen] [Info] Property targetpath: F:\usr\sap\DI1\JC00\j2ee\cluster\server0\temp\CBS\b\.B\116\t\5DD1DDDCD52BCDFBF8231FF394BC4A60\gen_wdp
 [wdgen] [Info] Property archivename: com.chiron.test~dc2test
 [wdgen] [Info] Property vendor: com.chiron.test
 [wdgen] [Info] Property dcname: dc2test
 [wdgen] [Info] Property projectlanguage: de
 [wdgen] [Info] Property language: Available languages are automatically determined!
 [wdgen] [Info] Property addpaths ...
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extddic/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/model
 [wdgen] [Info] SapMetamodelDictionaryContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] jrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.mw.jco/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapMetamodelWebdynproContent.zip - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] cmiapi.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/cmi/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproadmin.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynprobasesrvc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproclientserver.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpromodelimpl.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpromodel_dynamicrfc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynpropdfobject.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproportal.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproprogmodel.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_designtime_coupling.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_designtime_coupling_api.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_repository.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproruntime_repository_pmr.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] webdynproservices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/wd/webdynpro/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] exception.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.exception/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] aii_util_misc.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.util.misc/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] aii_proxy_rt.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/com.sap.aii.proxy.framework/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] logging.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] logging.perf.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/logging/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapDictionaryTypeServices.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] SapDictionaryTypesRuntime.jar - F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/ddic/ddicruntime/_comp/gen/default/public/default/lib/java
 [wdgen] [Info] Initialize generation templates from configuration jar:file:/F:/usr/sap/DI1/JC00/j2ee/cluster/server0/temp/CBS/b/.B/116/DCs/sap.com/tc/bi/extwd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
 [wdgen] [Error] com.sap.chiron.DITestApp2 --> Application DITestApp2: Component is missing
 [wdgen] [Error] com.sap.chiron.DITestApp2 --> Application DITestApp2: Startup plug is missing
 [wdgen] [Info] Catching throwable null [wdgen] [Info] com.sap.webdynpro.generation.ant.GenerationAntTaskError
 [wdgen] at com.sap.webdynpro.generation.ant.GenerationAnt.showCheckResult(GenerationAnt.java:157)
 [wdgen] at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2047)
 [wdgen] at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1554)
 [wdgen] at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:215)
 [wdgen] at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [wdgen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [wdgen] at java.lang.reflect.Method.invoke(Method.java:324)
 [wdgen] at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
 [wdgen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
 [wdgen] at org.apache.tools.ant.Task.perform(Task.java:364)
 [wdgen] at org.apache.tools.ant.Target.execute(Target.java:341)
 [wdgen] at org.apache.tools.ant.Target.performTasks(Target.java:369)
 [wdgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
 [wdgen] at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:111)
 [wdgen] at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:62)
 [wdgen] at com.sap.tc.buildplugin.AbstractPlugin.handleBuildStepSequence(AbstractPlugin.java:222)
 [wdgen] at com.sap.tc.buildplugin.AbstractPlugin.performBuild(AbstractPlugin.java:199)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 [wdgen] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 [wdgen] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [wdgen] at java.lang.reflect.Method.invoke(Method.java:324)
 [wdgen] at com.sap.tc.buildtool.PluginCommunicator.maybeInvoke(PluginCommunicator.java:114)
 [wdgen] at com.sap.tc.buildtool.PluginCommunicatorV2.communicate(PluginCommunicatorV2.java:42)
 [wdgen] at com.sap.tc.buildtool.PluginHandlerImpl.handlePluginCommunication(PluginHandlerImpl.java:354)
 [wdgen] at com.sap.tc.buildtool.PluginHandlerImpl.execute(PluginHandlerImpl.java:176)
 [wdgen] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
 [wdgen] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
 [wdgen] at com.sap.tc.buildcontroller.CBSBuildController.main(CBSBuildController.java:168)
 [wdgen] ERROR: Unknown exception during generation null (com.sap.webdynpro.generation.ant.GenerationAntTaskError)
 [wdgen] ERROR: Generation failed due to errors (0 seconds)
Ant runtime 6.234 seconds
Ant build finished with ERRORS
[Error] Generation failed!
Error: Build stopped due to an error: [Error] Generation failed!
Any help is appreciated!
Regards Manuel

Hi Manuel,
that red flash is visible on a WebDynpro application in a WD specific view, right? I'm not a WebDynpro expert but I would assume that it indicates an issue with the application - probably the same thing that is reported by the central build.
Do you get the same error message in a local DC build in your NWDS?
(BTW: The "folder ... exists but is empty" is usually not relevant. The folders mentioned in the log may be empty as they are only used for special purposes. If they are defined in the DC Metadata CBS will create empty folders in the filesystem and the build plugin simply checks this. If the folders do exists in your local NWDS and contain files then there's something wrong, otherwise it should be safe to ignore the message.)
From your description I would assume that something is really wrong with your WebDynpro application, maybe you accidentally deleted the component? (Maybe the WD forum is better suited for such questions?)
Regards,
Marc

Property Metadata in Web Dynpro

Similar Messages

Maybe you are looking for