date:20121120


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-5077:
--

Attachment: apache-ofbiz-getting-started.html

I have removed sidebar and add a line to have a link to mailing-list.
Currently link is to wiki but this page should be migrate to html.

 apache-ofbiz-getting-started wiki page migration to static
 --

 Key: OFBIZ-5077
 URL: https://issues.apache.org/jira/browse/OFBIZ-5077
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor
 Attachments: apache-ofbiz-getting-started.html, 
 apache-ofbiz-getting-started.html, OFBIZ-5077.patch


 Migration done by creating the new page by copy-paste from index.html and 
 change main content.
 I have choose to use the sidebar to not have link to mailing list or source 
 repository in the main content.
 I have remove in the sidebar the DemoSites part to avoid update maintenance 
 each time a new release is published.
 For the link at the beginning for the ofbiz-getting-started page, I have 
 tried to show clearly it's link to the wiki site.
 Say me if yes or not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning up the OFBiz Confluence spaces

2012-11-20 Thread Christian Geisert


Am 20.11.2012 09:52, schrieb Jacopo Cappellato:

Hi all,

we all are aware of the problems affecting our content in Confluence but before 
we discuss the next steps and evaluate different options and their pros and 
cons, in my opinion it would make sense to aggregate all the 5 spaces into 2. 
This would give us a rather easy and actionable plan that should improve the 
current situation (less spaces to administer etc...).


[..]


The end result would be:

* OFBiz website: html pages or ASF CMS
* Project Administration: Confluence space or ASF CMS
* Public Wiki: Confluence space

What do you think?


+100

Christian

[jira] [Created] (OFBIZ-5078) apache-ofbiz-project-overview migration from wiki to website

Olivier Heintz created OFBIZ-5078:
-

 Summary: apache-ofbiz-project-overview migration from wiki to 
website
 Key: OFBIZ-5078
 URL: https://issues.apache.org/jira/browse/OFBIZ-5078
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Priority: Minor


Created by copied html source of wiki page.
Comment the workflow deprecated part.

Add in the beginning page a override style defintion coming from download htlm 
page to have a correct width page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (OFBIZ-5078) apache-ofbiz-project-overview migration from wiki to website


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato reassigned OFBIZ-5078:


Assignee: Jacopo Cappellato

 apache-ofbiz-project-overview migration from wiki to website
 

 Key: OFBIZ-5078
 URL: https://issues.apache.org/jira/browse/OFBIZ-5078
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor

 Created by copied html source of wiki page.
 Comment the workflow deprecated part.
 Add in the beginning page a override style defintion coming from download 
 htlm page to have a correct width page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-5078) apache-ofbiz-project-overview migration from wiki to website


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-5078:
--

Attachment: OFBIZ-5078.patch
apache-ofbiz-project-overview.html

 apache-ofbiz-project-overview migration from wiki to website
 

 Key: OFBIZ-5078
 URL: https://issues.apache.org/jira/browse/OFBIZ-5078
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor
 Attachments: apache-ofbiz-project-overview.html, OFBIZ-5078.patch


 Created by copied html source of wiki page.
 Comment the workflow deprecated part.
 Add in the beginning page a override style defintion coming from download 
 htlm page to have a correct width page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4949) Add a new attribute for entity-engine-xml tag, nullify-absent-fields

2012-11-20 Thread Nicolas Malin (JIRA)


[ 
https://issues.apache.org/jira/browse/OFBIZ-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500961#comment-13500961
 ] 

Nicolas Malin commented on OFBIZ-4949:
--

My preference is #3.

Scott, I can implement your idea, if we have a consensus on it

 Add a new attribute for entity-engine-xml tag, nullify-absent-fields
 

 Key: OFBIZ-4949
 URL: https://issues.apache.org/jira/browse/OFBIZ-4949
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
Reporter: Olivier Heintz
Priority: Minor
 Attachments: OFBIZ-4949-NMA.patch, OFBIZ-4949.patch, 
 OFBIZ-4949.patch, OFBIZ-4949.patch


 This enhancement is useful when a entity is load by reader (ex: seed) and 
 sometime, it could be modify in data file. If a field is change from a value 
 to null, currently this modification will not be done in the next load.
 When you are first importing new data, quite naturally all fields other than 
 those specified in the file will be null. If, however, you're updating 
 existing data, you might want any field not specified in the file to retain 
 its current value, or you might want the contents of the file to specify 
 everything about a record, in other words take this data and null out the 
 rest. The alternative to set-other-fields-to-null (or whatever else we  
 might call it) would be a huge number of attribute= in the file.
 For portletWidget, entity PortalPortal have a lot of field with potential 
 default value, so sometime, first release use some field and when it's 
 reviewed and corrected, some field are changed to null to use the default 
 value (to follow best practice).
 This enhancement will be very useful for portletData file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4949) Add a new attribute for entity-engine-xml tag, nullify-absent-fields

