[jira] [Updated] (OFBIZ-4896) ProductionRunDeclaration doesn't show Routing

2014-11-25 Thread Swapnil Shah (JIRA) 

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

Swapnil Shah updated OFBIZ-4896:

Attachment: EditRoutingProductLink.png
EditProductionRun.png
ProductionRunDeclaration_Confirmed.png

> ProductionRunDeclaration doesn't show Routing
> -
>
> Key: OFBIZ-4896
> URL: https://issues.apache.org/jira/browse/OFBIZ-4896
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 12.04, Trunk
>Reporter: Pierre Smits
> Attachments: EditProductionRun.png, EditRoutingProductLink.png, 
> ProductionRunDeclaration_Confirmed.png
>
>
> When having created a new production run in MFG with a routing selected, the 
> routing isn't shown when the production run is confirmed.



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

[jira] [Commented] (OFBIZ-4896) ProductionRunDeclaration doesn't show Routing

2014-11-25 Thread Swapnil Shah (JIRA) 

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

Swapnil Shah commented on OFBIZ-4896:
-

[~pfm.smits] As per the current implementation, user first need to associate 
the Product with selected routing (via EditRoutingProductLink screen) in order 
to get all its associated routing task displayed under the 'Task' section over 
Edit Production Run screen. 

I am attaching few screenshots for reference that allows user to see all the 
tasks for routing associated to the product. Please let us know if you are 
attempting or expecting anything different and then we can try to take it as 
improvement over the above mentioned existing flow.
 

> ProductionRunDeclaration doesn't show Routing
> -
>
> Key: OFBIZ-4896
> URL: https://issues.apache.org/jira/browse/OFBIZ-4896
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Release Branch 12.04, Trunk
>Reporter: Pierre Smits
>
> When having created a new production run in MFG with a routing selected, the 
> routing isn't shown when the production run is confirmed.



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

[jira] [Commented] (OFBIZ-5042) Apache Solr Implementation

2014-11-25 Thread Sumit Pandit (JIRA) 

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

Sumit Pandit commented on OFBIZ-5042:
-

Hi Paul, Jacques,

I have implemented solr for one of my project using your patch with 
customization in some of the services. 
I am facing a big problem, see if you could help me out in this, also please 
let me know if you would required additional input- 

- Feature implemented - Auto completer for keyword search. 
- Problem facing - It is wroking fine on local (with less then 100 test 
products). But while deployed on production (with 5 live products). index 
documents are generated for for all products but suggester document is not 
generating for any of them.
- Proving some part of logs below,  See if you could suggest anything.
- Configurations - 
  1) SolrConfig.xml -

   auto_complete   
   
 suggest
 org.apache.solr.spelling.suggest.Suggester
 org.apache.solr.spelling.suggest.tst.TSTLookup
 internalName
 0.005
 true
   

   
 
  true
  suggest
  false
  5
  false


   suggest

  
 ---
  2)   Schema.xml

  


 



  


   


- Logs - Observing a lot of entires of logs as below - 
2014-11-22 12:15:06,260 (http-bio-0.0.0.0-8080-exec-71) [ 
SolrDeletionPolicy.java:165:INFO ] newest commit generation = 1082
2014-11-22 12:15:06,260 (http-bio-0.0.0.0-8080-exec-71) [   
SolrCore.java:1622:WARN ] [collection1] PERFORMANCE WARNING: Overlapping 
onDeckSearchers=2
2014-11-22 12:15:06,261 (http-bio-0.0.0.0-8080-exec-71) [  
SolrIndexSearcher.java:197:INFO ] Opening Searcher@15b7db9c main
2014-11-22 12:15:06,261 (http-bio-0.0.0.0-8080-exec-71) 
[DirectUpdateHandler2.java:602:INFO ] end_commit_flush
2014-11-22 12:15:06,262 (http-bio-0.0.0.0-8080-exec-112) 
[DirectUpdateHandler2.java:511:INFO ] start 
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
2014-11-22 12:15:06,262 (http-bio-0.0.0.0-8080-exec-112) 
[DirectUpdateHandler2.java:551:INFO ] No uncommitted changes. Skipping 
IW.commit.
2014-11-22 12:15:06,262 (http-bio-0.0.0.0-8080-exec-112) [   
SolrCore.java:1622:WARN ] [collection1] PERFORMANCE WARNING: Overlapping 
onDeckSearchers=3
2014-11-22 12:15:06,263 (http-bio-0.0.0.0-8080-exec-112) [  
SolrIndexSearcher.java:197:INFO ] Opening Searcher@711a6ab2 main
2014-11-22 12:15:06,263 (http-bio-0.0.0.0-8080-exec-112) 
[DirectUpdateHandler2.java:602:INFO ] end_commit_flush
2014-11-22 12:15:06,263 (http-bio-0.0.0.0-8080-exec-86) 
[DirectUpdateHandler2.java:511:INFO ] start 
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
2014-11-22 12:15:06,263 (http-bio-0.0.0.0-8080-exec-86) 
[DirectUpdateHandler2.java:551:INFO ] No uncommitted changes. Skipping 
IW.commit.
2014-11-22 12:15:06,263 (http-bio-0.0.0.0-8080-exec-86) [   
SolrCore.java:1622:WARN ] [collection1] PERFORMANCE WARNING: Overlapping 
onDeckSearchers=4
2014-11-22 12:15:06,264 (http-bio-0.0.0.0-8080-exec-86) [  
SolrIndexSearcher.java:197:INFO ] Opening Searcher@55b75f27 main
2014-11-22 12:15:06,264 (http-bio-0.0.0.0-8080-exec-86) 
[DirectUpdateHandler2.java:602:INFO ] end_commit_flush
2014-11-22 12:15:06,264 (http-bio-0.0.0.0-8080-exec-140) 
[DirectUpdateHandler2.java:511:INFO ] start 
commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
2014-11-22 12:15:06,265 (http-bio-0.0.0.0-8080-exec-140) 
[DirectUpdateHandler2.java:551:INFO ] No uncommitted changes. Skipping 
IW.commit.
2014-11-22 12:15:06,265 (http-bio-0.0.0.0-8080-exec-140) [   
SolrCore.java:1622:WARN ] [collection1] PERFORMANCE WARNING: Overlapping 
onDeckSearchers=5


