[jira] [Commented] (OFBIZ-6644) Webhelp umbrella task

[Ron Wheeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900581#comment-14900581
 ] 

Ron Wheeler commented on OFBIZ-6644:


In response to the question "Can anyone please provide suggestions on how to 
implement the
automatic generation of documents from GIT?" this response was created in the 
DITA users forum with links to 2 articles that might be helpful for us.

--

I’ve given a few conference presentations on Automating DITA Builds
over the past few years. You may find this information useful as you
investigate automation options for your project.

The slides from my talk at DITA North America in Seattle last year are
available here:
.

The presentation was expanded to an article for the CIDM Best Practices
Newsletter:
.

Both outline various automation approaches, including Git hooks and
continuous integration servers like Jenkins (as Radu suggested). Code
samples are included that you can use to trigger builds when you commit
changes to Git.

Hope that helps,

Roger

P.S.

The DITA For Small Teams project 
is also putting together a series of sample projects and resources that
can be used to automate the build process. There has been some
discussion lately about preparing Docker containers that would provide a
pre-configured DITA-OT and Jenkins, but I’m not sure how far that idea
has come.


> Webhelp umbrella task
> -
>
> Key: OFBIZ-6644
> URL: https://issues.apache.org/jira/browse/OFBIZ-6644
> Project: OFBiz
>  Issue Type: Task
>  Components: ALL COMPONENTS
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Priority: Minor
>
> This is only a placeholder to group the issues related with webhelp



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6015) Move Online Help Documentation from Webhelp into Trunk

[Ron Wheeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900577#comment-14900577
 ] 

Ron Wheeler commented on OFBIZ-6015:


in response to the question  "Can anyone please provide suggestions on how to 
implement the
automatic generation of documents from GIT?" this response was created in  the 
DITA users forum with links to 2 articles that might be helpful for us.

--

I’ve given a few conference presentations on Automating DITA Builds
over the past few years. You may find this information useful as you
investigate automation options for your project.

The slides from my talk at DITA North America in Seattle last year are
available here:
.

The presentation was expanded to an article for the CIDM Best Practices
Newsletter:
.

Both outline various automation approaches, including Git hooks and
continuous integration servers like Jenkins (as Radu suggested). Code
samples are included that you can use to trigger builds when you commit
changes to Git.

Hope that helps,

Roger


P.S.

The DITA For Small Teams project 
is also putting together a series of sample projects and resources that
can be used to automate the build process. There has been some
discussion lately about preparing Docker containers that would provide a
pre-configured DITA-OT and Jenkins, but I’m not sure how far that idea
has come. 

> Move Online Help Documentation from Webhelp into Trunk
> --
>
> Key: OFBIZ-6015
> URL: https://issues.apache.org/jira/browse/OFBIZ-6015
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS
>Reporter: Sharan Foga
>Assignee: Sharan Foga
>Priority: Minor
> Attachments: Webhelp Analysis.ods
>
>
> This Jira has been created to manage the migration of all the documentation 
> from the Webhelp branch into the current help system so that it will work 
> with what we already have (essentially so that we dont lose it!).  The 
> original issue for the Webhelp is 
> https://issues.apache.org/jira/browse/OFBIZ-4941
> As well as HR, there is also online documentation for Accounting, 
> Manufacturing (English, German and Dutch), Project Manager and Catalog - 
> though not as complete, so I will be consolidating and moving those too. The 
> files use the docbook format and are compatible with what we have although he 
> implemented everything into one file (i.e book) per module. I now think this 
> is the better way to go.
> Update as at July 2015
> ==
> The original code from the Webhelp branch was updated and converted to an 
> OFBiz addon. 
> The addon was created from the Webhelp branch but is setup as an addon.
> To see a what the webhelp will look like and function like. 
> Go to https://demo.ofbizextra.org/accounting/control/main
> Login as admin/ofbiz
> Select HR and then click the help button (The docbook webhelp should be 
> displayed)
> As well as using docbook and webhelp for displaying it. Some additonal 
> funcitonality has been added. These are as follows:
> 1) There are some ant targets created (e.g. ant webhelp, clean-webhelp)
> 2) There is a flag setup to indicate whether a module has webhelp or uses 
> OFBiz standard help (i.e. what we are using now). 
> To test it on the ofbizextra demo 
> Select Facilities and then click the help button (The normal OFBiz help menu 
> is displayed because no webhelp exists for this module)
> I think this could be good thing as we convert the existing documentation 
> from the current online help format to the webhelp because it wont break 
> anything and leaves the option open for people who are using the existing 
> help system.
> 3) There is also some functionality related to language that looks at the 
> language of the user to see if the webhelp exists in that language. If it 
> doesn't there is a message saying so but that documentation exists in another 
> language 
> The addon uses the patch Files. (.patch) I think this is because the addon 
> tries to maintain compatibility with different OFBiz versions but I think 
> it's still just xml or java code.
> I have done an initial (non technical) analysis of the files and attached 
> that too



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6271) build management with maven

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6271:


How many third party dependencies are part of OFBiz?
Do we need to build each of these as part of OFBiz?

