The way I understand it is that these files are completely optional. All of what is done in these files can be done through the Admin portal.
With that said, we really like defining these files. It means we can drop our application in on any JBoss portal server and have it configured for us. Our layout is pretty static and it's the only way I know of to manage the configuration and easily duplicate the configuration through our environments (dev, qa, uat, prod).
Thanks, I found the administration for these operations now. I just read the chapter about portlet deployment, and got the impression that they were required.
Could you point out exactly which chapter you are referring to?
http://docs.jboss.com/jbportal/v2.6.4/referenceGuide/html/xmldescriptors.html#descriptors_portlet is pretty explicit on the fact that these descriptors are optional...
I was following the tutorials in the reference guide: http://docs.jboss.com/jbportal/v2.6.4/referenceGuide/html/tutorials.html#d0e2127
The chapter you pointed was pretty clear, so thanks for pointing that out.
Maybe it should indeed made clearer in the tutorial that the descriptors are optional.
The documentation does not tell what descriptors are optional and what descriptors are mandatory?
Descriptors is a solution to automating the deployment, the problem is that these are read and written to the database at every start of the server.
If descriptors are not mandatory then it could build a war to deploy/update and a war to "run". Could you tell what files are optional?
All JBoss descriptor files are optional. If it's not part of JSR 168, you don't have to have it.