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

Eric Kingston commented on OFBIZ-6792:
--------------------------------------

I apologize for any misunderstanding, but the OFBIZ-6792.patch file clearly 
shows usage of the UtilHttp.setContentDisposition method, which, as I mentioned 
before doesn't exist.  From the comments made previously, i understood that 
this patch was going to be applied if there were no objections.  It appears 
that r1724697 didn't include the OFBIZ-6792.patch file, and the text changed 
link seems to revert back to the original code which threw an exception when 
running the sendEmailOrderConfirmation service.  So, it would seem that we're 
back where we started, with the response object not being available.  What am I 
missing?  

I will again try the sendEmailOrderConfirmation service now that r1724697 has 
been committed to see if a response object not available exception is still 
thrown or if it has been corrected.  I may be missing something but, this code 
looks like the original code that thew that exception in the first place.



> Exception when sending an order confirmation email
> --------------------------------------------------
>
>                 Key: OFBIZ-6792
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6792
>             Project: OFBiz
>          Issue Type: Bug
>          Components: order, specialpurpose/ecommerce
>    Affects Versions: Release Branch 14.12, Trunk
>         Environment: Eclipse IDE
>            Reporter: Eric Kingston
>            Assignee: Jacques Le Roux
>             Fix For: 14.12.01, Upcoming Branch, Release Branch 15.12
>
>         Attachments: OFBIZ-6792.patch
>
>
> Receive the following exception while placing an order through the ecommerce 
> application.....
> groovy.lang.MissingPropertyException: No such property: response for class: 
> CompanyHeader
> Following is the relevant portion of the stack trace...
> at 
> org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
>  ~[groovy-all-2.2.1.jar:2.2.1]
> at 
> org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
>  ~[groovy-all-2.2.1.jar:2.2.1]
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231)
>  ~[groovy-all-2.2.1.jar:2.2.1]
> at CompanyHeader.run(CompanyHeader.groovy:48) ~[?:?]
> ...
> Apparently, the response object is not available within the context when the 
> sendOrderConfirmation service is run.  
> Steps to reproduce the exception....
> 1.  Checkout OFBiz 14.12 Release (revision was 1722928 at the time of 
> checkout).
> 2.  Run the default build.
> 3.  Load the demo data.
> 4.  Start the OFBiz instance (it will use the OOTB default derby db of 
> course).
> 5.  Within a browser goto URL..  http://localhost:8080/ecommerce 
> 6.  Proceed to place an order adding at least one item to the cart.
> 7.  While checking out you may or may not have to create an account.  I 
> created an account for this test.
> 8.  Proceed through all the checkout steps and submit the order.
> Monitor the log and you will see the exception occur within a few seconds.  
> This exception doesn't occur in the OFBiz 13.07 release branch.  In fact, the 
> response object is not referenced at all in the CompanyHeader.groovy from the 
> 13.07 branch.  Whoever inserted the code that references the response object 
> within the CompanyHeader.groovy script, must have neglected to test the 
> changes with the ecommerce application.  I only found the error while 
> migrating our instance of OFBiz to the 14.12 release.  Our custom ecommerce 
> application employs the sendOrderConfirmation service the same way the OOTB 
> ecommerce application does.
> I hope I have provided sufficient information for someone to resolve this 
> issue.  Thanks.



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

Reply via email to