2012-11-20 Thread Adrian Crum (JIRA)

[
https://issues.apache.org/jira/browse/OFBIZ-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1350#comment-1350
]

Adrian Crum commented on OFBIZ-4949:

I prefer #3. It is similar to what I had in mind for the UEL integration.

I was thinking the UEL integration would use a child element like
import-context var1=foo var2=bar.../.

Add a new attribute for entity-engine-xml tag, nullify-absent-fields

Key: OFBIZ-4949
URL: https://issues.apache.org/jira/browse/OFBIZ-4949
Project: OFBiz
Issue Type: Sub-task
Components: framework
Affects Versions: SVN trunk
Reporter: Olivier Heintz
Priority: Minor
Attachments: OFBIZ-4949-NMA.patch, OFBIZ-4949.patch,
OFBIZ-4949.patch, OFBIZ-4949.patch

This enhancement is useful when a entity is load by reader (ex: seed) and
sometime, it could be modify in data file. If a field is change from a value
to null, currently this modification will not be done in the next load.
When you are first importing new data, quite naturally all fields other than
those specified in the file will be null. If, however, you're updating
existing data, you might want any field not specified in the file to retain
its current value, or you might want the contents of the file to specify
everything about a record, in other words take this data and null out the
rest. The alternative to set-other-fields-to-null (or whatever else we
might call it) would be a huge number of attribute= in the file.
For portletWidget, entity PortalPortal have a lot of field with potential
default value, so sometime, first release use some field and when it's
reviewed and corrected, some field are changed to null to use the default
value (to follow best practice).
This enhancement will be very useful for portletData file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4949) Add a new attribute for entity-engine-xml tag, nullify-absent-fields


[ 
https://issues.apache.org/jira/browse/OFBIZ-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501117#comment-13501117
 ] 

Jacopo Cappellato commented on OFBIZ-4949:
--

I like #3 too: an optional child element.
The following examples would then be valid xml files.
The default mode is create-update (as in current implementation); the 
following two are equivalent and both valid:
{code}
entity-engine-xml
Entity fieldId=ABC description=abc/
Entity fieldId=DEF description=def/
/entity-engine-xml
{code}
{code}
entity-engine-xml
create-update
Entity fieldId=ABC description=abc/
Entity fieldId=DEF description=def/
/create-update
/entity-engine-xml
{code}
The other modes need to be explicitly set:

{code}
entity-engine-xml
create-replace
Entity fieldId=ABC description=abc/
Entity fieldId=DEF description=def/
/create-replace
/entity-engine-xml
{code}
and you can have several modes:
{code}
entity-engine-xml
Entity fieldId=ABC description=abc/
create-replace
Entity fieldId=DEF description=def/
/create-replace
/entity-engine-xml
{code}
or the same:
{code}
entity-engine-xml
create-update
Entity fieldId=ABC description=abc/
/create-update
create-replace
Entity fieldId=DEF description=def/
/create-replace
/entity-engine-xml
{code}


 Add a new attribute for entity-engine-xml tag, nullify-absent-fields
 

 Key: OFBIZ-4949
 URL: https://issues.apache.org/jira/browse/OFBIZ-4949
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
Reporter: Olivier Heintz
Priority: Minor
 Attachments: OFBIZ-4949-NMA.patch, OFBIZ-4949.patch, 
 OFBIZ-4949.patch, OFBIZ-4949.patch


 This enhancement is useful when a entity is load by reader (ex: seed) and 
 sometime, it could be modify in data file. If a field is change from a value 
 to null, currently this modification will not be done in the next load.
 When you are first importing new data, quite naturally all fields other than 
 those specified in the file will be null. If, however, you're updating 
 existing data, you might want any field not specified in the file to retain 
 its current value, or you might want the contents of the file to specify 
 everything about a record, in other words take this data and null out the 
 rest. The alternative to set-other-fields-to-null (or whatever else we  
 might call it) would be a huge number of attribute= in the file.
 For portletWidget, entity PortalPortal have a lot of field with potential 
 default value, so sometime, first release use some field and when it's 
 reviewed and corrected, some field are changed to null to use the default 
 value (to follow best practice).
 This enhancement will be very useful for portletData file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-5079) ofbiz-documentation-index.html

