Hi,

Hmm odd.. however just to doublecheck, since you say “com.prosysopc.ua.types.opcua”, are you trying to generate the base namespace “http://opcfoundation.org/UA/”? That is already generated by us to the mentioned package and compiled as part of the SDK, as the SDK itself uses also those classes. This also means that this very package name cannot very easily be used for any other model. Also the base information model is not yet “user-update-able” either. I can give a more detailed answer if needed.

It is also possible that the above had nothing to do with this. But basically the “IdsCodegenUtils” is a hardcoded-package-private internal helper related to the base information model that optimizes classloading times as we know all NodeIds are numeric ids. Basically the only way (other than bugs etc.) it would appear in the output of Codegen is for the base info model.

P.S.
(yes, the tool probably could be improved to not allow attempting generating the base namespace “again”, but we also use that internally for the SDK as-is currently)

The models can depend on other models. Every model implicitly requires the base model “http://opcfoundation.org/UA/” (but that is nowadays also mentioned in the ‘Models’ xml block). However, I must note that we do not yet support OPC UA version 1.05.x, only 1.04.x. NOTE!, the model might not truly need 1.05 (e.g. every model made with the newest UaModeler will have it like that), but it might not be very easy for you to see if that is a true dependency on 1.05 or not. For now, assuming it is not (if compilation fails after generation it might need it e.g. if some 1.05 type is needed).

In the codegen configurations the models folder is given as the modelSources/modelSource entry (you can have multiple, every xml files in those folders is interpreted as a model file). The “No model for namespace: http://opcfoundation.org/UA/,” error meant there was not a model that would provide that namespace. All configured models are loaded. When generating the tool will pick up the required model with the namespace and the model’s their dependencies (recursively).

If you look at the SDK distribution zip (unzipped), the codegen/commandline/models/ (or codegen/maven-integeration/maven-integration-sample/models/) do contain the base information model ‘Opc.Ua.NodeSet2.xml’. So basically you must have both your model and the base model in the folder. Then you should (hopefully) be just able to generate your namespace. Alternatively if you just put your model to that folder and edit the sample configurations it should generate (with the assumption that there is no 1.05 “thing” that breaks it)

P.S.
Mentioning just in case, basically while it might look that you could use a different version of the base model as it is just a file, it will not work in practice due to multiple reasons, but skipping that for now as it is kinda a long post. Also we are generally aware that at some point we need to support 1.05 information models, but IF this model truly needs it it would be the first one we know of.