General JSON and binary support for custom structs

This is a really powerful feature that allows you to use the type
definition to encode and decode structs into a vec of variants. This
should with a little more work make it possible to create a client that
can read from any server without needing codegen for the types on that
server.

lib/Cargo.toml

@@ -31,15 +31,15 @@ client = ["opcua-client"]
 # Console logging just installs a logger that writes out to the screen, useful for general logging
 console-logging = ["env_logger"]
 # The json feature adds serialize/deserialize to all OPC-UA types.
-json = ["opcua-types/json"]
+json = ["opcua-types/json", "opcua-client/json"]
 # Includes all the code to populate the address space with the default node set. This is something that embedded
 # systems may or may not require.
 generated-address-space = ["opcua-server/generated-address-space", "opcua-core-namespace"]
 # Allows a server to register itself with a local discovery server. It does so by becoming a client to the LDS,
 # which brings in a dependency to opcua-client. Omitting the feature saves some memory.
 discovery-server-registration = ["opcua-server/discovery-server-registration"]
 # Methods for XML parsing and loading of nodesets from XML.
-xml = ["opcua-types/xml", "opcua-nodes/xml"]
+xml = ["opcua-types/xml", "opcua-nodes/xml", "opcua-client/xml"]
 
 
 [dependencies]

opcua-client/Cargo.toml

@@ -12,6 +12,10 @@ readme = "../README.md"
 documentation = "https://docs.rs/opcua/"
 edition = "2021"
 
+[features]
+json = ["opcua-types/json"]
+xml = ["opcua-xml", "opcua-types/xml"]
+
 [lib]
 name = "opcua_client"
 
@@ -31,4 +35,5 @@ serde = { workspace = true }
 
 opcua-types = { path = "../opcua-types" }
 opcua-core = { path = "../opcua-core" }
-opcua-crypto = { path = "../opcua-crypto" }
+opcua-crypto = { path = "../opcua-crypto" }
+opcua-xml = { path = "../opcua-xml", optional = true }