Olivier Heintz created OFBIZ-5079:
-

 Summary: ofbiz-documentation-index.html
 Key: OFBIZ-5079
 URL: https://issues.apache.org/jira/browse/OFBIZ-5079
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-5079) ofbiz-documentation-index merge - migration from wiki to html page


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-5079:
--

   Priority: Minor  (was: Major)
Description: 
Proposition for a new Documentation.html page.
This new one is a merge between current documentation and 
ofbiz-documentation-index.

This is the first step.
The second step is to remove some older link and/or added some. 
Summary: ofbiz-documentation-index merge - migration from wiki to html 
page  (was: ofbiz-documentation-index.html)

 ofbiz-documentation-index merge - migration from wiki to html page
 --

 Key: OFBIZ-5079
 URL: https://issues.apache.org/jira/browse/OFBIZ-5079
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Priority: Minor
 Attachments: documentation.html


 Proposition for a new Documentation.html page.
 This new one is a merge between current documentation and 
 ofbiz-documentation-index.
 This is the first step.
 The second step is to remove some older link and/or added some. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-5079) ofbiz-documentation-index merge - migration from wiki to html page


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-5079:
--

Attachment: documentation.html

 ofbiz-documentation-index merge - migration from wiki to html page
 --

 Key: OFBIZ-5079
 URL: https://issues.apache.org/jira/browse/OFBIZ-5079
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Priority: Minor
 Attachments: documentation.html


 Proposition for a new Documentation.html page.
 This new one is a merge between current documentation and 
 ofbiz-documentation-index.
 This is the first step.
 The second step is to remove some older link and/or added some. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (OFBIZ-5078) apache-ofbiz-project-overview migration from wiki to website


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-5078:
--

Attachment: apache-ofbiz-project-overview.html

only correction on title page

 apache-ofbiz-project-overview migration from wiki to website
 

 Key: OFBIZ-5078
 URL: https://issues.apache.org/jira/browse/OFBIZ-5078
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor
 Attachments: apache-ofbiz-project-overview.html, 
 apache-ofbiz-project-overview.html, OFBIZ-5078.patch


 Created by copied html source of wiki page.
 Comment the workflow deprecated part.
 Add in the beginning page a override style defintion coming from download 
 htlm page to have a correct width page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning up the OFBiz Confluence spaces

2012-11-20 Thread Olivier Heintz

Le 20/11/2012 09:52, Jacopo Cappellato a écrit :
 Hi all,

 we all are aware of the problems affecting our content in Confluence but 
 before we discuss the next steps and evaluate different options and their 
 pros and cons, in my opinion it would make sense to aggregate all the 5 
 spaces into 2. This would give us a rather easy and actionable plan that 
 should improve the current situation (less spaces to administer etc...).

 Currently we have the following Confluence spaces:

 Public Wiki
 End-User Documentation
 Technical Documentation
 Requirements and Designs
 Project Administration

 Because of a series of problems (lack of contributions and technical issues 
 with the Confluence instance offered by the ASF) the initial plan was not 
 very successful and we now have some spaces that are not used much and some 
 overlapping and confusion on the content of each.
 For this reason I am proposing the following change:

 1) copy the content from:

 End-User Documentation
 Technical Documentation
 Requirements and Designs

 to Public Wiki

 2) remove the spaces:

 End-User Documentation
 Technical Documentation
 Requirements and Designs

 3) keep the Project Administration space as is for now (where write access is 
 granted only to committers): we could then consider the migration to the new 
 ASF CMS technology starting from this space (if possible); if we are happy 
 and it works well we could plan on migrating the static html files of our 
 site to it too as a second step.

 The end result would be:

 * OFBiz website: html pages or ASF CMS
 * Project Administration: Confluence space or ASF CMS
 * Public Wiki: Confluence space

 What do you think?
