search

jamievkent / openesignforms

Automatically exported from code.google.com/p/openesignforms
0 stars 0 forks source link

Unexpected exception on document review (Multi-page document) #143

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I have created a Multi-page document. ONLY this document is giving me this 
issue. 

>> What is the expected output? What do you see instead?
When I am trying to proceed to "Document Review" from the last page of the 
multi-page document, it give me the following error.

"Sorry, an unexpected exception occurred.
There is no more information about this exception we can report."

>> What version of the product are you using? On what operating system?
Open eSignForms v15.2.7
Windows 8 using Chrome

>> Please provide any additional information below.
I had it before when I tried to change a single page document to a multipage 
document. As soon as I converted back to a single-page document, the issue 
disappeared.

Original issue reported on code.google.com by co...@thumbzup.com on 9 Feb 2015 at 1:31

GoogleCodeExporter commented 8 years ago 
Can you share the date/time it happened so we can look in the logs?  Also, what 
document is it in case we need to look at its programming.

Also, that exception often shows the actual cause, but hidden in a "view 
source".  If you can share the view source of the page when it occurs, it may 
show the exception stack trace to help identify what area went wrong.

Original comment by yoz...@gmail.com on 9 Feb 2015 at 5:13

GoogleCodeExporter commented 8 years ago 
Also, can we get the transaction template name you were running in case the 
issue is related to the package setup.

Original comment by yoz...@gmail.com on 9 Feb 2015 at 5:18

GoogleCodeExporter commented 8 years ago 
Who it may concern,

I just tried to re-submit the above test transaction today again @
10-02-2015 08:52
I started the transaction yesterday and could not continue when it gave me
the error

*Please see below details as requested:*
*Document Name:* Product_ChangeRequest [1] (Test)
*Package Name:* Product/ChangeRequest [1] (Production)
*Transaction Template Name:* Product/ChangeVarianceOrder

*Transaction ID:* 5b1c4df4-0c00-47ca-ae87-1256d3a6bd5e

Regards,

*Colet Smit*Quality Manager
*thum**b**zup Innovations (Pty) Ltd *
T: +27 (0)87 550 2680
M: +27 (0)72 394 2786
*colet@thumbzup.com <colet@thumbzup.com> *
267 West Avenue, 1st Floor, Centurion, 0157

Original comment by co...@thumbzup.com on 10 Feb 2015 at 7:03

GoogleCodeExporter commented 8 years ago 
When we checked, as soon as we clicked on the package you named, we got an 
warning message saying that the document 'Product_ChangeRequest' could not be 
found at the Production level.  When we checked, indeed, that document is in 
Test mode only.  Most likely you reverted it back to Test, but then forgot to 
promote it back to production.

Of course, we do not recommend going into Production until it passes in Test 
mode.  We were able to reproduce it just using the 'Test' button while in the 
document editor.

Again, if you do a 'view source' when the exception occurs, we see the 
information that will help us debug it.  

<!-- Here's the stack trace embedded in the HTML source:
  java.lang.NullPointerException
        at com.esignforms.open.jsp.libdocsgen.taglib.DocumentOut.doTag(DocumentOut.java:84)
        at org.apache.jsp.LIBRARYGENERATED_002dKEEP.document._1997a954_002d4b2f_002d49cf_002d89e6_002d09d96909e60a.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp._jspx_meth_esf_005fdocumentout_005f1(bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp.java:2157)
        at org.apache.jsp.LIBRARYGENERATED_002dKEEP.document._1997a954_002d4b2f_002d49cf_002d89e6_002d09d96909e60a.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp._jspx_meth_esf_005fform_005f0(bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp.java:373)
        at org.apache.jsp.LIBRARYGENERATED_002dKEEP.document._1997a954_002d4b2f_002d49cf_002d89e6_002d09d96909e60a.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp._jspx_meth_esf_005fhtml_005f0(bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp.java:173)
        at org.apache.jsp.LIBRARYGENERATED_002dKEEP.document._1997a954_002d4b2f_002d49cf_002d89e6_002d09d96909e60a.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp._jspx_meth_esf_005fcapture_005f0(bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp.java:135)
        at org.apache.jsp.LIBRARYGENERATED_002dKEEP.document._1997a954_002d4b2f_002d49cf_002d89e6_002d09d96909e60a.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25.bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp._jspService(bc57b647_002d2005_002d423a_002d8fa0_002d9aa6b2cc8e25_jsp.java:95)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
        at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)
        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)
        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)
        at com.esignforms.open.servlet.PickupTransaction.doGet(PickupTransaction.java:85)
        at com.esignforms.open.servlet.PickupTransaction.doPost(PickupTransaction.java:91)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:644)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)

We noted this is related to the use of ${document:page.number}.  

For now, I'd recommend not using that syntax to get you going again (perhaps 
just hard code the page numbers for now).  

This could be a flawed concept (${document:page.number} may not make sense once 
in review mode) for multi-page documents because the "review" mode combines the 
various pages and so this dynamic page number scheme may not work.  We'll 
investigate it further and see if we can resolve the issue so the correct page 
numbers are shown when in review mode.

Original comment by yoz...@gmail.com on 11 Feb 2015 at 1:49

GoogleCodeExporter commented 8 years ago

Original comment by yoz...@gmail.com on 11 Feb 2015 at 10:38

GoogleCodeExporter commented 8 years ago 
Colet, can you try again? We installed a patch release just now (p0211) and 
wanted to see if that is now working for you.  We had to take an entirely 
different approach to the page number as we apparently hadn't thought about 
multi-page documents also making use of this ${document:page.number} notation.  
Previously, it was using the page's defined page number per the order shown in 
the document, but in multi-page review, it's actually a blend of all previous 
pages that allow for 'review' mode.

Original comment by yoz...@gmail.com on 12 Feb 2015 at 12:18

GoogleCodeExporter commented 8 years ago 
It worked - thank you very much for the assistance.

Regards,

*Colet Smit*Quality Manager
*thum**b**zup Innovations (Pty) Ltd *
T: +27 (0)87 550 2680
M: +27 (0)72 394 2786
*colet@thumbzup.com <colet@thumbzup.com> *
267 West Avenue, 1st Floor, Centurion, 0157

Original comment by co...@thumbzup.com on 12 Feb 2015 at 1:40

GoogleCodeExporter commented 8 years ago 
Released in the 15.2.7_p0211 patch release and of course in the regular build 
for the subsequent release.

Original comment by yoz...@gmail.com on 12 Feb 2015 at 6:59