Strange behaviour after milo update

[johannwesely]

Hello,

i updatet the milo/dev1.0 to newest commit. And now i have some strange behaviour showing up in Ua Expert

I just see Bad waiting for Inital Data on my monitoreditems but wenn i browse the Node value i see it has actually been written. Do you have a suggestion what is wrong here? I think version before was from Mar 18 and there i didnt see any problems. Thanks in Advance

[kevinherron]

No, sorry, don't know what might be wrong. The demo server has continued to behave normally with UaExpert through all of the latest commits.

It may be something implementation specific; I think you'll have to debug a little more before I can be useful.

[kevinherron]

Small list of what has changed since March 18: https://github.com/eclipse-milo/milo/commits/dev/1.0/?since=2025-03-18&until=2025-03-28

Perhaps an NPE introduced by the latest commit? 92b3334

[johannwesely]

Hello i mixed some things up i downloaded the version before on Febuary 2 so the Version before has to be the commit on January 31( i guess) so there are a lot more changes Inbetween wich doesn't make it simpler for me. So actually i updated on Mar 18 and had to do some api changes i think i have to look up the changes i made there. And just now i realized something went wrong so i thought it is the new update.

[johannwesely]

So i try to list up the changes i had to do back then

• server.getEncodingContext() changed to .getdynamicEncodingContext() on any appearance
• server.getDatatypeManager() changed to getdynamicDataTypeManager() (only one appearance)
• -UsernameIdentityValidator Removed the boolean from constructor call and added CompositeValidator(AnonymousIdentityValidator.INSTANCE... instead
  is there something i have done wrong ? Or to take more care about ?

[kevinherron]

That seems okay as long as the types being used in the places where you switched to "dynamic" EncodingContext/DataTypeManager are indeed dynamic, i.e. you do not have code generated (or hand coded) classes for these types.

[johannwesely]

Ah I have one Custom Structure i want to use so in this case what do i have to do with the EncodingContext ?

[kevinherron]

When you encode it you would use the static context:

milo/milo-examples/server-examples/src/main/java/org/eclipse/milo/examples/server/ExampleNamespace.java

Lines 1193 to 1194 in 92b3334

	ExtensionObject xo =
	ExtensionObject.encode(getServer().getStaticEncodingContext(), value, binaryEncodingId);

I'm not sure if this is your issue unless some uncaught Exception somewhere is just breaking everything.

[kevinherron]

The ExampleNamespace what updated when this stuff changed to show usage of both dynamic and static types.

"dynamic" types are defined at runtime, e.g. a client learning about them from a server, or a server that can define new structs at runtime. No corresponding Java class to go with it, they all use the DynamicType classes.

"static" types have been defined at compile time. There's a Java class that is used, and it was either generated by a code generator or written by hand.

[johannwesely]

FYI: I changed everything to static (also DataTypeManager) and now it works fine again. I already have written the custom structures by hand so i just use them and at the moment, I can't foresee if there's a case where I need dynamic types.

[johannwesely]

I asume when there is a code generator for milo it will be also the static types ?

[kevinherron]

Yes, code generation is the assumed manner in which you will have actual classes for types. Writing them by hand only works when you have a few.