SOAP Binding Issue

Hi All,
My Requirement was to publish a RFC as a webserice in PI7.1.
I did the entire configuration and publish display the sender agreement as webservice and took the WSDL from there.
when I test this using SOAP UI tool then this WSDL works fine where the URL is standard
http://host:port/XISOAPAdapter/MessageServlet?channel=:CommunicationComponent:ComminicationChannel
But when I an tring to Use this wsdl in EP I am getting following error.
Cannot Chosse this operation:There is no associated SOAP Binding.
Am I doing Something wrong??
Please help.
Regards,

Hi Suraj,
Sorry for late Response.
Please find the below
- <wsdl:portType name="Z_QMNC_SAVE_CORRECTIONS.PortType">
- <wsdl:operation name="Z_QMNC_SAVE_CORRECTIONS">
<wsdl:input message="rfc:Z_QMNC_SAVE_CORRECTIONS.Input" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" />
<wsdl:output message="rfc:Z_QMNC_SAVE_CORRECTIONS.Output" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:binding name="Z_QMNC_SAVE_CORRECTIONS.PortTypeBinding" type="rfc:Z_QMNC_SAVE_CORRECTIONS.PortType" xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
- <wsdl:operation name="Z_QMNC_SAVE_CORRECTIONS">
<soap:operation soapAction="http://sap.com/xi/WebService/soap1.1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
- <wsdl:input>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:input>
- <wsdl:output>
<soap:body use="literal" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

Similar Messages

Is soap binding Document type working in Flex Builder 4?

Hi there,
I've spent three days trying to make a simple web service call with <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> work.
This works fine in FB3 since we're using tons of web service with document style...
I know I'm using a beta so things are being solved in FB4 final version, but no one out there is saying that, passing an object as a parameter in a web service calls with document soap bindings just doesn't work!
Flash Builder generated stubs will create an empty xml in the soap body! Passing strings and other primitive types seems to work, but in some circumstances you have to pass objects to the backend!
If someone is having this problem you simply have to change the backend soap binding style from "document" to "rpc" and all will work...
Is there an official Adobe position about this?
Regards,
Giorgio Grillini
P.S.: I'm using Flash Builder beta 2 with sdk 4 build 10485. Backend are Java web services deployed in jboss.

Can you post sample code that shows this issue?
BaBo,

Soap binding in wsdl and weblogic workshop

