You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi ... In java-taxi-1.0.0, there are a bunch of xml object classes like org.mitre.taxii.messages.xml11.ServiceInstanceType, org.mitre.taxii.messages.xml11.CollectionRecordType, and many others, that mapped TAXII xml entities onto Java objects. But in java-taxi-1.1.0 and 1.1.0.1, these are gone. What is the reason? It seems to me they are useful for Java client applications that want to pass around java TAXII objects within their own code, and not just read the TAXII returned xml once and discard it.
I do see that these classes are in java-taxii-clients-all.jar, but that is billed as just being for examples. Furthermore because that jar contains not just java-taxii classes but many third-party java packages, it is not suitable for including in a regular build path.
Thanks for shedding any light on this ...
The text was updated successfully, but these errors were encountered:
Hi ... In java-taxi-1.0.0, there are a bunch of xml object classes like org.mitre.taxii.messages.xml11.ServiceInstanceType, org.mitre.taxii.messages.xml11.CollectionRecordType, and many others, that mapped TAXII xml entities onto Java objects. But in java-taxi-1.1.0 and 1.1.0.1, these are gone. What is the reason? It seems to me they are useful for Java client applications that want to pass around java TAXII objects within their own code, and not just read the TAXII returned xml once and discard it.
I do see that these classes are in java-taxii-clients-all.jar, but that is billed as just being for examples. Furthermore because that jar contains not just java-taxii classes but many third-party java packages, it is not suitable for including in a regular build path.
Thanks for shedding any light on this ...
The text was updated successfully, but these errors were encountered: