Re: Problem regenerating schema for AAI v14 #aai

Venkata Harish K Kajur
 

Hi Keong,

The html and yaml gets automatically generated when you run install but the xsd was never part of the autogenerate maven profile.
For Beijing and earlier release, we never auto generated it. In order to run the generation of the xsd, here is the command:

cd ~/LF/aai/aai-common/aai-core/
mvn -PgenerateXsd install -DskipTests -Dgendoc.version=v14

I have actually noticed that recently within the internal release and realized that it makes sense for xsd to be also auto generated.
I am not sure why it was left out from the autogenerate profile but when developing the model driven feature, I ensured that the auto generate also does xsd generation.
Once that feature gets delivered to Casablanca, there wouldn't be a need to run the profile manually.

Thanks,
Harish

-----Original Message-----
From: onap-discuss@... <onap-discuss@...> On Behalf Of Keong Lim
Sent: Monday, July 30, 2018 1:18 AM
To: onap-discuss@...
Subject: [onap-discuss] Problem regenerating schema for AAI v14 #aai
Sensitivity: Confidential

Hi all,

I have updated the AAI v14 OXM file with new schema changes, as per https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_AAI-2DCCVPN-2BSchema-2BProposal-2Bfor-2BCasablanca-2BRelease&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=f44eG3iZaja2ozEA2yRZnQ&m=wGqk6dbredJelbUbsEpMZwAY7EZaQ2IW6NPX6da4Rdk&s=I5IYHqPmi6w9XAFjJu9BmOCMuFWZ6GONpoOzMWG0hCQ&e=.

I have followed the instructions in the tutorial: https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D10783023&d=DwIFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=f44eG3iZaja2ozEA2yRZnQ&m=wGqk6dbredJelbUbsEpMZwAY7EZaQ2IW6NPX6da4Rdk&s=2QdJLPrk8KGnZTXeCxUdx2nDm4yfOZoVSHCE161etzo&e=
e.g. steps 7 and 20:

===
Rebuild aai-common first:
$ cd ~/LF/AAI/aai-common
$ mvn clean install
Should result in BUILD SUCCESS
etc
===

I can find the generated files "aai_swagger_v14.html", "aai_swagger_v14.yaml", which are new and expanded compared to their v13 versions.

However, the "aai_schema_v14.xsd" is not changed at all. There is a placeholder file already committed to src/main/resources/aai_schema directory, with the contents as a copy of the v13 version. It appears this file was simply copied to the target/classes/aai_schema directory, rather than being regenerated from the new v14 OXM file.

Why is the v14 XSD file not automatically regenerated by this mvn command?
What command is required to regenerate the XSD file?

The pom.xml file in aai-core appear to have <execution> tags for <id>autoGenerateYaml</id> and <id>autoGenerateHtml</id>, but nothing for "auto generate XSD". Is this correct or broken?


Thanks,
Keong


Customer Experience and Platform Integration R&D Dept
--
Keong Lim, Huawei Technologies Co. Ltd (keong.lim@...) Ground Floor, Suite 1, 5 Lakeside Drive, BURWOOD EAST VIC 3151 AUSTRALIA
--
"If ye love wealth better than liberty, the tranquillity of servitude than the
animating contest of freedom-go from us in peace. We ask not your counsels
or arms. Crouch down and lick the hands which feed you. May your chains sit
lightly upon you, and may posterity forget that ye were our countrymen!"
- Samuel Adams

Join onap-discuss@lists.onap.org to automatically receive all group messages.