I'm trying to create a widget including a web service deployed by Soaplab. I tried the Web Service Multiple Operations builder but it can't fetch the wsdl of the service because it is a soaplab-typed web service.
This topic has been locked.
10 replies Latest Post - 2009-08-26T14:26:08Z by mburati
Pinned topic A soaplab web service widget
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-08-26T14:26:08Z at 2009-08-26T14:26:08Z by mburati
Re: A soaplab web service widget2009-07-30T14:52:31Z in response to SystemAdminI'm sorry, but we're going to need a little more information than that in order to help.
- What do you mean it can't fetch it?
Does it fail to find it?
Does it fetch it but then not show you the operations?
Does it fetch it but then give you an error/exception (and if so, then what error/exception are you getting)?
- Are you able to fetch it with the Web Service Call builder?
Re: A soaplab web service widget2009-07-30T15:07:57Z in response to mburatiyes, you're right...
Both the Web service call builder and The web service multiple operation builder find the wsdl on the remote site, and they both fail in returning the available operations of the web service.
The exception is a java.lang.nullpointer one and details refer to the com.bowstreet.designer.ui 6.1.2 plugin...
the wsdl file is here
Re: A soaplab web service widget2009-07-30T15:42:08Z in response to SystemAdminWhat version of WPF are you using (including fixpack level)?
That would certainly seem to be a bug. If this is blocking your work, I suggest contacting customer support to open a PMR.
Re: A soaplab web service widget2009-07-31T13:44:14Z in response to SystemAdminIs there any chance that they've changed/fixed something in that WSDL in the last day or so?
I tried to fetch that WSDL once quickly when you first posted that URL and saw an error that might have been what you were reporting, but didn't have time to really look at it then.
Since then, I've tried it late yesterday and then again this morning (with both LWF and WPF Designers) and am not seeing the error on fetching the WSDL (it shows me the operations instead), using the Web Service Call builder.
Can you try it again (restart Designer just in case, create a new model, new Web Service Call builder call, and fetch that WSDL) just to see if maybe something's changed in the WSDL?
Note, another option, since you're using LWF, might be to use the IBM Mashup Center HUB to consume the web service and then expose it as a HUB Feed, and consume that via the LWF REST Service Call builder.
Re: A soaplab web service widget2009-08-04T16:02:29Z in response to mburatiHi,
I'm a colleague of roberto and I'm working with him on the same widget.
I've tried one more time the WSDL as you suggested... and it works today!
Now I've another problem... I've added a Web Service Call builder... it can correctly fetch the WSDL file... what should I do now in order to have my widget running?
Is there any documentation I can use that descibe main steps? I had a look at the help file but I cannot understand exaclty what I should do... At the moment I get the following error message "Main action was not found".
Thanks in advance for your support,
Re: A soaplab web service widget2009-08-05T14:00:30Z in response to SystemAdminIt sounds like you're fairly new to Lotus Widget Factory, and I'm guessing also to WebSphere Portlet Factory.
I suggest going through the tutorials and samples first, and also the WebSphere Portlet Factory Wiki (eg, the Learning Roadmap) which also mostly applies to Lotus Widget Factory (both products are built from the same base):
Once you understand the samples and the local Consumer/Provider mechanisms, it'll make more sense how you do something with the local Data Service that the Web Service Call builder adds to your model's webapp. For instance, you can add a Service Definition builder to define the local service, then a Service Operation builder for the data service created by the WSC builder, and then if you turn on testing support in the Service Definition builder you may then be able to run your service provider model with an auto-generated test UI. If that all works, you can then create a Consumer model and consume that provider with Service Consumer and either View and Form or other UI builders to create the custom UI for your app.
Re: A soaplab web service widget2009-08-26T13:02:08Z in response to mburatiHi,
probably something has changed, we don't know what, but once I fetch the wsdl and operations are shown, the following errors appear (I translate):
describe_arg1_dummy-empty-part is not a WebApp valid object name. The name must be a valid Java identifier and cannot contain spaces
Lotus Widget Factory Builder error
This builder call caused the following exception: java.lang.NullPointerException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
transeq_ws_01.model Emboss_ws_02/WebContent/WEB-INF/models Web Service Multiple Operations:transeq_ws_mo Errore builder Lotus Widget Factory
Re: A soaplab web service widget2009-08-26T14:26:08Z in response to SystemAdminIt looks like the WSDL now includes an operation called describe which has an argument named "dummy-empty-part".
It's likely the hyphens that are causing the problem. It's not clear why, but all the other part names in that WSDL use camelCase to separate the individual words that make up the part name, but that one part name uses hyphens, which appears to be causing the problem.
If you have any control over that WSDL or know who does, you might suggest making the part names consistently use camelCase (as the rest of the WSDL parts and the schema elements and types do in that WSDl/Schema set).
I don't see anything in the WS-I interop spec that disallows such part names though, so you may want to contact customer support to report the issue that the web service builders have with that part name and see if anything can be done about it, if you do not have control over that WSDL.