[jira] [Assigned] (OFBIZ-4814) eCommerce Profile Back Button Fail
[
https://issues.apache.org/jira/browse/OFBIZ-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4814:
--
Assignee: Jacques Le Roux
eCommerce Profile Back Button Fail
--
Key: OFBIZ-4814
URL: https://issues.apache.org/jira/browse/OFBIZ-4814
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/ecommerce
Affects Versions: SVN trunk
Environment: demo-trunk
Reporter: Tom Burns
Assignee: Jacques Le Roux
Priority: Minor
Attachments: OFBIZ-4814 eCommerce Profile GoBack Branch.patch,
OFBIZ-4814 eCommerce Profile GoBack Trunk.patch, OFBIZ-4814 eCommerce Profile
GoBack.patch
1. Some navigation buttons reached from the eCommerce Profile screen fail to
return to the Profile screen.
Example:
Login as DemoCustomer
Click Profile
Click Update In the Contact Information Postal Address section.
Click Go Back
Expected: Return to profile page
Actual: Remain on Edit Contact Information page
2. Naming and display of back buttons is inconsistent across Profile Editing
screens.
Example:
Changes Password label should be Go Back but is [Go Back]
3. Create New Postal Address fails from OFBIZ-4801 Rev 1326397
Error message
State/Province --
Selected\Expected State Name = Expression selectedStateName is undefined on
line 163, column 42 in
component://ecommerce/webapp/ecommerce/customer/editcontactmech.ftl. The
problematic instruction: -- == ${selectedStateName} [on line 163,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4822) eCommerce Profile Improve Button Naming Consistency
[ https://issues.apache.org/jira/browse/OFBIZ-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4822: -- Assignee: Jacques Le Roux eCommerce Profile Improve Button Naming Consistency --- Key: OFBIZ-4822 URL: https://issues.apache.org/jira/browse/OFBIZ-4822 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: demo-trunk Reporter: Tom Burns Assignee: Jacques Le Roux Priority: Minor Fix For: SVN trunk This follows from OFBIZ-4814 bug fix. In eCommerce the naming and display of back buttons is inconsistent across the Profile Editing screens. Example: Changes Password label should be Go Back but is [Go Back] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4813) ajax autocomplete and dialog during session timeout
[ https://issues.apache.org/jira/browse/OFBIZ-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4813: -- Assignee: Jacques Le Roux ajax autocomplete and dialog during session timeout --- Key: OFBIZ-4813 URL: https://issues.apache.org/jira/browse/OFBIZ-4813 Project: OFBiz Issue Type: Bug Components: framework Reporter: Wai Assignee: Jacques Le Roux Attachments: ofbiz-4813.patch, ofbiz-4813.patch, ofbiz-4813.patch, spinner.gif 1. autocomplete feature shows the message no records found during a session timeout. This could be misleading for the user. 2. During a session timeout, clicking on ajax dialog button shows a large frame containing a message indicating session has timeout. Should show a more detailed message. 3. All ajax dialogs are on the left of browser window. A number of fixes have been implemented for this issue. 1. At session timeout, user enters a character into autocomplete input box results in a alert window popup. 2. At session timeout, clicking on ajax dialog button will cause alert window to popup. 3. A large round spinner is shown when the ajax dialog is loading. This spinner image comes from http://mentalized.net/activity-indicators/ and is royalty free. Note the round spinner does not show in Tomahawk theme as it uses its own spinner. 4. Now all ajax dialogs are centered. 5. Change session timeout message to something more detailed. 6. Server response to ajax request now contain html tags. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4793) unify admin port and key setting: single point of definition in start.properties
[ https://issues.apache.org/jira/browse/OFBIZ-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4793: -- Assignee: Jacques Le Roux unify admin port and key setting: single point of definition in start.properties Key: OFBIZ-4793 URL: https://issues.apache.org/jira/browse/OFBIZ-4793 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Environment: WXP SP3 Sun SDK 1.6.0_30 Reporter: Francis ANDRE Assignee: Jacques Le Roux Priority: Minor Attachments: ofbiz-admin-port.patch Hi If someone wants to change the admin password or port, he would have to change currently many files (-- build.xml, various .bat and .sh --). In order to avoid this error-prone pratice, I suggest to centralize the definition of the admin kay and port at 2 single points: the framework/start/src/org/ofbiz/base/start/start.properties and the framework/start/src/org/ofbiz/base/start/jetty.properties Rgds -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4797) eCommerce Edit Contact Information use Dependent drop-downs
[ https://issues.apache.org/jira/browse/OFBIZ-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4797: -- Assignee: Jacques Le Roux eCommerce Edit Contact Information use Dependent drop-downs --- Key: OFBIZ-4797 URL: https://issues.apache.org/jira/browse/OFBIZ-4797 Project: OFBiz Issue Type: Improvement Components: specialpurpose/ecommerce Affects Versions: SVN trunk Environment: demo-trunk Reporter: Tom Burns Assignee: Jacques Le Roux Priority: Minor Using Dependent drop-downs to filter the State drop down based on the selection in the Country drop-down will improve the usability of the component. Current Behavior: 1. Open eCommerce application 2. Log in as user with Postal Address say Demo Customer 3. In the menu bar select Profile 4. In Contact Information Postal Address select update. 5. The Country drop-down value is United States and the State/Province drop-down list displays all geo values. After improvement: 5. The Country drop-down value is United States and the State/Province drop-down list is limited to States in the United States. 6. Changing the value in the Country drop-down will update State/Province drop-down list with values for the selected country. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4798) Facility Edit Contact Information use Dependent drop-downs
[ https://issues.apache.org/jira/browse/OFBIZ-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4798: -- Assignee: Jacques Le Roux Facility Edit Contact Information use Dependent drop-downs -- Key: OFBIZ-4798 URL: https://issues.apache.org/jira/browse/OFBIZ-4798 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Environment: demo-trunk Reporter: Tom Burns Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-4798 Facility Contact Mech.patch Using Dependent drop-downs to filter the State drop down based on the selection in the Country drop-down will improve the usability of the component. Current Behavior: 1. Open eCommerce application 2. Log in as user with Postal Address say Demo Customer 3. In the menu bar select Profile 4. In Contact Information Postal Address select update. 5. The Country drop-down value is United States and the State/Province drop-down list displays all geo values. After improvement: 5. The Country drop-down value is United States and the State/Province drop-down list is limited to States in the United States. 6. Changing the value in the Country drop-down will update State/Province drop-down list with values for the selected country. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4792) Add a yui-compressor-ant-task
[ https://issues.apache.org/jira/browse/OFBIZ-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4792: -- Assignee: Jacques Le Roux Add a yui-compressor-ant-task - Key: OFBIZ-4792 URL: https://issues.apache.org/jira/browse/OFBIZ-4792 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Environment: Windows/Linux Reporter: Mandeep Sidhu Assignee: Jacques Le Roux Priority: Trivial Labels: build, compression, css, features, javascript Fix For: SVN trunk The idea is to create an ant task which uses [YUICompressor|http://developer.yahoo.com/yui/compressor/] to dynamically minify our own (or custom for users) js and css files (most of the bigest external ones are already compressed) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4588) Use flexibleStringRenderer for alt-target element on form
[ https://issues.apache.org/jira/browse/OFBIZ-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4588: -- Assignee: Jacques Le Roux Use flexibleStringRenderer for alt-target element on form - Key: OFBIZ-4588 URL: https://issues.apache.org/jira/browse/OFBIZ-4588 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Screen Widget Redesign, SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Priority: Minor Labels: form, renderer, widget Fix For: SVN trunk Attachments: JIRA-4588, OFBIZ-4588.patch At this time the alt-target element value is only parse on bsh interpreter. To resynchronise with the rest of framework, I propose to convert with a flexibleStringRenderer. Maybe remove bsh interpretor to use UEL and script call system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4472) New element auto-parameters-entity for link/hyperlink
[
https://issues.apache.org/jira/browse/OFBIZ-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4472:
--
Assignee: (was: Jacques Le Roux)
New element auto-parameters-entity for link/hyperlink
-
Key: OFBIZ-4472
URL: https://issues.apache.org/jira/browse/OFBIZ-4472
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: Screen Widget Redesign, SVN trunk
Reporter: Nicolas Malin
Priority: Minor
Attachments: OFBIZ-4472.patch, OFBIZ-4472.patch, OFBIZ-4472.patch
When you want edit/remove an entity from link call it's needed to give all pk
on parameter element as like :
{quote} field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
parameter param-name=exampleId/
parameter param-name=exampleFeatureId/
parameter param-name=fromDate/
hyperlink/
/field
{quote}
To simplify, I introduce auto-parameters-entity like this :
{quote}
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity entity-name=ExampleFeatureAppl/
hyperlink/
/field
{quote}
or
{quote}
form name=ListExampleFeatureAppls type=list
default-entity-name=ExampleFeatureAppl
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity/
hyperlink/
/field
{quote}
This method is inspired from auto-fields-entity and I homogenized on widget
renderer screen (link), menu (link) and form (hyperlink, sub-link)
Any comments are welcome
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4467) Improve auto-fields-entity (select include field and auto drop-down)
[ https://issues.apache.org/jira/browse/OFBIZ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4467: -- Assignee: (was: Jacques Le Roux) Improve auto-fields-entity (select include field and auto drop-down) Key: OFBIZ-4467 URL: https://issues.apache.org/jira/browse/OFBIZ-4467 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Screen Widget Redesign, SVN trunk Reporter: Nicolas Malin Priority: Minor Attachments: OFBIZ-4467-example.patch, OFBIZ-4467.patch, OFBIZ-4467.patch, OFBIZ-4467.png Hi Here are two improvments to complete the element 'auto-fields-entity' of forms. The first one consists in adding one fields allowing to select which fields are include in the form (same way as what is made on the definitions of service): For example: auto-fields-entity entity-name=Example include=pk default-field-type=display/ = To display only the primary key fields of the Example entity auto-fields-entity entity-name=Example include=nonpk default-field-type=edit = To display only the non primary key fields of the Example entity exclude field-name=longDescription/ = To exclude one precise fields of an entity The second one consists in including for fields with relation a drop-down or a display entity according to EntityType Any comments are welcome -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4780) Auto-completer request should be async.
[ https://issues.apache.org/jira/browse/OFBIZ-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4780: -- Assignee: Jacques Le Roux Auto-completer request should be async. --- Key: OFBIZ-4780 URL: https://issues.apache.org/jira/browse/OFBIZ-4780 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 11.04, SVN trunk Reporter: Deepak Dixit Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 11.04, SVN trunk Attachments: OFBIZ-4780.patch Currently auto-completer uses sync call to prepare auto-completer source (result list). Due to this user can't perform any other operation on lookup field and user should have to wait until response came. In general, synchronous requests should never be used because they tend to block the execution of anything else on the page (or even the entire browser UI), which isn't good. Also ajax-loader image not display on google chrome browser due to sync request. Need to use async request for auto-completer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4472) New element auto-parameters-entity for link/hyperlink
[
https://issues.apache.org/jira/browse/OFBIZ-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4472:
--
Assignee: Jacques Le Roux
New element auto-parameters-entity for link/hyperlink
-
Key: OFBIZ-4472
URL: https://issues.apache.org/jira/browse/OFBIZ-4472
Project: OFBiz
Issue Type: New Feature
Components: framework
Affects Versions: Screen Widget Redesign, SVN trunk
Reporter: Nicolas Malin
Assignee: Jacques Le Roux
Priority: Minor
Attachments: OFBIZ-4472.patch, OFBIZ-4472.patch, OFBIZ-4472.patch
When you want edit/remove an entity from link call it's needed to give all pk
on parameter element as like :
{quote} field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
parameter param-name=exampleId/
parameter param-name=exampleFeatureId/
parameter param-name=fromDate/
hyperlink/
/field
{quote}
To simplify, I introduce auto-parameters-entity like this :
{quote}
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity entity-name=ExampleFeatureAppl/
hyperlink/
/field
{quote}
or
{quote}
form name=ListExampleFeatureAppls type=list
default-entity-name=ExampleFeatureAppl
field name=deleteLink
hyperlink target=example_deleteExampleFeatureAppl
auto-parameters-entity/
hyperlink/
/field
{quote}
This method is inspired from auto-fields-entity and I homogenized on widget
renderer screen (link), menu (link) and form (hyperlink, sub-link)
Any comments are welcome
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4467) Improve auto-fields-entity (select include field and auto drop-down)
[ https://issues.apache.org/jira/browse/OFBIZ-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4467: -- Assignee: Jacques Le Roux Improve auto-fields-entity (select include field and auto drop-down) Key: OFBIZ-4467 URL: https://issues.apache.org/jira/browse/OFBIZ-4467 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Screen Widget Redesign, SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-4467-example.patch, OFBIZ-4467.patch, OFBIZ-4467.patch, OFBIZ-4467.png Hi Here are two improvments to complete the element 'auto-fields-entity' of forms. The first one consists in adding one fields allowing to select which fields are include in the form (same way as what is made on the definitions of service): For example: auto-fields-entity entity-name=Example include=pk default-field-type=display/ = To display only the primary key fields of the Example entity auto-fields-entity entity-name=Example include=nonpk default-field-type=edit = To display only the non primary key fields of the Example entity exclude field-name=longDescription/ = To exclude one precise fields of an entity The second one consists in including for fields with relation a drop-down or a display entity according to EntityType Any comments are welcome -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4427) Possible runtime errors with UtilValidate.isEmpty(Object) should be rather caught during compilation
[ https://issues.apache.org/jira/browse/OFBIZ-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4427: -- Assignee: Jacques Le Roux Possible runtime errors with UtilValidate.isEmpty(Object) should be rather caught during compilation Key: OFBIZ-4427 URL: https://issues.apache.org/jira/browse/OFBIZ-4427 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Minor Labels: UtilValidate.isEmpty Fix For: SVN trunk Attachments: OFBIZ-4427.patch, OFBIZ-4427_isEmpty.patch Hence we need tp remove the UtilValidate.isEmpty(Object) method and provide methods that accept explicit types. Scripting languages should use a facade class that provides methods for working with generic Objects or providing default behaviors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4733) Xml Deserializer does not support BigDecimal
[
https://issues.apache.org/jira/browse/OFBIZ-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4733:
--
Assignee: Jacques Le Roux
Xml Deserializer does not support BigDecimal
Key: OFBIZ-4733
URL: https://issues.apache.org/jira/browse/OFBIZ-4733
Project: OFBiz
Issue Type: Bug
Components: framework
Affects Versions: SVN trunk
Reporter: Alexander Reelsen
Assignee: Jacques Le Roux
In the last weeks the XML Serializer in trunk was extended to support
BigDecimal. Unfortunately deserializing is not supported, which leads to
services being broken when running via async as their are persisted in
runtime_data... like sending mails, when a bigdecimal is involved
Patch is:
--- a/framework/entity/src/org/ofbiz/entity/serialize/XmlSerializer.java
Fri Mar 16 16:32:16 2012 +0100
+++ b/framework/entity/src/org/ofbiz/entity/serialize/XmlSerializer.java
Mon Mar 19 09:08:17 2012 +0100
@@ -300,6 +300,9 @@
} else if (std-Integer.equals(tagName)) {
String valStr = element.getAttribute(value);
return Integer.valueOf(valStr);
+} else if (std-BigDecimal.equals(tagName)) {
+String valStr = element.getAttribute(value);
+return new BigDecimal(valStr);
} else if (std-Long.equals(tagName)) {
String valStr = element.getAttribute(value);
return Long.valueOf(valStr);
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4660) OrderListState need to be Serializable for clustering
[ https://issues.apache.org/jira/browse/OFBIZ-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4660: -- Assignee: Jacques Le Roux OrderListState need to be Serializable for clustering - Key: OFBIZ-4660 URL: https://issues.apache.org/jira/browse/OFBIZ-4660 Project: OFBiz Issue Type: Bug Components: order Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Assignee: Jacques Le Roux Priority: Critical Labels: clustering, order_list_state Attachments: order_list_state.patch, order_list_state.patch OrderListState is to be set to session, so it needs to be Serializable for clustering. I got this error: cause - Exception: java.lang.IllegalArgumentException Message: setAttribute: Non-serializable attribute __ORDER_LIST_STATUS__ stack trace --- java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute __ORDER_LIST_STATUS__ org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1456) org.apache.catalina.ha.session.DeltaSession.setAttribute(DeltaSession.java:658) org.apache.catalina.ha.session.DeltaSession.setAttribute(DeltaSession.java:642) org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:156) org.ofbiz.order.order.OrderListState.getInstance(OrderListState.java:137) 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.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:88) org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite$StaticMetaMethodSiteNoUnwrapNoCoerce.invoke(StaticMetaMethodSite.java:148) org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.call(StaticMetaMethodSite.java:88) org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:124) OrderList.run(OrderList.groovy:29) Regards, Chatree Srichart -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4689) Keywords list is missing in Catalog
[ https://issues.apache.org/jira/browse/OFBIZ-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4689: -- Assignee: Jacques Le Roux Keywords list is missing in Catalog Key: OFBIZ-4689 URL: https://issues.apache.org/jira/browse/OFBIZ-4689 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Release 10.04 Reporter: Ankit Jain Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 10.04 Attachments: OFBIZ-4689.patch In the catalog when you select Keywords tab the keyword list is not showing https://localhost:8443/catalog/control/EditProductKeyword?productId=GZ-1004 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4690) If Picklist is Cancelled than all the PicklistItem related to that PicklistId should also get Cancel.
[ https://issues.apache.org/jira/browse/OFBIZ-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4690: -- Assignee: Jacques Le Roux If Picklist is Cancelled than all the PicklistItem related to that PicklistId should also get Cancel. -- Key: OFBIZ-4690 URL: https://issues.apache.org/jira/browse/OFBIZ-4690 Project: OFBiz Issue Type: Improvement Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Ankit Jain Assignee: Jacques Le Roux Priority: Minor Fix For: Release Branch 10.04, Release Branch 11.04, SVN trunk Attachments: OFBIZ-4690.patch If Picklist is Cancelled than all the PicklistItem related to that PicklistId should also get Cancel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4667) At the time of page load unnecessary ajax request executed to get the lookup description.
[ https://issues.apache.org/jira/browse/OFBIZ-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4667: -- Assignee: Erwan de FERRIERES (was: Jacques Le Roux) Sure please do Erwan, Thanks At the time of page load unnecessary ajax request executed to get the lookup description. - Key: OFBIZ-4667 URL: https://issues.apache.org/jira/browse/OFBIZ-4667 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 11.04, SVN trunk Reporter: Amardeep Singh Jhajj Assignee: Erwan de FERRIERES Fix For: Release Branch 11.04, SVN trunk Attachments: OFBIZ-4667-R11.04.patch, OFBIZ-4667.patch At the time of page load unnecessary ajax request executed to get the lookup description if there is no value exists in lookup box, this increases unnecessary load and page take more time to load. This should be executed only when lookup field has some value. One more issue exists in lookup/ajax auto completer, when we select any auto-completer options from the drop down list or select any value from the lookup then request executed twice to get the description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4675) Incorrect fix applied in OFBIZ-4381
[ https://issues.apache.org/jira/browse/OFBIZ-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4675: -- Assignee: Jacques Le Roux Incorrect fix applied in OFBIZ-4381 --- Key: OFBIZ-4675 URL: https://issues.apache.org/jira/browse/OFBIZ-4675 Project: OFBiz Issue Type: Bug Components: commonext/setup Affects Versions: Release 10.04, Release Branch 11.04, SVN trunk Reporter: Anne Jessel Assignee: Jacques Le Roux Original Estimate: 10m Remaining Estimate: 10m The fix applied in OFBIZ-4381 was to copy DemoShipping.xml from the ecommerce component (where it is loaded as DEMO data), and add it to commonext component as SEED data. IMO this data should not be part of SEED data, as not all users will use this data. Also, the file should not be duplicated. I suggest reverting trunk r1167510, R11.04 r1167513, R10.04 r1167514. I suspect the correct fix for OFBIZ-4381 is either for the user to load the demo data, or to configure the carriers before trying to create a ProductStore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4667) At the time of page load unnecessary ajax request executed to get the lookup description.
[ https://issues.apache.org/jira/browse/OFBIZ-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4667: -- Assignee: Jacques Le Roux At the time of page load unnecessary ajax request executed to get the lookup description. - Key: OFBIZ-4667 URL: https://issues.apache.org/jira/browse/OFBIZ-4667 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 11.04, SVN trunk Reporter: Amardeep Singh Jhajj Assignee: Jacques Le Roux Fix For: Release Branch 11.04, SVN trunk Attachments: OFBIZ-4667-R11.04.patch, OFBIZ-4667.patch At the time of page load unnecessary ajax request executed to get the lookup description if there is no value exists in lookup box, this increases unnecessary load and page take more time to load. This should be executed only when lookup field has some value. One more issue exists in lookup/ajax auto completer, when we select any auto-completer options from the drop down list or select any value from the lookup then request executed twice to get the description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4580) Categories - calculated trails
[
https://issues.apache.org/jira/browse/OFBIZ-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4580:
--
Assignee: Jacques Le Roux
Categories - calculated trails
--
Key: OFBIZ-4580
URL: https://issues.apache.org/jira/browse/OFBIZ-4580
Project: OFBiz
Issue Type: Improvement
Reporter: Paul Piper
Assignee: Jacques Le Roux
Priority: Minor
Attachments: CategoryWorker-with-trail-export.patch
Hey folks,
been a while since I contributed. I noticed that currently ofbiz misses a
simple function to generate a category trail. Generating a trail, however, is
often useful when generating breadcrums, facetted search results, and proper
category trees in general. Hence I created the following as a timesaver:
{code:title=getCategoryTrail|borderStyle=solid}
public static List getCategoryTrail(String productCategoryId,DispatchContext
dctx){
GenericDelegator delegator = (GenericDelegator)
dctx.getDelegator();
ListString trailElements = FastList.newInstance();
trailElements.add(productCategoryId);
String parentProductCategoryId = productCategoryId;
while (UtilValidate.isNotEmpty(parentProductCategoryId)) {
// find product category rollup
try {
ListEntityCondition rolllupConds = FastList.newInstance();
rolllupConds.add(EntityCondition.makeCondition(productCategoryId,
parentProductCategoryId));
rolllupConds.add(EntityUtil.getFilterByDateExpr());
ListGenericValue productCategoryRollups =
delegator.findList(ProductCategoryRollup,
EntityCondition.makeCondition(rolllupConds), null,
UtilMisc.toList(-fromDate), null, true);
if (UtilValidate.isNotEmpty(productCategoryRollups)) {
// add only categories that belong to the top category to
trail
for (GenericValue productCategoryRollup :
productCategoryRollups) {
String trailCategoryId =
productCategoryRollup.getString(parentProductCategoryId);
parentProductCategoryId = trailCategoryId;
if (trailElements.contains(trailCategoryId)) {
break;
}else{
trailElements.add(trailCategoryId);
}
}
} else {
parentProductCategoryId = null;
}
} catch (GenericEntityException e) {
Debug.logError(e, Cannot generate trail from product
category, module);
}
}
Collections.reverse(trailElements);
return trailElements;
}
{code}
I suggest to add this to the CategoryWorker.java
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4663) ERROR in log file when starting OFBiz, debug-xa-resources is commented in entityengine.xml
[
https://issues.apache.org/jira/browse/OFBIZ-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4663:
--
Assignee: Jacques Le Roux
ERROR in log file when starting OFBiz, debug-xa-resources is commented in
entityengine.xml
--
Key: OFBIZ-4663
URL: https://issues.apache.org/jira/browse/OFBIZ-4663
Project: OFBiz
Issue Type: Sub-task
Components: framework
Affects Versions: SVN trunk
Reporter: Erwan de FERRIERES
Assignee: Jacques Le Roux
Fix For: SVN trunk
3229 [main] INFO org.ofbiz.base.container.ClassLoaderContainer -
CachedClassLoader created
3466 [main] INFO org.ofbiz.entity.DelegatorFactoryImpl - Creating new
delegator [default] (main)
3530 [main] ERROR org.ofbiz.base.util.UtilXml - XmlFileLoader: File
file:/home/erwan/workspace/Apache_OFBiz/ofbiz/framework/entity/config/entityengine.xml
process error. Line: 53. Error message: cvc-complex-type.2.4.a: Invalid
content was found starting with element 'delegator'. One of
'{debug-xa-resources}' is expected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4661) Autocomplete / Suggest does not work with umlauts
[ https://issues.apache.org/jira/browse/OFBIZ-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4661: -- Assignee: Jacques Le Roux Autocomplete / Suggest does not work with umlauts - Key: OFBIZ-4661 URL: https://issues.apache.org/jira/browse/OFBIZ-4661 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Christoph Neuroth Assignee: Jacques Le Roux Attachments: ofbiz-4661.patch Steps to Reproduce: * Change the internal_name of a product to Kochlöffel (that's German for cooking spoon. Just in case you ever need one while in a German-speaking country and don't have a dictionary handy). * Go to the catalog and use the product search box to the left to search for Koch, you should see the product as a suggestion * Clear the input field and search for löffel instead - the product is not found. The reason for this is that the special characters have to be url encoded for the GET request, but are never decoded. Easiest way to fix this is just to use a POST request instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-3189) Popup is not displayed on product page for order entry.
[ https://issues.apache.org/jira/browse/OFBIZ-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-3189: -- Assignee: Erwan de FERRIERES I confirm, thanks Erwan! Popup is not displayed on product page for order entry. --- Key: OFBIZ-3189 URL: https://issues.apache.org/jira/browse/OFBIZ-3189 Project: OFBiz Issue Type: Sub-task Components: order Affects Versions: SVN trunk Reporter: Jacques Le Roux Assignee: Erwan de FERRIERES Priority: Trivial See OFBIZ-3188 for more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4629) The Status of PicklistItem never changes from PICKITEM_PENDING to PICKITEM_COMPLETED.
[ https://issues.apache.org/jira/browse/OFBIZ-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4629: -- Assignee: Jacques Le Roux The Status of PicklistItem never changes from PICKITEM_PENDING to PICKITEM_COMPLETED. - Key: OFBIZ-4629 URL: https://issues.apache.org/jira/browse/OFBIZ-4629 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Release 10.04, SVN trunk Reporter: Ankit Jain Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-4629.patch, Updated-Ofbiz-4629.patch Whenever a order is verified picked the status of Picklistitem never changes to PICKITEM_COMPLETED, even if the order is completed the status always remain as PICKITEM_PENDING. I think when a PiclistItem is verified the status should change to PICKITEM_COMPLETED. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4657) ArrayIndexOutOfBoundsException in OrderServices.xml:updateOrderItemShipGroup
[
https://issues.apache.org/jira/browse/OFBIZ-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4657:
--
Assignee: Jacques Le Roux
ArrayIndexOutOfBoundsException in OrderServices.xml:updateOrderItemShipGroup
Key: OFBIZ-4657
URL: https://issues.apache.org/jira/browse/OFBIZ-4657
Project: OFBiz
Issue Type: Bug
Components: order
Affects Versions: SVN trunk
Reporter: Alexander Reelsen
Assignee: Jacques Le Roux
When changing the billing or shipping address of a sales order in the
ordermgr, a bsh exception is logged - with absolutely no trace where it is
coming from. And the change of the adress is successful as well.
The exception occurs here in OrderServices.xml in updateOrderItemShipGroup()
in the BSH script
call-bsh![CDATA[
shipmentMethod = parameters.get(shipmentMethod);
if (shipmentMethod != null) {
arr = shipmentMethod.split( @ );
parameters.put(shipmentMethodTypeId, arr[0]);
parameters.put(carrierPartyId, arr[1]);
parameters.put(carrierRoleTypeId, arr[2]);
}
]]/call-bsh
Splitting for not existing chars and assuming the array was split
successfully leads to the exception. The fix could work liks this, but as I
do not have a clue at all, why it is split by the at-sign anyway I dont know
if this fix does what it should. For us it does, because we do not care for
sales order ship groups.
call-bsh![CDATA[
shipmentMethod = parameters.get(shipmentMethod);
if (shipmentMethod != null) {
arr = shipmentMethod.split( @ );
if (arr.length = 3) {
parameters.put(shipmentMethodTypeId, arr[0]);
parameters.put(carrierPartyId, arr[1]);
parameters.put(carrierRoleTypeId, arr[2]);
}
}
]]/call-bsh
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4098) Ability to plug a new Cache Implementation
[ https://issues.apache.org/jira/browse/OFBIZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4098: -- Assignee: Jacques Le Roux Ability to plug a new Cache Implementation -- Key: OFBIZ-4098 URL: https://issues.apache.org/jira/browse/OFBIZ-4098 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Philippe Mouawad Assignee: Jacques Le Roux Attachments: ofbiz-4098.patch Original Estimate: 96h Remaining Estimate: 96h Hello, I would like to contribute a patch to enable switching from Ofbiz native Cache (today UtilCache) to another implementation like EhCache for example. To avoid big code impacts, UtilCache would stay the same and delegate to the real cache implementation this will impact less classes and big impacts would stay in UtilCache package. Ability to plug another implementation like EhCache for example would enable easily plugin with Terracota for example which on big Web Site gives much performance enhancements. Is the format to contribute this kind of evolution also a patch ? Thank you Regards Philippe http://www.ubik-ingenierie.com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4637) Can not create drop shipment order
[ https://issues.apache.org/jira/browse/OFBIZ-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4637: -- Assignee: Jacques Le Roux Can not create drop shipment order -- Key: OFBIZ-4637 URL: https://issues.apache.org/jira/browse/OFBIZ-4637 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Release Branch 11.04, SVN trunk Environment: My OFBiz 11.04 is updated on 26.12.2011 Reporter: Sergei Biletnikov Assignee: Jacques Le Roux Attachments: stacktrace.txt I have a problem when I create a drop shipment order via OFBiz order management component. How to reproduce: Choose the demo customer, add dropShip1 item, finalize order by specifying shipment method, payment type and ship address, click Create Order and you will see: ERROR: Could not create order (problem invoking the service: Could not commit transaction for service [checkCreateDropShipPurchaseOrders] call: Roll back error, could not commit transaction, was rolled back instead because of: Service [addSuggestionsToShoppingList] threw an unexpected exception/errorjava.lang.IllegalStateException: This object has been flagged as immutable (unchangeable), probably because it came from an Entity Engine cache. Cannot set a value in an immutable entity object. (This object has been flagged as immutable (unchangeable), probably because it came from an Entity Engine cache. Cannot set a value in an immutable entity object.)) The full stack trace can be found in the attachment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4601) Entity synchronization is skipping values to create, store and remove
[ https://issues.apache.org/jira/browse/OFBIZ-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4601: -- Assignee: Jacques Le Roux Entity synchronization is skipping values to create, store and remove - Key: OFBIZ-4601 URL: https://issues.apache.org/jira/browse/OFBIZ-4601 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 4.0, Release 09.04, Release 10.04, SVN trunk Reporter: Patrick Antivackis Assignee: Jacques Le Roux Attachments: patch-OFBIZ-4601.txt assembleValuesTocreate, assembleValuesToStore and assembleKeysToRemove are called multiple times during a synchronization (depending on the syncSplitMillis and the time period to synchronized). There is in theses methods a check to see if at the next call, the method need to look for values. This check depends only on entity without values at the current run, which is not enough -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4602) Null values are not synchronized in http mode
[ https://issues.apache.org/jira/browse/OFBIZ-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4602: -- Assignee: Jacques Le Roux Null values are not synchronized in http mode - Key: OFBIZ-4602 URL: https://issues.apache.org/jira/browse/OFBIZ-4602 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release 4.0, Release 09.04, Release 09.04.01, Release 10.04, SVN trunk Environment: Using entity synchronization over HTTP (not RMI) Reporter: Patrick Antivackis Assignee: Jacques Le Roux Attachments: patch-OFBIZ-4602.txt In order to send over http the values to create, store and remove, Ofbiz is Xml serializing the values. GenericValue xml serialization is managed in GenericEntity.makeXmlElement, unfortunately this method just don't serialized null valued fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4627) contribute Ofbiz Vietnamese tranlasting to community from HaNoi
[ https://issues.apache.org/jira/browse/OFBIZ-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4627: -- Assignee: Jacques Le Roux contribute Ofbiz Vietnamese tranlasting to community from HaNoi --- Key: OFBIZ-4627 URL: https://issues.apache.org/jira/browse/OFBIZ-4627 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Affects Versions: SVN trunk Reporter: Tri Duc Vo Assignee: Jacques Le Roux Labels: features Fix For: SVN trunk Attachments: EcommerceUiLabels.xml, ProductUiLabels.xml Original Estimate: 1,344h Remaining Estimate: 1,344h Dear Ofbiz community I'm Tri, from HaNoi, VietNam, and now our team build ERP based on Ofbiz opensource. Now we're completed translating 80% Ecommerce , 50% Catalog of Ofbiz. And we're going to complete 100% Vietnamese Ofbiz tranlasting and contribute them to community. We'll attach files soon Thank you -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4620) fail uploading audio/video files to database
[ https://issues.apache.org/jira/browse/OFBIZ-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4620: -- Assignee: Jacques Le Roux fail uploading audio/video files to database Key: OFBIZ-4620 URL: https://issues.apache.org/jira/browse/OFBIZ-4620 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Wai Assignee: Jacques Le Roux Attachments: OFBIZ-4620.patch When uploading binary files (eg. image/audio/video) to the database, ofbiz throws a type casting exception because it is trying to type cast HeapByteBuffer to byte[]. I think the problem stems from configuring ofbiz to use java.nio.ByteBuffer and its subclass java.nio.HeapByteBuffer to contain uploaded binary data but no accommodation is made in the code to work with this type of object. To test this, you need to set content.properties/content.upload.always.local.file=false use https://http://demo-trunk.ofbiz.apache.org/partymgr/control/viewprofile?partyId=Company and upload an image file. java.nio.HeapByteBuffer comes from java's rt.jar (make sure your classpath includes this) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-3313) Mountpoint for the ofbiz website
[ https://issues.apache.org/jira/browse/OFBIZ-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-3313: -- Assignee: (was: Jacques Le Roux) Mountpoint for the ofbiz website Key: OFBIZ-3313 URL: https://issues.apache.org/jira/browse/OFBIZ-3313 Project: OFBiz Issue Type: Bug Affects Versions: SVN trunk Reporter: Erwan de FERRIERES Fix For: SVN trunk Attachments: OFBIZ-3313.diff following Hans' commit for OFBiz website at the root of the webapp, images/css/etc... are not displayed. The component mountpoint is /, but should be /ofbiz The patch is correcting this. The website is then reachable at this address : http://localhost:8080/ofbiz/control/main -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4592) Try to see if we can integrate Commons-dbcp-jmx tool to monitor DBCP connections with JMX+JConsole
[ https://issues.apache.org/jira/browse/OFBIZ-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4592: -- Assignee: Jacques Le Roux Try to see if we can integrate Commons-dbcp-jmx tool to monitor DBCP connections with JMX+JConsole -- Key: OFBIZ-4592 URL: https://issues.apache.org/jira/browse/OFBIZ-4592 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Trivial Labels: DBCP, JConsole, JMX, monitor See [Mbean wrappers around Apache Commons DBCP datasources.|https://github.com/nicoulaj/commons-dbcp-jmx#readme] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4501) Incorrect use of eca for create/updateShipment
[ https://issues.apache.org/jira/browse/OFBIZ-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4501: -- Assignee: Jacques Le Roux Incorrect use of eca for create/updateShipment -- Key: OFBIZ-4501 URL: https://issues.apache.org/jira/browse/OFBIZ-4501 Project: OFBiz Issue Type: Bug Components: product Affects Versions: Release Branch 11.04, SVN trunk Reporter: Kiran Gawde Assignee: Jacques Le Roux Attachments: OFBIZ-4501-ModifiedCreateUpdateShipmentService.patch, OFBIZ-4501-ModifiedCreateUpdateShipmentService.patch, OFBIZ-4501-ShipmentServiceXml.patch, OFBIZ-4501-ShipmentServiceXml.patch, OFBIZ-4501-ShipmentServiceXml.patch createShipment service doesn't populate the facility and order info into shipment. Instead it is handled by eca rules. This is wrong. ECA rules should be used to update other objects or cause other actions and not update the object that is being committed. This makes it difficult to traverse the code. Can also cause bugs that are difficult troubleshoot. e.g: In this case, facilities are populated in shipment by method setShipmentSettingsFromPrimaryOrder, but eca rule checking for originFacilityId gets executed before it is populated. Following eca rules should be removed and instead the code should be added to create/updateshipment methods. !-- if new originFacilityId or destinationFacilityId, get settings from facilities -- eca service=createShipment event=commit condition field-name=originFacilityId operator=is-not-empty/ action service=setShipmentSettingsFromFacilities mode=sync/ /eca eca service=createShipment event=commit condition field-name=destinationFacilityId operator=is-not-empty/ action service=setShipmentSettingsFromFacilities mode=sync/ /eca eca service=updateShipment event=commit condition-field field-name=originFacilityId operator=not-equals to-field-name=oldOriginFacilityId/ condition field-name=originFacilityId operator=is-not-empty/ action service=setShipmentSettingsFromFacilities mode=sync/ /eca eca service=updateShipment event=commit condition-field field-name=destinationFacilityId operator=not-equals to-field-name=oldDestinationFacilityId/ condition field-name=destinationFacilityId operator=is-not-empty/ action service=setShipmentSettingsFromFacilities mode=sync/ /eca !-- if new primaryOrderId, get settings from order -- eca service=createShipment event=commit condition field-name=primaryOrderId operator=is-not-empty/ action service=setShipmentSettingsFromPrimaryOrder mode=sync/ /eca eca service=updateShipment event=commit condition-field field-name=primaryOrderId operator=not-equals to-field-name=oldPrimaryOrderId/ condition field-name=primaryOrderId operator=is-not-empty/ action service=setShipmentSettingsFromPrimaryOrder mode=sync/ /eca -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4555) add datetimepicker language file for zh-CN, zh-HK, zh-TW, and an en one in order to avoid jquery-ui-timepicker-en.js not found error
[ https://issues.apache.org/jira/browse/OFBIZ-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4555: -- Assignee: Jacques Le Roux add datetimepicker language file for zh-CN, zh-HK, zh-TW, and an en one in order to avoid jquery-ui-timepicker-en.js not found error -- Key: OFBIZ-4555 URL: https://issues.apache.org/jira/browse/OFBIZ-4555 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: SVN trunk Reporter: Leon Assignee: Jacques Le Roux Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-4555_DI.patch 1. add datetimepicker language file to system: jquery-ui-timepicker-zh-CN.js, jquery-ui-timepicker-zh-HK.js and jquery-ui-timepicker-zh-TW.js. 2. also add a jquery-ui-timepicker-en.js file, it's the default datetimepicker language file but not exist now. 3. run service createJsLanguageFileMapping to update sLanguageFileMapping.java accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4549) Electronic text record missing in Content Demo data
[ https://issues.apache.org/jira/browse/OFBIZ-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4549: -- Assignee: Jacques Le Roux Electronic text record missing in Content Demo data --- Key: OFBIZ-4549 URL: https://issues.apache.org/jira/browse/OFBIZ-4549 Project: OFBiz Issue Type: Bug Components: specialpurpose/ecommerce Affects Versions: SVN trunk Reporter: Jonatan Soto Assignee: Jacques Le Roux Attachments: DemoProduct.xml It is missing the related 'ElectronicText' record for a 'DataResource' when dataResourceId=SV-1000-ALT An error stack trace is shown when displaying the category that uses this content when a locale different to English is set. http://demo-trunk.ofbiz.apache.org/ecommerce/service-product-SERV-001-c -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4503) wrong jquery.custom.min address in product/commonScreens.xml
[
https://issues.apache.org/jira/browse/OFBIZ-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux reassigned OFBIZ-4503:
--
Assignee: Jacques Le Roux (was: Erwan de FERRIERES)
wrong jquery.custom.min address in product/commonScreens.xml
Key: OFBIZ-4503
URL: https://issues.apache.org/jira/browse/OFBIZ-4503
Project: OFBiz
Issue Type: Bug
Components: product
Affects Versions: SVN trunk
Reporter: Olivier Heintz
Assignee: Jacques Le Roux
Fix For: SVN trunk
Attachments: ProductCommonScreens.patch, ProductCommonScreens2.patch
in product/commonScreens.xml
--- applications/product/widget/catalog/CommonScreens.xml(révision
1188040)
+++ applications/product/widget/catalog/CommonScreens.xml(copie de
travail)
@@ -43,7 +43,7 @@
set field=applicationTitle
value=${uiLabelMap.ProductCatalogManagerApplication} global=true/
set field=layoutSettings.javaScripts[+0]
value=/images/jquery/ui/development-bundle/external /jquery.cookie.js
global=true/
set field=layoutSettings.javaScripts[+0]
value=/images/jquery/plugins/jsTree/jquery.jstree.js global=true/
-set field=layoutSettings.javaScripts[+0]
value=/images/jquery/jquery-1.8.13.custom.min.js global=true/
+set field=layoutSettings.javaScripts[+0]
value=/images/jquery/ui/js/jquery-ui-1.8.13.custom.min.js global=true/
/actions
widgets
include-screen name=ApplicationDecorator
location=component://commonext/widget/CommonScreens.xml/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4541) Unable to Manage Picklists
[ https://issues.apache.org/jira/browse/OFBIZ-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4541: -- Assignee: Jacques Le Roux Unable to Manage Picklists -- Key: OFBIZ-4541 URL: https://issues.apache.org/jira/browse/OFBIZ-4541 Project: OFBiz Issue Type: Bug Affects Versions: SVN trunk Reporter: Sam Hamilton Assignee: Jacques Le Roux If you try to manage a pick list you get the following error: Error rendering included template at location [component://product/webapp/facility/facility/PicklistManage.ftl]: freemarker.core.ParseException: Found unexpected directive: on line 227, column 21 Check whether you have a well-formed if-else block. To reproduce this error go to the following page: https://demo-trunk.ofbiz.apache.org/facility/control/PicklistManage?facilityId=WebStoreWarehouse -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4041) Materialized views
[ https://issues.apache.org/jira/browse/OFBIZ-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4041: -- Assignee: Jacques Le Roux Materialized views -- Key: OFBIZ-4041 URL: https://issues.apache.org/jira/browse/OFBIZ-4041 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: Release Branch 10.04 Reporter: Marc Morin Assignee: Jacques Le Roux Attachments: OFBIZ-4041.patch We make extensive use of view entities in our ofbiz application. We have noticed that when there is a large dataset and under some complex views, the query performance was not the best (not a index issue, just complex joins, etc...). With some commercial databases like Oracle, etc... we would have used materialized view semantics available for these dbms, but we are using PostgreSQL. So, we have extended the entity layer in Ofbiz to perform the materialization. This is pretty slick as all you need to do is the following: view-entity name=myView materialize=true.../view-entity and the system will do the following: - create a backing entity called myView that has the same fields as the view - backing entity has all the indexes inherited from the component entities - relations (fk,...) inherited from the component entities. - perform all the ECA actions automatically on all entities used in the view (direct members and nested members if case of view on views). (This is an eager update strategy only). So, the application doesn't change, it still accesses myView, but now, it's result is returned from the backing entity instead of the complex SQL statement. We're pretty excited about this feature!!! Really pushes Ofbiz framework to next level and allows materialized views to be more broadly used on dbms that don't naturally support it. We are prepared to contribute this feature back to the community if desired. A note of caution about it though we have added a visitor pattern to the model entities and this feature makes use of it. It would need to come with it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-2813) ProductStore did not allow the default timezone to be set
[ https://issues.apache.org/jira/browse/OFBIZ-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-2813: -- Assignee: Jacques Le Roux ProductStore did not allow the default timezone to be set - Key: OFBIZ-2813 URL: https://issues.apache.org/jira/browse/OFBIZ-2813 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Bob Morley Assignee: Jacques Le Roux Priority: Minor Attachments: OFBIZ-2813.patch, OFBIZ-2813.patch The ProductStore has the defaultLocaleString and the defaultCurrencyUomId but does not have a defaultTimeZoneString. What happens when a store is selected (from e-commerce or the pos) is that it will look to the user for a lastTimeZone and if that is not set, it would simply revert to the TimeZone.getDefault() (so the timezone based on the server). The trouble we had was that you may have an application server that is running in a completely different timezone than what is desired for the store. I will be attaching a patch to this ticket with changes related to this improvement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4393) View entity condition-expr doesn't handle null
[ https://issues.apache.org/jira/browse/OFBIZ-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4393: -- Assignee: Jacques Le Roux (was: Adrian Crum) View entity condition-expr doesn't handle null -- Key: OFBIZ-4393 URL: https://issues.apache.org/jira/browse/OFBIZ-4393 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Rev 1165137 Reporter: Anne Jessel Assignee: Jacques Le Roux Attachments: OFBIZ-4393-view-entity_condition-expr_null.patch, OFBIZ-4393-view-entity_condition-expr_null.patch Original Estimate: 2h Remaining Estimate: 2h condition-expr tag in view-entity can't be used to compare a field with null. An absent value attribute is read as an empty string, and the code currently checks for value being null to know when to compare against null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4393) View entity condition-expr doesn't handle null
[ https://issues.apache.org/jira/browse/OFBIZ-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4393: -- Assignee: Adrian Crum (was: Jacques Le Roux) Did not notice Adrian has already assigned to himself: I will simply review View entity condition-expr doesn't handle null -- Key: OFBIZ-4393 URL: https://issues.apache.org/jira/browse/OFBIZ-4393 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Rev 1165137 Reporter: Anne Jessel Assignee: Adrian Crum Attachments: OFBIZ-4393-view-entity_condition-expr_null.patch, OFBIZ-4393-view-entity_condition-expr_null.patch Original Estimate: 2h Remaining Estimate: 2h condition-expr tag in view-entity can't be used to compare a field with null. An absent value attribute is read as an empty string, and the code currently checks for value being null to know when to compare against null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-4477) JavaScript location is empty causes a double requests problem
[ https://issues.apache.org/jira/browse/OFBIZ-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-4477: -- Assignee: Jacques Le Roux JavaScript location is empty causes a double requests problem - Key: OFBIZ-4477 URL: https://issues.apache.org/jira/browse/OFBIZ-4477 Project: OFBiz Issue Type: Bug Components: themes Affects Versions: SVN trunk Environment: Ubuntu Reporter: Chatree Srichart Assignee: Jacques Le Roux Priority: Critical Attachments: check_empty_javascript_and_stylesheet.patch I see the JsLanguageFilesMapping.dateTime field does not have a script location for the en_US locale, so it will generate an empty script tag on the HTML header: .. .. script src= type=text/javascript/script .. .. which causes double requests problem on every requests. To solve this problem I have to check if the javaScript and styleSheet fields in header.ftl files for every themes are empty before generate the script and link tags. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OFBIZ-3913) Automated action triggered by event
[ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-3913: -- Assignee: Jacques Le Roux Automated action triggered by event --- Key: OFBIZ-3913 URL: https://issues.apache.org/jira/browse/OFBIZ-3913 Project: OFBiz Issue Type: New Feature Components: framework Affects Versions: SVN trunk Reporter: Nicolas Malin Assignee: Jacques Le Roux Attachments: ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.patch, ExternalDevice.png Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft. I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc... Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