Thanks in advance
Sumit Pandit

> Apache Solr Implementation
> --
>
> Key: OFBIZ-5042
> URL: https://issues.apache.org/jira/browse/OFBIZ-5042
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL COMPONENTS
>Reporter: Paul Piper
>Assignee: Jacques Le Roux
>  Labels: component, feature, solr
> Attachments: 2013-07-30 11 52 52.png, OFBIZ-5042 - solr in 
> specialpurpose.patch, OFBIZ-5042 - solr in specialpurpose.patch, OFBIZ-5042 - 
> solr in specialpurpose.patch, solr in specialpurpose splitted.z01, solr in 
> specialpurpose splitted.z02, solr in specialpurpose splitted.zip, solr in 
> specialpurpose.zip, solr-v1.00-r4284.zip
>
>
> Apache Solr, a modern search engine, seems to be one of

[jira] [Commented] (OFBIZ-5840) Create bootstrap theme

2014-11-25 Thread Adrian Crum (JIRA) 

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

Adrian Crum commented on OFBIZ-5840:


The Bootstrap theme has been added to the branch in rev 1641665.

Keep in mind you can style your theme using the Layout Demo page in Web Tools:

https://localhost:8443/webtools/control/WebtoolsLayoutDemo


> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework, themes
>Affects Versions: Trunk
>Reporter: Julien NICOLAS
>Assignee: Adrian Crum
>  Labels: bootstrap, theme
> Attachments: GlobalDecorator.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, bootified.js, 
> bootstrap-theme.zip, bootstrap.zip, htmlMenuMacroLibrary.patch
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



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

[jira] [Assigned] (OFBIZ-5840) Create bootstrap theme

2014-11-25 Thread Adrian Crum (JIRA) 

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

Adrian Crum reassigned OFBIZ-5840:
--

Assignee: Adrian Crum

> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework, themes
>Affects Versions: Trunk
>Reporter: Julien NICOLAS
>Assignee: Adrian Crum
>  Labels: bootstrap, theme
> Attachments: GlobalDecorator.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, bootified.js, 
> bootstrap-theme.zip, bootstrap.zip, htmlMenuMacroLibrary.patch
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



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

[jira] [Commented] (OFBIZ-5840) Create bootstrap theme

2014-11-25 Thread Adrian Crum (JIRA) 

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

Adrian Crum commented on OFBIZ-5840:


Gavin - please make sure your patches reference the OFBiz home folder. I had 
difficulty applying two of them.

> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework, themes
>Affects Versions: Trunk
>Reporter: Julien NICOLAS
>  Labels: bootstrap, theme
> Attachments: GlobalDecorator.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, bootified.js, 
> bootstrap-theme.zip, bootstrap.zip, htmlMenuMacroLibrary.patch
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



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

[jira] [Commented] (OFBIZ-5840) Create bootstrap theme

2014-11-25 Thread Taher Alkhateeb (JIRA) 

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

Taher Alkhateeb commented on OFBIZ-5840:


Hey everyone. I tried to pull a few times from the branch but I got the below 
error:

svn: E175002: GET request on 
'/repos/asf/!svn/rvr/1634810/ofbiz/branches/boostrap_theme/applications/content/lib/tika-core-1.0.jar'
 failed: 503 Service Unavailable

Is this a bad Internet connection on my part or is something wrong with this 
branch?

> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework, themes
>Affects Versions: Trunk
>Reporter: Julien NICOLAS
>  Labels: bootstrap, theme
> Attachments: GlobalDecorator.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, bootified.js, 
> bootstrap-theme.zip, bootstrap.zip, htmlMenuMacroLibrary.patch
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



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

[jira] [Commented] (OFBIZ-5430) "Please Select Your Shipping Method" error sometimes occurs when updating order items

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-5430:


