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
Tags and Categories not saved when form is multipart
I found a possible bug, or maybe some misunderstanding.
When a form includes a file upload, tags and categories are not saved.
In fact, the _assetTagNames and _assetCategoryIds are empty in the serviceContext variable.
This happens in both updateXXX and addXXX.
I tested regenerating the code without <document> and <image> tags, and indeed it get back to work properly.
Apparently, the problem is in extractFields() which rewrites the request variable. However, I checked the serviceContext in the original request: tags and categories are already missing.
The topic is probably the same as post http://www.xmlportletfactory.org/forum/-/message_boards/message/91311
1) I do not understand completely their suggestion, which is probably more complex that shown
2) I'd like to listen an "official" opinion.
I'm using the 6.1 version.
Please note: I'm working with the .vm files in /Resources, so any suggestion to fix the problem by myself is welcome.