We have had problems with XPages-enabled applications that inherent design elements from a template. The problem has been that .class files and files like plugin.xml and .project per default has been set to prohibit design refresh or design replace (the flag P has been set in the $flags field).

There are now a new functionality that can be used to set the flag for design elements called "Set prohibit refresh property". (By the way, this dialog should really be re-disigned so that it is more understandable. Replace the top checkbok with a pair of radio buttons, one which sets design prohibit refresh and the other wich removes design prohibit.) This works, but with a big caveat if I have interpreted my experiments correctly.

If you change a class in a Java design element and recompile the template and then run "load design" on the server console the new code is inherented and the application works. But if I chose to refresh the design in the Domino Designer by right clicking the application and selecting "Application -> Refresh design" it does not work. If I try to run the application (its a web application) i get an http 500 error. And if I examine the project files in the nsf I can se that plugin.xml and .project has gotten their P flags back.

So what is happening here? Should it be like this. If we must run the server command instead of updating the design directly in the Domino Designer it will definitley slow down our development.