Dear newsgroup,
I'm trying to develop a webservice with workshop 8.1. In my case, I already have
a "WSDL" file for the service I want to develop.
So I created a "Schema Project", imported the wsdl file in it (workshop automatically
compiled it !!) and generated a webservice from it. I then created a webservice
project and moved the generated "jws" file in the webservice project.
So far with no problem.
Now I opened the "jws" file and saw there is this error:
"ERROR: The binding for <Op name> does not declare one part"
"SUGGESTION: A document literal binding must have at most one part. Make sure
you have a WSDL that declares just one part for each message with a document literal
binding."
Indeed my wsdl has messages with more than one part. It looks like this:
<wsdl:message name="SubmitSMSIn">
<wsdl:part name="GNSHeaderHeader" element="fwk:GNSHeader">
</wsdl:part>
<wsdl:part name="GNSCredentialsHeader" element="fwk:GNSCredentials">
</wsdl:part>
<wsdl:part name="SubmitSMSRequestBody" element="sms:SubmitSMSRequest">
</wsdl:part>
</wsdl:message>
And corresponding binding looks like this:
<wsdl:binding name="smsBinding" type="smsPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="SubmitSMS">
<soap:operation style="document" soapAction="http://vodafone.net/ns/gns/sms/SubmitSMS">
</soap:operation>
<wsdl:input name="SubmitSMSInput">
<soap:body use="literal" parts="SubmitSMSRequestBody">
</soap:body>
<soap:header use="literal" message="SubmitSMSIn" part="GNSHeaderHeader"
wsdl:required="true">
</soap:header>
<soap:header use="literal" message="SubmitSMSIn" part="GNSCredentialsHeader"
wsdl:required="true">
</soap:header>
</wsdl:input>
<wsdl:output name="SubmitSMSOutput">
<soap:body use="literal" parts="SubmitSMSResponseBody">
</soap:body>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
MY QUESTION: Is this a workshop webservice limitation? I thought after reading
wsdl specification,(URL: http://www.w3.org/TR/wsdl.html#_soap-b, example 3), that
this should be possible.
What am I doing wrong.
Thanks for any help.
-- Asit Bhattacharya

Hi Asit,
Personally, I find dealing with the WSDL/SOAP language a humbling
experience and welcome the day that their syntax is completely buried
with the use of tools; to that end, I would recommend that you use the
WS-I test tools to validate/confirm all of the Rxxx issues.
Regards,
Bruce
Asit Bhattacharya wrote:
>
Hi Bruce,
Yes, you are right. "R2210" indeed does say that. Interestingly, it starts like
this:
"If a document-literal binding in a DESCRIPTION does not specify the parts attribute
on a soapbind:body element, the corresponding abstract wsdl:message MUST define
zero or one wsdl:parts."
Please NOTE the "if" part of the recommendation. As I understand, it is saying
when "parts" attribute is not specified in "soapbind:body" element then corresponding
"wsdl:message" is required to define zero or one "wsdl:parts".
In my original wsdl file example, I do have "parts" attribute specified for the
"soapbind:body" element. To me that that should be valid. What do you say.
Sincerely,
Asit Bhattacharya.
Bruce Stephens <[email protected]> wrote:
Hi Asit,
R2210 says: ...wsdl:message MUST define zero or one wsdl:parts.
I might suggest that you try your WSDL with the WS-I test tools. They
have a mode to consume and analyze WSDL that will give you a detailed
response correlated with the basic profile.
Regards,
Bruce
Asit Bhattacharya wrote:
Hi Bruce,
Thanks for your reply,
WS-I Basic Profile "R2201" says the following:
"A document-literal binding in a DESCRIPTION MUST, in each of its soapbind:body
element(s), have at most one part listed in the parts attribute, ifthe parts
attribute is specified."
It does not restrict a meesage (that is used in doc/lit soap binding)to have
multiple parts. If you look in my example wsdl (specially the soap:bindingportion),
you'll see I'm only using one part for soap:body binding.
Could you please explain why do you think that the SUGGESTION is valid?
Thanks for your help.
Regards.
Asit Bhattacharya.
Bruce Stephens <[email protected]> wrote:
Hello,
The suggestion is valid. You might want to reference the extensive
work
on this issue by the WS-I folks [1], see R2201 and following.
Regards,
Bruce
[1]
http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Asit Bhattacharya wrote:
Dear newsgroup,
I'm trying to develop a webservice with workshop 8.1. In my case,
I
already have
a "WSDL" file for the service I want to develop.
So I created a "Schema Project", imported the wsdl file in it (workshopautomatically
compiled it !!) and generated a webservice from it. I then createda webservice
project and moved the generated "jws" file in the webservice project.
So far with no problem.
Now I opened the "jws" file and saw there is this error:
"ERROR: The binding for <Op name> does not declare one part"
"SUGGESTION: A document literal binding must have at most one part.Make sure
you have a WSDL that declares just one part for each message with
a
document literal
binding."
Indeed my wsdl has messages with more than one part. It looks likethis:
<wsdl:message name="SubmitSMSIn">
<wsdl:part name="GNSHeaderHeader" element="fwk:GNSHeader">
</wsdl:part>
<wsdl:part name="GNSCredentialsHeader" element="fwk:GNSCredentials">
</wsdl:part>
<wsdl:part name="SubmitSMSRequestBody" element="sms:SubmitSMSRequest">
</wsdl:part>
</wsdl:message>
And corresponding binding looks like this:
<wsdl:binding name="smsBinding" type="smsPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"
/>
<wsdl:operation name="SubmitSMS">
<soap:operation style="document" soapAction="http://vodafone.net/ns/gns/sms/SubmitSMS">
</soap:operation>
<wsdl:input name="SubmitSMSInput">
<soap:body use="literal" parts="SubmitSMSRequestBody">
</soap:body>
<soap:header use="literal" message="SubmitSMSIn"part="GNSHeaderHeader"
wsdl:required="true">
</soap:header>
<soap:header use="literal" message="SubmitSMSIn"part="GNSCredentialsHeader"
wsdl:required="true">
</soap:header>
</wsdl:input>
<wsdl:output name="SubmitSMSOutput">
<soap:body use="literal" parts="SubmitSMSResponseBody">
</soap:body>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
MY QUESTION: Is this a workshop webservice limitation? I thought
after
reading
wsdl specification,(URL: http://www.w3.org/TR/wsdl.html#_soap-b,
example
3), that
this should be possible.
What am I doing wrong.
Thanks for any help.
-- Asit Bhattacharya

Attachment binding issue in workflow

Hi All,
I have used FM 'SAP_WAPI_ATTACHMENT_ADD ' in method of my workflow. Here after executing this FM i m getting id of the attachment for this workitem. But now i need to assign this to '_Attach_Objects' of workflow container. so please help me for this binding issue. which i need to bind from method to> task to> workflow. so from next step onwards in workflow i will get that attachment.
Smit Shah

Hi,
1) In the T.code SWO1, you have to create a custom method for the BO, there execute that method and check whether it working fine
2) Then goto T.code PFTC and Create a Task (Task no. will generate automatically), then call this method and generate the binding
3) Goto T.code SWDD and call that Task by assigning that Task no. and assign the binding
Then test your workflow.
For the Binding see this [link|http://help.sap.com/saphelp_nw04/helpdata/en/c8/bfc39b0fc57a49a0291378f8be0cd6/frameset.htm].
Regards,
Surjith

SOAP binding over MQ transport support

Hi All,
I would like to know if the OSB and SOA Suite 11g products support SOAP binding over MQ transport. If yes, how should we do it?
Regards,
Aditya

Hello Vlad Dyuzhev
I see that there are two native MQ transports for each of OSB and SOA 11g products
1) MQ transport (for OSB only)
2) Oracle JCA adapter for MQ Series (for SOA only?)
Both of them doesn't support SOAP messages, is my understanding correct?
Now we have another way with foreign JMS providers which are mapped to remote MQ setup, these can be used to send over the SOAP messages from both OSB and SOA using JMS transport. Is my understanding correct?
Please let me know.

