org.apache.cxf.interceptor.Fault

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • In order to reproduce, in an embedded client app, create a custom authorizer for roleQualifiers and add to the documentType. Add the super user panel to the document and open it (Or start up KC in embedded mode. Navigate to Researcher tab > Create a proposal > fill in required fields {code} * Sponsor Code:000340 * Proposal Type:New * Project Start Date:01/01/2013 * Lead Unit:000001 * Project End Date:03/31/2013 * Activity Type: Clnical Trial * Project Title: Test {code} and navigate to the proposal actions tab in the proposal Development document). The super user panel will not load fully and in the error logs you see the following stack trace. I have verified that the custom authorizer class does implement the DocumentTypeAuthorizer. {code} 2013-03-13 08:01:42,243 [qtp1675553600-66] D: U: WARN  org.apache.cxf.phase.PhaseInterceptorChain :: Application {http://rice.kuali.org/kew/v2_0}documentTypeService#{http://rice.kuali.org/kew/v2_0}canSuperUserApproveSingleActionRequest has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: DocumentType Authorizer 'org.kuali.kra.KcAuthorizer' configured for document type 'ProposalDevelopmentDocument does not implement org.kuali.rice.kew.framework.document.security.DocumentTypeAuthorizer at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:162) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:213) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:128) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:64 {code} This DocumentAuthorizer implementation to build custom role qualifiers works well in all situations except when called from the super user action tab. The problem occurs when the superUserAction.tab calls the DocumentTypeServiceImpl methods canSuperUser*. These methods try to authorize using the following code {code} boolean isSuperUser = KEWServiceLocator.getDocumentTypePermissionService().canSuperUserApproveDocument( principalId, documentType, currentNodeInstances, routeStatusCode); {code} The DocumentTypePermissionServiceAuthorizerImpl tries to get the custom implementation but cannot because the isAssignableFrom(extension.getClass()) of the getDocumentTypeAuthorizer returns false in this particular scenario. I have confirmed that this methods returns the right authorizer correctly in other situations when testing for canSave, canRecall etc. The issue also seems to happen only when the authorizer implementation is on the KC end. I tested this by adding "org.kuali.rice.kew.doctype.service.impl.KimDocumentTypeAuthorizer" to the authorizer element of the document type and that works. Let me know if you want to do a screenshare and debug through it.
    via by Gayathri Athreya,
  • In order to reproduce, in an embedded client app, create a custom authorizer for roleQualifiers and add to the documentType. Add the super user panel to the document and open it (Or start up KC in embedded mode. Navigate to Researcher tab > Create a proposal > fill in required fields {code} * Sponsor Code:000340 * Proposal Type:New * Project Start Date:01/01/2013 * Lead Unit:000001 * Project End Date:03/31/2013 * Activity Type: Clnical Trial * Project Title: Test {code} and navigate to the proposal actions tab in the proposal Development document). The super user panel will not load fully and in the error logs you see the following stack trace. I have verified that the custom authorizer class does implement the DocumentTypeAuthorizer. {code} 2013-03-13 08:01:42,243 [qtp1675553600-66] D: U: WARN  org.apache.cxf.phase.PhaseInterceptorChain :: Application {http://rice.kuali.org/kew/v2_0}documentTypeService#{http://rice.kuali.org/kew/v2_0}canSuperUserApproveSingleActionRequest has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: DocumentType Authorizer 'org.kuali.kra.KcAuthorizer' configured for document type 'ProposalDevelopmentDocument does not implement org.kuali.rice.kew.framework.document.security.DocumentTypeAuthorizer at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:162) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:213) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:128) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178) at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.java:64 {code} This DocumentAuthorizer implementation to build custom role qualifiers works well in all situations except when called from the super user action tab. The problem occurs when the superUserAction.tab calls the DocumentTypeServiceImpl methods canSuperUser*. These methods try to authorize using the following code {code} boolean isSuperUser = KEWServiceLocator.getDocumentTypePermissionService().canSuperUserApproveDocument( principalId, documentType, currentNodeInstances, routeStatusCode); {code} The DocumentTypePermissionServiceAuthorizerImpl tries to get the custom implementation but cannot because the isAssignableFrom(extension.getClass()) of the getDocumentTypeAuthorizer returns false in this particular scenario. I have confirmed that this methods returns the right authorizer correctly in other situations when testing for canSave, canRecall etc. The issue also seems to happen only when the authorizer implementation is on the KC end. I tested this by adding "org.kuali.rice.kew.doctype.service.impl.KimDocumentTypeAuthorizer" to the authorizer element of the document type and that works. Let me know if you want to do a screenshare and debug through it.
    via by Gayathri Athreya,
  • CONNECT Users - problem
    via by Unknown author,
  • spring | Apache Help Blog | Page 5
    via by Unknown author,
  • GitHub comment 8466#167272512
    via GitHub by wildfly-ci
    ,
    • org.apache.cxf.interceptor.Fault: DocumentType Authorizer 'org.kuali.kra.KcAuthorizer' configured for document type 'ProposalDevelopmentDocument does not implement org.kuali.rice.kew.framework.document.security.DocumentTypeAuthorizer at org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:162) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJAXWSMethodInvoker.java:213) at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:128) at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSMethodInvoker.java:178)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    4 more bugmates