Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.) Date of First Response: 2010-03-24 05:04:38 project_key: SOA Please undertake QE review of jBPM Reference Guide to ensure all documentation JIRAs have been dealt with correctly.
Link: Added: This issue is related to SOA-1898
Please add documentation for the new configuration parameter - number of retries (see JBPM-2691).
Link: Added: This issue is related to JBPM-2691
Thanks for the feedback, Martin. It would be really helpful to us, though, if you could cite section numbers as you go through the book so we know where to find things or, in this case, where they should go. Thanks!
Hello Martin, As per SOA-1998 I have just added information about changes in numbers of retries that Alejandro documented. Is that what the part to which you were referring? If so, it is now in the document (Section 10.4.) Cheers.
Hello David, I did not went trhough the book. I just verified bug fixes and realized that these things are not documented anywhere.
1) I suggest to put Section 10.4 under Chapter 3 because it deals with configuration. 2) Update the jbpm.cfg.xml listing in Chapter 3 and in the former Section 10.4 - job executor configuration uses <field .../> instead of <property .../> 3) The default value for retries is 1. It means that after a first failure, the job is retried once. 4) It would be better if jbpm.cfg.xml listings in Chapter 3 and Section 10.4 used the default value for retries field (now it reads 3).
Hello Martin, Thanks for your feedback. Much appreciated. 1. I have moved it, as per your recommendation. 2. See soa-1998 - Alejandro has now standardised it on property. 3 and 4. Talked to Alejandro on IRC. Three is now going to be the default value. There is only one listing now, instead of two. Cheers.
Link: Added: This issue related SOA-2015
Please add a note on <field .../> -> <property .../> transition to release notes. Thanks.
Okay, I have added this to the Release Note: Note: "Field" has become "property" to avoid direct field injection as Red Hat prefers you to use setter method invocation instead.
Fixed it. :-)
Link: Added: This issue related SOA-1285
FYI - can you please look at these question that Len has raised?
(3.5) Increasing the number of threads is not a bad plan. It can be used to increase throughput by carefully tuning the job executor parameters. See this article: http://www.theserverside.com/news/1363588/Scalability-and-Performance-of-jBPM-Workflow-Engine-in-a-JBoss-Cluster As for the missing properties, they are deprecated. (4.2.2) The addition came for a customer request to document these features: SOA-1285 and JBPM-2164. As for why a user would want to do this, in a production environment it is very sensible not to grant the table creation privilege to the database login that runs the application. In this scenario the user needs alternate means to create the schema. The JbpmSchema API and the Ant task provide such means. (4.2.3) The JbpmSchemaTask is packaged in jbpm-jpdl.jar. No script needs to be supplied - end users define and run this task in their own scripts, based on the sample snippet.
Len, As discussed on IRC, I have added information derived from Alejandro's responses to 4.2.2 and 4.2.3 to the document. Cheers.
Thanks, Len.