With Maven, we could set up a pprivate repo and build each of the dependencies 
from source and deploy them to a private OFBiz repo to assure ourselves of a 
secure set of jars.

A bit of work to set up and keep it up to date but would add a layer of control 
and security to OFBiz.

It would also reduce the current jar hell where multiple versions of third 
party libraries are listed as transitive dependencies and left to the 
classloader to sort out at run-time.

 build management with maven
 ---

 Key: OFBIZ-6271
 URL: https://issues.apache.org/jira/browse/OFBIZ-6271
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Adam Heath
Priority: Minor
 Attachments: console.log


 This is a new build system; the primary goal will be to not require any 
 changes to existing ofbiz layouts(for backwards compatibility, at least 
 initially).
 These pom.xml files are completely new; the existing build.xml infrastructure 
 will continue to exist.  The existing build.xml will never call into 
 maven(which is what processes the pom.xml), and maven will never call into 
 build.xml either.
 I have already committed a working pom.xml for the top level, and 
 framework/start.  Shortly, I will be adding framework/base and 
 framework/entity, but into this branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6271) build management with maven

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6271:


I did not say that it was a good idea for us:-)

It is a solution for the truly paranoid who does not want to include any jars 
from a public repo and wants to build everything including transitive 
dependencies from sources downloaded from the author.

It is a middle ground for companies that currently forbid the use of any open 
source software for security reasons. 
It would make the inclusion of any open source project very explicit which 
might make an auditor or risk manager sufficiently comfortable to allow some 
open source libraries into a closed shop.

It is a lot more work but not unmanageable. Certainly more efficient than 
banning open source or not using Maven.

Once you have the initial repo populated and want to upgrade a version, you 
would have to look at the transitive dependencies and rebuild all of those that 
also changed. If you removed the old versions at the same time, you would 
quickly find dependencies on the older versions so you could fix those as well.

I would suspect that the repo would be a couple of gigs but not tens of gigs.
Our repo is under 4 gigs with all our stuff as well as the dependencies 
downloaded over the past 8 years. (13 versions of Ant, 10 version of 
commons-logging, 9 versions of poi, 12 versions of jackrabbit).
We probably use over 100 external jars in our largest app which is made up of 
over 70 Maven projects.
So I would not be worried about the size of a private OFBiz repo.

This approach would not interfere with Maven at all.
Maven has no idea how my Nexus repo finds all the artifacts in my builds.
It refers to a single virtual repo in settings.xml and the repo administrator 
(me in our case) defines the contents of that virtual repo.

The fact that our Nexus includes both proxied artifacts from a few other repos 
besides Maven Central and our own hosted repo is hidden from Maven. 
It just asks our repo for stuff and the artifacts get downloaded to the 
developer's cache transparently to the developer.


 build management with maven
 ---

 Key: OFBIZ-6271
 URL: https://issues.apache.org/jira/browse/OFBIZ-6271
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Adam Heath
Priority: Minor
 Attachments: console.log


 This is a new build system; the primary goal will be to not require any 
 changes to existing ofbiz layouts(for backwards compatibility, at least 
 initially).
 These pom.xml files are completely new; the existing build.xml infrastructure 
 will continue to exist.  The existing build.xml will never call into 
 maven(which is what processes the pom.xml), and maven will never call into 
 build.xml either.
 I have already committed a working pom.xml for the top level, and 
 framework/start.  Shortly, I will be adding framework/base and 
 framework/entity, but into this branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6271) build management with maven

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6271:


Maven profiles are inherently evil and draw otherwise good people over to the 
dark side.
The https://maven.apache.org/plugins/maven-antrun-plugin/ can be used as Adam 
suggested but this requires the end user to build a maven project.

I favour a proper installer that allows one to install or upgrade their 
installation in a simple way that is defined in configuration and code that can 
be tested rather than in documentation which gets out of date and depends on 
the user's interpretation of what is written and their abiilty to follow 
instructions and type things accurately.
The installer can be built with Maven as a project.

If someone want to buld a custom installer, they just change the dependencies 
in the installer POM to point to their custom jar files that will override the 
Maven Central official OFBiz jars. 
They can substitute splash pages, panel text, readme, licenses, seed data or 
whatever is required to distribute their custom OFBiz.
THe complexity of seed data, demo data and test data can be hidden from the 
system administrator which could allow theOFBIZ dev team to rethink the data 
loading process witout worrying about complexity.

The installer can offer a default install and offer the person doing the 
install the abililty to ignore components or install options.

It can also do some sanity checks prior to installation.
It can automatically detect the OS to do the right things - desktop 
shortcuts, Windows registry entries, add to start menu - to make the 
installation process easier.
This makes support easier since the installations should become much more 
consistent.

 build management with maven
 ---

 Key: OFBIZ-6271
 URL: https://issues.apache.org/jira/browse/OFBIZ-6271
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Adam Heath
Priority: Minor
 Attachments: console.log


 This is a new build system; the primary goal will be to not require any 
 changes to existing ofbiz layouts(for backwards compatibility, at least 
 initially).
 These pom.xml files are completely new; the existing build.xml infrastructure 
 will continue to exist.  The existing build.xml will never call into 
 maven(which is what processes the pom.xml), and maven will never call into 
 build.xml either.
 I have already committed a working pom.xml for the top level, and 
 framework/start.  Shortly, I will be adding framework/base and 
 framework/entity, but into this branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6271) build management with maven

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6271:


Since the tasks are defined in Maven's lifecycle, I don't think that any 
equivalent to Ant -p makes sense.
Any goals that are defined in plug-ins are pretty well documented in the POM.

What sort of information would you like to see (and when)

mvn -x gives a detailed log of what Maven did while processing the build but 
that is at run-time.

Ron

 build management with maven
 ---

 Key: OFBIZ-6271
 URL: https://issues.apache.org/jira/browse/OFBIZ-6271
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Reporter: Adam Heath
Priority: Minor
 Attachments: console.log


 This is a new build system; the primary goal will be to not require any 
 changes to existing ofbiz layouts(for backwards compatibility, at least 
 initially).
 These pom.xml files are completely new; the existing build.xml infrastructure 
 will continue to exist.  The existing build.xml will never call into 
 maven(which is what processes the pom.xml), and maven will never call into 
 build.xml either.
 I have already committed a working pom.xml for the top level, and 
 framework/start.  Shortly, I will be adding framework/base and 
 framework/entity, but into this branch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6298) Java collection use optimized

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6298:


Since Java 7 is coming to EOL, this might be a good time to consider how the 
Java 8 Stream processing will be used under the various scenarios being 
discussed around the choice of underlying collection structure.

This also affects some of the performance discussion since Streams take 
advantage of multi-core CPUs to process collections in parallel.


 Java collection use optimized
 -

 Key: OFBIZ-6298
 URL: https://issues.apache.org/jira/browse/OFBIZ-6298
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor
  Labels: collection, performance

 With the javolution collection cleaning (OFBIZ-5169,OFBIZ-5781) , we need to 
 realize a second pass to control what instantiation would be better.
 For List between LinkedList, ArrayList
 {quote}
 Using ArrayList, rather than LinkedList, as a default is a good approach 
 because ArrayList will work better in most situations (in terms of 
 algorithmic runtimes and memory footprints).
 However I think it is important to wisely choose ArrayList or LinkedList 
 based on the context, because sometimes a linked list may be a better choice: 
 I am not saying we should do it now and we can tackle this at a later moment, 
 possibly focusing only on list that can be very big and analyzing their usage 
 to see if array or linked list is better; it would be also nice, when we use 
 ArrayList, to see if we can predict the capacity of the list and allocate it 
 at creation: if we can do this we will have a more predictable memory usage 
 and less unpredictable peaks under heavy load (when the array capacity is 
 reached and the array is copied to a new one with double capacity).
 {quote}
 more documentation on :
  * 
 https://docs.oracle.com/javase/tutorial/collections/implementations/list.html
  * 
 http://stackoverflow.com/questions/322715/when-to-use-linkedlist-over-arraylist
 For Map between HashMap and LinkedHashMap :
 {quote}
 Javolution Map Iterators return items in insertion sequence (HashMap does 
 not), so any code relying on the original insertion order must use a 
 LinkedHashMap.
 {quote}
  * 
 http://stackoverflow.com/questions/2889777/difference-between-hashmap-linkedhashmap-and-treemap
 If you detect an optimization, please comments this issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6298) Java collection use optimized

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6298:


http://winterbe.com/posts/2014/07/31/java8-stream-tutorial-examples/ is one 
tutorial.
If you google java stream tutorial you will find lots of entries.

I am not sure how collections are used in OFBiz but there was some talk of 
using a factory to encapsulate creation of collections. 
There may be a case for providing high level functions that encapsulate some 
operations on collections using streams as part of the classes delivered by the 
factory.
If you combine this with the new Java 8 ability to add code to interfaces, 
there may be some interesting possibilities to reduce the amount of code 
required in OFBIz and to hide some of the complexity of dealing with the myriad 
of OFBiz entities. The classes produced by the factory would share the same 
interface but have some methods overridden in the classes to provide the class 
specific behaviour.

I have started to use Streams in other applications that I have written and 
they do reduce the amount of code required. 
They do lock you into Java 8 but so does Oracle's short term view of Java 7- 
OES this year. 
I have only started to look at rewriting some of the interfaces in my 
applications to add default methods to the interfaces. This has a lot of 
potential for my application since it has a lot of classes that share 
processing patterns to implement plug-ins that are configured at runtime using 
Spring. It seems to have the potential to make creation of custom plug-ins a 
lot easier since a new plug-in might only have to override one or two methods 
to implement new functionality.
I would be surprised if this did not apply to OFBiz as well since many business 
processes have similar flows but require some special processing for different 
entities within the same family. 
The ability to pass methods as arguments also should help in these cases as 
well.  