+1
I have done a merge of OFBiz website Documentation page with the
ofbiz-documentation-index wiki page, to have more visibility of what is
where.
I think that some wiki page should be migrated to ofbiz user help
integrated to ofbiz.
 Jacopo

[jira] [Updated] (OFBIZ-5080) Screen Cache Not working

2012-11-20 Thread K Sharad Bhushan (JIRA)


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

K Sharad Bhushan updated OFBIZ-5080:


Attachment: AbstractCache.java.patch

 Screen Cache Not working
 

 Key: OFBIZ-5080
 URL: https://issues.apache.org/jira/browse/OFBIZ-5080
 Project: OFBiz
  Issue Type: Bug
  Components: ALL APPLICATIONS
Affects Versions: SVN trunk, Release 11.04.01
Reporter: K Sharad Bhushan
Priority: Minor
  Labels: patch
 Fix For: SVN trunk

 Attachments: AbstractCache.java.patch


 I have been trying to use screen cache, and identified that it was not 
 working as expected. 
 When debugged i have found that the key name used by cache and key name used 
 for look up in for a cache were not same. 
 I have corrected that and have tested in my enviornment.Not sure if any one 
 was using it
 Attaching the patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (OFBIZ-5080) Screen Cache Not working

2012-11-20 Thread K Sharad Bhushan (JIRA)

K Sharad Bhushan created OFBIZ-5080:
---

 Summary: Screen Cache Not working
 Key: OFBIZ-5080
 URL: https://issues.apache.org/jira/browse/OFBIZ-5080
 Project: OFBiz
  Issue Type: Bug
  Components: ALL APPLICATIONS
Affects Versions: SVN trunk, Release 11.04.01
Reporter: K Sharad Bhushan
Priority: Minor
 Fix For: SVN trunk
 Attachments: AbstractCache.java.patch

I have been trying to use screen cache, and identified that it was not working 
as expected. 

When debugged i have found that the key name used by cache and key name used 
for look up in for a cache were not same. 

I have corrected that and have tested in my enviornment.Not sure if any one was 
using it

Attaching the patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (OFBIZ-5079) ofbiz-documentation-index merge - migration from wiki to html page


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato reassigned OFBIZ-5079:


Assignee: Jacopo Cappellato

 ofbiz-documentation-index merge - migration from wiki to html page
 --

 Key: OFBIZ-5079
 URL: https://issues.apache.org/jira/browse/OFBIZ-5079
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor
 Attachments: documentation.html


 Proposition for a new Documentation.html page.
 This new one is a merge between current documentation and 
 ofbiz-documentation-index.
 This is the first step.
 The second step is to remove some older link and/or added some. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (OFBIZ-5080) Screen Cache Not working


 [ 
https://issues.apache.org/jira/browse/OFBIZ-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacopo Cappellato reassigned OFBIZ-5080:


Assignee: Jacopo Cappellato

 Screen Cache Not working
 

 Key: OFBIZ-5080
 URL: https://issues.apache.org/jira/browse/OFBIZ-5080
 Project: OFBiz
  Issue Type: Bug
  Components: ALL APPLICATIONS
Affects Versions: SVN trunk, Release 11.04.01
Reporter: K Sharad Bhushan
Assignee: Jacopo Cappellato
Priority: Minor
  Labels: patch
 Fix For: SVN trunk

 Attachments: AbstractCache.java.patch


 I have been trying to use screen cache, and identified that it was not 
 working as expected. 
 When debugged i have found that the key name used by cache and key name used 
 for look up in for a cache were not same. 
 I have corrected that and have tested in my enviornment.Not sure if any one 
 was using it
 Attaching the patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-5080) Screen Cache Not working


[ 
https://issues.apache.org/jira/browse/OFBIZ-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501311#comment-13501311
 ] 

Jacopo Cappellato commented on OFBIZ-5080:
--

It seems that you are right and it has been broken a long time ago during a 
code refactoring by the following commit:
{code}

Author: doogie
Date: Mon Nov 23 03:03:59 2009
New Revision: 883226

URL: http://svn.apache.org/viewvc?rev=883226view=rev
Log:
Use getOrCreateUtilCache here too.

Modified:
   ofbiz/trunk/framework/widget/src/org/ofbiz/widget/cache/AbstractCache.java

