Re: svn commit: r1071328 - /ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl
Make sense. Thanks for the clarification. :-) -- Ashish On Thu, Feb 17, 2011 at 12:55 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Ashish, I don't think so: we don't have jQuery in 10.04 Jacques From: Ashish Vijaywargiya vijaywargiya.ash...@gmail.com This changes can be back-ported to releasebranch10.04. Thanks! -- Ashish -- Forwarded message -- From: sascharodek...@apache.org Date: Wed, Feb 16, 2011 at 11:25 PM Subject: svn commit: r1071328 - /ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl To: comm...@ofbiz.apache.org Author: sascharodekamp Date: Wed Feb 16 17:55:52 2011 New Revision: 1071328 URL: http://svn.apache.org/viewvc?rev=1071328view=rev Log: Bug Fix DateTimePicker shows wrong current time ( https://issues.apache.org/jira/browse/OFBIZ-4169) - When changing the plugin configuration the dtp shows the correct time - Thanks Nikkel K for reporting. Modified: ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl Modified: ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl URL: http://svn.apache.org/viewvc/ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl?rev=1071328r1=1071327r2=1071328view=diff == --- ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl (original) +++ ofbiz/trunk/framework/widget/templates/htmlFormMacroLibrary.ftl Wed Feb 16 17:55:52 2011 @@ -111,8 +111,8 @@ under the License. showSecond: true, timeFormat: 'hh:mm:ss', stepHour: 1, -stepMinute: 5, -stepSecond: 10, +stepMinute: 1, +stepSecond: 1, /#if showOn: 'button', buttonImage: '',
[jira] Created: (OFBIZ-4183) Screen Link Ajax Windows
Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-4183: --- Attachment: Unbenannt.jpg Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995716#comment-12995716 ] Jacques Le Roux commented on OFBIZ-4183: Hi Sasccha, Yes, why not? Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995722#comment-12995722 ] Sascha Rodekamp commented on OFBIZ-4183: Just want to clarify before committing things ;) Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995725#comment-12995725 ] Jacques Le Roux commented on OFBIZ-4183: Maybe you could speak about it on dev ML before: this is best practice Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995727#comment-12995727 ] Erwan de FERRIERES commented on OFBIZ-4183: --- Hi, could the screen be just the screen, without the menu, header, footer? Cheers, Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995729#comment-12995729 ] Sascha Rodekamp commented on OFBIZ-4183: that was just an example screen, i used the previous link screen. You can add any screen u want. It's expected that you create a certain screen for the layered link which only contains the information you need. The layered box doesn't contain any logic it's just a container for the screen which should be opened. So the screen it self can decide what to show or if you load a form (i.e.) how to react on a submit (either reload the site or perform the submit as Ajax request in the background). Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
Hi Hans,
Isn't that more of an order related setting rather than anything the payment
gateway needs to worry about? Surely we already have processes for this sort
of thing?
Also, we're going to end up with a hell of a mess if we keep putting payment
processor specific code in the order logic.
Regards
Scott
On 17/02/2011, at 7:57 PM, hans...@apache.org wrote:
Author: hansbak
Date: Thu Feb 17 06:57:51 2011
New Revision: 1071517
URL: http://svn.apache.org/viewvc?rev=1071517view=rev
Log:
update to cybersource payment gateway: added a properties setting that orders
are still accepted but put into the created stage when a credit card fails
authorisation. The default is the current setting: order is not created
Modified:
ofbiz/trunk/applications/accounting/config/payment.properties
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java
ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java
Modified: ofbiz/trunk/applications/accounting/config/payment.properties
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff
==
--- ofbiz/trunk/applications/accounting/config/payment.properties (original)
+++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17
06:57:51 2011
@@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false
# AVS Decline Codes -- May not be supported any longer
#payment.cybersource.avsDeclineCodes=
+# Ignore status of cybersource transaction reply (Y|N) (if cybersource
response transaction status not equals ACCEPT then OFBiz will still create
the order but in status 'created'.
+# default N = Don't create order if cybersource reported transaction status
not equals ACCEPT.
+payment.cybersource.ignoreStatus=N
+# It happens pretty often that a creditcard is rejected for not valid
reasons, one can check to Cybersource fraud queue and after that the order
can still be rejected or approved.
+
+
# ClearCommerce Configuration
Modified:
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff
==
--- ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
(original)
+++ ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
Thu Feb 17 06:57:51 2011
@@ -267,6 +267,7 @@ under the License.
attribute name=errors type=Boolean mode=OUT optional=false/
attribute name=messages type=List mode=OUT optional=true/
attribute name=processAmount type=BigDecimal mode=OUT
optional=true/
+attribute name=authCode type=String mode=OUT optional=true/
/service
service name=authOrderPayments engine=java
@@ -276,6 +277,7 @@ under the License.
attribute name=processResult type=String mode=OUT
optional=false/
attribute name=authResultMsgs type=List mode=OUT
optional=true/
attribute name=reAuth type=Boolean mode=IN optional=true/
+attribute name=authCode type=String mode=OUT optional=true/
/service
service name=releaseOrderPayments engine=java
Modified:
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java?rev=1071517r1=1071516r2=1071517view=diff
==
---
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
(original)
+++
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
Thu Feb 17 06:57:51 2011
@@ -201,6 +201,7 @@ public class PaymentGatewayServices {
results.put(processAmount, thisAmount);
results.put(finished, Boolean.TRUE);
results.put(errors, Boolean.FALSE);
+results.put(authCode,
authPaymentResult.get(authCode));
return results;
} else {
boolean needsNsfRetry =
needsNsfRetry(orderPaymentPreference, authPaymentResult, delegator);
@@ -399,6 +400,9 @@ public class PaymentGatewayServices {
continue;
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
I agree, this is the wrong place for it.
What's more, isn't it a bad thing to change this such that it considers failed
auths successful in any way?
Why not just change your ProductStore settings to go into the Created status on
auth failure instead of the Rejected status?
Benefits include no code changes, can be different for different stores in the
same system, order history data shows actual payment processing results, and so
on.
-David
On Feb 17, 2011, at 1:11 AM, Scott Gray wrote:
Hi Hans,
Isn't that more of an order related setting rather than anything the payment
gateway needs to worry about? Surely we already have processes for this sort
of thing?
Also, we're going to end up with a hell of a mess if we keep putting payment
processor specific code in the order logic.
Regards
Scott
On 17/02/2011, at 7:57 PM, hans...@apache.org wrote:
Author: hansbak
Date: Thu Feb 17 06:57:51 2011
New Revision: 1071517
URL: http://svn.apache.org/viewvc?rev=1071517view=rev
Log:
update to cybersource payment gateway: added a properties setting that
orders are still accepted but put into the created stage when a credit card
fails authorisation. The default is the current setting: order is not created
Modified:
ofbiz/trunk/applications/accounting/config/payment.properties
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java
ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java
Modified: ofbiz/trunk/applications/accounting/config/payment.properties
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff
==
--- ofbiz/trunk/applications/accounting/config/payment.properties (original)
+++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17
06:57:51 2011
@@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false
# AVS Decline Codes -- May not be supported any longer
#payment.cybersource.avsDeclineCodes=
+# Ignore status of cybersource transaction reply (Y|N) (if cybersource
response transaction status not equals ACCEPT then OFBiz will still create
the order but in status 'created'.
+# default N = Don't create order if cybersource reported transaction status
not equals ACCEPT.
+payment.cybersource.ignoreStatus=N
+# It happens pretty often that a creditcard is rejected for not valid
reasons, one can check to Cybersource fraud queue and after that the order
can still be rejected or approved.
+
+
# ClearCommerce Configuration
Modified:
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff
==
---
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
(original)
+++
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
Thu Feb 17 06:57:51 2011
@@ -267,6 +267,7 @@ under the License.
attribute name=errors type=Boolean mode=OUT optional=false/
attribute name=messages type=List mode=OUT optional=true/
attribute name=processAmount type=BigDecimal mode=OUT
optional=true/
+attribute name=authCode type=String mode=OUT
optional=true/
/service
service name=authOrderPayments engine=java
@@ -276,6 +277,7 @@ under the License.
attribute name=processResult type=String mode=OUT
optional=false/
attribute name=authResultMsgs type=List mode=OUT
optional=true/
attribute name=reAuth type=Boolean mode=IN optional=true/
+attribute name=authCode type=String mode=OUT
optional=true/
/service
service name=releaseOrderPayments engine=java
Modified:
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java?rev=1071517r1=1071516r2=1071517view=diff
==
---
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
(original)
+++
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
Thu Feb 17 06:57:51 2011
@@ -201,6 +201,7 @@ public class PaymentGatewayServices {
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
This feature is not always for all paymentmethods for every order.
Certain payment processors can be easily checked and approved afterwards
with the payment processor while others do not have this feature.
Regards,
Hans
On Thu, 2011-02-17 at 22:11 +1300, Scott Gray wrote:
Hi Hans,
Isn't that more of an order related setting rather than anything the payment
gateway needs to worry about? Surely we already have processes for this sort
of thing?
Also, we're going to end up with a hell of a mess if we keep putting payment
processor specific code in the order logic.
Regards
Scott
On 17/02/2011, at 7:57 PM, hans...@apache.org wrote:
Author: hansbak
Date: Thu Feb 17 06:57:51 2011
New Revision: 1071517
URL: http://svn.apache.org/viewvc?rev=1071517view=rev
Log:
update to cybersource payment gateway: added a properties setting that
orders are still accepted but put into the created stage when a credit card
fails authorisation. The default is the current setting: order is not
created
Modified:
ofbiz/trunk/applications/accounting/config/payment.properties
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java
ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java
Modified: ofbiz/trunk/applications/accounting/config/payment.properties
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff
==
--- ofbiz/trunk/applications/accounting/config/payment.properties (original)
+++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb
17 06:57:51 2011
@@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false
# AVS Decline Codes -- May not be supported any longer
#payment.cybersource.avsDeclineCodes=
+# Ignore status of cybersource transaction reply (Y|N) (if cybersource
response transaction status not equals ACCEPT then OFBiz will still
create the order but in status 'created'.
+# default N = Don't create order if cybersource reported transaction
status not equals ACCEPT.
+payment.cybersource.ignoreStatus=N
+# It happens pretty often that a creditcard is rejected for not valid
reasons, one can check to Cybersource fraud queue and after that the order
can still be rejected or approved.
+
+
# ClearCommerce Configuration
Modified:
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff
==
---
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
(original)
+++
ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml
Thu Feb 17 06:57:51 2011
@@ -267,6 +267,7 @@ under the License.
attribute name=errors type=Boolean mode=OUT
optional=false/
attribute name=messages type=List mode=OUT optional=true/
attribute name=processAmount type=BigDecimal mode=OUT
optional=true/
+attribute name=authCode type=String mode=OUT
optional=true/
/service
service name=authOrderPayments engine=java
@@ -276,6 +277,7 @@ under the License.
attribute name=processResult type=String mode=OUT
optional=false/
attribute name=authResultMsgs type=List mode=OUT
optional=true/
attribute name=reAuth type=Boolean mode=IN optional=true/
+attribute name=authCode type=String mode=OUT
optional=true/
/service
service name=releaseOrderPayments engine=java
Modified:
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java?rev=1071517r1=1071516r2=1071517view=diff
==
---
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
(original)
+++
ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java
Thu Feb 17 06:57:51 2011
@@ -201,6 +201,7 @@ public class PaymentGatewayServices {
results.put(processAmount, thisAmount);
results.put(finished, Boolean.TRUE);
[jira] Closed: (OFBIZ-865) Deploy exception when serviceengine.xml contains resource-loader
[ https://issues.apache.org/jira/browse/OFBIZ-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-865. - Resolution: Won't Fix Assignee: Jacques Le Roux Sorry but this patch is totally outdated Deploy exception when serviceengine.xml contains resource-loader -- Key: OFBIZ-865 URL: https://issues.apache.org/jira/browse/OFBIZ-865 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Reporter: Victor Polischuk Assignee: Jacques Le Roux Priority: Minor Fix For: SVN trunk Attachments: OFBIZ-865.patch, OFBIZ-865.patch If in serviceengine.xml uses internal resource-loader, org.ofbiz.base.config.ResourceLoader could not found it, because resource-loader does not exists in root element service-config (now it has been moved into service-engine). For example: service-config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=http://www.ofbiz.org/dtds/service-config.xsd; service-engine name=default ... resource-loader name=service-classloader class=.../ global-services loader = service-classloader location = /services.xml / ... /service-engine /service-config java.lang.IllegalArgumentException: ResourceLoader not found with name [service-classloader] in serviceengine.xml at org.ofbiz.base.config.ResourceLoader.loadResource(ResourceLoader.java:47) at org.ofbiz.base.config.MainResourceHandler.getStream(MainResourceHandler.java:75) at org.ofbiz.base.config.MainResourceHandler.getDocument(MainResourceHandler.java:64) at org.ofbiz.service.ModelServiceReader.getModelServices(ModelServiceReader.java:125) at org.ofbiz.service.ModelServiceReader.init(ModelServiceReader.java:100) at org.ofbiz.service.ModelServiceReader.getModelServiceMap(ModelServiceReader.java:81) at org.ofbiz.service.DispatchContext.getGlobalServiceMap(DispatchContext.java:309) at org.ofbiz.service.DispatchContext.loadReaders(DispatchContext.java:79) at org.ofbiz.service.GenericDispatcher.init(GenericDispatcher.java:127) at org.ofbiz.service.GenericDispatcher.init(GenericDispatcher.java:115) at org.ofbiz.service.GenericDispatcher.getLocalDispatcher(GenericDispatcher.java:75) at org.ofbiz.service.GenericDispatcher.getLocalDispatcher(GenericDispatcher.java:39) at org.ofbiz.entityext.EntityServiceFactory.getLocalDispatcher(EntityServiceFactory.java:34) at org.ofbiz.entityext.EntityServiceFactory.getDispatchContext(EntityServiceFactory.java:39) at org.ofbiz.entityext.eca.DelegatorEcaHandler.setDelegator(DelegatorEcaHandler.java:53) at org.ofbiz.entity.GenericDelegator.init(GenericDelegator.java:234) at org.ofbiz.entity.GenericDelegator.getGenericDelegator(GenericDelegator.java:116) at org.ofbiz.catalina.container.CatalinaContainer.init(CatalinaContainer.java:163) at org.ofbiz.base.container.ContainerLoader.loadContainer(ContainerLoader.java:141) at org.ofbiz.base.container.ContainerLoader.load(ContainerLoader.java:65) at org.ofbiz.base.start.Start.initStartLoaders(Start.java:248) at org.ofbiz.base.start.Start.init(Start.java:87) at org.ofbiz.base.start.Start.main(Start.java:403) Solution: change the org.ofbiz.base.util.UtilXml.firstChildElement(Element, String, String, String). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
no sorry Scott, this option is only for this payment method, other payment methods used: paypal, google. One could sure have this setting at a higher level, however still it needs an override at a lower level too. I am sorry, but this is all I can say and do not have more time to spend on this. Regards, Hans On Thu, 2011-02-17 at 22:52 +1300, Scott Gray wrote: But you're typically only using one payment processor per store right? So the store settings should be sufficient, but even if not this should really be solved in a more generic way with some sort of setting at a higher level. Also it looks like your using the deprecated payment.properties for configuration instead of the PaymentGatewayConfig entities. Regards Scott On 17/02/2011, at 10:28 PM, Hans Bakker wrote: This feature is not always for all paymentmethods for every order. Certain payment processors can be easily checked and approved afterwards with the payment processor while others do not have this feature. Regards, Hans On Thu, 2011-02-17 at 22:11 +1300, Scott Gray wrote: Hi Hans, Isn't that more of an order related setting rather than anything the payment gateway needs to worry about? Surely we already have processes for this sort of thing? Also, we're going to end up with a hell of a mess if we keep putting payment processor specific code in the order logic. Regards Scott On 17/02/2011, at 7:57 PM, hans...@apache.org wrote: Author: hansbak Date: Thu Feb 17 06:57:51 2011 New Revision: 1071517 URL: http://svn.apache.org/viewvc?rev=1071517view=rev Log: update to cybersource payment gateway: added a properties setting that orders are still accepted but put into the created stage when a credit card fails authorisation. The default is the current setting: order is not created Modified: ofbiz/trunk/applications/accounting/config/payment.properties ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java Modified: ofbiz/trunk/applications/accounting/config/payment.properties URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/config/payment.properties (original) +++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17 06:57:51 2011 @@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false # AVS Decline Codes -- May not be supported any longer #payment.cybersource.avsDeclineCodes= +# Ignore status of cybersource transaction reply (Y|N) (if cybersource response transaction status not equals ACCEPT then OFBiz will still create the order but in status 'created'. +# default N = Don't create order if cybersource reported transaction status not equals ACCEPT. +payment.cybersource.ignoreStatus=N +# It happens pretty often that a creditcard is rejected for not valid reasons, one can check to Cybersource fraud queue and after that the order can still be rejected or approved. + + # ClearCommerce Configuration Modified: ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml Thu Feb 17 06:57:51 2011 @@ -267,6 +267,7 @@ under the License. attribute name=errors type=Boolean mode=OUT optional=false/ attribute name=messages type=List mode=OUT optional=true/ attribute name=processAmount type=BigDecimal mode=OUT optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service name=authOrderPayments engine=java @@ -276,6 +277,7 @@ under the License. attribute name=processResult type=String mode=OUT optional=false/ attribute name=authResultMsgs type=List mode=OUT optional=true/ attribute name=reAuth type=Boolean mode=IN optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service name=releaseOrderPayments engine=java Modified:
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
That's really not good enough, but I'm not going to waste my time arguing with you. Regards Scott On 17/02/2011, at 11:00 PM, Hans Bakker wrote: no sorry Scott, this option is only for this payment method, other payment methods used: paypal, google. One could sure have this setting at a higher level, however still it needs an override at a lower level too. I am sorry, but this is all I can say and do not have more time to spend on this. Regards, Hans On Thu, 2011-02-17 at 22:52 +1300, Scott Gray wrote: But you're typically only using one payment processor per store right? So the store settings should be sufficient, but even if not this should really be solved in a more generic way with some sort of setting at a higher level. Also it looks like your using the deprecated payment.properties for configuration instead of the PaymentGatewayConfig entities. Regards Scott On 17/02/2011, at 10:28 PM, Hans Bakker wrote: This feature is not always for all paymentmethods for every order. Certain payment processors can be easily checked and approved afterwards with the payment processor while others do not have this feature. Regards, Hans On Thu, 2011-02-17 at 22:11 +1300, Scott Gray wrote: Hi Hans, Isn't that more of an order related setting rather than anything the payment gateway needs to worry about? Surely we already have processes for this sort of thing? Also, we're going to end up with a hell of a mess if we keep putting payment processor specific code in the order logic. Regards Scott On 17/02/2011, at 7:57 PM, hans...@apache.org wrote: Author: hansbak Date: Thu Feb 17 06:57:51 2011 New Revision: 1071517 URL: http://svn.apache.org/viewvc?rev=1071517view=rev Log: update to cybersource payment gateway: added a properties setting that orders are still accepted but put into the created stage when a credit card fails authorisation. The default is the current setting: order is not created Modified: ofbiz/trunk/applications/accounting/config/payment.properties ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java Modified: ofbiz/trunk/applications/accounting/config/payment.properties URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/config/payment.properties (original) +++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17 06:57:51 2011 @@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false # AVS Decline Codes -- May not be supported any longer #payment.cybersource.avsDeclineCodes= +# Ignore status of cybersource transaction reply (Y|N) (if cybersource response transaction status not equals ACCEPT then OFBiz will still create the order but in status 'created'. +# default N = Don't create order if cybersource reported transaction status not equals ACCEPT. +payment.cybersource.ignoreStatus=N +# It happens pretty often that a creditcard is rejected for not valid reasons, one can check to Cybersource fraud queue and after that the order can still be rejected or approved. + + # ClearCommerce Configuration Modified: ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml Thu Feb 17 06:57:51 2011 @@ -267,6 +267,7 @@ under the License. attribute name=errors type=Boolean mode=OUT optional=false/ attribute name=messages type=List mode=OUT optional=true/ attribute name=processAmount type=BigDecimal mode=OUT optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service name=authOrderPayments engine=java @@ -276,6 +277,7 @@ under the License. attribute name=processResult type=String mode=OUT optional=false/ attribute name=authResultMsgs type=List mode=OUT optional=true/ attribute name=reAuth type=Boolean mode=IN optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service
Re: Update service engine documentation
From: Jacques Le Roux jacques.le.r...@les7arts.com From: David E Jones d...@me.com On Feb 16, 2011, at 12:51 AM, Jacques Le Roux wrote: Hi, Reading this sentence in https://cwiki.apache.org/confluence/display/OFBTECH/Service+Engine+Guide Services which are used in different applications can be defined only once by creating Global Service Definition files or services specific to an application can be restricted and available only to that application. and considering https://issues.apache.org/jira/browse/OFBIZ-865, I wonder 2 things 1. Should we not remove the reference to Global Service Definition since it's never used OOTB, and a bit confusing since anyway services defined by components are also reacheable outside those components? This is backwards. The global service definitions are ALWAYS used in the OOTB code, not never. a. Corollary: should we not remove the resource-loader element from serviceengine.xml since it's broken for more than 3 years? In what way is it broken? Oops forget it, I read https://issues.apache.org/jira/browse/OFBIZ-865 too fast, it's only if you put resource-loader in root element service-config. Now it has been moved into service-engine, this is clear in service-config.xsd. BTW should we close OFBIZ-865? What I understand from xml definitions (did not look into code): OOTB we only define resource-loader in ofbiz-component files and this is referred by service-resource in the same file and defines thus Global Service Definition, right? If it's right I'd like to put some words there to clarify our current OOTB most use. 2. Is it still possible to restrict services to an application, and if yes how? Else I will remove the whole sentence, it's just confusing. Yes, it is possible, but not used much. A WEB-INF directory can have a services.xml file in it, etc, etc. I'd recommend not starting to remove that unless you plan to really get into it. Thanks I wil ltry to explain that in a sentence also. Done Jacques However, if we did that it would solve some issues with the service dispatcher, and we could move to a model of having one dispatcher per delegator (instead of per webapp, plus per delegator for other things, plus funny special ones scattered around with fixed names that cause problems with multiple delegators). I have not planned to touch at the framework, but yes why not? Thanks Jacques -David
[jira] Commented: (OFBIZ-3385) Axis2 integration returns Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
[
https://issues.apache.org/jira/browse/OFBIZ-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995746#comment-12995746
]
Jacques Le Roux commented on OFBIZ-3385:
Hi Chris,
I will certainly have to work on this, any update?
Thanks
Axis2 integration returns Unsupported Content-Type: text/html;charset=utf-8
Supported ones are: [text/xml]
Key: OFBIZ-3385
URL: https://issues.apache.org/jira/browse/OFBIZ-3385
Project: OFBiz
Issue Type: Bug
Components: framework
Affects Versions: SVN trunk
Reporter: chris snow
Attachments: patch.txt, patch2.txt
I have setup the findPartiesById service to export=true and tried to call
the web service using Netbeans 6.5.
I received the following error message:
{code}
com.sun.xml.internal.ws.server.UnsupportedMediaException: Unsupported
Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
at
com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:284)
at
com.sun.xml.internal.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:118)
at
com.sun.xml.internal.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:278)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:180)
at
com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83)
at
com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:105)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211)
at
com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
at $Proxy28.findPartiesById(Unknown Source)
at javaapplication7.Main.main(Main.java:74)
{code}
Watching the tcp steam with wireshark, I can see that the prefix ns2 is added
to the map-Entry items:
{code}
S:Envelope xmlns:S=http://schemas.xmlsoap.org/soap/envelope/;
S:Body
ns2:findPartiesById xmlns:ns2=http://ofbiz.apache.org/service/;
map-Map
ns2:map-Entry
ns2:map-Key
ns2:std-String value=idToFind/
/ns2:map-Key
ns2:map-Value
ns2:std-String value=admin/
/ns2:map-Value
/ns2:map-Entry
ns2:map-Entry
ns2:map-Key
ns2:std-String value=login.username/
/ns2:map-Key
ns2:map-Value
ns2:std-String value=admin/
/ns2:map-Value
/ns2:map-Entry
ns2:map-Entry
ns2:map-Key
ns2:std-String value=login.password/
/ns2:map-Key
ns2:map-Value
ns2:std-String value=ofbiz/
/ns2:map-Value
/ns2:map-Entry
/map-Map
/ns2:findPartiesById
/S:Body
/S:Envelope
{code}
If I copy this soap message and paste into SoapUI, the soap call fails.
However, if I strip off the ns2 prefix from the map-Entry items (as below),
the call succeeds:
{code}
S:Envelope xmlns:S=http://schemas.xmlsoap.org/soap/envelope/;
S:Body
ns2:findPartiesById xmlns:ns2=http://ofbiz.apache.org/service/;
map-Map
map-Entry
map-Key
std-String value=idToFind/
/map-Key
map-Value
std-String value=admin/
/map-Value
/map-Entry
map-Entry
map-Key
std-String value=login.username/
/map-Key
map-Value
std-String value=admin/
/map-Value
/map-Entry
map-Entry
map-Key
std-String value=login.password/
/map-Key
map-Value
std-String value=ofbiz/
/map-Value
/map-Entry
/map-Map
/ns2:findPartiesById
/S:Body
/S:Envelope
{code}
My java class is:
{code}
[jira] Commented: (OFBIZ-4060) Bug In Jquery Integration - js File Not Found
[ https://issues.apache.org/jira/browse/OFBIZ-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995779#comment-12995779 ] Manuela Gruendlinger commented on OFBIZ-4060: - Hi there! The warning message logged now is still a bit distracting and at times even wrong. For example, when trying to load the i18n file for locale 'de_DE' the message suggests that 'en' would be used as a fallback: [java] 2011-02-17 12:53:21,050 (http-0.0.0.0-8443-1) [ComponentLocationResolver.java:44 :WARN ] A jquery.ui.datepicker i18n file is missing for the language.country couple you want. Simply add it there: [C:/ofbiz/framework/images/webapp/images/jquery/ui/development-bundle/ui/i18n/jquery.ui.datepicker-de-DE.js]. Else anyway the 'en' default will be used This is actually wrong because as a fallback, the file for locale 'de' will be used, which is still OK since it isn't necessary to maintain another copy of the same variant. Are there any further changes planned for this? Thanks regards Manuela Bug In Jquery Integration - js File Not Found - Key: OFBIZ-4060 URL: https://issues.apache.org/jira/browse/OFBIZ-4060 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Adrian Crum Assignee: Jacques Le Roux Priority: Minor Fix For: SVN trunk I'm getting this error in the log: 2010-12-15 09:58:38,203 (http-0.0.0.0-8443-2) [ComponentLocationResolver.java:43 :WARN ] Unable to get file URL for component location; expanded location was [C:/ofbiz/framework/images/webapp/images/jquery/ui/development-bundle/ui/i18n/jquery.ui.datepicker-en-US.js], original location was [component://images/webapp/images/jquery/ui/development-bundle/ui/i18n/jquery.ui.datepicker-en-US.js] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4060) Bug In Jquery Integration - js File Not Found
[ https://issues.apache.org/jira/browse/OFBIZ-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995787#comment-12995787 ] Sascha Rodekamp commented on OFBIZ-4060: Hi Manuela, it's quite interesting that your fallback language is 'de' it should be 'en' in any case. I never noticed this behavior before. So i will check and give you more information asap. Hava good day Sascha Bug In Jquery Integration - js File Not Found - Key: OFBIZ-4060 URL: https://issues.apache.org/jira/browse/OFBIZ-4060 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: SVN trunk Reporter: Adrian Crum Assignee: Jacques Le Roux Priority: Minor Fix For: SVN trunk I'm getting this error in the log: 2010-12-15 09:58:38,203 (http-0.0.0.0-8443-2) [ComponentLocationResolver.java:43 :WARN ] Unable to get file URL for component location; expanded location was [C:/ofbiz/framework/images/webapp/images/jquery/ui/development-bundle/ui/i18n/jquery.ui.datepicker-en-US.js], original location was [component://images/webapp/images/jquery/ui/development-bundle/ui/i18n/jquery.ui.datepicker-en-US.js] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (OFBIZ-4181) ProductEntityLabels extention
[ https://issues.apache.org/jira/browse/OFBIZ-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-4181. -- ProductEntityLabels extention - Key: OFBIZ-4181 URL: https://issues.apache.org/jira/browse/OFBIZ-4181 Project: OFBiz Issue Type: Improvement Components: product Affects Versions: SVN trunk Reporter: Nikkel K Assignee: Christian Geisert Priority: Minor Fix For: SVN trunk Attachments: ProductEntityLabels.xml.patch Hi all, I did add and edit some german Labels for ProductEntityLabels.xml. Greetings, Konstantin -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
Its interesting how serious issues are getting handled, In last two weeks I have seen interesting comments by same person, see See, http://mail-archives.apache.org/mod_mbox/ofbiz-dev/201102.mbox/%3C1296861866.2554.9.camel@hans-laptop%3E http://ofbiz.135035.n4.nabble.com/Re-svn-commit-r1068279-1-2-in-ofbiz-trunk-applications-order-entitydef-order-script-org-ofbiz-order--td3275530.html#a3276070 There are few others. Is contribution so important for Ofbiz community that they will ignore all these poor quality commits? Thanks and Regards Anil Patel On Feb 17, 2011, at 5:04 AM, Scott Gray wrote: That's really not good enough, but I'm not going to waste my time arguing with you. Regards Scott On 17/02/2011, at 11:00 PM, Hans Bakker wrote: no sorry Scott, this option is only for this payment method, other payment methods used: paypal, google. One could sure have this setting at a higher level, however still it needs an override at a lower level too. I am sorry, but this is all I can say and do not have more time to spend on this. Regards, Hans On Thu, 2011-02-17 at 22:52 +1300, Scott Gray wrote: But you're typically only using one payment processor per store right? So the store settings should be sufficient, but even if not this should really be solved in a more generic way with some sort of setting at a higher level. Also it looks like your using the deprecated payment.properties for configuration instead of the PaymentGatewayConfig entities. Regards Scott On 17/02/2011, at 10:28 PM, Hans Bakker wrote: This feature is not always for all paymentmethods for every order. Certain payment processors can be easily checked and approved afterwards with the payment processor while others do not have this feature. Regards, Hans On Thu, 2011-02-17 at 22:11 +1300, Scott Gray wrote: Hi Hans, Isn't that more of an order related setting rather than anything the payment gateway needs to worry about? Surely we already have processes for this sort of thing? Also, we're going to end up with a hell of a mess if we keep putting payment processor specific code in the order logic. Regards Scott On 17/02/2011, at 7:57 PM, hans...@apache.org wrote: Author: hansbak Date: Thu Feb 17 06:57:51 2011 New Revision: 1071517 URL: http://svn.apache.org/viewvc?rev=1071517view=rev Log: update to cybersource payment gateway: added a properties setting that orders are still accepted but put into the created stage when a credit card fails authorisation. The default is the current setting: order is not created Modified: ofbiz/trunk/applications/accounting/config/payment.properties ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java Modified: ofbiz/trunk/applications/accounting/config/payment.properties URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/config/payment.properties (original) +++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17 06:57:51 2011 @@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false # AVS Decline Codes -- May not be supported any longer #payment.cybersource.avsDeclineCodes= +# Ignore status of cybersource transaction reply (Y|N) (if cybersource response transaction status not equals ACCEPT then OFBiz will still create the order but in status 'created'. +# default N = Don't create order if cybersource reported transaction status not equals ACCEPT. +payment.cybersource.ignoreStatus=N +# It happens pretty often that a creditcard is rejected for not valid reasons, one can check to Cybersource fraud queue and after that the order can still be rejected or approved. + + # ClearCommerce Configuration Modified: ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml Thu Feb 17 06:57:51 2011 @@ -267,6 +267,7 @@ under the License. attribute name=errors type=Boolean mode=OUT optional=false/ attribute name=messages
[jira] Created: (OFBIZ-4184) Trunk: When using IE, ShowAllPromotions in Demo is Broken
Trunk: When using IE, ShowAllPromotions in Demo is Broken -- Key: OFBIZ-4184 URL: https://issues.apache.org/jira/browse/OFBIZ-4184 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Trunk demo, using IE. Reporter: mz4wheeler Priority: Minor From the trunk ecommerce demo, when using IE (only), the following link shows promotioms broken, where they all line up on the bottom left of the screen. http://demo-trunk.ofbiz.apache.org/ecommerce/control/showAllPromotions It does work fine with FF and Chrome. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4184) Trunk: When using IE, ShowAllPromotions in Demo is Broken
[ https://issues.apache.org/jira/browse/OFBIZ-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995888#comment-12995888 ] Jacques Le Roux commented on OFBIZ-4184: Which version of IE are you using? Could you please attach a screen copy? Thanks Trunk: When using IE, ShowAllPromotions in Demo is Broken -- Key: OFBIZ-4184 URL: https://issues.apache.org/jira/browse/OFBIZ-4184 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Trunk demo, using IE. Reporter: mz4wheeler Priority: Minor From the trunk ecommerce demo, when using IE (only), the following link shows promotioms broken, where they all line up on the bottom left of the screen. http://demo-trunk.ofbiz.apache.org/ecommerce/control/showAllPromotions It does work fine with FF and Chrome. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (OFBIZ-4185) processCaptureResult error with billing account
processCaptureResult error with billing account
---
Key: OFBIZ-4185
URL: https://issues.apache.org/jira/browse/OFBIZ-4185
Project: OFBiz
Issue Type: Bug
Components: accounting
Affects Versions: Release Branch 10.04
Reporter: Wickersheimer Jeremy
Fix For: Release Branch 10.04
When using a billing account the processCaptureResult will fail with a missing
captureRefNum parameter.
There is a hack that sets it to an empty string but i guess a change occurred
and calling makeValid will convert that empty string to null making the service
call fail.
The fix is simply a matter of copying the workaround in {{private static void
processCaptureResult(DispatchContext dctx, MapString, Object result,
GenericValue userLogin, GenericValue paymentPreference, String
authServiceType)}}:
{code}
@@ -2032,8 +2032,11 @@ public class PaymentGatewayServices {
result.put(serviceTypeEnum, authServiceType);
ModelService model = dctx.getModelService(processCaptureResult);
MapString, Object context = model.makeValid(result,
ModelService.IN_PARAM);
+if (context.get(captureRefNum) == null) {
+context.put(captureRefNum, ); // FIXME: this is an hack to
avoid a service validation error for processCaptureResult (captureRefNum is
mandatory, but it is not used for billing accounts)
+}
MapString, Object capRes;
try {
capRes = dispatcher.runSync(processCaptureResult, context);
} catch (GenericServiceException e) {
{code}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1071517 - in /ofbiz/trunk/applications: accounting/config/ accounting/servicedef/ accounting/src/org/ofbiz/accounting/payment/ accounting/src/org/ofbiz/accounting/thirdparty/cybersour
many stores use atleast two processors, one for CC processor, like Authorize net to their bank, one for Paypal. = BJ Freeman Strategic Power Office with Supplier Automation http://www.businessesnetwork.com/automation/viewforum.php?f=52 Specialtymarket.com http://www.specialtymarket.com/ Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Scott Gray sent the following on 2/17/2011 1:52 AM: But you're typically only using one payment processor per store right? So the store settings should be sufficient, but even if not this should really be solved in a more generic way with some sort of setting at a higher level. Also it looks like your using the deprecated payment.properties for configuration instead of the PaymentGatewayConfig entities. Regards Scott On 17/02/2011, at 10:28 PM, Hans Bakker wrote: This feature is not always for all paymentmethods for every order. Certain payment processors can be easily checked and approved afterwards with the payment processor while others do not have this feature. Regards, Hans On Thu, 2011-02-17 at 22:11 +1300, Scott Gray wrote: Hi Hans, Isn't that more of an order related setting rather than anything the payment gateway needs to worry about? Surely we already have processes for this sort of thing? Also, we're going to end up with a hell of a mess if we keep putting payment processor specific code in the order logic. Regards Scott On 17/02/2011, at 7:57 PM, hans...@apache.org wrote: Author: hansbak Date: Thu Feb 17 06:57:51 2011 New Revision: 1071517 URL: http://svn.apache.org/viewvc?rev=1071517view=rev Log: update to cybersource payment gateway: added a properties setting that orders are still accepted but put into the created stage when a credit card fails authorisation. The default is the current setting: order is not created Modified: ofbiz/trunk/applications/accounting/config/payment.properties ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/thirdparty/cybersource/IcsPaymentServices.java ofbiz/trunk/applications/order/src/org/ofbiz/order/shoppingcart/CheckOutHelper.java Modified: ofbiz/trunk/applications/accounting/config/payment.properties URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/config/payment.properties?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/config/payment.properties (original) +++ ofbiz/trunk/applications/accounting/config/payment.properties Thu Feb 17 06:57:51 2011 @@ -118,6 +118,12 @@ payment.cybersource.ignoreAvs=false # AVS Decline Codes -- May not be supported any longer #payment.cybersource.avsDeclineCodes= +# Ignore status of cybersource transaction reply (Y|N) (if cybersource response transaction status not equals ACCEPT then OFBiz will still create the order but in status 'created'. +# default N = Don't create order if cybersource reported transaction status not equals ACCEPT. +payment.cybersource.ignoreStatus=N +# It happens pretty often that a creditcard is rejected for not valid reasons, one can check to Cybersource fraud queue and after that the order can still be rejected or approved. + + # ClearCommerce Configuration Modified: ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml?rev=1071517r1=1071516r2=1071517view=diff == --- ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/services_paymentmethod.xml Thu Feb 17 06:57:51 2011 @@ -267,6 +267,7 @@ under the License. attribute name=errors type=Boolean mode=OUT optional=false/ attribute name=messages type=List mode=OUT optional=true/ attribute name=processAmount type=BigDecimal mode=OUT optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service name=authOrderPayments engine=java @@ -276,6 +277,7 @@ under the License. attribute name=processResult type=String mode=OUT optional=false/ attribute name=authResultMsgs type=List mode=OUT optional=true/ attribute name=reAuth type=Boolean mode=IN optional=true/ +attribute name=authCode type=String mode=OUT optional=true/ /service service name=releaseOrderPayments engine=java Modified: ofbiz/trunk/applications/accounting/src/org/ofbiz/accounting/payment/PaymentGatewayServices.java URL:
[jira] Updated: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-4183: --- Attachment: LayeredLink_new.jpg Here is a new clearer screen shot Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Attachments: LayeredLink_new.jpg, Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp resolved OFBIZ-4183. Resolution: Fixed Fix Version/s: SVN trunk This feature is committed @ Rev: 1071698 Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Fix For: SVN trunk Attachments: LayeredLink_new.jpg, Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (OFBIZ-4183) Screen Link Ajax Windows
[ https://issues.apache.org/jira/browse/OFBIZ-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp closed OFBIZ-4183. -- Screen Link Ajax Windows Key: OFBIZ-4183 URL: https://issues.apache.org/jira/browse/OFBIZ-4183 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Sascha Rodekamp Assignee: Sascha Rodekamp Fix For: SVN trunk Attachments: LayeredLink_new.jpg, Unbenannt.jpg Hi, i created a new Screen link feature. Similar to the Form Lookups can i open a link in a layered JS Box (see Screenshot). It looks nice and is helpful in some cases. Is this interesting for the trunk? Cheers Sascha -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (OFBIZ-4186) Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration
Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration - Key: OFBIZ-4186 URL: https://issues.apache.org/jira/browse/OFBIZ-4186 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Rene Scheibe Priority: Critical .classpath still references the 6.0.30 jars while framework/catalina/lib already contains the 6.0.32 jars -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-4186) Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration
[ https://issues.apache.org/jira/browse/OFBIZ-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rene Scheibe updated OFBIZ-4186: Attachment: OFBIZ-4186_tomcat-6.0.32_classpath.patch fixed .classpath to use tomcat-6.0.32 jars Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration - Key: OFBIZ-4186 URL: https://issues.apache.org/jira/browse/OFBIZ-4186 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Rene Scheibe Priority: Critical Labels: eclipse Attachments: OFBIZ-4186_tomcat-6.0.32_classpath.patch .classpath still references the 6.0.30 jars while framework/catalina/lib already contains the 6.0.32 jars -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (OFBIZ-4186) Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration
[ https://issues.apache.org/jira/browse/OFBIZ-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES reassigned OFBIZ-4186: - Assignee: Erwan de FERRIERES Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration - Key: OFBIZ-4186 URL: https://issues.apache.org/jira/browse/OFBIZ-4186 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Rene Scheibe Assignee: Erwan de FERRIERES Priority: Critical Labels: eclipse Attachments: OFBIZ-4186_tomcat-6.0.32_classpath.patch .classpath still references the 6.0.30 jars while framework/catalina/lib already contains the 6.0.32 jars -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4186) Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration
[ https://issues.apache.org/jira/browse/OFBIZ-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995975#comment-12995975 ] Erwan de FERRIERES commented on OFBIZ-4186: --- Thanks for the reminder, I totally forgot ! Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration - Key: OFBIZ-4186 URL: https://issues.apache.org/jira/browse/OFBIZ-4186 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Rene Scheibe Assignee: Erwan de FERRIERES Priority: Critical Labels: eclipse Attachments: OFBIZ-4186_tomcat-6.0.32_classpath.patch .classpath still references the 6.0.30 jars while framework/catalina/lib already contains the 6.0.32 jars -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4130) Tenant super user (tenant admin) can view all database details of all tenants
[ https://issues.apache.org/jira/browse/OFBIZ-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996238#comment-12996238 ] Jacques Le Roux commented on OFBIZ-4130: Pierre, Should we keep open? Tenant super user (tenant admin) can view all database details of all tenants - Key: OFBIZ-4130 URL: https://issues.apache.org/jira/browse/OFBIZ-4130 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Release Branch 10.04, SVN trunk Reporter: Pierre Smits Priority: Critical Fix For: Release Branch 10.04, SVN trunk When a new tenant is created and the super user of the tenant (the tenant-admin) logs in to WebTools and views the tables Tenant and TenantDataSource he/she can see all details of the tenant databases, incl TenantName, userID and password of the tenant databases. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4184) Trunk: When using IE, ShowAllPromotions in Demo is Broken
[ https://issues.apache.org/jira/browse/OFBIZ-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996249#comment-12996249 ] mz4wheeler commented on OFBIZ-4184: --- Nope.. 32bit. Maybe it's my screen resolution. I play with a few settings. Trunk: When using IE, ShowAllPromotions in Demo is Broken -- Key: OFBIZ-4184 URL: https://issues.apache.org/jira/browse/OFBIZ-4184 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Trunk demo, using IE. Reporter: mz4wheeler Priority: Minor Attachments: .jpg, screenshot-1.jpg From the trunk ecommerce demo, when using IE (only), the following link shows promotioms broken, where they all line up on the bottom left of the screen. http://demo-trunk.ofbiz.apache.org/ecommerce/control/showAllPromotions It does work fine with FF and Chrome. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-4184) Trunk: When using IE, ShowAllPromotions in Demo is Broken
[ https://issues.apache.org/jira/browse/OFBIZ-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996256#comment-12996256 ] mz4wheeler commented on OFBIZ-4184: --- OK: When I'm NOT in compatibility mode, the issue persists. If I use compatibility mode, the screen renders correctly. Shouldn't it work correctly in both modes? Trunk: When using IE, ShowAllPromotions in Demo is Broken -- Key: OFBIZ-4184 URL: https://issues.apache.org/jira/browse/OFBIZ-4184 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: SVN trunk Environment: Trunk demo, using IE. Reporter: mz4wheeler Priority: Minor Attachments: .jpg, screenshot-1.jpg From the trunk ecommerce demo, when using IE (only), the following link shows promotioms broken, where they all line up on the bottom left of the screen. http://demo-trunk.ofbiz.apache.org/ecommerce/control/showAllPromotions It does work fine with FF and Chrome. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (OFBIZ-4186) Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration
[ https://issues.apache.org/jira/browse/OFBIZ-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES closed OFBIZ-4186. - Resolution: Fixed Fix Version/s: SVN trunk Done at 1071898. Thanks Rene Missed .classpath update on Tomcat 6.0.30 to 6.0.32 migration - Key: OFBIZ-4186 URL: https://issues.apache.org/jira/browse/OFBIZ-4186 Project: OFBiz Issue Type: Bug Components: ALL COMPONENTS Affects Versions: SVN trunk Reporter: Rene Scheibe Assignee: Erwan de FERRIERES Priority: Critical Labels: eclipse Fix For: SVN trunk Attachments: OFBIZ-4186_tomcat-6.0.32_classpath.patch .classpath still references the 6.0.30 jars while framework/catalina/lib already contains the 6.0.32 jars -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (OFBIZ-4187) The lookup widget does not support the target-parameter tag anymore
The lookup widget does not support the target-parameter tag anymore
---
Key: OFBIZ-4187
URL: https://issues.apache.org/jira/browse/OFBIZ-4187
Project: OFBiz
Issue Type: Bug
Components: framework
Reporter: Bruno Busco
The actual call_fieldlookup2 and call_fieldlookup3 javascript functions do not
accept the optional document.${formName}.${item}.value parameters that are
passed when one or more target-parameter tags are used in the lookup widget.
This causes that the lookup screens do not receive the parameters.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