WSDL with SOAP Binding and Attachement

Hello
I'm trying to define a WSDL-Definition which defines a operation called getFile() which returns a file as a SOAP attachement. I created the follwing file which I can verify without any problems. However if I try to compile it with wscompile (wscompile -gen:server -mapping build/mapping.xml -d build -nd build -classpath . config.xml) I get the follwing error:
error: output message of binding operation "getFile" does not have a SOAP body extension
When I remove the line
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
wscompile generates the classes but gives the following warnings:
warning: ignoring port "FileDistributorIFPort": not a SOAP port
warning: Service "FileDistributorService" does not contain any usable ports
Which is somehow clear because I did not define the soap binding.
Any ideas what I can do so I can transmit a file via SOAP using attachements?
Here's the file
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="FileDistributorService"
targetNamespace="urn:Foo"
xmlns:tns="urn:Foo"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<types>
<xsd:schema targetNamespace="urn:Foo"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:element name="getFile">
<xsd:complexType>
<xsd:all>
<xsd:element name="mySymbol" type="xsd:string"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="getFileResponse">
<xsd:complexType>
<xsd:all>
<xsd:element name="result" type="float"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ArrayOfBinary">
<xsd:complexContent>
<xsd:restriction base="soapenc:Array">
<xsd:attribute ref="soapenc:arrayType"
wsdl:arrayType="xsd:binary[]"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
</types>
<message name="m1">
<part name="body" element="tns:getFile"/>
</message>
<message name="m2">
<part name="body" element="tns:getFileResponse"/>
<part name="file" type="tns:ArrayOfBinary"/>
</message>
<portType name="pt1">
<operation name="getFile">
<input message="tns:m1"/>
<output message="tns:m2"/>
</operation>
</portType>
<binding name="b1" type="tns:pt1">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="getFile">
<soap:operation soapAction="getFile"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<mime:multipartRelated>
<mime:part>
<soap:body parts="body" use="literal"/>
</mime:part>
<mime:part>
<mime:content part="file" type="tns:ArrayOfBinary"/>
</mime:part>
</mime:multipartRelated>
</output>
</operation>
</binding>
<service name="FileDistributorService">
<port name="FileDistributorIFPort" binding="tns:b1">
<soap:address location="http://localhost:8080/fxm/FileDistributorImpl"/>
</port>
</service>
</definitions>
Thanks a lot!
Oliver