BTW Christian, did you get a chance to extract the relevant fixing changes?

> "Please Select Your Shipping Method" error sometimes occurs when updating 
> order items
> -
>
> Key: OFBIZ-5430
> URL: https://issues.apache.org/jira/browse/OFBIZ-5430
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Christian Carlow
>
> Sometimes when an order item is appended or existing order items are updated, 
> a "Please Select Your Shipment Method" error occurs.  I'm not exactly sure 
> what causes this but it seems to be intermittent because sometimes I'm able 
> to perform both of the operations without the error occur.  
> The problem seems to be that an extra empty ship group is added to the cart 
> and takes the index position of first ship group.  Because the empty ship 
> group contains no shipmentMethodTypeId or carrierPartyId the error occurs.
> Logic needs to exist to prevent the empty ship group that causes this issue 
> from ever being added to the cart.



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

[jira] [Commented] (OFBIZ-5430) "Please Select Your Shipping Method" error sometimes occurs when updating order items

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-5430:


I got this again today using a local instance. I could not reproduce on a 
custom test server but I could OOTB on trunk demo adding a GZ-1005 to the 
DEMO10090 order I could reproduce. I will investigate this again because it's 
blocking me on OFBIZ-5761. Even if I'm now sure it's unrelated to pending work 
for OFBIZ-5761 (pfew, I prefer that!) I'm using locally (Nicolas's patch with 
minor unrelated changes), I want to be sure I dont mix things. Because the 
custom test server uses a slightly different code (my last patch for 
OFBIZ-5761) and I can't reproduce there. We will get it!

> "Please Select Your Shipping Method" error sometimes occurs when updating 
> order items
> -
>
> Key: OFBIZ-5430
> URL: https://issues.apache.org/jira/browse/OFBIZ-5430
> Project: OFBiz
>  Issue Type: Bug
>  Components: order
>Affects Versions: Trunk
>Reporter: Christian Carlow
>
> Sometimes when an order item is appended or existing order items are updated, 
> a "Please Select Your Shipment Method" error occurs.  I'm not exactly sure 
> what causes this but it seems to be intermittent because sometimes I'm able 
> to perform both of the operations without the error occur.  
> The problem seems to be that an extra empty ship group is added to the cart 
> and takes the index position of first ship group.  Because the empty ship 
> group contains no shipmentMethodTypeId or carrierPartyId the error occurs.
> Logic needs to exist to prevent the empty ship group that causes this issue 
> from ever being added to the cart.



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

[jira] [Commented] (OFBIZ-5886) Create an ant target to quickly get rid of changes applied by build-dev

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-5886:


OK wait, a bit more work than expected, much fun here :/
{code}
Command: Commit  
Modified: C:\Stash\build.xml  
Sending content: C:\Stash\build.xml  
Error: Commit failed (details follow):  
Error: Working copy text base is corrupt  
Error: Checksum mismatch for text base of 'C:\Stash\build.xml':  
Error:expected:  7636c16b4c091c8f86f47bd592eeb3a0  
Error:  actual:  5914579d83c7ea7d1d4e3a5c76737131  
Error: Try a 'Cleanup'. If that doesn't work you need to do a fresh checkout.  
Completed!:   
{code}

> Create an ant target to quickly get rid of changes applied by build-dev
> ---
>
> Key: OFBIZ-5886
> URL: https://issues.apache.org/jira/browse/OFBIZ-5886
> Project: OFBiz
>  Issue Type: New Feature
>  Components: framework
>Affects Versions: Trunk
> Environment: Both local and servers
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Branch
>
>
> It's annoying when you need to commit changes to have to before remove the 
> changes applied by the build-dev target which applies the dev patches located 
> in runtime/patches



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

[jira] [Closed] (OFBIZ-5886) Create an ant target to quickly get rid of changes applied by build-dev

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux closed OFBIZ-5886.
--
Resolution: Implemented

The new "revert-dev" ant target can be sued to quickly get rid of changes 
applied by "build-dev", locally or on a server

> Create an ant target to quickly get rid of changes applied by build-dev
> ---
>
> Key: OFBIZ-5886
> URL: https://issues.apache.org/jira/browse/OFBIZ-5886
> Project: OFBiz
>  Issue Type: New Feature
>  Components: framework
>Affects Versions: Trunk
> Environment: Both local and servers
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Trivial
> Fix For: Upcoming Branch
>
>
> It's annoying when you need to commit changes to have to before remove the 
> changes applied by the build-dev target which applies the dev patches located 
> in runtime/patches



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

[jira] [Created] (OFBIZ-5886) Create an ant target to quickly get rid of changes applied by build-dev

2014-11-25 Thread Jacques Le Roux (JIRA) 
Jacques Le Roux created OFBIZ-5886:
--

 Summary: Create an ant target to quickly get rid of changes 
applied by build-dev
 Key: OFBIZ-5886
 URL: https://issues.apache.org/jira/browse/OFBIZ-5886
 Project: OFBiz
  Issue Type: New Feature
  Components: framework
Affects Versions: Trunk
 Environment: Both local and servers
Reporter: Jacques Le Roux
Assignee: Jacques Le Roux
Priority: Trivial
 Fix For: Upcoming Branch


It's annoying when you need to commit changes to have to before remove the 
changes applied by the build-dev target which applies the dev patches located 
in runtime/patches



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

[jira] [Commented] (OFBIZ-5566) Production Run Header and tasks quantityProduced incorrect when completing/closing

2014-11-25 Thread Swapnil Shah (JIRA) 

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

Swapnil Shah commented on OFBIZ-5566:
-

[~ofbizzer] As per the existing implementation, whenever any task is completed, 
system assumes that all 'Qty to Produced' set over production run header is 
produced EXCEPT the Rejected Qty. So :
# As per the above reported flow by user, when she hits 'Quick Complete' then,
#- First task end up showing Produced=8 because 2 units got rejected from it at 
the time of declaration
#- Second task end up showing Produced=9 because 1 units got rejected from it 
at the time of declaration
#- Now because user has already stocked In 1 unit via "Production Run Declare 
And Produce" section and last (Second) task had finally produced only 9 units, 
so finally for the whole production run only 9 units can be produced and hence 
upon 'Quick Complete' the '"Production Run Declare And Produce"' section shows 
to stock in the remaining qty of 8 units.
# Finally when user performs 'Quick Close' then the remaining 8 units get 
produced/stocked in and hence the total Produced Qty is shown as '9 units' over 
header (which doesn't exceed what is produced through last routing task).

Of course as of now there is no checks in place in the existing implementation 
that prevents user to produce less than or equal to what is produced in its 
immediate predecessor task probably by assuming that there is enough WIP to 
fulfill and produce the whole qty by subsequent task. But if there is any 
special case then we can definitely plan it as improvement. 

> Production Run Header and tasks quantityProduced incorrect when 
> completing/closing
> --
>
> Key: OFBIZ-5566
> URL: https://issues.apache.org/jira/browse/OFBIZ-5566
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Christian Carlow
>
> The produced quantity gets set incorrectly when completing or closing 
> production runs.  
> To reproduce:
> 1.  Create a production run to product 10 of PIZZA
> 2.  Click "Confirm" then "Quick Start All Tasks"
> 3.  Declare 2 produced and 2 rejected for the first task
> 4.  Declare 1 produced and 1 rejected for the second task
> 5.  Stock In 1 in "Production Run Declare And Produce" section
> 6.  Notice at this point the quantity produced for the header is 1 and 2 for 
> the first task and 1 for the second task
> 7.  Click "Quick Close" or "Quick Complete"
> 8.  Notice the quantity produced for the header was changed to 9 and 8 for 
> the first task and 9 for the second
> This doesn't make sense.  First, the second task should not have a quantity 
> produced greater than the prior task.  Also since the first task only 
> produced 8, the production run header seems like it should be limited to a 
> max quantity produced value of 8.
> Besides that problem, I don't think the quantities should be increased to 
> values greater than what was already declared.  In other words when I close 
> the production run, I expected the quantity produced for the header to remain 
> 1 and 2 for the first task and 1 for the second.



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

[jira] [Comment Edited] (OFBIZ-5560) Production Run Task Issue Components does not take into account manual issuances created on the Materials tab

2014-11-25 Thread Swapnil Shah (JIRA) 

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

Swapnil Shah edited comment on OFBIZ-5560 at 11/25/14 11:30 AM:


Hi [~ofbizzer],
It seems this issue is not reproducible. There is no way through which material 
can be issued (manually or systemically) unless and until Production run is 
confirmed.  It is possible to add the material manually (apart from what is 
already defined in BoM) via Material screen but it would simply mean that user 
is adding  (and NOT ISSUING) the requirement for material and same would be 
issue only upon confirming the production and starting the corresponding task.

We can mark it as resolved for now.


was (Author: swash78):
Hi,
It seems this issue is not reproducible. There is no way through which material 
can be issued (manually or systemically) unless and until Production run is 
confirmed.  It is possible to add the material manually (apart from what is 
already defined in BoM) via Material screen but it would simply mean that user 
is adding  (and NOT ISSUING) the requirement for material and same would be 
issue only upon confirming the production and starting the corresponding task.

We can mark it as resolved for now.

> Production Run Task Issue Components does not take into account manual 
> issuances created on the Materials tab
> -
>
> Key: OFBIZ-5560
> URL: https://issues.apache.org/jira/browse/OFBIZ-5560
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Christian Carlow
>
> Production Run Task Issue Components functionality does not take into account 
> manual issuances created on the Materials tab.  
> To reproduce:
> 1.  Create a production run for 2 of product PIZZA
> 2.  Issue 1 of product PEPPERS to a task on the Materials tab
> 3.  Return to the "Edit Production Run" tab and click confirm
> 4.  Click "Quick Start All Tasks"
> 5.  Click the "Issue Components" button for the task
> 6.  Notice the functionality tries to issue 2 even though 1 has already been 
> manually issued



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

[jira] [Commented] (OFBIZ-5560) Production Run Task Issue Components does not take into account manual issuances created on the Materials tab

2014-11-25 Thread Swapnil Shah (JIRA) 

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

Swapnil Shah commented on OFBIZ-5560:
-

Hi,
It seems this issue is not reproducible. There is no way through which material 
can be issued (manually or systemically) unless and until Production run is 
confirmed.  It is possible to add the material manually (apart from what is 
already defined in BoM) via Material screen but it would simply mean that user 
is adding  (and NOT ISSUING) the requirement for material and same would be 
issue only upon confirming the production and starting the corresponding task.

We can mark it as resolved for now.

> Production Run Task Issue Components does not take into account manual 
> issuances created on the Materials tab
> -
>
> Key: OFBIZ-5560
> URL: https://issues.apache.org/jira/browse/OFBIZ-5560
> Project: OFBiz
>  Issue Type: Bug
>  Components: manufacturing
>Affects Versions: Trunk
>Reporter: Christian Carlow
>
> Production Run Task Issue Components functionality does not take into account 
> manual issuances created on the Materials tab.  
> To reproduce:
> 1.  Create a production run for 2 of product PIZZA
> 2.  Issue 1 of product PEPPERS to a task on the Materials tab
> 3.  Return to the "Edit Production Run" tab and click confirm
> 4.  Click "Quick Start All Tasks"
> 5.  Click the "Issue Components" button for the task
> 6.  Notice the functionality tries to issue 2 even though 1 has already been 
> manually issued



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

buildbot success in ASF Buildbot on ofbiz-branch12

2014-11-25 Thread buildbot 
The Buildbot has detected a restored build on builder ofbiz-branch12 while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch12/builds/110

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz12-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release12.04] 1641550
Blamelist: jleroux

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Commented] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Pierre Smits (JIRA) 

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

