The Compiere ERP package ([url removed, login to view]) uses metadata to describe the windows and elements used within the application. They are role-specific. Currently Compiere has a Swing client interface and a web-based interface. We are not satisfied with either, and instead want a new interface based upon XUL ([url removed, login to view]). The task we require is to create a Java routine that will take a user’s authentication credentials and window selection option chosen and produce XUL output. You can get a good heads-start towards how to accomplish this by reviewing the Compiere servlet code. Ideally, this routine will be a Cocoon ([url removed, login to view]) transformer class. Extra money will be paid for this functionality, and in particular, if the Cocoon authentication mechanism is integrated. The new interface we are building will be based upon a Cocoon framework, and we’d like to use this class as part of a pipeline to dynamically construct the interface elements based upon the URL selected and the authentication credentials associated with the user’s session (based upon Compiere’s authentication framework). Ultimately, XSL stylesheets will be applied to the XUL to create an HTML or Thinlet-based interface ([url removed, login to view]). This, however, is outside of the current scope. Possible future work includes developing Cocoon flow-control scripts (based on Woody) to manage/control screen navigation. Developer must check-in code nightly to a CVS repository.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be provided in ANT-runnable scripts with JUnit test classes. Cocoon sitemap(s) with test URLs are highly desireable.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. However, it is likely that your work will be transferred to a GPL-type license and submitted to Compiere's open-source organization. We feel strongly about using and contributing back to the open-source community.
4) We require nighly source code check-in via our CVS repository and usage of our bugzilla bug tracking system. Usage of Eclipse 3 is desired so we have consistent project setup.
Java 1.4.2, Linux or Windows. All software can be provided by us, and is all open-source.