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
Related
After having used the FSharp.Data TypeProviders in several different projects working on JSON I was look for a similar approach to consuming WSDL based services. Seeing this example I was hopefull. Unfortunately that doesn't work using mono on a Mac.
Are there any alternatives or solutions to the error
"The type provider
'FSharp.Data.TypeProviders.DesignTime.DataProviders' reported an error:
The .NET SDK 4.0 or 4.5 tools could not be found (FS3033)"
The following is written with very little knowledge of mono, but some knowledge of this WSDL type provider. I use it a lot and have some experience in all the quirks, including reading the source of it to try to understand what has happened where and why from time to time. Add also some knowledge of the svcutil-tool in general and the bugs and what not of this sub par tool.
I guess the main problem here is that the "path" to svcutil on mono is wrong or svcutil is missing entirely. Or a permutation of that problem like missing some registry key for pointing to svcutil path.
On the other hand I do think that svcutil should be available also on mono.
The WSDL provider is an non-erasing type provider and generates a proxy by using the svcutil for generating code and then compiling it. Making sure you have the svcutil available and then making sure its in path/registry/whatever, MIGHT help you. Otherwise, Im 99% sure, you will not be able to use this type provider on mono unfortunately. The unsure part here is if you generate a library in a windows environment, and then reuse this dll, within mono, that might work.
Looking at the source at github: https://github.com/fsprojects/FSharp.Data.TypeProviders/blob/master/src/FSharp.Data.TypeProviders/Util.fs#L106 (line 106++)
and
https://github.com/fsprojects/FSharp.Data.TypeProviders/blob/master/src/FSharp.Data.TypeProviders/TypeProviders.fs (parts where SvcUtil is used)
you might get a clue as to where, how and what not, to make sure the SvcUtil.exe is available at correct paths.
https://github.com/fsprojects/FSharp.Data.TypeProviders/blob/master/src/FSharp.Data.TypeProviders/Util.fs#L82 does reference a few registry keys and also adds a few paths hard coded.
Hopefully that might fix it for you by making sure you actually have the svcutil at "correct" path...
I do not like this dependency on svcutil (it has bit me too grrr), or other external tools in the type providers, in general, and hopefully some kind soul will embark on a mission to rewrite this at some time.
I need to translate SAP BO InfoView interface. The language we require doesn't have native BO language pack.
I discovered a bunch of .properties files, translated them, but not all of the texts was converted.
Maybe someone could give me some advices, or some ideas for solution?
Thanks.
I would think any text not in the properties or xml config files are in 2 main places:
Hard coded in the JSP files. A general search and replace should work at finding where these are.
The Java applet WebI controller. This one is compiled and packaged jar. I believe this is where the text that you haven't been able to translate yet resides. This one will be trickier to update and changes to it will most likely end any support from SAP if you run into troubles.
I've been using spring.net with xml configuration for some times, and I just saw that spring team released CodeConfig a month ago.
What I like about the xml config is that if I have a problem on the live server I can easily change the xml configuration to enable some specific debugging settings, or disable a specific component simply changing the xml configuration.
What is the advantage of using a code configuration instead of an xml configuration other than compile time check?
With code config, possible benefits you could get are:
Better refactoring support; e.g. renaming an injected property
More compact configuration, compared to xml
Developers can use code, in which they are often more at home than in xml
Benefit of the last point is also that developers new to the framework will have a significantly less steep learning curve than with the xml config.
From the docs:
While there are several positive
aspects to expressing configuration
metadata in XML files, there are also
many problems with this approach
including the verbosity of XML and its
heavy dependence on string-literals
which are both prone to typing errors
and unusually resistant to most modern
refactoring tools in use today. The
CodeConfig approach removes these
problems by providing a type safe,
code-based, approach to dependency
injection. It keeps the configuration
metadatda external to your class so
your class can be a POCO, free of any
DI related annotations.
Just to highlight one thing, you can mix and match configuration styles. From within a CodeConfig class you can refere to XML config files using the [ImportResource] attribute (see here), and in the XML you can use the namespace (see here).
Cheers,
Mark
I've done a bit of searching around for a good RDF editor. But I'm not sure what one is the most utilised. Can anyone recommend one? I'm looking to write some simple RDF and maybe parse one or two RDF documents.
Many thanks
Are you looking to work at the raw Triples level and in a human readable/editable syntax such as Turtle? If so you can get by just with Notepad or maybe try out my rdfEditor which is an early Alpha release but gives you nice syntax highlighting, checking and auto-completion. This is designed only for editing raw RDF data and does not give you any IDE tools for creating your data.
If you want to work at the class/individual (i.e. more abstract level) and have the editor care about the underlying RDF then you probably want to try either TopBraid Composer or Protege
There's a new TextMate bundle for the Turtle RDF language which offers a bunch of cool features. https://github.com/peta/turtle.tmbundle
Judging from the screenshots, Rhodonite http://rhodonite.angelite.nl/ makes a good impression.
Unfortunately it seems to be abandonded and I could not get it to run on Windows7 (x64). But maybe it runs on your system (download is Windows only)
If you're looking for a web-based RDF / Ontology editor, have a look at Web Protege, an open source web-based project by the Protege team mentioned in the accepted answer.
If you need a more advanced RDF editor, look at RDF and SPARQL plugin for JetBrains IDEs. It supports all RDF 1.1 formats as well as SPARQL 1.1. Including the RDF-star and SPARQL-star extensions.
It features syntax highlighting and validation, prefixed name completion, SPARQL 1.1 Protocol support and much more.
You don't have to buy a JetBrains IDE, since the plugin works with the free versions too.
I have two files, one with webservice description (wsdl), second with data structures used in webservice (xsd). I have nothing more, webservice doesn't work yet. I need to merge them into one, because Delphi 7 WSDL Importer doesn't handle included xsd files to well. Where can I find tool to do it?
EDIT
I copied xsd content into <types> section and it works. I tried it before, but I must have made a mistake and Delphi WSDL import didn't work. I have to improve my copy/paste skills.
You might change the include into an import.
I have seen various tools handling either one better than the other.
As an alternative, use XMLSpy: here you can edit your WSDL and import your XSD into it.
This question has an answer on how to place the content of the XSD into the WSDL.
I copied xsd content into section and it works. I tried it before, but I must have made a mistake and Delphi WSDL import didn't work. I have to improve my copy/paste skills.
You could also try the updated importer from here:
http://cc.embarcadero.com/Item/24535
Support was added for external schema files.