Not very sure, but i suspect that there is an error here in your WSDL :
<mime:multipartRelated>
<mime:part>
<soap:body parts="body" use="literal"/>
</mime:part>
<mime:part>
<mime:content part="file" type="tns:ArrayOfBinary"/>The type attribute should be a valid Mime Type.
Quoting from the WSDL Specification
The type attribute contains the MIME type string. A type value has two portions, separated by a slash (/), either of which may be a wildcard (*). Not specifying the type attribute indicates that all MIME types are acceptable.
Why not try the following instead of the last line above
<mime:content part="file" type="*/*"/>

How to call a webservice with SOAP Binding Style RPC

Hi Guys,
I'm pretty new to the LiveCycle ES product and I'm trying to call a web service that is of SOAP binding style 'RPC'. After some research I found out that Adobe LC ES only support WSDL files of doc/literal type.
My question is, is there a workaround for calling RPC style web services? can RPC style web services be converted into doc/literal type?
Any information regarding this would be greatly appreciated.
Kazz.

Hello,
I had the same problem and I've regenerated my WSDL ( Apache Axis ) with docu/litteral parameters.
I think it's the only way...
thomas

Error if I add 2 WebServices in a Process - WSDL does not SOAP binding

We have designed a simple process flow (exposed as a webservice) that consists of 2 separate services.
Something like this:
entry->service1->service2->exit
We get the following error 'WSDL does not have SOAP binding'
Annotation: Caught Compilation Error(s).
Please fix before proceeding.
com.stc.codegen.framework.model.CodeGenException
        at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateFiles(JaxRpcCodelet.java:409)
        at com.stc.wsclient.design.codegen.impl.WSClientCodelet.generateFiles(WSClientCodelet.java:435)
        at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.processCodelets(CodeGenFrameworkImpl.java:602)
        at com.stc.codegen.frameworkImpl.model.CodeGenFrameworkImpl.process(CodeGenFrameworkImpl.java:1263)
        at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:395)
        at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.process(DeploymentVisitorImpl.java:307)
        at com.stc.codegen.frameworkImpl.model.DeploymentVisitorImpl.traverseDeployment(DeploymentVisitorImpl.java:267)
        at com.stc.codegen.driver.module.DeploymentBuildAction.loadCodeGen(DeploymentBuildAction.java:901)
        at com.stc.codegen.driver.module.DeploymentBuildAction.access$700(DeploymentBuildAction.java:173)
        at com.stc.codegen.driver.module.DeploymentBuildAction$1.run(DeploymentBuildAction.java:590)
        at org.openide.util.Task.run(Task.java:136)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:599)
Caused by: com.stc.codegen.framework.model.CodeGenException
        at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateBeans(JaxRpcCodelet.java:483)
        at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateFiles(JaxRpcCodelet.java:407)
        ... 11 more
Caused by: com.stc.codegen.framework.model.CodeGenException: WSDL does not have SOAP Binding
        at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.showWarningSOAPBinding(JaxRpcCodelet.java:761)
        at com.stc.wsclient.design.codegen.impl.JaxRpcCodelet.generateBeans(JaxRpcCodelet.java:464)
.. ... 12 moreAny idea's?
regards,
Vinod

Hi Vinod,
the two web services being called are two different web services (two WSLDs) or one web service but two different operations (one WSDL)?
In latter case you have to define new partner in your process and assign it to one of the web services calls. Then you will have one more partner also in connectivity map and you have to connect it to new web service application and map it in deployment profile.
Regards,
Juraj

HTTP Binding & SOAP Binding

I have a client where I need to post xml message to an aspx site. The XML need to be in a SOAP envelope. When using http binding to do a http post the message is not in a soap envelope. Is there a simple way of using http binding that will post the message in a soap envelope? I used obtunnel to capture the message of a http binding vs a soap binding.
HTTP Binding:
POST /httpreceive.aspx/httpreceive.aspx HTTP/1.1
Host: devsoa.test.com:1234
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: text/xml
Content-length: 336
<?xml version="1.0" encoding="UTF-8"?>
<AddressBookEntry xmlns="http://xmlns.oracle.com/TestService">
<AddressBookNumber>43</AddressBookNumber>
<Name>test user</Name>
<AddressLine1/>
<AddressLine2/>
<City/>
<State/>
<PostalCode/>
<Phone/>
<Fax/>
<Email/>
<ElectDest/>
</AddressBookEntry>
SOAP Binding:
POST /httpreceive.aspx HTTP/1.1
Host: devsoa.test.com:1234
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
SOAPAction: "process"
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: text/xml; charset=UTF-8
Content-length: 734
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<MsgSoapHeader xmlns="http://xmlns.oracle.com/TestService">
     <Authentication>
          <UserName>testUser</UserName>
          <Password>testPwd</Password>
     </Authentication>
     <Properties>
          <Company>TEST</Company>
     </Properties>
