13:55:11 Deployment Message : weblogic.application.ModuleException: java.lang.RuntimeException: Invalid schema document passed to AbstractDataBinding.addSchemaDocument, not in W3C schema namespace
How to handle the above exepction.
Related
There is an API running on the CloudHub (Mule 4.4) and protected with the standard SLA Rate Limit policy.
We have a requirement to provide a custom error message body instead of the default one generated by the policy when authentication fails.
The default error body returned by the policy looks like this:
{
"error": "Invalid client id or secret"
}
When I run the application in debugger in Studio, it is intercepting the exception and I can see that the error type produced by the policy is CLIENT-ID-ENFORCEMENT:INVALID_CREDENTIALS.
This as well indicates that the exception is reaching the Mule application itself. So, it must be a way to override the default handler with the custom one.
First, I've tried adding the handler for error type to HTTP request processing flow beside the other API Kit errors. It did not intercept the error.
Then, I've defined a separate error handler for the error type and set it as a "Default Error Handler" in the global configuration.
<configuration doc:name="Configuration" doc:id="7a7e22cd-2ee7-42ee-af15-eaf2693d72d9" defaultErrorHandler-ref="apiErrorHandler" />
<error-handler name="apiErrorHandler">
<on-error-propagate enableNotifications="true" logException="true" type="CLIENT-ID-ENFORCEMENT:*">
<ee:transform xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">
<ee:message>
<ee:set-payload><![CDATA[%dw 2.0
output application/json
---
{message: "Unauthorised"}]]></ee:set-payload>
</ee:message>
</on-error-propagate>
</error-handler>
This didn't work as well.
Can you pls advise the right way to customise the error messages returned the standard SLA policy?
To be clear, I'm well aware that it is possible to code your own custom policy. But the intention is to keep the standard one and just customise the response for some error types.
This is not currently possible. Policies have to handle their own errors, they can not be intercepted in the flow.
I have been given with the credentials and endpoint from Radixx but when I used to use the endpoint to get security token . I am getting this error :
Additional Source Information: ERR9999: Unexpected error in GetSecurityGUID.Error Generation Source Location: DSAIXUAT1APP01 Session ID: -1 Error Details: Your user ID and Password combination did not validate.
API Store - Error
Configured WSO2 to take in an external identity service provider
Logging into the store with the oidc configurations redirecting a user to a different login page
API Store - ErrorError occurred while executing the action generateApplicationKey
Caused by: org.wso2.carbon.apimgt.impl.workflow.WorkflowException: Error occurred while executing SubscriberKeyMgtClient.
Caused by: org.wso2.carbon.apimgt.api.APIManagementException: Can not create OAuth application : DannyApp_PRODUCTION
Caused by: org.wso2.carbon.apimgt.keymgt.stub.subscriber.APIKeyMgtSubscriberServiceAPIManagementException: APIKeyMgtSubscriberServiceAPIManagementException
Caused by: org.wso2.carbon.apimgt.api.APIManagementException: Error occurred while executing SubscriberKeyMgtClient.
at org.wso2.carbon.apimgt.impl.utils.APIUtil.handleException(APIUtil.java:1507)
[2019-01-23 15:59:43,414] ERROR - APIUtil Error occurred while creating ServiceProvider for app Danny Developer_DannyApp_PRODUCTION
org.wso2.carbon.identity.application.common.IdentityApplicationManagementException: Already an application available with the same name.
I have a validate action in the OSB request pipeline which raises an error if the request is not according the schema.
In the error handler, I remove the header info and add some required header info before replying with a failure. However the response I get is the request body and not the fault which is in $fault. Is there a way to have OSB generate a standard soapFault using the $fault variable instead of having to manually create the error response body?
I'm having the same issue with the general error handler defined for the business service and the pipeline error handler when internal errors are raised.
Additionally, Is there a best-practice on how this is usually done for normal services and in case of passthrough services?
thanks
I´m binding a fileupload control to a managed bean. The property within the managed bean is of type "UploadedFile". When I save the Bean I get the following client side javascript error:
dojo/parser::parse() error SyntaxError: Unexpected token )(…)
This occurs only with managed beans. When the control is bound to a domino document there is no such error.
Here is some code for you: I use the very basic version of the control and instantly get the javascript error:
<xp:fileUpload id="fileUpload1"
value="#{registration.User.attachment}">
</xp:fileUpload>
Does anyone have experience with this or is there any property which I forgot to set?