I'm trying to import schema files in the WSO2 Governance Registry (4.6.0) which include an import to other xsd's. The import happens using the include element.
Eg:
<xs:include schemaLocation="OtherSchemaToImport.xsd"/>
When uploading the XSD I receive following error:
Unable to upload file File upload failed. Failed to add resource
/_system/governance/myXsd.xsd.
Could not read the XML Schema Definition file. this.schema.needs
When removing the include, and specifying all elements in one XSD, the problem disappears, this is however not an acceptable solution.
Could you please give me some advice, things to try or a solution.
You can overcome this when you upload all resources as *.gar file. Where, you have to edit import definition with the location where you keep the imported resources and make a archive file and upload.
Related
I am trying to create a blueprint for entity-client sub-generator by following the official guide. Tried several times. But when I try to use the generated blueprint, while importing jdl, it always says
Trying to use blueprint generator-jhipster-helloworld
WARNING! No blueprint found for entity-client falling back to default generator
then it generates the entity clients in the default way.
I can see the blueprint is linked into the node-modules folder of the generated app.
If anybody has created a simple working "entity-client sub-generator" blueprint, Please share the code with me. For example, "that adds <h1>lorem ipsum<h1> on the top of component.html file for the generated client of entity (on importing a simple jdl with just one entity)" would be sufficient.
Sample JDL
entity Item{
code String required,
description String required,
quantity Integer required
}
Best Regards.
I'll be gratefull if you can help me with the following error: When I try to import a WSDL file in Azure API management I have the next error:
WsdlImportRuleImportNotSupported : WSDL Import is currently not supported
Is there a way to solve it ?
thank you!
If you look in the WSDL file you are trying to import there is a wsdl:Import element that references an external file. We don't support importing WSDLs that are split into multiple files. We can import eternal references XSD schemas though.
If your wsdl is coming from a later WCF service you can request the wsdl using a query parameter ?singleWSDL and it will merge the WSDL into a single file for you. There are also OSS tools on GitHub for doing a WSDL merge.
I am trying to update the metadata (programatically, from Python) of several CSV/JSON files that are exported from BigQuery. The application that exports the data is the same with the one modifying the files (thus using the same server certificate). The export goes all well, that is until I try to use the objects.patch() method to set the metadata I want. The problem is that I keep getting the following error:
apiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/storage/v1/b/<bucket>/<file>?alt=json returned "Forbidden">
Obviously, this has something to do with bucket or file permissions, but I can't manage to get around it. How come if the same certificate is being used in writing files and updating file metadata, i'm unable to update it? The bucket is created with the same certificate.
If that's the exact URL you're using, it's a URL problem: you're missing the /o/ between the bucket name and the object name.
I have a couple of XSD's in my application. Something like the below,
XSD
common
common.xsd
request
request.xsd
response
response.xsd
I have to use the common.xsd in the request and response xsd's. So I have used import statement. The config is as below,
<xsd:import namespace="www.some.namespace.com" schemaLocation="../common/common.xsd"/>
The problem here is, this works absolutely fine in Tomcat. But when I deploy the same application in WebSphere, it is throwing error as file not found. In the logs, I could see WebSpher is looking for the xsd in the IBM installation folder. The path it is looking is, "C:/IBM installation folder/common/common.xsd".
Can anyone help ?
Thanks in advance.
Just remove the schemaLocation attribute of the import element. Just keep the namespace attribute alone and be sure that you are importing the correct namespace.
I have several services which I would like to deploy to azure.
Each service has an xsd schema which is placed in the project where the service is.
In the validation module I try to load the schema this way:
XmlSchemaSet schemaSet = new XmlSchemaSet();
Uri baseSchema = new Uri(AppDomain.CurrentDomain.BaseDirectory);
string mySchema = new Uri(baseSchema, "LogInService.xsd").ToString();
XmlSchema schemaLogIn = XmlSchema.Read(new XmlTextReader(mySchema), null);
schemaSet.Add(schemaLogIn);
... but apparently the path AppDomain.CurrentDomain.BaseDirectory is incorrect, and when I try to deploy the service I get the following error:
Could not find file 'F:\sitesroot\0\LogInService.xsd'
(on dev this code is working perfectly)
My question is, where am I supposed to put the xsd files - or how can I change the code above so it will work on the cloud?
I think your path is correct, what is probably happening is that your xsd is not being included in the package that is being uploaded. Check the properties of the file, in particular the build action property to make sure it will be copied.