A development environment for the factory should be set up before you try to install the development environment for the user interface. Follow this tutorial to set up your factory development environment. The following software packages are necessary for the development of GWT Views for the Qualipso Factory. Information on how to install each package is beyond the scope of this documentation; their respective web sites should provide enough information about that task.
Although not mandatory, the use of Eclipse as a development environment is advised. There are plugins available for both Maven and GWT integration, which provide advantages such as the GWT Development Mode (automatic refresh, debugger, etc), templates, code completion between resources, etc. A great deal of work has been done to make the Maven process compatible with Eclipse. This means that you can compile everything only with Maven, but you can also use Eclipse and use all the pretty features of GWT integrated with Eclipse (with the GWT plugin).
The "Factory UI" is a Maven project stored in the INRIA Subversion repository located at:
It contains all the Maven modules (code) necessary for the development of Qualipso Factory views. To start your development, you have to first checkout this project from the repository.
One point: it shouldn't be necessary to download and compile the whole factory UI just to develop and test one service. So at one near point in time, you will just have to download one pom project (factory-assembly) and a template to develop a view, same procedure as to develop an abstract service.
root.username=root root.password=root server.host=localhost server.port=8080 http.host=localhost http.port=8080 naming.host=localhost naming.port=1099 xacml.policy.repository.classname=org.qualipso.factory.security.repository.file.FilePolicyRepository
... <application-policy name="qualipso"> <authentication> <login-module code="org.jboss.security.ClientLoginModule" flag="required"> <!-- Any existing security context will be restored on logout --> <module-option name="restore-login-identity">true</module-option> </login-module> </authentication> </application-policy> ... <application-policy name="JBossWSDigest"> <authentication> <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="sufficient"> <module-option name="usersProperties">props/jbossws-users.properties</module-option> <module-option name="rolesProperties">props/jbossws-roles.properties</module-option> <module-option name="unauthenticatedIdentity">guest</module-option> </login-module> </authentication> </application-policy> ...
mvn clean install
|Module name||Description||External tool||Compilation|
|factory-ui-service-parent||Parent module for external services||N/A||required|
|factory-ui-shared-OpenParts||OpenParts framework allowing composite integration (every project should inherit it)||N/A||required|
|factory-ui-shared-QGWT||QGWT framework allowing to use a common graphical style (every project should inherit it)||N/A||required|
|factory-ui-shared-skin||Skin framework allowing to customize the style||N/A||required|
|factory-identity-manager||User management module||N/A||required|
|factory-ui-service-bugtracker||Bug tracker module||Mantis||optional|
|factory-ui-service-git||Git module||No (JGit included)||optional|
|factory-ui-service-issuetracker||Issue tracker module||No||optional|
|factory-ui-service-mailing||Mailing list module||??||optional|
|factory-ui-assembly||WAR generator module||N/A||required|
mvn clean package
Question: I'm not really sure, but if you use the eclipse gwt plugin, you don't really need to install GWT sdk, right?
Question: Maybe it's best to download the Eclipse JEE package, which already comes with server integration.
Question: I've seen on the mailing list that the server jetty was required to deploy the factory UI. Why is'nt it a prerequisite ?
Question: Tests on generate lots of warnings about missing resources like 'dummyService_partloaderXX/..nocache.js' or 'dummyService_shellpartloadingXX/...nochace.js' or 'INEXISTENT_SERVICE/...' like on this build, but they seem harmless.
Question: Is there any easier way to do step 4 other than running maven in each modules' dirs?
Question: Factory-ui-test tries to run Selenium tests... it should be 'mvn install'ed only after deploying?