I'm trying to configure locate the DTDs for Saxon extensions and java types (IntelliJ editor configuration).
The namespaces:
http://saxon.sf.net
http://saxon.sf.net/java-type
...have no DTDs available in the classpath. I've looked in the jars and everywhere and can't find an explanation or references to such DTDs on the web. I'm able to use extensions and java types, such as saxon:evaluate, successfully.
I'm using Saxon 9B.
There are no elements or attributes in these namespaces, only functions and types. DTDs define elements and attributes. So there would be nothing for a DTD to say.
What problem are you actually trying to solve: what would you want to do with this DTD if it existed?
Related
I know that there is a way to generate the client-side code from the swagger yaml with swagger-codegen, but is there a way to generate the swagger yaml with the C++ annotations similar to what can be done in Java.
There seem to be annotation libraries available for other languages e.g python C# (https://swagger.io/blog/api-development/swagger-annotation-libraries/) but I am not able to find any support for C++.
I don`t think so. As far as I know the Swagger Core Annotations are part of the Swagger Core Project, and in the documentation you can find:
Swagger Core is a Java implementation of the OpenAPI Specification.
Current version supports JAX-RS2.
Also the Prerequisites says:
You need the following installed and available in your $PATH:
Java 8
Apache maven 3.0.4 or greater
Jackson 2.4.5 or greater
Update:
I'm not quite sure if oatpp-swagger can fit your requirements.
To set up the docbook toolchain with Saxon, in our classpath,
I understand we need a JAR file with some extensions.
Now I can't find it on the internet.
Here is the information from Bob Stayton's wonderful book on "Docbook: XSL"
The DocBook stylesheets have some custom extension functions written specifically for the Saxon processor. These functions are contained in a saxon653.jar file that is included with the DocBook distribution in its extensions subdirectory. There may be several saxon jar files there, labeled by the version number of Saxon. Use the one closest to your Saxon version number. See the section “DocBook Saxon and Xalan extensions” for a more complete description of the DocBook Saxon extensions.
I had all this set up on the Computer Science server at the University where
I teach. Unfortunately, that server was lost. I am trying to recreate
the toolchain. I use docbook to create the class notes for two of my courses. And I need this to set up my classes for the Spring 2017 semester.
I located this in the sourceforge docbook project under files
docbook-xsl-saxon-1.00
NOT the docbook-xsl-doc-1.79.1.zip to which webpage points
I`m using Apache Tika 1.4 to extract content from my documents. But it also comes with org.bouncycastle.* classes, and I use another version of bouncycastle which is conflicting with the Tika packages.
If the Tika was using the bouncycastle (bcprov) jar, I could exclude that using exclusion tag from Maven, but the TikaApp has copied the org.bouncycastle classes into it, so, I cannot exclude them.
There`s some way to remove this package without recompiling or branching Apache Tika and set to use another JAR to this specified package or something like that?
Thanks
Your problem is that you're using completely the wrong packaging of Tika!
The tika-app jar is a standalone, runnable jar, containing all of the Tika code + all dependencies required to let it run. It's intended to be used from the command line, standalone, to allow non-Java users to call Tika, and to allow for easy testing.
If you're writing your own Java application, which it sounds like you are, you will want to depend on the tika-core artifact as a minimum. That contains all the interfaces, the mime detection, service loaders etc. You'll then almost certainly also want to depend on tika-parsers , which provides all the code to do the actual parsing of the file formats, along with pulling in their required dependencies. This gives you the full control you seem to want.
Finally, there's also an OSGi bundle available, for those who prefer the control and classloading that OSGi offers, that's in the tika-bundle artifact. There's also a CXF powered JAX-RS version, which offers Tika's services over a RESTful interface, that comes in the tika-server artifact.
I am trying to migrate from axis to cxf. Here's the problem i am facing: some packages has incorrect names being generated by cxf. Specifically there is a difference for a types, that located in xsd files, imported to main wsdl through <s:import> element: looks like cxf prefers xsd's file namespaces while axis not. This is gonna take much more time to migrate if i should change package names for all xsd types. Is it possible to ignore xsd namespaces?
CXF's wsdl2java has a -pnamespace=package flag that can be used to map namespaces to non-default packages.
I have WSDL files and would like to compare and match WSDL elements in these files syntactically. Do you have any suggestions for Java libraries that can be used finding syntactical similarities between two terms in Web (for me, wsdl elements)?
Thanks.
There's also WSDL Analyzer which builds upon the most recent version of the Membrane SOA Model. It's a web application which not only allows you to validate and check your
WSDL against best practices but also lets you compare different versions of your WSDL.
Disclaimer: I'm one of it's developers.
Well, you can use SOAPUI to load the wsdl definitions and compare them.
Including link with some documentation relating to your question. Hope is of some help.
http://www.soapui.org/SOAP-and-WSDL/working-with-wsdls.html
edit:
Also, check out http://www.membrane-soa.org, which as some libraries for comparing wsdl files.
Some specific examples are here: http://www.membrane-soa.org/compare-wsdl-java-api.htm