If there is an effort to look at collections, it seems that it would be a good 
time to look at Java 8 since the whole nature of collections is changed and 
Java 8 does optimization that is not possible in Java 7 without adding a lot of 
complexity (parallel processing with multi-core optimization).

 Java collection use optimized
 -

 Key: OFBIZ-6298
 URL: https://issues.apache.org/jira/browse/OFBIZ-6298
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL COMPONENTS
Affects Versions: Trunk
Reporter: Nicolas Malin
Assignee: Nicolas Malin
Priority: Minor
  Labels: collection, performance

 With the javolution collection cleaning (OFBIZ-5169,OFBIZ-5781) , we need to 
 realize a second pass to control what instantiation would be better.
 For List between LinkedList, ArrayList
 {quote}
 Using ArrayList, rather than LinkedList, as a default is a good approach 
 because ArrayList will work better in most situations (in terms of 
 algorithmic runtimes and memory footprints).
 However I think it is important to wisely choose ArrayList or LinkedList 
 based on the context, because sometimes a linked list may be a better choice: 
 I am not saying we should do it now and we can tackle this at a later moment, 
 possibly focusing only on list that can be very big and analyzing their usage 
 to see if array or linked list is better; it would be also nice, when we use 
 ArrayList, to see if we can predict the capacity of the list and allocate it 
 at creation: if we can do this we will have a more predictable memory usage 
 and less unpredictable peaks under heavy load (when the array capacity is 
 reached and the array is copied to a new one with double capacity).
 {quote}
 more documentation on :
  * 
 https://docs.oracle.com/javase/tutorial/collections/implementations/list.html
  * 
 http://stackoverflow.com/questions/322715/when-to-use-linkedlist-over-arraylist
 For Map between HashMap and LinkedHashMap :
 {quote}
 Javolution Map Iterators return items in insertion sequence (HashMap does 
 not), so any code relying on the original insertion order must use a 
 LinkedHashMap.
 {quote}
  * 
 http://stackoverflow.com/questions/2889777/difference-between-hashmap-linkedhashmap-and-treemap
 If you detect an optimization, please comments this issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6225) Add a basic VAT report with frequency setting

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6225:


Good point.

 Add a basic VAT report with frequency setting
 -

 Key: OFBIZ-6225
 URL: https://issues.apache.org/jira/browse/OFBIZ-6225
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
  Labels: reporting, vat
 Attachments: OFBIZ-6225 - Vat control reports.patch, 
 OFBIZ-6225-TaxReport.patch


 Few years ago I began to work on that. I just stumbled upon it so I note it 
 here to continue when I will get a chance. It would be something basic with a 
 find and single input form, rendered with FOP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6225) Add a basic VAT report with frequency setting

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6225:


Are you using iText http://itextpdf.com/ to read in the existing form and fill 
in the fields?
This would make it more easier to build and maintain and more portable since 
you would just have either map OFBiz fields to form field names if the form 
existed or create a form that matched the government's requirements and make a 
new map. The processing code would be the same for all VAT reports.


 Add a basic VAT report with frequency setting
 -

 Key: OFBIZ-6225
 URL: https://issues.apache.org/jira/browse/OFBIZ-6225
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
  Labels: reporting, vat
 Attachments: OFBIZ-6225 - Vat control reports.patch, 
 OFBIZ-6225-TaxReport.patch


 Few years ago I began to work on that. I just stumbled upon it so I note it 
 here to continue when I will get a chance. It would be something basic with a 
 find and single input form, rendered with FOP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6225) Add a basic VAT report with frequency setting

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6225:


But can it read an exiting form and parse it so that you just have to fill in 
the fields using an API?

It seems to be easier and not require any programming if you can just 
change/replace the form's PDF file and maybe some name remapping when any 
government changes the format.
Could save a lot of FOP programming if all of the VAT agencies give you a PDF 
to fill in. 
Could also be easier to add fields to an existing PDF that is not already set 
up for automatic filling than to create the FOP instructions to draw the form 
from scratch for each government. Certainly requires a lower skill set.

How picky are the government's about using their forms?

Just a thought from the cheap seats.

 Add a basic VAT report with frequency setting
 -

 Key: OFBIZ-6225
 URL: https://issues.apache.org/jira/browse/OFBIZ-6225
 Project: OFBiz
  Issue Type: Improvement
  Components: accounting
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
  Labels: reporting, vat
 Attachments: OFBIZ-6225 - Vat control reports.patch, 
 OFBIZ-6225-TaxReport.patch


 Few years ago I began to work on that. I just stumbled upon it so I note it 
 here to continue when I will get a chance. It would be something basic with a 
 find and single input form, rendered with FOP



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5534) Dirty reads from entity cache

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-5534:


If you are going to fix the current system, at step 2b) you might consider just 
clearing the transaction cache and internal cache and let the next request 
reload the cache from the database.
This might be simpler and might avoid possible race conditions between 
transactions - or at least let the database sort out who won.

 Dirty reads from entity cache
 -

 Key: OFBIZ-5534
 URL: https://issues.apache.org/jira/browse/OFBIZ-5534
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Release Branch 11.04, Release Branch 12.04, Release 
 Branch 13.07, Trunk
Reporter: Jacopo Cappellato
Assignee: Adam Heath
 Attachments: unittest-dirtyreadsfromcache.patch


 Even if database transaction isolation level is set to ReadCommitted, a 
 transaction can get uncommitted records from the entity cache, under certain 
 circumstances.
 Here is a test case:
 1) transaction T1 creates a record
 2) T1 calls findOne to retrieve it: the read will be successful (because T1 
 can read data generated in T1 even if not committed) and the record will be 
 added to the cache
 3) T1 calls another service with requireNewTransaction set to true: this will 
 run the second service in a new transaction T2
 4) T2 calls findOne to retrieve the record created by T1: if useCache is set 
 to false it should fail; if useCache is set to true it will succeed (getting 
 the record from cache, even if the data is not committed to the db)
 The result in #4 is wrong because T2 should not see the uncommitted record
 We should never add uncommitted records to the entity cache.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-3949) Better RoleType Documentation

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-3949:


Where?
This relates to a question that I asked in the mailing list about best 
practices for roles and relationships.
Some of the things that I lump in under best practices could be described as 
only practices since it appears that some roles are used by the system 
without further configuration by the system admin.(see MANAGER and 
SHIPMENT_CLERK above)

Assigning these roles without being aware of how the system will interpret them 
can cause security problems or unexpected behaviour.

 Better RoleType Documentation
 -

 Key: OFBIZ-3949
 URL: https://issues.apache.org/jira/browse/OFBIZ-3949
 Project: OFBiz
  Issue Type: Improvement
  Components: site
Reporter: chris snow
 Attachments: roletype.pdf, roletype.xml


 This issue is for discussing improving the documentation for RoleType.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6110) Move as much as possible demo data from ecommerce to product or order components

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6110:


This would require a commitment to a BaseApplication set which seems to be 
possible. 
Does eCommerce move into the base set? 
How many installations use eCommerce as opposed to other Base Applications such 
as Human  Resources?

In any event, the extra seed data in the Base Applications that would accrue 
because of data moving from special purpose is pretty minimal in the overall 
scheme of things.

The mixing of demo data with core makes the system harder to understand. 

I would like to see the demo data moved to a separate project where technical 
writers and system administrators can work on it in a more productive 
environment than is currently possible.
I don't have the time for this if it involves producing patch files every time 
I find a spelling mistake or need to add seed data to clarify a wiki screenshot.



 Move as much as possible demo data from ecommerce to product or order 
 components
 

 Key: OFBIZ-6110
 URL: https://issues.apache.org/jira/browse/OFBIZ-6110
 Project: OFBiz
  Issue Type: Improvement
  Components: order, product, specialpurpose/ecommerce
Affects Versions: Trunk
Reporter: Jacques Le Roux
Priority: Minor
 Fix For: Upcoming Branch


 It would be better if we have most of the demo product data in product or 
 maybe in order component. Because almost all what can be done concerning 
 ordering in ecommerce can also be done in order manager from which anyway 
 ecommerce depends on
 More generally each component should have the data to be able to work as much 
 on its own as possible. Even if that means redundancy of some sorts. Most of 
 the time, we can avoid redudancy when there are components dependencies and 
 the component data are loaded after the main one.
 This is when 
 https://cwiki.apache.org/confluence/display/OFBIZ/Component+and+Component+Set+Dependencies
  helps and shows why it should be actively maintained! For instance I'm not 
 sure we show data loading order there...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6029) Telecom Number is missing the extension

[Ron Wheeler (JIRA)]

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

Ron Wheeler closed OFBIZ-6029.
--
Resolution: Invalid

Extension is held elsewhere

 Telecom Number is missing the extension
 ---

 Key: OFBIZ-6029
 URL: https://issues.apache.org/jira/browse/OFBIZ-6029
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Minor
  Labels: entities, telecom

 The Telecom_number entity is missing a place to store the extension number.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6059) UOM missing 2 entries

[Ron Wheeler (JIRA)]

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

Ron Wheeler updated OFBIZ-6059:
---
Attachment: UnitData.xml.patch

 UOM missing 2 entries
 -

 Key: OFBIZ-6059
 URL: https://issues.apache.org/jira/browse/OFBIZ-6059
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Trivial
  Labels: uom
 Attachments: UnitData.xml.patch


 Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
 uomTypeId=DATA_MEASURE/  
  UomConversion uomId=DATA_Pb uomIdTo=DATA_Tb 
 conversionFactor=1024/
 were left out when PB was added.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6059) UOM missing 2 entries

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6059:


Patch attached

 UOM missing 2 entries
 -

 Key: OFBIZ-6059
 URL: https://issues.apache.org/jira/browse/OFBIZ-6059
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Trivial
  Labels: uom
 Attachments: UnitData.xml.patch


 Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
 uomTypeId=DATA_MEASURE/  
  UomConversion uomId=DATA_Pb uomIdTo=DATA_Tb 
 conversionFactor=1024/
 were left out when PB was added.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (OFBIZ-6021) Part Demo Data is unnecessarily confusing

[Ron Wheeler (JIRA)]

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

Ron Wheeler closed OFBIZ-6021.
--
Resolution: Invalid

Confusing but that is the way it works!

 Part Demo Data is unnecessarily confusing
 -

 Key: OFBIZ-6021
 URL: https://issues.apache.org/jira/browse/OFBIZ-6021
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Minor
  Labels: demo
   Original Estimate: 1h
  Remaining Estimate: 1h

 There is a party called admiin and a  ContactMech called admin.
 This makes the demo data hard to follow and can be easily fixed by remaing 
 the contactMechId. .
   PartyRole partyId=admin roleTypeId=EMAIL_ADMIN/
 PartyRole partyId=Company roleTypeId=_NA_/
 PartyRelationship partyIdFrom=admin roleTypeIdFrom=EMAIL_ADMIN 
 partyIdTo=Company roleTypeIdTo=_NA_ fromDate=2000-01-01 00:00:00/
 PartyRole partyId=DemoEmployee roleTypeId=EMAIL_ADMIN/
 PartyRelationship partyIdFrom=DemoEmployee 
 roleTypeIdFrom=EMAIL_ADMIN partyIdTo=Company roleTypeIdTo=_NA_ 
 fromDate=2000-01-01 00:00:00/
 ContactMech contactMechId=admin contactMechTypeId=EMAIL_ADDRESS 
 infoString=ofbizt...@example.com/
 PartyContactMech partyId=admin contactMechId=admin 
 fromDate=2003-01-01 00:00:00.0 allowSolicitation=Y/
 PartyContactMechPurpose contactMechPurposeTypeId=PRIMARY_EMAIL 
 partyId=admin contactMechId=admin fromDate=2003-01-01 00:00:00.0/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6082) HELP_HR_Main.xml invalid Docbook syntax

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6082:


Index: applications/humanres/data/helpdata/HELP_HR_main.xml
===
--- applications/humanres/data/helpdata/HELP_HR_main.xml(revision 
1659295)
+++ applications/humanres/data/helpdata/HELP_HR_main.xml(working copy)
@@ -33,8 +33,8 @@
 as a quot;Group memberquot;. /para
 
   paraThe number of organizational levels can be as many as required./para
-  
- title Nodes In the Company Tree/title
+section
+  title Nodes In the Company Tree/title
 
 paraThere are three node types in the tree, each identified by a
 different icon. The top of the tree represents your Company, the highest
@@ -41,14 +41,15 @@
 level in the organization. The Company and departments under the
 Company can have sub departments or positions. Under positions are
 the people who fulfill the position./para
-  
-titleUsage/title
+  /section
+  section
+   titleUsage/title
 
-itemizedlist
+   itemizedlist
   listitem
 paraNavigate the organization to view departments, positions and
 people/para
-  /listitem
+ /listitem
 
   listitem
 paraAdd or remove a department/para
@@ -67,5 +68,5 @@
 position/para
   /listitem
 /itemizedlist
-  
+  /section
 /section


 HELP_HR_Main.xml invalid Docbook syntax
 ---

 Key: OFBIZ-6082
 URL: https://issues.apache.org/jira/browse/OFBIZ-6082
 Project: OFBiz
  Issue Type: Bug
  Components: humanres
Affects Versions: Trunk
 Environment: All
Reporter: Ron Wheeler

 Titles can only be used once in a section.
 Add sub-sctions to HELP_HR_Main.xml 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6082) HELP_HR_Main.xml invalid Docbook syntax

[Ron Wheeler (JIRA)]

Ron Wheeler created OFBIZ-6082:
--

 Summary: HELP_HR_Main.xml invalid Docbook syntax
 Key: OFBIZ-6082
 URL: https://issues.apache.org/jira/browse/OFBIZ-6082
 Project: OFBiz
  Issue Type: Bug
  Components: humanres
Affects Versions: Trunk
 Environment: All
Reporter: Ron Wheeler


Titles can only be used once in a section.
Add sub-sctions to HELP_HR_Main.xml 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6059) UOM missing 2 entries

[Ron Wheeler (JIRA)]

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

Ron Wheeler updated OFBIZ-6059:
---
Summary: UOM missing 2 entries  (was: RB UOM missing 2 entries)

 UOM missing 2 entries
 -

 Key: OFBIZ-6059
 URL: https://issues.apache.org/jira/browse/OFBIZ-6059
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Trivial
  Labels: uom

 Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
 uomTypeId=DATA_MEASURE/  
  UomConversion uomId=DATA_PB uomIdTo=DATA_TB conversionFactor=1024/
 were left out when PB was added.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6059) UOM missing 2 entries

[Ron Wheeler (JIRA)]

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

Ron Wheeler updated OFBIZ-6059:
---
Description: 
Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
uomTypeId=DATA_MEASURE/  
 UomConversion uomId=DATA_Pb uomIdTo=DATA_Tb conversionFactor=1024/

were left out when PB was added.


  was:
Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
uomTypeId=DATA_MEASURE/  
 UomConversion uomId=DATA_PB uomIdTo=DATA_TB conversionFactor=1024/

