Welcome to XMLPortletFactory Home Site
XMLPortletFactory is a software tool that creates database tables maintenance (CRUD) portlets from XML files. Portlets generated only work on Liferay portals, and come out with source files (JSPs, .java, etc.) so programmers can extend and modify whatever is being generated to suit your software development needs. In Help and Support section you will find Wikis, Tutorials and samples to get started.
With XMLPortletFactory you will be able to generate full CRUD working portlets with ease, accelerating your development process, allowing you to focus on higher level tasks.
XMLPortletFactory is licensed under the terms of GNU General Public License version 3.0 (GPLv3), and is OS Independent.
Note: XMLPortletFactory is still a young project, which ha not passed all possible tests and although is very solid and I use it in production environments, you should use it after appropriate tests.
Some of the most noticeable benefits
- Frees you of 99% coding time in CRUD table maintenance portlets. You obtain full working portlet with all source code, programmers heaven!!!.
- No more problems with versions. You make one XML file, generate portlet in all 6.0.x, 6.1.x and 6.2.x versions of Liferay.
- Forget about creating tables. Because XMLPortletFactory uses Liferay's service builder, tables are automatically created for you at portlet deployment.
- Languages English, French, Italian, Finnish and Spanish allready implemented, easy to implement other languajes.
- Is GPLv3 licensed. The GNU General Public License is a free, copyleft license for software and other kinds of works.
- Your developed XMLs get the benefits of new XMLPortletFactory developments and improvements.
- Generated portlets use Liferay's search container, tags, etc. so they have very "Liferay" behavior, melting very well with themes.
Saludos, Jack A. Rider
RE: Search doesn't work in multi application
I did it as follows:
Made the search code part of the .vm template, generating the portlet java file.
I updated the Portlet_XXXXXXPortlet_java.vm with the code, necessary to do the proper filtering. It was actually quite easy. If you are interested in the actual code modification, let me know.
Other ways include modifying the schema and/or using conditional schema elements to enable/disable <filter> processing only if a <mdfilter>true</mdilter> (as in master-detail filter new tag) is present...
Again, those are just ideas...