Pierre Smits commented on OFBIZ-5884:
-

You tell me where this is going.

In the xsd for forms we have the definition 'attribute name="allow-multiple" 
for drop-down fields. This, in back-end, is intended to enable multi-select 
options. This is not available when it comes to survey questions. 

We have the elaborate combining functionality to group answers to a specific 
question. Yes, that functionality is useful for specific purposes. But it 
requires a lot of screen space.

> Have question of type 'Selected Option' to allow selection of multiple 
> options in surveys
> -
>
> Key: OFBIZ-5884
> URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> Project: OFBiz
>  Issue Type: Improvement
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: questionnaire, survey
>
> Currently 'Select Option' only allows to select one option. This should also 
> allow the selection of multiple options.
> Though there is the possibility to group multiple questions together by means 
> of the SurveyMultiResp functionality, that might not always prove to be right 
> the solution for survey creators. 
> A simple 'multi-option' select question saves real estate.



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

buildbot success in ASF Buildbot on ofbiz-branch13

2014-11-25 Thread buildbot 
The Buildbot has detected a restored build on builder ofbiz-branch13 while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/ofbiz-branch13/builds/174

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz13-commit' 
triggered this build
Build Source Stamp: [branch ofbiz/branches/release13.07] 1641549
Blamelist: jleroux

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Comment Edited] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-5884 at 11/25/14 9:26 AM:
--

Is this discussion not going in the same direction than the lot one OFBIZ-5704? 

Pierre, are you proposing a data model change? It's not clear to me, if yes 
please attach a patch...


was (Author: jacques.le.roux):
Is this discussion not going in the same way than the lot one OFBIZ-5704? 

Pierre, are you proposing a data model change? It's not clear to me, if yes 
please attach a patch...

> Have question of type 'Selected Option' to allow selection of multiple 
> options in surveys
> -
>
> Key: OFBIZ-5884
> URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> Project: OFBiz
>  Issue Type: Improvement
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: questionnaire, survey
>
> Currently 'Select Option' only allows to select one option. This should also 
> allow the selection of multiple options.
> Though there is the possibility to group multiple questions together by means 
> of the SurveyMultiResp functionality, that might not always prove to be right 
> the solution for survey creators. 
> A simple 'multi-option' select question saves real estate.



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

[jira] [Comment Edited] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux edited comment on OFBIZ-5884 at 11/25/14 9:26 AM:
--

Is this discussion not going in the same way than the lot one OFBIZ-5704? 

Pierre, are you proposing a data model change? It's not clear to me, if yes 
please attach a patch...


was (Author: jacques.le.roux):
Is this discussion not going in the same way than the lot one? 

Pierre, are you proposing a data model change? It's not clear to me, if yes 
please attach a patch...

> Have question of type 'Selected Option' to allow selection of multiple 
> options in surveys
> -
>
> Key: OFBIZ-5884
> URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> Project: OFBiz
>  Issue Type: Improvement
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: questionnaire, survey
>
> Currently 'Select Option' only allows to select one option. This should also 
> allow the selection of multiple options.
> Though there is the possibility to group multiple questions together by means 
> of the SurveyMultiResp functionality, that might not always prove to be right 
> the solution for survey creators. 
> A simple 'multi-option' select question saves real estate.



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

