[jira] [Updated] (OFBIZ-5535) Void item, quantity update, and discounts don't work for configurable items
[ https://issues.apache.org/jira/browse/OFBIZ-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-5535: -- Attachment: OFBIZ-5535.patch This solves the issue. > Void item, quantity update, and discounts don't work for configurable items > --- > > Key: OFBIZ-5535 > URL: https://issues.apache.org/jira/browse/OFBIZ-5535 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/pos >Affects Versions: SVN trunk > Environment: all >Reporter: Chris Lombardi >Priority: Minor > Fix For: SVN trunk > > Attachments: OFBIZ-5535.patch > > > void item, quantity update and discounts work off of the sku in the pos. I > fixed it to use the cart index so these operations will work when there are > multiple configurations per sku in the cart. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (OFBIZ-5535) Void item, quantity update, and discounts don't work for configurable items
Chris Lombardi created OFBIZ-5535: - Summary: Void item, quantity update, and discounts don't work for configurable items Key: OFBIZ-5535 URL: https://issues.apache.org/jira/browse/OFBIZ-5535 Project: OFBiz Issue Type: Bug Components: specialpurpose/pos Affects Versions: SVN trunk Environment: all Reporter: Chris Lombardi Priority: Minor Fix For: SVN trunk void item, quantity update and discounts work off of the sku in the pos. I fixed it to use the cart index so these operations will work when there are multiple configurations per sku in the cart. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] Commented: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
[ https://issues.apache.org/jira/browse/OFBIZ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666357#action_12666357 ] Chris Lombardi commented on OFBIZ-1581: --- Sorry, I have been completely consumed by construction. I did update this further, but as best I can now tell I only broke it. I'm sure if I made any good progress I would have uploaded another patch. > Change ConfigureItem to use XPage instead of XDialog > > > Key: OFBIZ-1581 > URL: https://issues.apache.org/jira/browse/OFBIZ-1581 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1581-2.patch > > > I'm adding in price information to the ConfigureItem page, and was quickly > running out of space. So I'd like to change it to an XPage so I can take > advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1945) Create/use order for POS save / load sale
[ https://issues.apache.org/jira/browse/OFBIZ-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628103#action_12628103 ] Chris Lombardi commented on OFBIZ-1945: --- Synchronization issues aside, this should work such that any POS has access to the list of not completed orders (ORDERHEADER). Changing the behavior is as easy as changing the query that fetches the list of orders. I haven't tried this, but given an appropriate query, it should allow pulling up orders placed through other channels. Restricting the list, i.e. having orders available at any POS to a certain user id, should also be easy. It should also allow for taking advantage of ofbiz infrastructure because this more closely adheres to the "normal" ofbiz order flow. I was thinking of routing product requests to specific stations, etc. I'm sure others will have more and better ideas. > Create/use order for POS save / load sale > - > > Key: OFBIZ-1945 > URL: https://issues.apache.org/jira/browse/OFBIZ-1945 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1945.patch > > > Currently, the "load sale" / "save sale" pos functions save a shopping list. > I'd like to change that so that orders are created and updated. This would > increase the security of the solution and allow work orders to be created, > etc. > I'm about 90% there, but I'm hitting a wall. I can currently save off a > created order, restore the order, update payments, etc. This includes saving > discounts, item configurations, etc. However, there's a problem in saving > the new items to the order. I'm probably overlooking something obvious, so > if someone wants to double check me, I'd appreciate it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1945) Create/use order for POS save / load sale
[ https://issues.apache.org/jira/browse/OFBIZ-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1945: -- Attachment: ofbiz-1945.patch Currently doesn't save the added order items. > Create/use order for POS save / load sale > - > > Key: OFBIZ-1945 > URL: https://issues.apache.org/jira/browse/OFBIZ-1945 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Reporter: Chris Lombardi > Attachments: ofbiz-1945.patch > > > Currently, the "load sale" / "save sale" pos functions save a shopping list. > I'd like to change that so that orders are created and updated. This would > increase the security of the solution and allow work orders to be created, > etc. > I'm about 90% there, but I'm hitting a wall. I can currently save off a > created order, restore the order, update payments, etc. This includes saving > discounts, item configurations, etc. However, there's a problem in saving > the new items to the order. I'm probably overlooking something obvious, so > if someone wants to double check me, I'd appreciate it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1945) Create/use order for POS save / load sale
Create/use order for POS save / load sale - Key: OFBIZ-1945 URL: https://issues.apache.org/jira/browse/OFBIZ-1945 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Reporter: Chris Lombardi Currently, the "load sale" / "save sale" pos functions save a shopping list. I'd like to change that so that orders are created and updated. This would increase the security of the solution and allow work orders to be created, etc. I'm about 90% there, but I'm hitting a wall. I can currently save off a created order, restore the order, update payments, etc. This includes saving discounts, item configurations, etc. However, there's a problem in saving the new items to the order. I'm probably overlooking something obvious, so if someone wants to double check me, I'd appreciate it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1528) Can't reconfigure items once they are added to cart
[ https://issues.apache.org/jira/browse/OFBIZ-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626812#action_12626812 ] Chris Lombardi commented on OFBIZ-1528: --- In my travels, I found a site with an interesting way of handling this issue. http://www.ttiglobal.com/ViewCart.aspx > Can't reconfigure items once they are added to cart > --- > > Key: OFBIZ-1528 > URL: https://issues.apache.org/jira/browse/OFBIZ-1528 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > > Steps to duplicate. > 1. Add an aggregated item to your shopping cart in the ecommerce app. > 2. View your shopping cart. > 3. Click on the aggregated item in your shopping cart. > 4. A new, default aggregated item is shown, not the aggregated item with the > configuration your previously chose. > I'm not sure what the best practice is here, but the current process flow was > unexpected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1606) Add numeric keypad popup function
[ https://issues.apache.org/jira/browse/OFBIZ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614469#action_12614469 ] Chris Lombardi commented on OFBIZ-1606: --- You could put the numbers above the letters, like a normal (I think it's the same in FR) keyboard. That would give the user numbers in a familiar format, but not go over 800x600. It might not be as convenient (though I could see two sides to that) but it would be pretty close. For number-only entry, I'd just pop the smaller numerical only keypad. Are there internationalization issues with the numerical only keypad also? TMK everyone uses the standard arabic number (0,1,2...) symbols. > Add numeric keypad popup function > - > > Key: OFBIZ-1606 > URL: https://issues.apache.org/jira/browse/OFBIZ-1606 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1606.patch > > > Some areas in the POS require a keyboard instead of a touchscreen for input. > Here is a dialog that can be used for numerical entry via a touchscreen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[ https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1716: -- Attachment: ofbiz-1716.patch Updated patch to work with current trunk. Tested, works ok. > POS: CVV2 code is not always deleted from the DB > > > Key: OFBIZ-1716 > URL: https://issues.apache.org/jira/browse/OFBIZ-1716 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: SVN trunk, Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Critical > Attachments: ofbiz-1716.patch, ofbiz-1716.patch > > > I ran a transaction that was declined by the processor. I later noticed that > the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[ https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608446#action_12608446 ] Chris Lombardi commented on OFBIZ-1716: --- I don't remember. The patch looks pretty straight forward though, I'll test it today. > POS: CVV2 code is not always deleted from the DB > > > Key: OFBIZ-1716 > URL: https://issues.apache.org/jira/browse/OFBIZ-1716 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: SVN trunk, Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Critical > Attachments: ofbiz-1716.patch > > > I ran a transaction that was declined by the processor. I later noticed that > the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1427) Modal windows require keyboard and mouse
[ https://issues.apache.org/jira/browse/OFBIZ-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1427: -- Attachment: 23June2008_OnScreenKeyboard.patch 23June2008_OnScreenKeyboard.patch changes: Added Uppercase / Lowercase functionality, including single button shift and shift-lock Fixed the behavior of the cancel button Removed unused code and general cleanup Would like to add other layout / language support, need to think more on how to implement that. I haven't looked into BS's added code in SaveSale.java, but thought I would put up what I have as I may not get around to it again this week. > Modal windows require keyboard and mouse > > > Key: OFBIZ-1427 > URL: https://issues.apache.org/jira/browse/OFBIZ-1427 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk > Environment: Any >Reporter: Vince Clark >Assignee: Jacques Le Roux >Priority: Minor > Attachments: 23June2008_OnScreenKeyboard.patch, keyboard.diff > > > Modal windows such as "Cash Out" require the use of a keyboard and mouse to > enter data because the keypad cannot be accessed for input. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[ https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1716: -- Attachment: ofbiz-1716.patch I have to test this patch. > POS: CVV2 code is not always deleted from the DB > > > Key: OFBIZ-1716 > URL: https://issues.apache.org/jira/browse/OFBIZ-1716 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: SVN trunk, Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Critical > Attachments: ofbiz-1716.patch > > > I ran a transaction that was declined by the processor. I later noticed that > the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[ https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588410#action_12588410 ] Chris Lombardi commented on OFBIZ-1716: --- I'll fix it to delete the cvv and track2 information per DJ's comment. JLR, do you have any objections? > POS: CVV2 code is not always deleted from the DB > > > Key: OFBIZ-1716 > URL: https://issues.apache.org/jira/browse/OFBIZ-1716 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: SVN trunk, Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Critical > > I ran a transaction that was declined by the processor. I later noticed that > the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1663) POS: All payment types allow change to be made
[ https://issues.apache.org/jira/browse/OFBIZ-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588355#action_12588355 ] Chris Lombardi commented on OFBIZ-1663: --- Thanks SG! I must have skimmed past the references to 4.0. JLR, did you encounter this defect in 4.0 or trunk? That would explain why I wasn't able to reproduce it. > POS: All payment types allow change to be made > > > Key: OFBIZ-1663 > URL: https://issues.apache.org/jira/browse/OFBIZ-1663 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 4.0 > > Attachments: ofbiz-1663.patch > > > I fat-fingered the amount of the transaction when I was testing credit card > processing and was surprised to see the POS making change for a credit card > transaction. > I would imagine change would be allowed if and only if the amount of change > is less than the amount of cash given. This would apply for both cash sales > and multiple payment type sales. > Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OFBIZ-1663) POS: All payment types allow change to be made
[ https://issues.apache.org/jira/browse/OFBIZ-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi reopened OFBIZ-1663: --- So even after ofbiz-1706 has been fixed, you are still seeing this error? That's interesting. I do plan on fixing this, I'm admittedly slow because I'm working on something else at the moment, but I will return. If you would like, assign it to me so it isn't cluttering up your list. > POS: All payment types allow change to be made > > > Key: OFBIZ-1663 > URL: https://issues.apache.org/jira/browse/OFBIZ-1663 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Fix For: Release Branch 4.0 > > Attachments: ofbiz-1663.patch > > > I fat-fingered the amount of the transaction when I was testing credit card > processing and was surprised to see the POS making change for a credit card > transaction. > I would imagine change would be allowed if and only if the amount of change > is less than the amount of cash given. This would apply for both cash sales > and multiple payment type sales. > Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[ https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588241#action_12588241 ] Chris Lombardi commented on OFBIZ-1716: --- I'm not sure of the scenario where you wouldn't just report back to the customer that their card has been declined and instead retain the cvv code for later retries. 1. Online e-commerce 2. POS 3. Card taken over phone by sales 4. Recurring subscriptions For cases 1, 2 and 3, just report back declined. The customer may enter in a different credit card. For case 4, you shouldn't retain the cvv code past the initial transaction. In reading the code, there was some retry logic for a not sufficient funds (nsf) case. Could anyone explain when this is actually used? I'm having a hard time figuring out when you wouldn't just report back to the customer with a decline. > POS: CVV2 code is not always deleted from the DB > > > Key: OFBIZ-1716 > URL: https://issues.apache.org/jira/browse/OFBIZ-1716 > Project: OFBiz > Issue Type: Bug > Components: ALL COMPONENTS >Affects Versions: SVN trunk, Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Critical > > I ran a transaction that was declined by the processor. I later noticed that > the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
[
https://issues.apache.org/jira/browse/OFBIZ-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580999#action_12580999
]
Chris Lombardi commented on OFBIZ-1716:
---
I have to go read the interchange guidelines to determine what is allowable for
retention of cvv2 for retries in an ecommerce context. If anyone has any
comments on this, please chime in.
Here's the section that may need to be changed:
PaymentGatewayServices: 1770
if (context != null && authResult.booleanValue()) {
orderPaymentPreference.set("statusId", "PAYMENT_AUTHORIZED");
orderPaymentPreference.set("securityCode", null);
orderPaymentPreference.set("track2", null);
} else if (context != null && !authResult.booleanValue()) {
orderPaymentPreference.set("statusId", "PAYMENT_DECLINED");
} else {
orderPaymentPreference.set("statusId", "PAYMENT_ERROR");
}
> POS: CVV2 code is not always deleted from the DB
>
>
> Key: OFBIZ-1716
> URL: https://issues.apache.org/jira/browse/OFBIZ-1716
> Project: OFBiz
> Issue Type: Bug
> Components: specialpurpose/pos
>Affects Versions: Release Branch 4.0
>Reporter: Chris Lombardi
>
> I ran a transaction that was declined by the processor. I later noticed that
> the cvv2 code was still present in the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1716) POS: CVV2 code is not always deleted from the DB
POS: CVV2 code is not always deleted from the DB Key: OFBIZ-1716 URL: https://issues.apache.org/jira/browse/OFBIZ-1716 Project: OFBiz Issue Type: Bug Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi I ran a transaction that was declined by the processor. I later noticed that the cvv2 code was still present in the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1627) POS payment failures should not be retried and notified by email
[ https://issues.apache.org/jira/browse/OFBIZ-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1627: -- Attachment: ofbiz-1627.patch This patch changes the error message. > POS payment failures should not be retried and notified by email > > > Key: OFBIZ-1627 > URL: https://issues.apache.org/jira/browse/OFBIZ-1627 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1627.patch > > > After receiving an intentional connection error to a payment processor, I > receieved the following error on the POS. > "Problem connecting to payment processor; we will continue to retry and > notify you by email." > This is either 1) an incorrect error message or 2) a troubling process flow > that needs to be corrected. > I'm not sure which yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1627) POS payment failures should not be retried and notified by email
[ https://issues.apache.org/jira/browse/OFBIZ-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580173#action_12580173 ] Chris Lombardi commented on OFBIZ-1627: --- I have the machine set up again for this scenario and I do see the same error message. > POS payment failures should not be retried and notified by email > > > Key: OFBIZ-1627 > URL: https://issues.apache.org/jira/browse/OFBIZ-1627 > Project: OFBiz > Issue Type: Bug > Components: accounting >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > > After receiving an intentional connection error to a payment processor, I > receieved the following error on the POS. > "Problem connecting to payment processor; we will continue to retry and > notify you by email." > This is either 1) an incorrect error message or 2) a troubling process flow > that needs to be corrected. > I'm not sure which yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579115#action_12579115 ] Chris Lombardi commented on OFBIZ-1674: --- I believe we are starting to get chip cards, but I don't know what the statistics are for market penetration. I have one item of clarification. If a card is swiped, the CV2 and postal code is not requested. If the card is unable to be swiped (bad magnetic stripe, etc) the CV2 and postal code are requested. I don't think that the CVV2 code entry is a US only process (the postal code thing could be), but I could be wrong. Entering in either CVV2 or postal code, when a card is keyed, is optional, if you don't mind paying the higher rate. I don't know that I would have bothered to put that in if I weren't knee deep in that code already. I would assume that the incidence of unswipable cards is pretty low - but then again I haven't seen any stats on that since I come from the card not present world. If someone wants to get the card present transactions going in another country, I'd be glad to help work out a way to have localized credit card checkout process flows. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Fix For: SVN trunk > > Attachments: ofbiz-1674.patch, ofbiz-1674.patch, ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1606) Add numeric keypad popup function
[ https://issues.apache.org/jira/browse/OFBIZ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578952#action_12578952 ] Chris Lombardi commented on OFBIZ-1606: --- Processes that require the keyboard or a keypad dialog: 1. Voiding a sale requires alpha-numeric entry. Is it possible to change OrderId to all-numeric? 2. Paid-in/paid-out. Is there anything else? I don't seem to see anything. > Add numeric keypad popup function > - > > Key: OFBIZ-1606 > URL: https://issues.apache.org/jira/browse/OFBIZ-1606 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1606.patch > > > Some areas in the POS require a keyboard instead of a touchscreen for input. > Here is a dialog that can be used for numerical entry via a touchscreen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1687: -- Attachment: ofbiz-1687-2.patch This was easier than I thought it would be. Patch #2 removes the credit card printouts in the log and masks the card number printouts on the receipts. > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1687-1.patch, ofbiz-1687-2.patch > > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1687: -- Attachment: (was: ofbiz-1687-1.patch) > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1687-1.patch > > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1687: -- Attachment: ofbiz-1687-1.patch > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1687-1.patch > > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1687: -- Attachment: ofbiz-1687-1.patch Patch to add in formatPrintableCreditCard() and tests to base. I'll add another patch to utilize this in POS, but not today. > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1687-1.patch > > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578598#action_12578598 ] Chris Lombardi commented on OFBIZ-1674: --- Works great on linux with the MSR. It's ready for review. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch, ofbiz-1674.patch, ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1706) Using a check in the POS causes an error in changing status
Using a check in the POS causes an error in changing status --- Key: OFBIZ-1706 URL: https://issues.apache.org/jira/browse/OFBIZ-1706 Project: OFBiz Issue Type: Bug Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Environment: XP with derby Reporter: Chris Lombardi I always see an error when I use CHECK for payment in the POS. 2008-03-13 16:01:46,188 (Thread-439) [ ServiceEcaRule.java:144:INFO ] Running Service ECA Service: capturePaymentsByInvoice, triggered by rule on Service: createInvoiceForOrder 2008-03-13 16:01:46,359 (Thread-439) [PaymentGatewayServices.java:1003:INFO ] (Capture) Invoice [#CI2] total: 0.0 2008-03-13 16:01:46,959 (Thread-439) [PaymentGatewayServices.java:1068:INFO ] The Remaining Total for order: RSCO10001 is: 0.00 2008-03-13 16:01:46,959 (Thread-439) [PaymentGatewayServices.java:1071:INFO ] Actual Expected Capture Amount : 0.00 2008-03-13 16:01:47,400 (Thread-439) [ UtilProperties.java:533:INFO ] Loaded 275 properties for: OrderErrorUiLabels (en) 2008-03-13 16:01:47,500 (Thread-439) [ UtilProperties.java:851:INFO ] ResourceBundle OrderErrorUiLabels (en_US) created in 390.0 mS 2008-03-13 16:01:47,500 (Thread-439) [ ServiceDispatcher.java:518:ERROR] Error in Service [changeOrderStatus]: ERROR : Could not change order status ; status is not a valid change.: [ORDER_CREATED] -> [ORDER_COMPLETED] 2008-03-13 16:01:47,510 (Thread-439) [TransactionUtil.java:275:ERROR] exception report -- [TransactionUtil.rollback] Exception: java.lang.Exception Message: Stack Trace stack trace --- java.lang.Exception: Stack Trace org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:274) org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:256) org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:522) org.ofbiz.service.ServiceDispatcher.runSync(ServiceDispatcher.java:213) org.ofbiz.service.GenericDispatcher.runSync(GenericDispatcher.java:149) org.ofbiz.order.order.OrderChangeHelper.orderStatusChanges(OrderChangeHelper.java:158) org.ofbiz.order.order.OrderChangeHelper.completeOrder(OrderChangeHelper.java:121) org.ofbiz.order.shoppingcart.CheckOutHelper.processPayment(CheckOutHelper.java:1061) org.ofbiz.order.shoppingcart.CheckOutHelper.processPayment(CheckOutHelper.java:866) org.ofbiz.pos.PosTransaction.processSale(PosTransaction.java:802) org.ofbiz.pos.event.PaymentEvents.processSale(PaymentEvents.java:368) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.ofbiz.pos.config.ButtonEventConfig.invoke(ButtonEventConfig.java:208) org.ofbiz.pos.config.ButtonEventConfig.invokeButtonEvent(ButtonEventConfig.java:105) org.ofbiz.pos.component.PosButton$1.construct(PosButton.java:121) net.xoetrope.xui.helper.SwingWorker$2.run(Unknown Source) java.lang.Thread.run(Thread.java:619) 2008-03-13 16:01:47,510 (Thread-439) [TransactionUtil.java:285:INFO ] [TransactionUtil.rollback] transaction rolled back 2008-03-13 16:01:47,510 (Thread-439) [ OrderChangeHelper.java:160:ERROR] Problems adjusting order header status for order #RSCO10001 2008-03-13 16:01:47,771 (Thread-439) [ ServiceEcaRule.java:127:INFO ] For Service ECA [changeOrderItemStatus] on [commit] got false for condition: [statusId][equals][ITEM_CANCELLED][true][String] 2008-03-13 16:01:47,771 (Thread-439) [ ServiceEcaRule.java:144:INFO ] Running Service ECA Service: checkOrderItemStatus, triggered by rule on Service: changeOrderItemStatus 2008-03-13 16:01:47,811 (Thread-439) [ ServiceEcaRule.java:127:INFO ] For Service ECA [changeOrderItemStatus] on [commit] got false for condition: [statusId][equals][ITEM_APPROVED][true][String] 2008-03-13 16:01:47,811 (Thread-439) [ ServiceEcaRule.java:127:INFO ] For Service ECA [changeOrderItemStatus] on [commit] got false for condition: [statusId][equals][ITEM_APPROVED][true][String] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1674: -- Attachment: ofbiz-1674.patch 2 weeks and 2 laptops later, I'm back. This is solid on windows, I need to test on linux with the MSR. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch, ofbiz-1674.patch, ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574819#action_12574819 ] Chris Lombardi commented on OFBIZ-1674: --- Not yet, I found a couple of issues. I'm going to do more testing tomorrow. And I need to remove my obsolete comments... > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch, ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1674: -- Attachment: ofbiz-1674.patch Interestingly, a few of the processors did support the cvv response, but it wasn't saved anywhere. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch, ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574589#action_12574589 ] Chris Lombardi commented on OFBIZ-1674: --- What AVS issues are you referring to? Ofbiz already stores the AVS response. The patch I uploaded does request the postal code from the operator and uses the available infrastructure to send the postal code to PaymentGatewayServices. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574540#action_12574540 ] Chris Lombardi commented on OFBIZ-1674: --- I have to do more research. I thought that a bad cvv2 code would cause a transaction to be denied, but that's not always the case. The CVV2 gets it's own response which should be stored and potentially acted upon, I think. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1674: -- Attachment: ofbiz-1674.patch This is pretty stable, but I need to test more. > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1674.patch > > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573532#action_12573532 ] clearchris edited comment on OFBIZ-1687 at 2/28/08 4:56 PM: I haven't looked at it yet, I was reading through the interchange guidelines today (dry reading that) and wanted to record this before I forgot. If you take a look at it before I do (probably after I finish up the other cc related issue), please put the function somewhere reusable as I'd also like to mask the credit card numbers printed in cleartext in the logs. EDIT: saw this on the mailing list, attaching to issue. From: Vince M. Clark ([EMAIL PROTECTED]) Sent: Thu 2/28/08 2:13 PM To: dev@ofbiz.apache.org Scott did this for us a few months ago. Scott, feel free to commit to trunk. was (Author: clearchris): I haven't looked at it yet, I was reading through the interchange guidelines today (dry reading that) and wanted to record this before I forgot. If you take a look at it before I do (probably after I finish up the other cc related issue), please put the function somewhere reusable as I'd also like to mask the credit card numbers printed in cleartext in the logs. > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1687) POS: full credit card number is printed on receipt
[ https://issues.apache.org/jira/browse/OFBIZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573532#action_12573532 ] Chris Lombardi commented on OFBIZ-1687: --- I haven't looked at it yet, I was reading through the interchange guidelines today (dry reading that) and wanted to record this before I forgot. If you take a look at it before I do (probably after I finish up the other cc related issue), please put the function somewhere reusable as I'd also like to mask the credit card numbers printed in cleartext in the logs. > POS: full credit card number is printed on receipt > -- > > Key: OFBIZ-1687 > URL: https://issues.apache.org/jira/browse/OFBIZ-1687 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > > Card processing guidelines allow only the last 4 digits of a card number to > be printed on a receipt. The rest should be replaced with asterisk or 'x' > characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1687) POS: full credit card number is printed on receipt
POS: full credit card number is printed on receipt -- Key: OFBIZ-1687 URL: https://issues.apache.org/jira/browse/OFBIZ-1687 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: SVN trunk Reporter: Chris Lombardi Priority: Minor Card processing guidelines allow only the last 4 digits of a card number to be printed on a receipt. The rest should be replaced with asterisk or 'x' characters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573327#action_12573327 ] Chris Lombardi commented on OFBIZ-1674: --- AVS (zip code only) is also be required. Is anyone aware of international address validation service requirements? I.e. is there an analogous service that requires a postal code? > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572497#action_12572497 ] clearchris edited comment on OFBIZ-1674 at 2/26/08 9:03 AM: Could you describe your card not present scenario? Is it exclusively CNP? Are store reps taking and fulfilling MOTO transactions? Edit: I think I misunderstood your comment. Are you: 1. Running as CNP, but would prefer to run as card present. 2. Actually running MOTO / other transactions without the card actually being present. And yes, having card present would save probably around 1% on each txn, or about 30-50% on cc fees. was (Author: clearchris): Could you describe your card not present scenario? Is it exclusively CNP? Are store reps taking and fulfilling MOTO transactions? > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1674) POS: credit card data compliance
[ https://issues.apache.org/jira/browse/OFBIZ-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572497#action_12572497 ] Chris Lombardi commented on OFBIZ-1674: --- Could you describe your card not present scenario? Is it exclusively CNP? Are store reps taking and fulfilling MOTO transactions? > POS: credit card data compliance > > > Key: OFBIZ-1674 > URL: https://issues.apache.org/jira/browse/OFBIZ-1674 > Project: OFBiz > Issue Type: New Feature > Components: specialpurpose/pos >Reporter: Chris Lombardi > > I would like to see the POS have mastercard/visa compliance for basic card > present transactions. > Here's the current list of issues: > Present indicator exists, but is not set by POS. Does anyone use the POS for > card not present (MOTO) transactions? > Card Swiped indicator does not exist, should be added. > track2 data should be added and have scope similar to cvv2, transmitted for > auth, then deleted. > cvv2 data should be requested on manual (keyed) card entry, transmitted for > auth, then deleted. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1674) POS: credit card data compliance
POS: credit card data compliance Key: OFBIZ-1674 URL: https://issues.apache.org/jira/browse/OFBIZ-1674 Project: OFBiz Issue Type: New Feature Components: specialpurpose/pos Reporter: Chris Lombardi I would like to see the POS have mastercard/visa compliance for basic card present transactions. Here's the current list of issues: Present indicator exists, but is not set by POS. Does anyone use the POS for card not present (MOTO) transactions? Card Swiped indicator does not exist, should be added. track2 data should be added and have scope similar to cvv2, transmitted for auth, then deleted. cvv2 data should be requested on manual (keyed) card entry, transmitted for auth, then deleted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1673) POS: Clear One payment does not work
[ https://issues.apache.org/jira/browse/OFBIZ-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1673: -- Attachment: ofbiz-1673.patch Here's the fix. I think I was the culprit on this one. > POS: Clear One payment does not work > > > Key: OFBIZ-1673 > URL: https://issues.apache.org/jira/browse/OFBIZ-1673 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1673.patch > > > The "clear one" payment button does not work in the POS.c -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1673) POS: Clear One payment does not work
POS: Clear One payment does not work Key: OFBIZ-1673 URL: https://issues.apache.org/jira/browse/OFBIZ-1673 Project: OFBiz Issue Type: Bug Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi Priority: Minor The "clear one" payment button does not work in the POS.c -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1671) POS: Msr has double event issue in linux
[ https://issues.apache.org/jira/browse/OFBIZ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1671: -- Attachment: ofbiz-1671.patch Score! This fixes the MSR problem, and I suspect it also fixes the more general linux double-event issue. It causes no harm on WinXP. We may also want to switch the "UseWindow" setting in xpos.properties back to false. > POS: Msr has double event issue in linux > > > Key: OFBIZ-1671 > URL: https://issues.apache.org/jira/browse/OFBIZ-1671 > Project: OFBiz > Issue Type: Bug >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1671.patch > > > I am unable to get a card swipe to be recognized by the POS under linux > because the POS is seeing 2 events for each character swiped. > Here's the line that is showing me the card number with each character output > twice. If I swipe a card outside the POS, the characters from the swipe > appear normal. > Msr.java:121:INFO ] Msr Info : ;|| > Possibly related to OFBIZ-567. However, unlike 567, pushing a button on the > POS does not resolve the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1671) POS: Msr has double event issue in linux
[ https://issues.apache.org/jira/browse/OFBIZ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571841#action_12571841 ] Chris Lombardi commented on OFBIZ-1671: --- Suspect the problem is the following lines setting up frame0 to listen to events twice in PosScreen.java. // configure the frame/window listeners KeyboardAdaptor.attachComponents(appFrame, false); KeyboardAdaptor.attachComponents(appWin, false); >From logging I added: 2008-02-23 20:11:17,858 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: default/paypanel 2008-02-23 20:11:18,396 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: default/mgrpanel 2008-02-23 20:11:18,843 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: default/promopanel 2008-02-23 20:11:18,877 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: frame0 2008-02-23 20:11:18,877 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: frame0 2008-02-23 20:11:19,400 (main) [ KeyboardAdaptor.java:86 :INFO ] Attach component: default/pospanel I'll test with the msr when I'm in front of the machine. > POS: Msr has double event issue in linux > > > Key: OFBIZ-1671 > URL: https://issues.apache.org/jira/browse/OFBIZ-1671 > Project: OFBiz > Issue Type: Bug >Reporter: Chris Lombardi > > I am unable to get a card swipe to be recognized by the POS under linux > because the POS is seeing 2 events for each character swiped. > Here's the line that is showing me the card number with each character output > twice. If I swipe a card outside the POS, the characters from the swipe > appear normal. > Msr.java:121:INFO ] Msr Info : ;|| > Possibly related to OFBIZ-567. However, unlike 567, pushing a button on the > POS does not resolve the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OFBIZ-1671) POS: Msr has double event issue in linux
[ https://issues.apache.org/jira/browse/OFBIZ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi reopened OFBIZ-1671: --- After further testing, it seems I am left with two choices: 1. Set UseWindow=true and have all the dialogs pop under and freeze the POS, but be able to swipe a credit card. 2. Set UseWindow=false and the dialogs work properly, but I can't swipe a cc because of the double event issue. I'm going to have to fix at least one of these issues to get a workable POS. > POS: Msr has double event issue in linux > > > Key: OFBIZ-1671 > URL: https://issues.apache.org/jira/browse/OFBIZ-1671 > Project: OFBiz > Issue Type: Bug >Reporter: Chris Lombardi > > I am unable to get a card swipe to be recognized by the POS under linux > because the POS is seeing 2 events for each character swiped. > Here's the line that is showing me the card number with each character output > twice. If I swipe a card outside the POS, the characters from the swipe > appear normal. > Msr.java:121:INFO ] Msr Info : ;|| > Possibly related to OFBIZ-567. However, unlike 567, pushing a button on the > POS does not resolve the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1663) POS: All payment types allow change to be made
[ https://issues.apache.org/jira/browse/OFBIZ-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571748#action_12571748 ] Chris Lombardi commented on OFBIZ-1663: --- I haven't been able to reproduce this. >From the error message, it sounds like the POS isn't able to create a split >shipment when there are multiple payment types. Are there any special items >in your POS that require a split shipment? > POS: All payment types allow change to be made > > > Key: OFBIZ-1663 > URL: https://issues.apache.org/jira/browse/OFBIZ-1663 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1663.patch > > > I fat-fingered the amount of the transaction when I was testing credit card > processing and was surprised to see the POS making change for a credit card > transaction. > I would imagine change would be allowed if and only if the amount of change > is less than the amount of cash given. This would apply for both cash sales > and multiple payment type sales. > Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-1671) POS: Msr has double event issue in linux
[ https://issues.apache.org/jira/browse/OFBIZ-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi closed OFBIZ-1671. - Resolution: Invalid Thanks JLR, that was it. I think I was staring at the code too long yesterday. Interestingly, this issue doesn't go away after a button is clicked as does the keyboard issue. > POS: Msr has double event issue in linux > > > Key: OFBIZ-1671 > URL: https://issues.apache.org/jira/browse/OFBIZ-1671 > Project: OFBiz > Issue Type: Bug >Reporter: Chris Lombardi > > I am unable to get a card swipe to be recognized by the POS under linux > because the POS is seeing 2 events for each character swiped. > Here's the line that is showing me the card number with each character output > twice. If I swipe a card outside the POS, the characters from the swipe > appear normal. > Msr.java:121:INFO ] Msr Info : ;|| > Possibly related to OFBIZ-567. However, unlike 567, pushing a button on the > POS does not resolve the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1671) POS: Msr has double event issue in linux
POS: Msr has double event issue in linux Key: OFBIZ-1671 URL: https://issues.apache.org/jira/browse/OFBIZ-1671 Project: OFBiz Issue Type: Bug Reporter: Chris Lombardi I am unable to get a card swipe to be recognized by the POS under linux because the POS is seeing 2 events for each character swiped. Here's the line that is showing me the card number with each character output twice. If I swipe a card outside the POS, the characters from the swipe appear normal. Msr.java:121:INFO ] Msr Info : ;|| Possibly related to OFBIZ-567. However, unlike 567, pushing a button on the POS does not resolve the issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1666) POS: Manually entered CC information should also allow CVV2 entry
POS: Manually entered CC information should also allow CVV2 entry - Key: OFBIZ-1666 URL: https://issues.apache.org/jira/browse/OFBIZ-1666 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi Priority: Minor If a credit card is manually entered into the POS, the POS should also request the CVV2/CVC2/CID value. (The 3 or 4 small numbers printed on the card). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1663) POS: All payment types allow change to be made
[ https://issues.apache.org/jira/browse/OFBIZ-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571050#action_12571050 ] Chris Lombardi commented on OFBIZ-1663: --- BTW, what is the traditional ofbiz process for getting translations? Even as much as some of you are multilingual there are some rather exotic languages in there. Do we just go to babelfish and hope for the best? > POS: All payment types allow change to be made > > > Key: OFBIZ-1663 > URL: https://issues.apache.org/jira/browse/OFBIZ-1663 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1663.patch > > > I fat-fingered the amount of the transaction when I was testing credit card > processing and was surprised to see the POS making change for a credit card > transaction. > I would imagine change would be allowed if and only if the amount of change > is less than the amount of cash given. This would apply for both cash sales > and multiple payment type sales. > Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1663) POS: All payment types allow change to be made
[ https://issues.apache.org/jira/browse/OFBIZ-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1663: -- Attachment: ofbiz-1663.patch This fixes the issue in the POS application. I don't think it should harm any other scenarios unless there are situations where people pay more than what is required. Are there? Also, this adds a new error message. I left all the languages in english as I don't think anyone wants my translations. Mon Francais et autre langue e tres mal. :) > POS: All payment types allow change to be made > > > Key: OFBIZ-1663 > URL: https://issues.apache.org/jira/browse/OFBIZ-1663 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1663.patch > > > I fat-fingered the amount of the transaction when I was testing credit card > processing and was surprised to see the POS making change for a credit card > transaction. > I would imagine change would be allowed if and only if the amount of change > is less than the amount of cash given. This would apply for both cash sales > and multiple payment type sales. > Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-1417) Native database error messages don't show in the log
[ https://issues.apache.org/jira/browse/OFBIZ-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi closed OFBIZ-1417. - Resolution: Duplicate > Native database error messages don't show in the log > > > Key: OFBIZ-1417 > URL: https://issues.apache.org/jira/browse/OFBIZ-1417 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Fix For: SVN trunk > > > Native database error messages don't get displayed in the ofbiz log. It > would be very nice if we could capture the error message for SQL errors and > print them in the log. This is an example of an error message generated by > ofbiz: > Results in: > Target exception: org.ofbiz.entity.GenericDataSourceException: SQL Exception > while executing the following: > SELECT I.PARTY_ID, I.PARTY_ID_FROM, I.STATUS_ID, I.BILLING_ACCOUNT_ID, > I.INVOICE_DATE, I.PAID_DATE, I.INVOICE_TYPE_ID, I.INVOICE_ID, > SUM((COALESCE(II.QUANTITY,1) * COALESCE(II.AMOUNT,0))) FROM > OFBIZ.INVOICE_ITEM II INNER JOIN OFBIZ.INVOICE I ON II.INVOICE_ID = > I.INVOICE_ID GROUP BY I.INVOICE_ID -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1663) POS: All payment types allow change to be made
POS: All payment types allow change to be made Key: OFBIZ-1663 URL: https://issues.apache.org/jira/browse/OFBIZ-1663 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi Priority: Minor I fat-fingered the amount of the transaction when I was testing credit card processing and was surprised to see the POS making change for a credit card transaction. I would imagine change would be allowed if and only if the amount of change is less than the amount of cash given. This would apply for both cash sales and multiple payment type sales. Does anyone have any international scenarios that would not follow this rule? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1624) Dates used in ManufacturingExampleData.xml incompatible with mysql
[ https://issues.apache.org/jira/browse/OFBIZ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1624: -- Attachment: ofbiz-1624.patch This fixes the issue. > Dates used in ManufacturingExampleData.xml incompatible with mysql > -- > > Key: OFBIZ-1624 > URL: https://issues.apache.org/jira/browse/OFBIZ-1624 > Project: OFBiz > Issue Type: Bug > Components: manufacturing >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1624.patch > > > I'll look into this tomorrow. > When I run "ant run-install" I get the following errors: > [java] 2008-02-07 21:24:56,633 (main) [EntitySaxReader.java:217:INFO > ] Beginning import from URL: > file:/home/clombard/ofbiz/trunk/applications/manufacturing/data/ManufacturingExampleData.xml > [java] 2008-02-07 21:24:56,633 (main) [EntitySaxReader.java:255:INFO > ] Transaction Timeout set to 2 hours (7200 seconds) > [java] 2008-02-07 21:24:56,642 (main) [EntitySaxReader.java:556:WARN > ] > [java] runtime exception report > -- > [java] Could not set field FixedAsset.dateAcquired to the value 2005-1-1 > 00:01:00.0 > [java] Exception: java.lang.IllegalArgumentException > [java] Message: Timestamp format must be -mm-dd hh:mm:ss[.f] > [java] stack trace > --- > [java] java.lang.IllegalArgumentException: Timestamp format must be > -mm-dd hh:mm:ss[.f] > [java] java.sql.Timestamp.valueOf(Timestamp.java:194) > [java] org.ofbiz.entity.GenericEntity.setString(GenericEntity.java:469) > [java] > org.ofbiz.entity.util.EntitySaxReader.startElement(EntitySaxReader.java:550) > [java] javolution.xml.sax.XMLReaderImpl.parseAll(Unknown Source) > [java] javolution.xml.sax.XMLReaderImpl.parse(Unknown Source) > [java] > org.ofbiz.entity.util.EntitySaxReader.parse(EntitySaxReader.java:258) > [java] > org.ofbiz.entity.util.EntitySaxReader.parse(EntitySaxReader.java:218) > [java] > org.ofbiz.entity.util.EntityDataLoader.loadData(EntityDataLoader.java:211) > [java] > org.ofbiz.entityext.data.EntityDataLoadContainer.start(EntityDataLoadContainer.java:267) > [java] > org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:79) > [java] org.ofbiz.base.start.Start.startStartLoaders(Start.java:261) > [java] org.ofbiz.base.start.Start.startServer(Start.java:310) > [java] org.ofbiz.base.start.Start.start(Start.java:314) > [java] org.ofbiz.base.start.Start.main(Start.java:397) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1627) POS payment failures should not be retried and notified by email
POS payment failures should not be retried and notified by email Key: OFBIZ-1627 URL: https://issues.apache.org/jira/browse/OFBIZ-1627 Project: OFBiz Issue Type: Bug Components: accounting Affects Versions: SVN trunk Reporter: Chris Lombardi After receiving an intentional connection error to a payment processor, I receieved the following error on the POS. "Problem connecting to payment processor; we will continue to retry and notify you by email." This is either 1) an incorrect error message or 2) a troubling process flow that needs to be corrected. I'm not sure which yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566898#action_12566898 ] Chris Lombardi commented on OFBIZ-1580: --- Yes, the height works very well. It's not impossible to hit the wrong row, but it's pretty easy to hit the right one. I'm now getting a 3/4 on target rate or better. I think my best was 20 in a row on target. Thanks JLR and thanks to the XUI team for all their work on this! > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1624) Dates used in ManufacturingExampleData.xml incompatible with mysql
Dates used in ManufacturingExampleData.xml incompatible with mysql -- Key: OFBIZ-1624 URL: https://issues.apache.org/jira/browse/OFBIZ-1624 Project: OFBiz Issue Type: Bug Components: manufacturing Affects Versions: SVN trunk Reporter: Chris Lombardi Priority: Minor I'll look into this tomorrow. When I run "ant run-install" I get the following errors: [java] 2008-02-07 21:24:56,633 (main) [EntitySaxReader.java:217:INFO ] Beginning import from URL: file:/home/clombard/ofbiz/trunk/applications/manufacturing/data/ManufacturingExampleData.xml [java] 2008-02-07 21:24:56,633 (main) [EntitySaxReader.java:255:INFO ] Transaction Timeout set to 2 hours (7200 seconds) [java] 2008-02-07 21:24:56,642 (main) [EntitySaxReader.java:556:WARN ] [java] runtime exception report -- [java] Could not set field FixedAsset.dateAcquired to the value 2005-1-1 00:01:00.0 [java] Exception: java.lang.IllegalArgumentException [java] Message: Timestamp format must be -mm-dd hh:mm:ss[.f] [java] stack trace --- [java] java.lang.IllegalArgumentException: Timestamp format must be -mm-dd hh:mm:ss[.f] [java] java.sql.Timestamp.valueOf(Timestamp.java:194) [java] org.ofbiz.entity.GenericEntity.setString(GenericEntity.java:469) [java] org.ofbiz.entity.util.EntitySaxReader.startElement(EntitySaxReader.java:550) [java] javolution.xml.sax.XMLReaderImpl.parseAll(Unknown Source) [java] javolution.xml.sax.XMLReaderImpl.parse(Unknown Source) [java] org.ofbiz.entity.util.EntitySaxReader.parse(EntitySaxReader.java:258) [java] org.ofbiz.entity.util.EntitySaxReader.parse(EntitySaxReader.java:218) [java] org.ofbiz.entity.util.EntityDataLoader.loadData(EntityDataLoader.java:211) [java] org.ofbiz.entityext.data.EntityDataLoadContainer.start(EntityDataLoadContainer.java:267) [java] org.ofbiz.base.container.ContainerLoader.start(ContainerLoader.java:79) [java] org.ofbiz.base.start.Start.startStartLoaders(Start.java:261) [java] org.ofbiz.base.start.Start.startServer(Start.java:310) [java] org.ofbiz.base.start.Start.start(Start.java:314) [java] org.ofbiz.base.start.Start.main(Start.java:397) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564112#action_12564112 ] Chris Lombardi commented on OFBIZ-1580: --- Ok, I did reproduce this issue. I caused the dialog to pop and walked away. When I came back the cpu was at 100% and I wasn't able to make the dialog go away. > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1608) Percent discount doesn't show up in Journal
[ https://issues.apache.org/jira/browse/OFBIZ-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1608: -- Attachment: screenshot-1.jpg Sales discount entered at 50%, nothing shown. > Percent discount doesn't show up in Journal > --- > > Key: OFBIZ-1608 > URL: https://issues.apache.org/jira/browse/OFBIZ-1608 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Priority: Minor > Attachments: screenshot-1.jpg > > > If a value is entered as a sales discount, the value is shown in the journal. > If a percentage is entered, neither the value nor the percentage is shown. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1608) Percent discount doesn't show up in Journal
Percent discount doesn't show up in Journal --- Key: OFBIZ-1608 URL: https://issues.apache.org/jira/browse/OFBIZ-1608 Project: OFBiz Issue Type: Bug Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi Priority: Minor If a value is entered as a sales discount, the value is shown in the journal. If a percentage is entered, neither the value nor the percentage is shown. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1606) Add numeric keypad popup function
[ https://issues.apache.org/jira/browse/OFBIZ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564090#action_12564090 ] Chris Lombardi commented on OFBIZ-1606: --- After thinking about it more, this needs to accept an initial number, for field editing. BTW, there were buttons missing from the keypad intentionally. I made the percent and minus sign configurable, to be displayed or not based on context. I haven't thought about it deeply yet, but my first thoughts are that having a minus sign available isn't ideal. It basically allows for the reversal of the intention of any function. I.e. negative discount (?), negative cash in, etc. Does anyone have any experience with registers and care to weigh in? Is the percent sign used anywhere? > Add numeric keypad popup function > - > > Key: OFBIZ-1606 > URL: https://issues.apache.org/jira/browse/OFBIZ-1606 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1606.patch > > > Some areas in the POS require a keyboard instead of a touchscreen for input. > Here is a dialog that can be used for numerical entry via a touchscreen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564062#action_12564062 ] clearchris edited comment on OFBIZ-1580 at 1/30/08 7:50 AM: JLR, I am unable to reproduce this. I'm running the SVN XUI libs, WinXP sp2 on my old 1mhz laptop. I'm also running netbeans 6.0. The dialog pops right up, "no items sold". Can you get other dialogs to pop up? was (Author: clearchris): JLR, I am unable to reproduce this. I'm running the SVN XUI libs, WinXP sp2 on my old 1mhz laptop. I'm also running netbeans 6.0. The dialog pops right up, "no items sold". > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564062#action_12564062 ] Chris Lombardi commented on OFBIZ-1580: --- JLR, I am unable to reproduce this. I'm running the SVN XUI libs, WinXP sp2 on my old 1mhz laptop. I'm also running netbeans 6.0. The dialog pops right up, "no items sold". > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1606) Add numeric keypad popup function
[ https://issues.apache.org/jira/browse/OFBIZ-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1606: -- Attachment: ofbiz-1606.patch > Add numeric keypad popup function > - > > Key: OFBIZ-1606 > URL: https://issues.apache.org/jira/browse/OFBIZ-1606 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1606.patch > > > Some areas in the POS require a keyboard instead of a touchscreen for input. > Here is a dialog that can be used for numerical entry via a touchscreen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1606) Add numeric keypad popup function
Add numeric keypad popup function - Key: OFBIZ-1606 URL: https://issues.apache.org/jira/browse/OFBIZ-1606 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: SVN trunk Reporter: Chris Lombardi Priority: Minor Some areas in the POS require a keyboard instead of a touchscreen for input. Here is a dialog that can be used for numerical entry via a touchscreen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563291#action_12563291 ] Chris Lombardi commented on OFBIZ-1580: --- Well that should have been obvious. Thanks JLR! > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563014#action_12563014 ] Chris Lombardi commented on OFBIZ-1580: --- 1. Perhaps a pop-up would work on this too... click the journal, get a panel that allows to page down, etc. I don't know. My current thinking is to use popups/panels that become visible in the appropriate context. 2. That could be interesting. About the journal styling, I think I may have fixed a defect we weren't aware of. When I change the font on the latest trunk, the font changes. When I change the font on release4.0, the font does not change. Taking an educated guess, we need to change the font path in xpos.properties from posstyles.xml to styles/postyles.xml. That said, I do like the default style better than what is currently in the posstyles.xml. > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562957#action_12562957 ] Chris Lombardi commented on OFBIZ-1580: --- The touchscreen report: I tried to do everything as if there were 5 people waiting in line. The touchscreen is an 15 inch elo 1515L hooked to a gentoo linux machine with massively over-specified CPU and RAM. From what I have seen at other establishments, 15" is pretty big for a POS. 1. The scrollbars were actually easier to target than I expected. In 10 pokes in the upper half of the scrollbar, I did add one or two items by accident though. That could be partly solved with space between the scrollbar and the buttons. (I'm not advocating for that though) 2. I tried selecting items in the journal for changing configurations. When I was in a rush, I missed and needed between 3 and 5 pokes to get it right. When I slowed down, I was off about 1 in 5 selections. When I missed, an adjacent row was selected. There may be a better method for selecting items from the journal. Suggestions anyone? 3. On the cash in/out screens... I could not use the dropdown list without doing a very careful poke with my nail. No amount of finger poking could get the dropdown to show. Strangely, under linux, the window title shows up in black on a dark blue background. In windows, it's white text on blue. I also noticed that the amount field required a keyboard to enter the amounts. I tend to agree with your assessment about having a keyboard pop-up. I have seen that done pretty well on my nokia 770. What happens is when you poke a text field the keyboard pops up. 4. On the Configure Item screen, I noticed that I can't select multiple items on a multi-select question (modem and ethernet card for pc001) as poking one item deselects the other. I'll have to see if I can change the selection model. 5. The unused part of the journal is a bright white on my touchscreen that really distracts me from the rest of the screen. This shows as a slightly pink gray on my Windows laptop which doesn't match but also doesn't distract. > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
[ https://issues.apache.org/jira/browse/OFBIZ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1581: -- Attachment: ofbiz-1581-2.patch Updated to use an page instead of a dialog, increasing the available space. This also shows the prices of the choices. The formatting is off, I need to think a bit about navigation via a touchscreen before I settle on a final method of navigation and screen layout. This patch is not intended to be committed yet. > Change ConfigureItem to use XPage instead of XDialog > > > Key: OFBIZ-1581 > URL: https://issues.apache.org/jira/browse/OFBIZ-1581 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > Attachments: ofbiz-1581-2.patch > > > I'm adding in price information to the ConfigureItem page, and was quickly > running out of space. So I'd like to change it to an XPage so I can take > advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1598) Methods in MenuEvents.java need to be synchronized (probably to do for all the events)
[ https://issues.apache.org/jira/browse/OFBIZ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1598: -- Attachment: ofbiz-1598.patch Supplemental patch to synchronize the remaining events. > Methods in MenuEvents.java need to be synchronized (probably to do for all > the events) > -- > > Key: OFBIZ-1598 > URL: https://issues.apache.org/jira/browse/OFBIZ-1598 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Attachments: MenuEvents.java.patch, ofbiz-1598.patch > > > 2008-01-25 12:04:23,421 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-7000) > 2008-01-25 12:04:23,421 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-2002) > Exception in thread "AWT-EventQueue-0" > java.lang.ArrayIndexOutOfBoundsException: 1 > at net.xoetrope.xui.data.XBaseModel.get(Unknown Source) > at net.xoetrope.swing.XSwingTableModel.getValueAt(Unknown Source) > at javax.swing.JTable.getValueAt(JTable.java:1903) > at javax.swing.JTable.prepareRenderer(JTable.java:3911) > at > javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2072) > at > javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:1974) > at javax.swing.plaf.basic.BasicTableUI.paint(BasicTableUI.java:1897) > at javax.swing.plaf.ComponentUI.update(ComponentUI.java:142) > at javax.swing.JComponent.paintComponent(JComponent.java:743) > at javax.swing.JComponent.paint(JComponent.java:1006) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at javax.swing.JViewport.paint(JViewport.java:728) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at > javax.swing.JComponent.paintWithOffscreenBuffer(JComponent.java:4972) > at javax.swing.JComponent.paintDoubleBuffered(JComponent.java:4925) > at javax.swing.JComponent._paintImmediately(JComponent.java:4868) > at javax.swing.JComponent.paintImmediately(JComponent.java:4675) > at > javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:451) > at > javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:114) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) > at > java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) > at > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-2644) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-5005) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-1001) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi reopened OFBIZ-1580: --- Did you intend to leave XuiCoreSwing_v2_0_6_jdk1_5.jar in framework/guiapp/lib? > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Fix For: SVN trunk > > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1598) Methods in MenuEvents.java need to be synchronized (probably to do for all the events)
[ https://issues.apache.org/jira/browse/OFBIZ-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562591#action_12562591 ] Chris Lombardi commented on OFBIZ-1598: --- JLR, do you have the rest of this? I knock this out quick, I just don't want to keep having our emails/patches cross in transit. :) > Methods in MenuEvents.java need to be synchronized (probably to do for all > the events) > -- > > Key: OFBIZ-1598 > URL: https://issues.apache.org/jira/browse/OFBIZ-1598 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > Attachments: MenuEvents.java.patch > > > 2008-01-25 12:04:23,421 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-7000) > 2008-01-25 12:04:23,421 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-2002) > Exception in thread "AWT-EventQueue-0" > java.lang.ArrayIndexOutOfBoundsException: 1 > at net.xoetrope.xui.data.XBaseModel.get(Unknown Source) > at net.xoetrope.swing.XSwingTableModel.getValueAt(Unknown Source) > at javax.swing.JTable.getValueAt(JTable.java:1903) > at javax.swing.JTable.prepareRenderer(JTable.java:3911) > at > javax.swing.plaf.basic.BasicTableUI.paintCell(BasicTableUI.java:2072) > at > javax.swing.plaf.basic.BasicTableUI.paintCells(BasicTableUI.java:1974) > at javax.swing.plaf.basic.BasicTableUI.paint(BasicTableUI.java:1897) > at javax.swing.plaf.ComponentUI.update(ComponentUI.java:142) > at javax.swing.JComponent.paintComponent(JComponent.java:743) > at javax.swing.JComponent.paint(JComponent.java:1006) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at javax.swing.JViewport.paint(JViewport.java:728) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at javax.swing.JComponent.paintChildren(JComponent.java:843) > at javax.swing.JComponent.paint(JComponent.java:1015) > at > javax.swing.JComponent.paintWithOffscreenBuffer(JComponent.java:4972) > at javax.swing.JComponent.paintDoubleBuffered(JComponent.java:4925) > at javax.swing.JComponent._paintImmediately(JComponent.java:4868) > at javax.swing.JComponent.paintImmediately(JComponent.java:4675) > at > javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:451) > at > javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:114) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) > at > java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242) > at > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) > at > java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-2644) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-5005) > 2008-01-25 12:04:23,546 (Thread-2163) [ Log4jLoggerWriter.java:67 :INFO ] > [POS @ pos-1 TX:10180] - is Aggregated Item(GZ-1001) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-1597) Set events to synchronized in POS
[ https://issues.apache.org/jira/browse/OFBIZ-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi closed OFBIZ-1597. - Resolution: Fixed Duplicate of OFBIZ-1598. Closing. > Set events to synchronized in POS > - > > Key: OFBIZ-1597 > URL: https://issues.apache.org/jira/browse/OFBIZ-1597 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: Release Branch 4.0 >Reporter: Chris Lombardi >Priority: Minor > > The pos allows multiple events to run at once, but it seems to cause general > sluggishness in the UI and random problems. Marking the menuevents > synchronized in ofbiz-1580 has increased performance (or at least the > responsiveness) and eliminated some issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1597) Set events to synchronized in POS
Set events to synchronized in POS - Key: OFBIZ-1597 URL: https://issues.apache.org/jira/browse/OFBIZ-1597 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: Release Branch 4.0 Reporter: Chris Lombardi Priority: Minor The pos allows multiple events to run at once, but it seems to cause general sluggishness in the UI and random problems. Marking the menuevents synchronized in ofbiz-1580 has increased performance (or at least the responsiveness) and eliminated some issues. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-6.patch I thought that issue had resolved with the new xui build, but apparently, you are a faster clicker than I or have a slower machine. I marked all the methods in MenuEvents.java to synchronized and it seems to solve the issue. We could probably stand to do that for all the events. As an added bonus, the gui seems much snappier and responsive. > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI > 3.2rc2b.PNG, xpos.properties.patch, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-6.patch Argh. I did fix the file. I guess I just can't keep myself from running a build one last time to make sure it works. I updated the patch to remove a println and I removed xpos.properties from this patch. I also updated XuiScreen to check for a change to the field being updated in xpos.properties before rewriting the whole file. ;) > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, ofbiz-1580-6.patch, POS XUI 3.2rc2b.PNG, > xpos.properties.patch, xpos.properties.patch, XuiCoreSwing-v3.2rc2b.jar, > XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.2rc2b
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-6.patch Thanks for fixing those issues. Some of the default behavior changed between the versions. I added in code to specify the behavior of the scrollbars per your commend, and remove the comments you mentioned. I have a few observations and opinions, conveniently numbered for easy rebuttal. :) 1) The grand total is also displayed above the journal, in its own box. Maybe the grand total line should be removed from the Journal. 2) IMHO, the size of the AMT should be increased to handle the proper size, based upon business. This would be easier to predict if the total was not displayed in the Journal. 3) I'm not sure of the validity of using thin scrollbars in an application ostensibly to be used on a touchscreen. I'll have to plug in my touchscreen and start poking at it. Number 3 is a particular problem for me, as it seems that navigation by finger requires a different set of widgets or navigational style than navigation by mouse. Is anyone aware of a guide to solving these issues? > XUI update to x3.2rc2b > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: framework, specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-6.patch, ofbiz-1580-6.patch, > ofbiz-1580-6.patch, POS XUI 3.2rc2b.PNG, xpos.properties.patch, > XuiCoreSwing-v3.2rc2b.jar, XuiOptional-v3.2rc2b.jar > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
[ https://issues.apache.org/jira/browse/OFBIZ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562126#action_12562126 ] Chris Lombardi commented on OFBIZ-1581: --- I have updated the code for this, but I don't know how to make a patch for it separate from ofbiz-1580 as it is dependent on and changes the same files as ofbiz-1580. > Change ConfigureItem to use XPage instead of XDialog > > > Key: OFBIZ-1581 > URL: https://issues.apache.org/jira/browse/OFBIZ-1581 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > > I'm adding in price information to the ConfigureItem page, and was quickly > running out of space. So I'd like to change it to an XPage so I can take > advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
[ https://issues.apache.org/jira/browse/OFBIZ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1581: -- Attachment: (was: ofbiz-1581.patch) > Change ConfigureItem to use XPage instead of XDialog > > > Key: OFBIZ-1581 > URL: https://issues.apache.org/jira/browse/OFBIZ-1581 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux >Priority: Minor > > I'm adding in price information to the ConfigureItem page, and was quickly > running out of space. So I'd like to change it to an XPage so I can take > advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: (was: ofbiz-1580-5.patch) > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-6.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-6.patch This fixes all issues I'm aware of. XUI 3.2 release candidate 2B is required to fix the cpu utilization issue. Comments welcome. > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-5.patch, ofbiz-1580-6.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: (was: ofbiz-1580-3.patch) > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-5.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-5.patch Fixed the windowing and journal issues. The one issue remaining is that using this patch and updated xui libs (I'm testing with xui 3.2 rc2) in the framework/guiapp/lib directory pegs the CPU of my machine, even when the application isn't being actively used. I haven't a clue what is causing the CPU usage though. I really didn't end up having to change much to upgrade the XUI libs. > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-3.patch, ofbiz-1580-5.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580-3.patch This one works mostly. I'm seeing some weird mouseover issues and the journal seems hosed. Some formatting is off too. It requires XUI 3.1, both the swingcore and optional jars. > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-3.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: (was: ofbiz-1580.patch) > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Jacques Le Roux > Attachments: ofbiz-1580-3.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
[ https://issues.apache.org/jira/browse/OFBIZ-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1581: -- Attachment: ofbiz-1581.patch Proof of concept for using XPage. Works fine for the first item, but shows a problem with the forced caching on subsequent item adds. Will clean up and resubmit after I fix the blocking issue. > Change ConfigureItem to use XPage instead of XDialog > > > Key: OFBIZ-1581 > URL: https://issues.apache.org/jira/browse/OFBIZ-1581 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Priority: Minor > Attachments: ofbiz-1581.patch > > > I'm adding in price information to the ConfigureItem page, and was quickly > running out of space. So I'd like to change it to an XPage so I can take > advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1581) Change ConfigureItem to use XPage instead of XDialog
Change ConfigureItem to use XPage instead of XDialog Key: OFBIZ-1581 URL: https://issues.apache.org/jira/browse/OFBIZ-1581 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: SVN trunk Reporter: Chris Lombardi Priority: Minor I'm adding in price information to the ConfigureItem page, and was quickly running out of space. So I'd like to change it to an XPage so I can take advantage of the extra screen space. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1580) XUI update to x3.1
[ https://issues.apache.org/jira/browse/OFBIZ-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1580: -- Attachment: ofbiz-1580.patch > XUI update to x3.1 > -- > > Key: OFBIZ-1580 > URL: https://issues.apache.org/jira/browse/OFBIZ-1580 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi > Attachments: ofbiz-1580.patch > > > I have been having problems with the limitations of the current version of > XUI. Specifically, the limitations of not being able to remove event > handlers and the forced caching of XPage objects. > It compiles, but it throws an exception at runtime. > I think it is a configuration issue, I haven't tracked it down yet, but I > thought I'd put it out here in case anyone wants to take a look. > Run the patch, then delete the following files: > rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java > rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java > I updated Journal.java, but I want to see it work before I update the other > files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1580) XUI update to x3.1
XUI update to x3.1 -- Key: OFBIZ-1580 URL: https://issues.apache.org/jira/browse/OFBIZ-1580 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: SVN trunk Reporter: Chris Lombardi I have been having problems with the limitations of the current version of XUI. Specifically, the limitations of not being able to remove event handlers and the forced caching of XPage objects. It compiles, but it throws an exception at runtime. I think it is a configuration issue, I haven't tracked it down yet, but I thought I'd put it out here in case anyone wants to take a look. Run the patch, then delete the following files: rm specialpurpose/pos/src/org/ofbiz/pos/screen/ConfigureItem.java rm specialpurpose/pos/src/org/ofbiz/pos/screen/LoadSale.java rm specialpurpose/pos/src/org/ofbiz/pos/screen/PaidInOut.java rm specialpurpose/pos/src/org/ofbiz/pos/screen/SaveSale.java rm specialpurpose/pos/src/org/ofbiz/pos/screen/SelectProduct.java I updated Journal.java, but I want to see it work before I update the other files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1562) Implement formatting for configurable items in POS receipts
[ https://issues.apache.org/jira/browse/OFBIZ-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1562: -- Attachment: ofbiz-1562.patch > Implement formatting for configurable items in POS receipts > --- > > Key: OFBIZ-1562 > URL: https://issues.apache.org/jira/browse/OFBIZ-1562 > Project: OFBiz > Issue Type: Improvement > Components: specialpurpose/pos >Affects Versions: SVN trunk >Reporter: Chris Lombardi > Fix For: SVN trunk > > Attachments: ofbiz-1562.patch > > > This patch implements better formatting for configurable items in receipts. > Also implements offset pricing for configurable items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1562) Implement formatting for configurable items in POS receipts
Implement formatting for configurable items in POS receipts --- Key: OFBIZ-1562 URL: https://issues.apache.org/jira/browse/OFBIZ-1562 Project: OFBiz Issue Type: Improvement Components: specialpurpose/pos Affects Versions: SVN trunk Reporter: Chris Lombardi Fix For: SVN trunk This patch implements better formatting for configurable items in receipts. Also implements offset pricing for configurable items. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1495: -- Attachment: ofbiz-1495.patch Updated to support offset pricing per my earlier post, with one difference. The offset is relative to the default option, not the selected option. > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1495: -- Attachment: (was: ofbiz-1495.patch) > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556171#action_12556171 ] Chris Lombardi commented on OFBIZ-1495: --- Yes, I have been watching OFBIZ-1453 with interest. I approve of the issue and implementation and didn't have anything to add, so I haven't been involved. The thing I have been thinking about is that there's some assumptions to be made here for pricing and the type of question. I.e. multiselect questions should display the absolute price. I'm also trying to work over some other scenarios. I'll clean up what I have an submit a patch tomorrow. > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554807 ] Chris Lombardi commented on OFBIZ-1495: --- Excellent writeup. I had no idea this would touch so many areas. I can add some methods to ProductConfigWrapper to help push more component logic away from the presentation layer. If I understand this properly, there are four ways to show the pricing of an aggregated item. i) Total price only ii) Default price only iii) Unattainable base price iv) True base pricing with component detail (base price shown is unattainable) v) Default price and offset component pricing (component prices are shown relative to the *selected* option) Are these the only ways we anticipate showing aggregate item pricing, or am I missing something? > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1453) store/load possibility for AGGREGATED product configurations
[ https://issues.apache.org/jira/browse/OFBIZ-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554511 ] Chris Lombardi commented on OFBIZ-1453: --- I reviewed only the latest patch, and it looks good to me. +1 > store/load possibility for AGGREGATED product configurations > > > Key: OFBIZ-1453 > URL: https://issues.apache.org/jira/browse/OFBIZ-1453 > Project: OFBiz > Issue Type: Improvement > Components: order, product >Affects Versions: SVN trunk >Reporter: Bilgin Ibryam >Priority: Minor > Fix For: SVN trunk > > Attachments: aggregated_full_for_review.patch, > aggregated_full_for_review.patch, aggregated_full_for_review.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554447 ] clearchris edited comment on OFBIZ-1495 at 12/26/07 12:44 PM: -- JLR: Actually, in the ecommerce app, it shows the total price in the shopping cart, but no components pricing. When you go to add an item, it shows the default price for the item and the offset pricing for components. When an aggregate item is displayed in a list (catalog view) it shows only the base price of the item. I'm not sure what you are proposing for where. Edit: Sorry, upon re-reading this, that sounded harsh. I didn't mean it to be. was (Author: clearchris): JLR: Actually, in the ecommerce app, it shows the total price in the shopping cart, but no components pricing. When you go to add an item, it shows the default price for the item and the offset pricing for components. When an aggregate item is displayed in a list (catalog view) it shows only the base price of the item. I'm not sure what you are proposing for where. > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554463 ] Chris Lombardi commented on OFBIZ-1495: --- Here's a tweak to ProductConfigWrapper. Does anyone have any thoughts on putting the default price logic here? I can tweak BI's patch to include the new methods if desired as the patches are complementary and not mutually exclusive. > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-1495) Aggregate items base price is displayed yet unattainable
[ https://issues.apache.org/jira/browse/OFBIZ-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lombardi updated OFBIZ-1495: -- Attachment: ofbiz-1495.patch Added code to keep the default price in the ProductConfigWrapper > Aggregate items base price is displayed yet unattainable > > > Key: OFBIZ-1495 > URL: https://issues.apache.org/jira/browse/OFBIZ-1495 > Project: OFBiz > Issue Type: Improvement > Components: order >Affects Versions: SVN trunk >Reporter: Chris Lombardi >Assignee: Bilgin Ibryam >Priority: Minor > Attachments: ofbiz-1495.patch, totalPrice.patch > > > I did some research, and I couldn't find a way to get a valid base price that > made intuitive sense. So then I went to the e-commerce store to see how it > was implemented there. > Configurable PC > PC001 Your Price: $50.00 > Hey, 50$ for a PC, I want one! So I click on the item. > Configurable PC > PC001 > Product Aggregated Price: $385.00 > What? > So, whatever is being called for the price of a "PC001" should probably > report the price of the default configuration, not the price of the > "unconfigured" product that you can't buy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