Modified: 
ofbiz/trunk/framework/widget/src/org/ofbiz/widget/cache/AbstractCache.java
URL: 
http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/src/org/ofbiz/widget/cache/AbstractCache.java?rev=883226r1=883225r2=883226view=diff
==
--- ofbiz/trunk/framework/widget/src/org/ofbiz/widget/cache/AbstractCache.java 
(original)
+++ ofbiz/trunk/framework/widget/src/org/ofbiz/widget/cache/AbstractCache.java 
Mon Nov 23 03:03:59 2009
@@ -49,14 +49,7 @@
}

protected UtilCacheWidgetContextCacheKey, GenericWidgetOutput 
getOrCreateCache(String widgetName) {
-synchronized (UtilCache.utilCacheTable) {
-String name = getCacheName(widgetName);
-UtilCacheWidgetContextCacheKey, GenericWidgetOutput cache = 
UtilCache.findCache(name);
-if (cache == null) {
-cache = UtilCache.createUtilCache(name, 0, 0, true);
-cache.setPropertiesParams(new String[] {name});
-}
-return cache;
-}
+String name = getCacheName(widgetName);
+return UtilCache.getOrCreateUtilCache(widgetName, 0, 0, 0, true, 
false, name);
}
}
{code}

 Screen Cache Not working
 

 Key: OFBIZ-5080
 URL: https://issues.apache.org/jira/browse/OFBIZ-5080
 Project: OFBiz
  Issue Type: Bug
  Components: ALL APPLICATIONS
Affects Versions: SVN trunk, Release 11.04.01
Reporter: K Sharad Bhushan
Assignee: Jacopo Cappellato
Priority: Minor
  Labels: patch
 Fix For: SVN trunk

 Attachments: AbstractCache.java.patch


 I have been trying to use screen cache, and identified that it was not 
 working as expected. 
 When debugged i have found that the key name used by cache and key name used 
 for look up in for a cache were not same. 
 I have corrected that and have tested in my enviornment.Not sure if any one 
 was using it
 Attaching the patch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (OFBIZ-4949) Add a new attribute for entity-engine-xml tag, nullify-absent-fields


[ 
https://issues.apache.org/jira/browse/OFBIZ-4949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501352#comment-13501352
 ] 

Jacques Le Roux commented on OFBIZ-4949:


Indeed #3 sounds good to me too, flexible and powerful.
Even better when suggested by Jacopo ;), thanks!

 Add a new attribute for entity-engine-xml tag, nullify-absent-fields
 

 Key: OFBIZ-4949
 URL: https://issues.apache.org/jira/browse/OFBIZ-4949
 Project: OFBiz
  Issue Type: Sub-task
  Components: framework
Affects Versions: SVN trunk
Reporter: Olivier Heintz
Priority: Minor
 Attachments: OFBIZ-4949-NMA.patch, OFBIZ-4949.patch, 
 OFBIZ-4949.patch, OFBIZ-4949.patch


 This enhancement is useful when a entity is load by reader (ex: seed) and 
 sometime, it could be modify in data file. If a field is change from a value 
 to null, currently this modification will not be done in the next load.
 When you are first importing new data, quite naturally all fields other than 
 those specified in the file will be null. If, however, you're updating 
 existing data, you might want any field not specified in the file to retain 
 its current value, or you might want the contents of the file to specify 
 everything about a record, in other words take this data and null out the 
 rest. The alternative to set-other-fields-to-null (or whatever else we  
 might call it) would be a huge number of attribute= in the file.
 For portletWidget, entity PortalPortal have a lot of field with potential 
 default value, so sometime, first release use some field and when it's 
 reviewed and corrected, some field are changed to null to use the default 
 value (to follow best practice).
 This enhancement will be very useful for portletData file. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Cleaning up the OFBiz Confluence spaces

2012-11-20 Thread Jacques Le Roux

