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

James McGill commented on OFBIZ-3903:
-------------------------------------


This is the error message.  I realize I'm getting a different error from the 
one I expected to get, but it still illustrates the problem.

Message: Error rendering screen 
[component://example/widget/example/PortletScreens.xml#PortletErrorExample2]: 
org.ofbiz.entity.transaction.GenericTransactionException: The current 
transaction is marked for rollback, not beginning a new transaction and 
aborting current operation; the rollbackOnly was caused by: Error in Service 
[exampleErrorService]: You must be logged in to complete the [] process. (The 
current transaction is marked for rollback, not beginning a new transaction and 
aborting current operation; the rollbackOnly was caused by: Error in Service 
[exampleErrorService]: You must be logged in to complete the [] process.)



If I add [ userLogin : userLogin ] to the service call, I get the expected 
error message, but the same result on the portal page.

org.ofbiz.entity.transaction.GenericTransactionException: The current 
transaction is marked for rollback, not beginning a new transaction a
nd aborting current operation; the rollbackOnly was caused by: Error in 
simple-method [ [file:/home/jmcgill/ares-production-trunk/framework
/example/script/org/ofbiz/example/example/ExampleServices.xml#exampleErrorService]]:
 ; [Example Error]




> Service error in one portlet causes a rendering failure in another portlet.
> ---------------------------------------------------------------------------
>
>                 Key: OFBIZ-3903
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3903
>             Project: OFBiz
>          Issue Type: Bug
>          Components: specialpurpose/myportal
>    Affects Versions: Release 09.04
>            Reporter: James McGill
>
> I have a portlet that calls a service.  If that service has an error, it 
> causes a different portlet to throw a stack trace on the screen.
> I will attach steps to reproduce.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to