This is the first step to making utilCacheTable concurrent, and
non-blocking. To do so, the constructor has to have no side-effects.
This means it can't modify utilCacheTable itself; this will be moved to
the helper function created above.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@883217 13f79535-47bb-0310-9956-ffa450edef68
Ecommerce, Webtools and hhfacility components
Moved forms from webapp to widget folder
Removed empty folders
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@829443 13f79535-47bb-0310-9956-ffa450edef68
The WebTools main screen is still untouched so that all screens can be reached in the same way as before.
When we are OK with the new screens grouping under menus we will remove the main screen as it is now.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@823806 13f79535-47bb-0310-9956-ffa450edef68
This commit requires ant clean. Also, external libraries that reference GenericDelegator will need to be updated.
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@821643 13f79535-47bb-0310-9956-ffa450edef68
I was planning to wait longer, but I can't wait more. I have added a lot of small trivial changes in this patch and they are blocking me to go further on other issues...
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@813307 13f79535-47bb-0310-9956-ffa450edef68
And there is always this initialisation issue which compels you to choose a file first before being able to choose all files
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@812708 13f79535-47bb-0310-9956-ffa450edef68
in Webtools, in the ECA section of services info, the I have added a column for fields set.
In availableservices.ftl, I have also replaced
<td><b>${uiLabelMap.WebtoolsIsService}</b> ${condition.isService?default(uiLabelMap.CommonNA)}</td>
by
<#if condition.isService?has_content>
<td><b>${uiLabelMap.WebtoolsIsService}</b> ${condition.isService}</td>
<td colspan="2"> </td>
</#if>
I think we don't need to show informations (actually always NA) about attributes not used. But as I was not sure everybody would agree, I only did this one as an example. So What do you think, should we do it for all occurrences ?
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@808786 13f79535-47bb-0310-9956-ffa450edef68
I found on my local machine that for every 100,000 rows in the result set getResultSizeAfterPartialList would take an additional 5-7 seconds to execute.
findCountByCondition was taking roughly 2 seconds at most to count 700,000 records
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@807859 13f79535-47bb-0310-9956-ffa450edef68
A new help system is implemented which is compatible with the current system which uses the ofboz.docs.org site to store the data.
The new help system has a number of advantages over the old version:
1. complete multilanguage without config xml files, using the locale.
2. Having an automatic multilevel index of all help pages using the ContentAssoc entity
3. Using the content manager for retrieval.
4. Template driven, aware of the different visual themes.
5. A first step towards the storage of OFBiz documentation within the OFBiz system itself.
6. Easy update via normal svn in seed data.
7. Aware of portlets on (userdefined) Portal pages.
8. Create awareness of the capabilities of the content component
The reason of this development was the requirement to provide user documents to the customers of Antwebsystems Co.Ltd
Some of the possible extensions could be:
1. a search function
2. print all or specific help files in PDF format
3. make the help screens work better with the business theme
4. Explain how help can be extended
5. In the help screen be able to send a message to the local support team
6. But most of all, create more help content!
git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@804546 13f79535-47bb-0310-9956-ffa450edef68