From: Jacopo Cappellato jacopo.cappell...@gmail.com
 Hi all,
 
 we all are aware of the problems affecting our content in Confluence but 
 before we discuss the next steps and evaluate different options and their 
 pros and cons, in my opinion it would make sense to aggregate all the 5 
 spaces into 2. This would give us a rather easy and actionable plan that 
 should improve the current situation (less spaces to administer etc...).
 
 Currently we have the following Confluence spaces:
 
 Public Wiki
 End-User Documentation
 Technical Documentation
 Requirements and Designs
 Project Administration
 
 Because of a series of problems (lack of contributions and technical issues 
 with the Confluence instance offered by the ASF) the initial plan was not 
 very successful and we now have some spaces that are not used much and some 
 overlapping and confusion on the content of each.
 For this reason I am proposing the following change:
 
 1) copy the content from:
 
 End-User Documentation
 Technical Documentation
 Requirements and Designs
 
 to Public Wiki
 
 2) remove the spaces:
 
 End-User Documentation
 Technical Documentation
 Requirements and Designs
 
 3) keep the Project Administration space as is for now (where write access is 
 granted only to committers): we could then consider the migration to the new 
 ASF CMS technology starting from this space (if possible); if we are happy 
 and it works well we could plan on migrating the static html files of our 
 site to it too as a second step.
 
 The end result would be:
 
 * OFBiz website: html pages or ASF CMS
 * Project Administration: Confluence space or ASF CMS
 * Public Wiki: Confluence space
 
 What do you think?
 
 Jacopo

The plans sounds good to me. I'm constantly  watching changes in wiki, so it's 
not an issue for me to get the non admin parts open. For the rest (ASF CMS) the 
future will tell...

Jacques

[jira] [Commented] (OFBIZ-5079) ofbiz-documentation-index merge - migration from wiki to html page


[ 
https://issues.apache.org/jira/browse/OFBIZ-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501369#comment-13501369
 ] 

Jacques Le Roux commented on OFBIZ-5079:


We will need to change the link to OFBIZ-2219 when the new help will be used. 
We should rather give information directly in the static page.
Also obviously, with Jacopo new suggestion about workspaces grouping, the page 
will need to be modified...

 ofbiz-documentation-index merge - migration from wiki to html page
 --

 Key: OFBIZ-5079
 URL: https://issues.apache.org/jira/browse/OFBIZ-5079
 Project: OFBiz
  Issue Type: Improvement
Reporter: Olivier Heintz
Assignee: Jacopo Cappellato
Priority: Minor
 Attachments: documentation.html


 Proposition for a new Documentation.html page.
 This new one is a merge between current documentation and 
 ofbiz-documentation-index.
 This is the first step.
 The second step is to remove some older link and/or added some. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Is it a good time to remove the debian folder?

2012-11-20 Thread Adam Heath

On 11/16/2012 04:24 AM, Jacopo Cappellato wrote:
 I don't think that the comment is about the license clearance: yesterday I 
 had an email exchange with Daniel Dekany (ddekany) and he is still waiting 
 for the CLA.

Well, that's odd.  I just checked our records, and I signed a CLA on
2012-05-21, and it was mailed the same day.  We keep a copy of all
such agreements, so it looks like this got dropped on their end.

Re: Key-Encryption-key support, r1334257

2012-11-20 Thread Adam Heath

On 11/18/2012 05:38 AM, Carsten Schinzer wrote:
 Hello again and thanks.
 
 ant target works, the different jarfile does in principle as well, would
 need the full cp though incuding the reference to commons-codec library.
 
 I got my stuff and will continue working my way through to make my
 databases and tenant dbs crypto-ready !
 
 Thanks  regards

Yeah, we don't use tenants here, so I have no way to test that.  I
would hope that the system works without actually having a kek
defined, and just would function like it used to(if the kek is
null/not-defined, it skips the code block).

Re: Slim-down effort: current situation

2012-11-20 Thread Adam Heath

On 11/16/2012 05:40 AM, Jacques Le Roux wrote:
 Very well summed up, Paul
 
 Thanks
 
 Jacques
 
 From: madppiper p...@ilscipio.com
 @jacopo: That sounds like a terrific idea of yours! I have to read up on
 [Proposal], but from your outline here, i would say it is a more sincere
 step. 

 @Olivier: I liked your presenation on addon-manager a lot and as already
 discussed would think that a tool like this (sort of like a yum- install
 manager) could be beneficial to whatever we come up with here. But the tool
 for me is an addition to the proposal above, it is not a contradiction to
 it.

AIE! NO YUM!  BAD!  YUM SUCKAGE!

I've had the mis-fortune to use yum, and apt-get both.  The former is
really crappy, slow, and not smart at all.

Re: Slim-down effort: current situation

2012-11-20 Thread Jacques Le Roux

No worries Adam,

Paul gave Yum just as a sort-of-like example. I don't know the addons 
technology, but I'm sure it's not related at all with Yum or even apt-get (more 
Ant and maybe Ivy)
And of course, we all prefer get-apt (at least I do, actually I don't even know 
Yum  :D)