</MsgSoapHeader>
</env:Header>
<env:Body>
     <AddressBookEntry xmlns="http://xmlns.oracle.com/TestService">
          <AddressBookNumber>12345</AddressBookNumber>
          <Name>test user</Name>
          <AddressLine1/>
          <AddressLine2/>
          <City/>
          <State/>
          <PostalCode/>
          <Phone/>
          <Fax/>
          <Email/>
          <ElectDest/>
     </AddressBookEntry>
</env:Body>
</env:Envelope>
Edited by: sns724 on Mar 16, 2009 1:32 PM
Edited by: sns724 on Mar 16, 2009 4:07 PM
Edited by: sns724 on Mar 16, 2009 4:07 PM

No, this is just a .net asp site (httpreceive.aspx) that take http post. I have to use http binding to do an http post since there is no web service. Therefore there is no wsdl to import for the partner link. However, they expect the xml to be in a soap envelope with a custom soap header for authentication. I'm able to get the soap envelope using soap binding but not http binding. What I need is to be able to do a http post with the message in a soap envelope. Any help will be greatly appreciated.

Improper Faults in SOAP binding

Maybe someone has seen this and can help with a solution or workaround. We've got a BPEL process that needs to be exposed as a web service to a .NET client. The problem is that only one fault is included in the generated bindings node.
I've defined a BPEL process that throws three test faults. The WSDL has the following portType:
<portType name="TestFaults">
          <operation name="process">
               <input message="client:TestFaultsRequestMessage" />
               <output message="client:TestFaultsResponseMessage"/>
<fault name="faultOne" message="client:FaultOneMessage"/>
<fault name="faultTwo" message="client:FaultTwoMessage"/>
<fault name="faultThree" message="client:FaultThreeMessage"/>
          </operation>
     </portType>
