Saxon

The class UntypedAtomicValue has been merged into its parent class, StringValue. You can detect whether a StringValue is untyped atomic by calling getPrimitiveType(), which will return BuiltInAtomicType.UNTYPED_ATOMIC. I'm afraid I forget exactly why this change was made

InstructionInfo (an interface) was present in Saxon 10 but no longer used: there were no classes that implemented this interface. At one time it was used as part of the TraceListener interface, but in that role it had been replaced by net.sf.saxon.trace.Traceable.

Both these classes were part of what we call the "system programming interface" - available to applications that want to do deep integration, but not guaranteed stable from one release to another. If you want the best possible stability, try to stick to interfaces in the s9api package.

I would recommend you move to the latest maintenance release on the 12.x branch, that is 12.6 rather than 12.2, to get all the latest bug fixes.

Hi @Michael Kay, Thanks for your quick reply.

This is regarding InstructionInfo class, It has a method called getProperty("select") :

  StructuredQName getObjectName();

  Object getProperty(String var1);

  Iterator<String> getProperties();

Since this interface is removed tried modifying my code by using Traceable instance but not able to succeed to getThe properties. any code snippet/test class to achieve these features

Well, as far as I can see in 10.x the interface InstructionInfo has no concrete implementation classes, so I don't know where an instance of the class would be coming from to enable you to call getProperties().

If we go back a little earlier, in 9.9, InstructionInfo was passed as the first argument to TraceListener.enter(), and that's where you're most likely to encounter it. At that stage many XSLT instructions and XPath expressions implemented this interface, and they returned different sets of properties. In 10.x TraceListener.enter() expects a Traceable, which has an interface gatherProperties(), to which you supply BiConsumer<String, Object>`.

I think that if you do something like

HashMap<String, Object> props = new HashMap<>();
traceable.gatherProperties((k, v) -> properties.put(k, v));

then this will put the properties into a map for you.

However, the default implementation of TraceLlistener.enter() doesn't examine the properties of the supplied Traceable, because the properties to be traced are provided in a separate argument, the second argument of TraceListener.enter().

I think the design was changed to allow dynamic properties to be included in the trace output as well as static properties.

Hi Team,

I am not finding https://mvnrepository.com/artifact/com.saxonica/Saxon-EE 12.3 version in maven repository, I am missing anything?

Its related to : https://saxonica.plan.io/issues/6024

Ashok Kumar NV wrote in #note-5:

I am not finding https://mvnrepository.com/artifact/com.saxonica/Saxon-EE 12.3 version in maven repository, I am missing anything?

You can download Saxon EE from https://www.saxonica.com/download/java.xml or use Saxonica's Maven repository https://dev.saxonica.com/maven/, e.g. https://maven.saxonica.com/maven/com/saxonica/Saxon-EE/12.5/index.html. See also https://blog.saxonica.com/norm/2020/10/02-maven.html.

Hi Norm Tovey-Walsh Tovey-Walsh,

Can we wait to have this feature? Kindly update the progress so it will be helpful to take further actions in our product.

Regards, Ashok

Sorry, what exactly is holding up your progress? If it's the Maven repository you need, please use Saxon's Maven repository. (Note that because Saxon-EE is a commercial product requiring a license, you can't expect to do a fully-automated Maven install).

We have the license and we are using Saxons 12.5, Since we are not supporting UntypedAtomicValue in the latest version, My assumption was this will be put it back to the product.

No, we have no intention to reintroduce UntypedAtomicValue as a separate class. As I think I explained, these are internal classes forming part of the low-level "system programming interface", which is available for use (and may be the only way of doing low-level instrumentation) but is subject to change between releases. If you want a stable API, you need to stick to classes in the s9api package. In 12.5 untyped atomic values are represented as instances of the StringValue class which can be examined to see if they are untypedAtomic using the isUntypedAtomic() method.