Jacques

From: Adam Heath doo...@brainfood.com
 On 11/16/2012 05:40 AM, Jacques Le Roux wrote:
 Very well summed up, Paul
 
 Thanks
 
 Jacques
 
 From: madppiper p...@ilscipio.com
 @jacopo: That sounds like a terrific idea of yours! I have to read up on
 [Proposal], but from your outline here, i would say it is a more sincere
 step. 

 @Olivier: I liked your presenation on addon-manager a lot and as already
 discussed would think that a tool like this (sort of like a yum- install
 manager) could be beneficial to whatever we come up with here. But the tool
 for me is an addition to the proposal above, it is not a contradiction to
 it.
 
 AIE! NO YUM!  BAD!  YUM SUCKAGE!
 
 I've had the mis-fortune to use yum, and apt-get both.  The former is
 really crappy, slow, and not smart at all.

[jira] [Updated] (OFBIZ-4941) Proposal for a new help system

[
https://issues.apache.org/jira/browse/OFBIZ-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jacques Le Roux updated OFBIZ-4941:
---

Attachment: OFBIZ-4941.patch

New patch without generated files but with a new webhelp.all target to generate
them all in a single shoot. This is for test only, we will commit with the
generated files (in applications\content\webapp\ofbizhelp for now)

To run the webhelp.all target from OFBiz root, use:

ant -f applications/content/template/docbook/webhelp/build.ofbiz.xml
webhelp.all

Proposal for a new help system
--

Key: OFBIZ-4941
URL: https://issues.apache.org/jira/browse/OFBIZ-4941
Project: OFBiz
Issue Type: Wish
Components: ALL COMPONENTS
Affects Versions: SVN trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
Fix For: SVN trunk

Attachments: content.7z, docbook diff.patch, docbook-xsl-1.77.1.zip,
HelpAccounting.jpg, help_content.jpg, help_ofbizhelp.jpg, helppdf.zip,
HelpPerformanceReview1.jpg, HelpPerformanceReview2.jpg, HelpRoadmap.jpg,
help_webhlep.jpg, jh.jar, LicenseFiles.zip, LICENSE.html, OFBIZ-4941.patch,
OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch,
OFBIZ-4941.patch, OFBIZ-4941 POC HR Help.patch, ofbiz-common.xsl,
WebhelpFiles.zip, WebhelpFiles.zip, WebhelpHRAppDocbook.zip,
WebhelpHRAppDocbook.zip, webhelp.jpg

Quoting Tom Burns at OFBIZ-4869
{quote}
This is a status update just to let anyone who is interested know that this
item is being worked on.
I started out using the OFBiz structure for help docs but after a while I
needed/wanted something more expressive.
Here is what I wound up using for development:
Java Help System http://java.net/projects/javahelp/content
DocBook 5: The Definitive Guide
http://www.docbook.org/tdg5/en/html/docbook.html
http://www.docbook.org/xml/5.0/
DocBook XSL: The Complete Guide
http://www.sagehill.net/docbookxsl/index.html

http://sourceforge.net/projects/docbook/files/docbook-xsl/1.77.1/docbook-xsl-1.77.1.zip
Help Master - FE for managing java help files. Best feature drag and drop
TOC creates TOC matching file folder structure. Convenient launcher for
viewing testing. http://www.halogenware.com/software/helpmaster.html
XML Mind XML Editor - Free Personal Edition is far better then editing in
Eclipse. download from http://www.xmlmind.com/xmleditor/download.shtml
Tutorial - DocBook editing with XML Mind XML Editor. Worth going through
http://www.xmlmind.com/xmleditor/tutorial.html
Read Me First style guide from Sun (cost from Amazon 1 cent + shipping)
Attached are some screen shots of the results.
Every screen is/will be documented in a similar structure. This is as much
for defining requirements and testing as for help. More work but worth it.
The screenshots show a Java Help format generated using DocBook XSL. This
will likely not be the final presentation format.
Note the Performance Review screen shots do not match the trunk. There is a
bug in update screen and I did some clean up of labels and drop-down list.
There are issues like this all through the application so I did not want to
get bogged down with patches at this time.
{quote}

[jira] [Commented] (OFBIZ-5077) apache-ofbiz-getting-started wiki page migration to static