However, when I deploy the process on 10.1.2.0.2 [build #2196 ] we don't get the proper bindings element. It looks like this:
<binding name="TestFaultsBinding" type="tns:TestFaults">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
     <operation name="process">
<soap:operation style="document" soapAction="process"/>
     <input>
<soap:body use="literal"/>
</input>
     <output>
<soap:body use="literal"/>
</output>
     <fault>
<soap:fault name="faultTwo" use="literal" encodingStyle=""/>
</fault>
</operation>
</binding>
The problem is that our .NET client isn't seeing all of the faults, and I assume it is because the different faults aren't included in the SOAP binding??
I've since deployed this same process on 10.1.3. Of course, the new version (which we can't use because we're on AIX) seems to create the binding properly:
<binding name="TestFaultsBinding" type="tns:TestFaults">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="process">
<soap:operation style="document" soapAction="process" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<fault name="faultThree">
<soap:fault name="faultThree" use="literal" encodingStyle="" />
</fault>
<fault name="faultOne">
<soap:fault name="faultOne" use="literal" encodingStyle="" />
</fault>
<fault name="faultTwo">
<soap:fault name="faultTwo" use="literal" encodingStyle="" />
</fault>
</operation>
</binding>

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread

A data-binding issue with a combo box.

Hi,
Iu2019m having a data-binding issue with a combo box. The field it is bound to is an integer. The valid values in the combo box are 1, 2, and 3. If I add a record when it is set to 1 or 2, the value gets stored correctly. If I add a record when it is set to 3, it is stored as 1. However, I can bring up the record just added on the form, change it to 3, and click u201CUpdateu201D and it is saved correctly as 3. If I change it so that the valid values are 4, 5, and 6, it saves a 1 regardless of what is selected in the combo box. It looks like the combo box is correctly bound for updates but not for adds. The table is a master type UDO. Any ideas? Iu2019m somewhat committed to the field being an integer. I'm using 2007A PL47.
Thanks,
Mike
Edited by: Mike Angelastro on Jul 1, 2009 2:43 PM

I tried a few things on my own. The result is that I decided that it was not a good idea to use a combo box bound to an integer (numeric) field. I donu2019t think the SDK can handle it. The reason it was an integer field in the first place is that before I changed it to a combo box it was a group of two option buttons. Option buttons use an integer (numeric) field. This worked just fine until I added a third option; the SDK didnu2019t handle the third option correctly when adding records. I thought that using a combo box instead would fix that. I was wrong; the problem remained. So I decided to use a character (alphanumeric) field instead. This works just fine.
So here is my advice: Never use option buttons if they need to be bound to the database; a combo box will actually work better when bound to the database. But use a character (alphanumeric) field.
Edited by: Mike Angelastro on Jul 5, 2009 9:15 PM

[svn:cairngorm3:] 17187: Fixed binding issue on the source property of the contact's picture

Revision: 17187
Revision: 17187
Author:   [email protected]
Date:     2010-08-04 13:44:35 -0700 (Wed, 04 Aug 2010)
Log Message:
Fixed binding issue on the source property of the contact's picture
Modified Paths:
    cairngorm3/trunk/samples/insync/insync-modularExtended-contacts/src/insync/contacts/prese ntation/ContactForm.mxml

Revision: 17187
Revision: 17187
Author:   [email protected]
Date:     2010-08-04 13:44:35 -0700 (Wed, 04 Aug 2010)
Log Message:
Fixed binding issue on the source property of the contact's picture
Modified Paths:
    cairngorm3/trunk/samples/insync/insync-modularExtended-contacts/src/insync/contacts/prese ntation/ContactForm.mxml

[svn:cairngorm3:] 17186: Fixed binding issue on the source property of the contact's picture

Revision: 17186
Revision: 17186
Author:   [email protected]
Date:     2010-08-04 13:43:41 -0700 (Wed, 04 Aug 2010)
Log Message:
Fixed binding issue on the source property of the contact's picture
Modified Paths:
    cairngorm3/trunk/samples/insync/insync-basic/src/insync/presentation/ContactForm.mxml

Revision: 17186
Revision: 17186
Author:   [email protected]
Date:     2010-08-04 13:43:41 -0700 (Wed, 04 Aug 2010)
Log Message:
Fixed binding issue on the source property of the contact's picture
Modified Paths:
    cairngorm3/trunk/samples/insync/insync-basic/src/insync/presentation/ContactForm.mxml

SAP PI 7.31 / Sender SOAP Channel Issue with XML tag Main/@versionMajor has incorrect value 000; expected value is 003

Hi PI Experts,
We are on SAP PI 7.31 SP 10.
We are in the process of integrating ARIBA P2P solution using SOAP Adapter as sender to connect Ariba with our PI system.
We have configured all required components in ESR and ID(Most of them are content provided by Ariba).When we try to post a message into PI using SOAP UI we are ending with below error.

http://<host name> : <port name> /XISOAPAdapter/MessageServlet?channel= <party name> : <service name> : <channel name>
For the above issue we had configured SOAP Sender channel as above,and the URL we are using to hit PI is as above screenshot.
We have followed the note on this topic with out any luck.
1378872
We are not sure where is problem.As the issue is not reaching to PI not able to see the messages in SXMB_MONI.
and in the SXMB_ADM PI has been configured as Integration Server.
I had even tried to change the message protocol as XI3.0 in SOAP sender channel and noluck.
I have tried to ximessage=true query also in URL and noticed that not working.This is clear that the message we are trying to send from Ariba is not compatible with XI3.0 protocol,Ariba is not having any option to change at their end as it is a cloud application and many customers have been using same with out any issues.
We have tried maintain the Java System properties in NWA as XPI.Adapter.Version.Major = 3 but no luck.
Can some one provide us the solution to get rid of this issue?

Standalone (J2SE) adapter - axis SOAP adapter - issue duplicate messages

All,
Perhaps you can help me. I've setup a scenario where an standalone (J2SE) adapter sends a file to SAP XI channel, configured on the central adapter engine, of type SOAP configured to use Axis servlet.
The connection is setup and the standalone adapter channel logs thre response from the SOAP channel which reads HTTP error 500, indicating a duplicate message.
SAP has identified this problem and proposes in the FAQ for Axis (note 1039369) to set on the SOAP channel module CallSapAdapter property ignoreDuplicate to true in the module processor.
I've implemented this as suggested however found the problem persists. I'm still receiving an HTTP 500 error.
Your help is much appreciated solving this problem.
Thanks
Harald

As there was a bugfix recently, make sure that you have installed the latest patch.
If this does not work, open an OSS ticket for this issue.
Stefan

SOAP Binding Issue

Similar Messages

Maybe you are looking for