Customizing Web Service Resource Document

[Hurtz]

I'm trying to adapt a document in a web service resource. The import of the fields did not work and so I tried to build the document according to the required request.

I want namespaces to assign to the node. When I give, for example, the node "Process" the namespace test, then the following code is generated:

<test:Process xmlns:test="test">

However, test is not intended to refer to "test", but to a URI. In addition, this namespace is to be defined in Soap Envelop.

At which point I have to make the changes so that my document is set up in the desired way?

[Steve]

Hi Hurtz,

Could you explain the error when you tried to import the fields? When was this importing from an XSD or WSDL?

In the Web Service Resource you can build a document and add the namespace on the associated element.

1) Open or create a web service resource
2) Create a new document (you can rename this to anything you like, bu right clicking the document name and clicking on rename)
3) Add a node to the Document called: Process
3) Underneath the element, add the namespace URI (e.g http://mytest.com/uri)

This will generate a document as described below. It does not matter that the namespace is defined in the Soap Envelope. You can define the namespace at the Element level. Also the prefix does not need to match 'test'. When you associate a namespace with an element, Ebase will automatically create a prefix for you. This is just used as a namespace lookup map.

You can click on the yellow <xml> icon above the documents to view a sample of the XML generated.

If you are asking whether you can substitute a namespace URI. Then the answer is no, this cannot be done, it must be entered at design time.

I hope this helps.

Steve

[Hurtz]

Thank you for the quick reply. I tried to include the WSDL of a starter store Websphere Commerce . In addition I had referenced the WSDL file via URL. The XSD files are not loaded. The WSDL is not integrated properly.

Now I 've found the error and integrated the WSDL and all associated XSD files locally . Now the documents and the fields corresponding to the WSDL is generated. This procedure is written in the WebSphere Commerce documentation. A web service client can not be generated via the URL. IBM : " Although you can read the WSDL files over the Web , They can not be used to generate a web client If you are creating a Web client based on the WSDL files , you can copy the WSDL files into your development environment . . "

Now, however, I have the problem that there are numerous fields . When I click on "Import fields from external resource" in my form , then do not appear to me all the fields of the resource. Furthermore , I then tried to delete unnecessary fields . This reduced the number of fields that can be imported. The required fields are unfortunately still not on the list and can not be imported .

Hopefully you can help me.

[Steve]

Hi Hurtz,

I am wondering whether you had the appropriate "Resource Fields" created in the web service resource. You should be able to right click a field to attach a 'Resource Field'. Also the element should have an XML type (e.g String, Integer).

If the fields are generated automatically, all elements within a repeating node will be created as table and columns. You cannot import fields from the resource if they are a column of a table. You will need to create a table in your form and import the columns from the resource from within the table dialog.

I was a little unclear whether you had a WSDL/XSD that you could import?

Could you save the WSDL and send to support@ebasetech.com, and I have have a look for you. We only support importing document/literal web services.

I suspect that either you are missing a resource field for the element, or the element is a column of a table.

Kind regards

Steve

[Hurtz]

Hi Steve,

You have been right. The "fields" were included as columns in tables. When I import the tables, it works as you said.

Maybe you can help successfully submit the request described in the email and receive an appropriate response to me still.