I have a WebService that is a service dispacher and it has a Body with the type anyType, so that way I have only one webservice and my client only needs to know the schema to put in the Body for the specific service that he is calling.
Now the problem is that everytime I create a new service or modify an existing one, I need to send the new schema for them. I need a way so I can generate the WSDL with the body replaced with the schema of the desired service, so I don't have to resend the schema everytime it changes.
Thanks in advance!
BTW I'm using Tibco Designer, if it matters :P
Create an XSLT that expects the generic WSDL as an input and takes a path to a schema as a parameter. Use the XSLT to generate the WSDL you want for your consumers.
Related
Let's suppose there is a link to a web-service, e.g. http://1.2.3.4:56789/ws_bla_bla_bla/some_service?WSDL
This address shows xml document, as I guess this is called Initial WSDL.
What is it? Just a list of possibe requests/responces pairs and their xml-structure?
WSDL describes the web service and used to generate client side class which you can used to communicate with service (proxy classes)
couple of generators
http://easywsdl.com/
http://www.wsdl2code.com/
SoapUI is another tool which you can used to test service based on WSDL.
Suppose I have an existing Java service implementing a JSON HTTP API, and I want to add a Swagger schema and automatically validate requests and responses against it without retooling the service to use the Swagger framework / code generation. Is there anything providing a Java API that I can tie into and pass info about the requests / responses to validate?
(Just using a JSON schema validator would mean manually implementing a lot of the additional features in Swagger.)
I don't think there's anything ready to do this alone, but you can easily do this by the following:
Grab the SchemaValidator from the Swagger Inflector project. You can use this to validate inbound and outbound payloads
Assign a schema portion to your request/response definitions. That means you'll need to assign a specific section of the JSON schema to your operations
Create a filter for your API to grab the payloads and use the schema
That will let you easily see if the payloads match the expected structure.
Of course, this is all done for you automatically with Inflector but there should be enough of the raw components to help you do this inside your own implementation
I have to implement a simple bpel workflow, which only executes a select query on database. I have been able to create a Data Service wsdl file. Its flow is attached along with this question as an image file. Please have a look at that first. If you see the image, I some how ended up making a complex structure for parameter "Name" (auto-magically generated wsdl code by wso2 Data Service Server). It has a complex element called "Customer" which has 2 string values "Name" and "nid". I have also copied the wsdl file in case you need to see it. Here: http://pastebin.com/QTKZbdzn
I believe I am not sending any input parameters, while when I try to directly invoke the Data Service without Receive module, it gives an error, saying "No Start activity has been defined for the process".
Anyone who has implemented a similar BPEL workflow for the Data Service, please let me know. The data service works fine! I have tested it separately. thanks!
UPDATE
I ended up making a BPM like this:
I have to change the DSS also, so that I provide some input to the BPM. Like rather than "select * from customer" I am now implementing "select * from customer where nid = ?". It proved to be pretty succesfull. Thanks for helping me out joergl & vimesh. But if you still figure out how query with no where clause would work, update it here.
I have made a bpel flow with data service.
The very first thing we need to do is adding a receive element in the bpel flow. Actually it let us to send a request to the bps and at the same time bps makes a new instance with the request.
So then you can do whatever you wish, like invoking ESB proxies, DSS services, etc. while invoking the external service you can parameters to that request. Even though you are not sending any input parameters to the DSS service you should make a request to the DSS inside BPS in the correct format.(I mean the body part)
You can simply go ahead with the bpel samples available in this and then better start with DSS integrations.
I want to test the results from a WSDL service in a browser like IE9 or FireFox. I know that I can view the WSDL XML, but I want to test the return results of an endpoint called GetEmployeeById that accepts a parameter called Id and returns a class. I am assuming this is all serialized to XML, so a browser would be a good fit for testing this. Is this possible?
In case you are using Visual Studio for .net development, I think something much better than a browser probably would to use:
wcftestclient <url>
which can be called from the command prompt and is part of the tools from visual studio.
The tool will help you to build and receive complex objects and see the results already serialized.
internet explorer let's you make a request with simple string parameters if the WSDL provides enough information.
If you haven't seen it, then probably the WSDL is only for discoverability reasons, probably just points to another service in a different transport protocol, not port 80, if the service is not on port 80 you won't be able to use your browser.
You have another more complex tool called FIDDLER that you can format any kind of http request, as well as receiving any kind of requests, like json for example.
You can use this URL to test WSDL endpoints, send request and see response.
Suppose I have a simple HTTP form that uses POST to pass some parameters
and returns OK or BAD (which I do). A client wants this to be published
as a WSDL description. Looking into WSDL I see an infinite morass of
formalisms, but no practical tools.
Surely there must be a simple way to create a wrapper for a simple form processor?
When you do a POST of the form data, do you use HTML to send the users data? If yes then you have to change both client and server. The idea you encapsulate the form's data in a SOAP envelope and send it over HTTP. So I am not sure what you mean by
a wrapper for a simple form processor