[jira] [Commented] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-5884:


Is this discussion not going in the same way than the lot one? 

Pierre, are you proposing a data model change? It's not clear to me, if yes 
please attach a patch...

> Have question of type 'Selected Option' to allow selection of multiple 
> options in surveys
> -
>
> Key: OFBIZ-5884
> URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> Project: OFBiz
>  Issue Type: Improvement
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: questionnaire, survey
>
> Currently 'Select Option' only allows to select one option. This should also 
> allow the selection of multiple options.
> Though there is the possibility to group multiple questions together by means 
> of the SurveyMultiResp functionality, that might not always prove to be right 
> the solution for survey creators. 
> A simple 'multi-option' select question saves real estate.



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

[jira] [Commented] (OFBIZ-5885) EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize

2014-11-25 Thread Deepak Dixit (JIRA) 

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

Deepak Dixit commented on OFBIZ-5885:
-

Thanks Jacques.

> EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize
> ---
>
> Key: OFBIZ-5885
> URL: https://issues.apache.org/jira/browse/OFBIZ-5885
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Release Branch 13.07, Trunk
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch, 12.04.06, 13.07.02
>
> Attachments: OFBIZ-5885.patch
>
>
> EntityListIterator Not Closed for Entity JobSandbox in 
> ServiceUtil.purgeOldJobs method. Need to close the entity list iterator 
> properly.



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

[jira] [Closed] (OFBIZ-5885) EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux closed OFBIZ-5885.
--
   Resolution: Fixed
Fix Version/s: 13.07.02
   12.04.06
   Upcoming Branch

Thanks Deepak,

Your patch is in
trunk r1641548
R13.07 r1641549
R12.04 r1641550

This action follows [David Allen's Two Minute 
Rule|http://www.success.com/article/1-on-1-david-allens-two-minute-rule]

I'm still wondering why americans put all titles words 1st letters in 
uppercase...Marketing habit maybe...


> EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize
> ---
>
> Key: OFBIZ-5885
> URL: https://issues.apache.org/jira/browse/OFBIZ-5885
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Release Branch 13.07, Trunk
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch, 12.04.06, 13.07.02
>
> Attachments: OFBIZ-5885.patch
>
>
> EntityListIterator Not Closed for Entity JobSandbox in 
> ServiceUtil.purgeOldJobs method. Need to close the entity list iterator 
> properly.



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

Re: [jira] [Commented] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Pierre Smits 
Yes, it is a usability issue.

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Tue, Nov 25, 2014 at 9:33 AM, Scott Gray (JIRA)  wrote:

>
> [
> https://issues.apache.org/jira/browse/OFBIZ-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224223#comment-14224223
> ]
>
> Scott Gray commented on OFBIZ-5884:
> ---
>
> Opening a new ticket to replace OFBIZ-5688 doesn't somehow make this
> ticket any different.
>
> If layout is your only concern then we could look at altering the
> templates/css that render/style the surveys but I don't see any benefit to
> redesigning the data model for a problem that is already solved.
>
> > Have question of type 'Selected Option' to allow selection of multiple
> options in surveys
> >
> -
> >
> > Key: OFBIZ-5884
> > URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> > Project: OFBiz
> >  Issue Type: Improvement
> >  Components: content
> >Affects Versions: Trunk
> >Reporter: Pierre Smits
> >  Labels: questionnaire, survey
> >
> > Currently 'Select Option' only allows to select one option. This should
> also allow the selection of multiple options.
> > Though there is the possibility to group multiple questions together by
> means of the SurveyMultiResp functionality, that might not always prove to
> be right the solution for survey creators.
> > A simple 'multi-option' select question saves real estate.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

[jira] [Assigned] (OFBIZ-5885) EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux reassigned OFBIZ-5885:
--

Assignee: Jacques Le Roux

> EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize
> ---
>
> Key: OFBIZ-5885
> URL: https://issues.apache.org/jira/browse/OFBIZ-5885
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Release Branch 13.07, Trunk
>Reporter: Deepak Dixit
>Assignee: Jacques Le Roux
>Priority: Minor
> Attachments: OFBIZ-5885.patch
>
>
> EntityListIterator Not Closed for Entity JobSandbox in 
> ServiceUtil.purgeOldJobs method. Need to close the entity list iterator 
> properly.



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

[jira] [Commented] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Scott Gray (JIRA) 

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

Scott Gray commented on OFBIZ-5884:
---

Opening a new ticket to replace OFBIZ-5688 doesn't somehow make this ticket any 
different.

If layout is your only concern then we could look at altering the templates/css 
that render/style the surveys but I don't see any benefit to redesigning the 
data model for a problem that is already solved.

> Have question of type 'Selected Option' to allow selection of multiple 
> options in surveys
> -
>
> Key: OFBIZ-5884
> URL: https://issues.apache.org/jira/browse/OFBIZ-5884
> Project: OFBiz
>  Issue Type: Improvement
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: questionnaire, survey
>
> Currently 'Select Option' only allows to select one option. This should also 
> allow the selection of multiple options.
> Though there is the possibility to group multiple questions together by means 
> of the SurveyMultiResp functionality, that might not always prove to be right 
> the solution for survey creators. 
> A simple 'multi-option' select question saves real estate.



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

[jira] [Updated] (OFBIZ-5885) EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize

2014-11-25 Thread Deepak Dixit (JIRA) 

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

Deepak Dixit updated OFBIZ-5885:

Attachment: OFBIZ-5885.patch

Here is the patch for this issue.

> EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize
> ---
>
> Key: OFBIZ-5885
> URL: https://issues.apache.org/jira/browse/OFBIZ-5885
> Project: OFBiz
>  Issue Type: Bug
>  Components: framework
>Affects Versions: Release Branch 13.07, Trunk
>Reporter: Deepak Dixit
>Priority: Minor
> Attachments: OFBIZ-5885.patch
>
>
> EntityListIterator Not Closed for Entity JobSandbox in 
> ServiceUtil.purgeOldJobs method. Need to close the entity list iterator 
> properly.



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

[jira] [Closed] (OFBIZ-5064) Failure in create operation for entity PaymentGatewayResponse

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux closed OFBIZ-5064.
--
Resolution: Invalid

Thanks Divesh,

Makes perfect sense to me. PaymentGatewayResponse.resultDeclined is an 
indicator which is indeed a sole character (supposed to be "Y" or "N")

I close as invalid

> Failure in create operation for entity PaymentGatewayResponse
> -
>
> Key: OFBIZ-5064
> URL: https://issues.apache.org/jira/browse/OFBIZ-5064
> Project: OFBiz
>  Issue Type: Bug
>  Components: accounting
> Environment: Linux
>Reporter: Nilesh S Patil
>
> An error appear in the log and gradually add records in JOBSANDBOX entity:
> 2012-08-08 19:26:33,917 (default#36-invoker-Thread-22) [ 
> GenericDelegator.java:866:ERROR] Failure in create operation for entity 
> [PaymentGatewayResponse]: org.ofbiz.entity.GenericEntityException: Error 
> while inserting: 
> [GenericEntity:PaymentGatewayResponse][altReference,[null-field](java.lang.String)][amount,3.00(java.math.BigDecimal)][createdStamp,2012-08-08
>  19:26:33.915(java.sql.Timestamp)][createdTxStamp,2012-08-08 
> 19:26:33.915(java.sql.Timestamp)][currencyUomId,USD][gatewayAvsResult,[null-field](java.lang.String)][gatewayCode,57355P(java.lang.String)][gatewayCvResult,[null-field](java.lang.String)][gatewayFlag,1(java.lang.String)][gatewayMessage,This
>  transaction has been 
> approved.(java.lang.String)][gatewayScoreResult,[null-field](java.lang.String)][lastUpdatedStamp,2012-08-08
>  19:26:33.915(java.sql.Timestamp)][lastUpdatedTxStamp,2012-08-08 
> 19:26:33.915(java.sql.Timestamp)][orderPaymentPreferenceId,10021(java.lang.String)][paymentGatewayResponseId,10013(java.lang.String)][paymentMethodId,10220(java.lang.String)][paymentMethodTypeId,CREDIT_CARD(java.lang.String)][paymentServiceTypeEnumId,PRDS_PAY_CAPTURE(java.lang.String)][referenceNum,4547539856(java.lang.String)][resultBadCardNumber,[null-field](java.lang.String)][resultBadExpire,[null-field](java.lang.String)][resultDeclined,[null-field](java.lang.String)][resultNsf,[null-field](java.lang.String)][subReference,[null-field](java.lang.String)][transCodeEnumId,PGT_CAPTURE(java.lang.String)][transactionDate,2012-08-01
>  22:12:33.145(java.sql.Timestamp)] (SQL Exception while executing the 
> following:INSERT INTO PAYMENT_GATEWAY_RESPONSE (PAYMENT_GATEWAY_RESPONSE_ID, 
> PAYMENT_SERVICE_TYPE_ENUM_ID, ORDER_PAYMENT_PREFERENCE_ID, 
> PAYMENT_METHOD_TYPE_ID, PAYMENT_METHOD_ID, TRANS_CODE_ENUM_ID, AMOUNT, 
> CURRENCY_UOM_ID, REFERENCE_NUM, ALT_REFERENCE, SUB_REFERENCE, GATEWAY_CODE, 
> GATEWAY_FLAG, GATEWAY_AVS_RESULT, GATEWAY_CV_RESULT, GATEWAY_SCORE_RESULT, 
> GATEWAY_MESSAGE, TRANSACTION_DATE, RESULT_DECLINED, RESULT_NSF, 
> RESULT_BAD_EXPIRE, RESULT_BAD_CARD_NUMBER, LAST_UPDATED_STAMP, 
> LAST_UPDATED_TX_STAMP, CREATED_STAMP, CREATED_TX_STAMP) VALUES (?, ?, ?, ?, 
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Data 
> truncation: Data too long for column 'RESULT_DECLINED' at row 1)). Rolling 
> back transaction.
> 2012-08-08 19:26:33,918 (default#36-invoker-Thread-22) 
> [PaymentGatewayServices.java:2969:ERROR] 
>  exception report 
> --
> Exception: org.ofbiz.entity.GenericEntityException
> Message: Error while inserting: 
> [GenericEntity:PaymentGatewayResponse][altReference,[null-field](java.lang.String)][amount,3.00(java.math.BigDecimal)][createdStamp,2012-08-08
>  19:26:33.915(java.sql.Timestamp)][createdTxStamp,2012-08-08 
> 19:26:33.915(java.sql.Timestamp)][currencyUomId,USD][gatewayAvsResult,[null-field](java.lang.String)][gatewayCode,57355P(java.lang.String)][gatewayCvResult,[null-field](java.lang.String)][gatewayFlag,1(java.lang.String)][gatewayMessage,This
>  transaction has been 
> approved.(java.lang.String)][gatewayScoreResult,[null-field](java.lang.String)][lastUpdatedStamp,2012-08-08
>  19:26:33.915(java.sql.Timestamp)][lastUpdatedTxStamp,2012-08-08 
> 19:26:33.915(java.sql.Timestamp)][orderPaymentPreferenceId,10021(java.lang.String)][paymentGatewayResponseId,10013(java.lang.String)][paymentMethodId,10220(java.lang.String)][paymentMethodTypeId,CREDIT_CARD(java.lang.String)][paymentServiceTypeEnumId,PRDS_PAY_CAPTURE(java.lang.String)][referenceNum,4547539856(java.lang.String)][resultBadCardNumber,[null-field](java.lang.String)][resultBadExpire,[null-field](java.lang.String)][resultDeclined,[null-field](java.lang.String)][resultNsf,[null-field](java.lang.String)][subReference,[null-field](java.lang.String)][transCodeEnumId,PGT_CAPTURE(java.lang.String)][transactionDate,2012-08-01
>  22:12:33.145(java.sql.Timestamp)] (SQL Exception while executing the 
> following:INSERT INTO PAYMENT_GATEWAY_RESPONSE (PAYMENT_GATEWAY_RESPONSE_ID, 
> PAYMENT_SERVICE_TYPE_ENUM_ID, ORDER_PAYME

[jira] [Created] (OFBIZ-5885) EntityListIterator Not Closed for Entity JobSandbox, caught in Finalize

2014-11-25 Thread Deepak Dixit (JIRA) 
Deepak Dixit created OFBIZ-5885:
---

 Summary: EntityListIterator Not Closed for Entity JobSandbox, 
caught in Finalize
 Key: OFBIZ-5885
 URL: https://issues.apache.org/jira/browse/OFBIZ-5885
 Project: OFBiz
  Issue Type: Bug
  Components: framework
Affects Versions: Trunk, Release Branch 13.07
Reporter: Deepak Dixit
Priority: Minor


EntityListIterator Not Closed for Entity JobSandbox in ServiceUtil.purgeOldJobs 
method. Need to close the entity list iterator properly.



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

[jira] [Closed] (OFBIZ-5846) Field definition problem, program should use purposeFromDate in stead of fromDate.

2014-11-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux closed OFBIZ-5846.
--
Resolution: Fixed

Wrong button I guess, thanks Scott

> Field definition problem, program should use purposeFromDate in stead of 
> fromDate.
> --
>
> Key: OFBIZ-5846
> URL: https://issues.apache.org/jira/browse/OFBIZ-5846
> Project: OFBiz
>  Issue Type: Bug
>  Components: party
>Affects Versions: Trunk
>Reporter: Supachai Chaima-ngua
>Assignee: Jacques Le Roux
>  Labels: partymgr
> Fix For: Upcoming Branch, 12.04.06, 13.07.02
>
> Attachments: ofbizbug-deleltecontectmech.patch
>
>
> field definition problem, program should use purposeFromDate in stead of 
> fromDate.
> deletePcmCtx.put("fromDate", tempVal.get("purposeFromDate"));



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

[jira] [Created] (OFBIZ-5884) Have question of type 'Selected Option' to allow selection of multiple options in surveys

2014-11-25 Thread Pierre Smits (JIRA) 
Pierre Smits created OFBIZ-5884:
---

 Summary: Have question of type 'Selected Option' to allow 
selection of multiple options in surveys
 Key: OFBIZ-5884
 URL: https://issues.apache.org/jira/browse/OFBIZ-5884
 Project: OFBiz
  Issue Type: Improvement
  Components: content
Affects Versions: Trunk
Reporter: Pierre Smits


Currently 'Select Option' only allows to select one option. This should also 
allow the selection of multiple options.

Though there is the possibility to group multiple questions together by means 
of the SurveyMultiResp functionality, that might not always prove to be right 
the solution for survey creators. 

A simple 'multi-option' select question saves real estate.



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