were left out when PB was added.



 UOM missing 2 entries
 -

 Key: OFBIZ-6059
 URL: https://issues.apache.org/jira/browse/OFBIZ-6059
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Trivial
  Labels: uom

 Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
 uomTypeId=DATA_MEASURE/  
  UomConversion uomId=DATA_Pb uomIdTo=DATA_Tb 
 conversionFactor=1024/
 were left out when PB was added.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6059) RB UOM missing 2 entries

[Ron Wheeler (JIRA)]

Ron Wheeler created OFBIZ-6059:
--

 Summary: RB UOM missing 2 entries
 Key: OFBIZ-6059
 URL: https://issues.apache.org/jira/browse/OFBIZ-6059
 Project: OFBiz
  Issue Type: Improvement
  Components: framework
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Trivial


Uom abbreviation=Pb description=Petabyte of Data uomId=DATA_Pb 
uomTypeId=DATA_MEASURE/  
 UomConversion uomId=DATA_PB uomIdTo=DATA_TB conversionFactor=1024/

were left out when PB was added.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6029) Telecom Number is missing the extension

[Ron Wheeler (JIRA)]

Ron Wheeler created OFBIZ-6029:
--

 Summary: Telecom Number is missing the extension
 Key: OFBIZ-6029
 URL: https://issues.apache.org/jira/browse/OFBIZ-6029
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Minor


The Telecom_number entity is missing a place to store the extension number.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (OFBIZ-6021) Part Demo Data is unnecessarily confusing

[Ron Wheeler (JIRA)]

Ron Wheeler created OFBIZ-6021:
--

 Summary: Part Demo Data is unnecessarily confusing
 Key: OFBIZ-6021
 URL: https://issues.apache.org/jira/browse/OFBIZ-6021
 Project: OFBiz
  Issue Type: Improvement
  Components: party
Affects Versions: 13.07.01
 Environment: All
Reporter: Ron Wheeler
Priority: Minor


There is a party called admiin and a  ContactMech called admin.
This makes the demo data hard to follow and can be easily fixed by remaing the 
contactMechId. .

  PartyRole partyId=admin roleTypeId=EMAIL_ADMIN/
PartyRole partyId=Company roleTypeId=_NA_/
PartyRelationship partyIdFrom=admin roleTypeIdFrom=EMAIL_ADMIN 
partyIdTo=Company roleTypeIdTo=_NA_ fromDate=2000-01-01 00:00:00/
PartyRole partyId=DemoEmployee roleTypeId=EMAIL_ADMIN/
PartyRelationship partyIdFrom=DemoEmployee roleTypeIdFrom=EMAIL_ADMIN 
partyIdTo=Company roleTypeIdTo=_NA_ fromDate=2000-01-01 00:00:00/

ContactMech contactMechId=admin contactMechTypeId=EMAIL_ADDRESS 
infoString=ofbizt...@example.com/
PartyContactMech partyId=admin contactMechId=admin 
fromDate=2003-01-01 00:00:00.0 allowSolicitation=Y/
PartyContactMechPurpose contactMechPurposeTypeId=PRIMARY_EMAIL 
partyId=admin contactMechId=admin fromDate=2003-01-01 00:00:00.0/




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-4941:


Separate the documentation into a sub-project and let the documentation team 
that are not software writers commit to the docs.

Of course, the software committers would all be committers on the doc project.

This would also allow the documentation to be tagged, branched and released 
separately.
It is likely to be released more frequently than the software project which 
would be helpful.

I would suggest that we consider including the demo data in the documentation 
project so that the demos could be improved and coordinated with the 
documentation so that the OOTB demo matches the documentation and the demo data 
can be used in examples and figures.

If people are using the demo data as test data, we would have be careful with 
branching and tagging to support changes in the code that affects the entity 
model but at least the load of maintaining demo/test data would be more widely 
shared.


 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: Trunk
Reporter: Jacques Le Roux
Assignee: Paul Foxworthy
Priority: Minor
 Attachments: HelpAccounting.jpg, HelpPerformanceReview1.jpg, 
 HelpPerformanceReview2.jpg, HelpRoadmap.jpg, LICENSE.html, LicenseFiles.zip, 
 OFBIZ-4941 POC HR Help.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, 
 OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, 
 WebhelpFiles.zip, WebhelpFiles.zip, WebhelpHRAppDocbook.zip, 
 WebhelpHRAppDocbook.zip, content.7z, docbook diff.patch, 
 docbook-xsl-1.77.1.zip, help_content.jpg, help_ofbizhelp.jpg, 
 help_webhlep.jpg, helppdf.zip, jh.jar, ofbiz-common.xsl, 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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-6015) Move Online Help Documentation from Webhelp into Trunk

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-6015:


