Error in CAF Project Deployment

Question

Hi All,
I have created a simple CAF project named as "firstcaf" in NWDS of NetWeaver CE. But at the deployment time I am getting an error like bellow
May 30, 2007 7:11:43 PM /userOut/daView_category (eclipse.UserOutLocation) [Thread[Deploy Thread,5,main]] ERROR: Deploy Exception.An unresolved dependencies error occurred while sorting the deployment batch items regarding the dependencies.; nested exception is:
     java.rmi.RemoteException:  class com.sap.engine.services.dc.cm.deploy.sdu_deps_resolver.UnresolvedDependenciesException:
1. Component: name: 'firstcafear', vendor: 'demo.sap.com', location: 'NetWeaver Developer Studio', version: '20070530190930', software type: 'J2EE', dependencies: '[name: 'cafruntimeear', vendor: 'sap.com', name: 'cafcore~ear', vendor: 'sap.com']'
Unresolved dependency:
name: 'cafruntimeear', vendor: 'sap.com'     ( The component sap.com_cafruntimeear doesn't exist in the deployment batch and is not deployed.)
Unresolved dependency:
name: 'cafcoreear', vendor: 'sap.com'     ( The component sap.com_cafcoreear doesn't exist in the deployment batch and is not deployed.)
Could anybody send me any idea how to resolve this problem?
Another one question regarding WebDynpro. In CE when I am creating a Web Dynpro project I am getting a "web.xml" file under Resources -> WEB-INF. Can anybody tell me why this file is required and what purpose this file will be used?
Thanks and regards
Chandan
Message was edited by: Chandan
        Chandan Jash

Answer 1

Hi,
the answer of the first question is simple - the CAF runtime is not included in the NW CE trial download. Therefore, you can't deploy any CAF projects..
The trial download version includes only the Java EE 5 compatible server, Web Dynpro, and Data Dictionary... No additional tools and technologies such as CAF, Visual Composer, GP and so on are supported in the trial.
The latter however, are available in the official product SAP NetWeaver Composition Environment, which is currently available for productive use through the official SAP ramp-up process.
As to the second question (web dynpro generates web.xml) - the reason for this is that the web dynpro container runs as extension of the standard web container of the server, which runs web components packaged as WAR files. Therefore, it's just a matter of unifying the packaging and deployment artifacts. From web dynpro application developer's perspective, it's all transparent - you are not expected to do any changes to this xml file.
Hope that helps!