I though it was a good starting point to test purpose but you're right, it may be better to create your own farm.
Maybe you can "copy" a class in your project like DashBoardActionsBean, make the class implements ResultsProviderFarm and modify everything that is related to the new class name and new class location (package name, annotation declaration...) I guess that the "farm" definition is based on the Seam class name (see @Name annotation) and the fact that the class implements ResultsProviderFarm... I don't know if what I said is right, it's just some ideas... Maybe Narcis has a more clear answer (is there an extension point to contribute to activate a new farm ?) PS : if your project didn't contain any .java file before you'll have to add an ejb-jar.xml file in your META-INF directory and a seam.properties file in the src/main/resources directory. It enables your file to be managed by seam, look at the dgac demo we did for example purpose. Damien _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
