Hi,

(I’m assuming SDK 4.x)

That is prone to errors and some parts are incorrect. Sorry for sounding rude, but based on what did you end up code like that? Did you read the Codegen manual “Prosys_OPC_UA_SDK_for_Java_Codegen_Manual” in the ‘codegen’ folder that is in the SDK zip you downloaded? And then Chapter 18 in the Client tutorial as the manual refers to that on using the generated classes?

Anyway a short list of things that are wrong:
– The constructors of the generated classes should never be called manually!! This is really important! They are generated as protected for a reason (they might have been public in some older versions accidentally), SDK will call them for you (and must call). Each generated class models a single node (type). OPC UA types usually have a group of nodes. Basically everything goes wrong if you try to instantiate them manually (rest of nodes are basically “null”). Instead use the AddressSpace.getNode version that takes the Class parameter and pass the FiberPulseImpl.class (this is assuming you know the node is of that type, otherwise you will need to do instanceof etc checks)
– The model must be registered outside of the classes that would be registered, e.g. after creating the UaClient object would be a good place (anyway, before you call getNode so that it knows internally to return correct UaNode subtype, as those are what are generated), note that some of the generation targets will create proper services META-INF files that we’ll can use internally to automatically register the model for you when the client connects, see the manual for more info
– While not an error, I would not make the code for Subscriptions etc. within the node objects, since basically each UaNode object is a temporary object that encapsulates state from the server. Based on the AddressSpace.getCache parameters it will be recreated if it is too old when you next time call getNode (unless you hold a reference to it manually and use that instead)

So just do
0. Generate the model
1. Assuming you are not using the automatic model registration detection, call client.registerModel, otherwise it will be automatically found (assuming the generated resource files are within classpath)
2. Call client.getAddressSpace.getNode(nodeId, FiberPulseImpl.class) and use it

Oh, sorry, that explains a lot.

That is quite an old version, we (and OPC UA in general) have come a long way since (but there is still a lot to be improved at least documentation-wise…).
Basically for SDK 3.x we had to mostly rebuild the codegen pretty much from scratch. However the outputs are mostly the same (at least the core concepts are the same, 4.x did have other changes for the SDK, https://downloads.prosysopc.com/opcua/Prosys_OPC_UA_SDK_for_Java_4_Release_Notes.html#version-4-0-0 which also affected the outputs, e.g. “stack classes” are now part of the SDK etc.).

My suggestions should mostly apply to 2.x (but it has been so long, i.e. I might forget something). Anyway for that you will need to do the model registration manually, since automatic registration ‘client_model_provider’ ‘server_model_provider’ generation targets were added in 4.x. Also the registration might only work after UaClient.connect() has been called (but try after creating the UaClient first, if that gives an exception, then register after connect())

Also it should be noted that after 2.1.2 the generator did get some bugfixes in subsequent 2.x releases. Additionally, OPC UA 1.03 and 1.04 have added more features that the 2.x SDK nor it’s codegen cannot use (e.g. 1.03 added Structures with optional fields and Union Structures), i.e. if you try to generate a model that is using any 1.03 or 1.04 features or types any of the following could happen during generation: wont work, will fail silently or generates incorrect classes (e.g. since it doesn’t know optional structures are a thing, it would treat them as normal ones, so binary encoding would be incorrect). So generally I recommend to update to 4.x, where possible.