Topic-based writing seems like a good way to build documentation and encourages 
reuse rather that copy and paste.
Splitting up the documentation into sections based on screens/business 
processes with concepts as separate fragments will make the use of the 
documentation for various purposes (on-line help, program specifications, 
training, manuals, job-aids, etc.) much easier.
It may also encourage developers and business consultants to contribute 
fragments from user requirements, design specifications or even design 
discussions that can be used to construct documents.
The big issue here is naming and tagging fragments so that it is easy to find 
the pieces that you want.
The initial suggestion about using the SCM (SVN) to store them only works if 
the documentation team has write access and can manage the structure of the 
fragments easily. A CMS would be a better choice. If the document production 
steps can support access to fragments in the CMS, that would be ideal.



 Move Online Help Documentation from Webhelp into Trunk
 --

 Key: OFBIZ-6015
 URL: https://issues.apache.org/jira/browse/OFBIZ-6015
 Project: OFBiz
  Issue Type: Improvement
  Components: ALL APPLICATIONS
Reporter: Sharan Foga
Assignee: Sharan Foga
Priority: Minor

 This Jira has been created to manage the migration of all the documentation 
 from the Webhelp branch into the current help system so that it will work 
 with what we already have (essentially so that we dont lose it!).  The 
 original issue for the Webhelp is 
 https://issues.apache.org/jira/browse/OFBIZ-4941
 As well as HR, there is also online documentation for Accounting, 
 Manufacturing (English, German and Dutch), Project Manager and Catalog - 
 though not as complete, so I will be consolidating and moving those too.
 The files use the docbook format and are compatible with what we have 
 although he implemented everything into one file whereas we use one file per 
 screen - so I'll need to split it up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-4941:


http://www.slideshare.net/wapxana/documentation-with-open-source-tools  has a 
nice discussion of Docbook and AsciiDoc (slides - no audio so it take 3 minute 
to view 40 slides)
Never used AsciiDoc but have used Docbook and currently DITA.  I like 
structured XML since it removes formatting from content.
I have used Wikimedia and other languages with some of the characteristics of 
AsciiDoc. Don't like the wide variance of structuring syntax.

AsciiDoc:
-  has include which should help with structuring documents from fragments 
which encourages reuse.
- supported by multiple output processors - Ruby, Java JavaScript, etc which 
makes it easy to see that the content should have a long life as UI technology 
changes
- dynamic (on-screen) and static output (PDF) can be produced  from the same 
fragments might encourage better and more comprehensive documentation.
- supports in-line GraphViz so we might get more visual documentation that is 
uptodate.
- MIT license should be OK.

Will need to think about how to store content fragments to encourage reuse and 
increase consistency of documentation.


 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: Trunk
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Minor
 Attachments: HelpAccounting.jpg, HelpPerformanceReview1.jpg, 
 HelpPerformanceReview2.jpg, HelpRoadmap.jpg, LICENSE.html, LicenseFiles.zip, 
 OFBIZ-4941 POC HR Help.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, 
 OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, OFBIZ-4941.patch, 
 WebhelpFiles.zip, WebhelpFiles.zip, WebhelpHRAppDocbook.zip, 
 WebhelpHRAppDocbook.zip, content.7z, docbook diff.patch, 
 docbook-xsl-1.77.1.zip, help_content.jpg, help_ofbizhelp.jpg, 
 help_webhlep.jpg, helppdf.zip, jh.jar, ofbiz-common.xsl, 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}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5704) Extend lot entity to include party Id of manufacturer

[Ron Wheeler (JIRA)]

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

Ron Wheeler commented on OFBIZ-5704:


The discussion seems to be wandering a bit.
As an outsider it appears to me that there is general agreement of the need 
- for lot numbers to uniquely identify a lot
- for a lot to have multiple lot numbers
- to be able to trace material and the origin of its components throughout its 
lifespan 

There seems to be a minor disagreement about how this should be implemented 
internally. 
I would hope that the screens and reports would look pretty much the same 
regardless of database or entity structure.
However, it might be useful to have a comparison of use cases possible under 
each implementation strategy to see if there is a significant benefit from one 
over the other.

From what I have gleaned from the parts of the discussion that dealt with the 
actual problem, I would want to be sure that the more complex data structure 
can be hidden from the end-user in the normal cases without losing the 
benefits of the more comprehensive design. If the additional functionality 
only helps very obscure use cases but makes the normal usage of lot numbers 
overly complicated for the data-entry person and management, that would be a 
consideration. 

Can we get back to a serious discussion of the implementation since it does 
seem to be an important problem for many industries in this day of wildly 
popular litigation and great public and political enthusiasm for  high 
regulatory penalties. 

 Extend lot entity to include party Id of manufacturer
 -

 Key: OFBIZ-5704
 URL: https://issues.apache.org/jira/browse/OFBIZ-5704
 Project: OFBiz
  Issue Type: Improvement
  Components: manufacturing, product, workeffort
Affects Versions: Release Branch 11.04, Release Branch 12.04, Release 
 Branch 13.07, Trunk
Reporter: Pierre Smits
 Attachments: OFBiz-5704-Product-EntityModel-Lot.patch


 Rationale
 Lot or batch management affects two places, namely the outbound process (and 
 its functionalities) and inbound. 
 It is possible that multiple parties have the same ID for the batch or the 
 lot. Howver, in current feature set there is no discrimination between lots 
 from supplier A, supplier B, or even the primary (internal) company in OFBiz.
 Therefore the entity 'Lot' should be extended with another key, namely that 
 of the partyId of the manufacturer (or supplier).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)