Namespace on wsdl request

Hi all,
we need to accept a wsdl request with out a namespace on the top element in the body but our system keeps rejecting it as its returning null.
the request coming in is 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:syn="https://test.com/SynERP">
<soapenv:Header/>
<soapenv:Body>
<stockReceivedRequest>
<stockReceived>
<dateReceived>2015-02-11</dateReceived>
<timeReceived>17:11:43</timeReceived>
<courier>DHL</courier>
<poNumber>GU12533</poNumber>
<stockDetailReceived>
<stockDetail>
<productCode>test1</productCode>
<altProductCode/>
<productName>test</productName>
<quantity>2</quantity>
</stockDetail>
</stockDetailReceived>
</stockReceived>
</stockReceivedRequest>
</soapenv:Body>
</soapenv:Envelope>
the request we expect is;
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:syn="https://test.com/SynERP">
<soapenv:Header/>
<soapenv:Body>
<syn:stockReceivedRequest>
<stockReceived>
<dateReceived>2015-02-11</dateReceived>
<timeReceived>17:11:43</timeReceived>
<courier>DHL</courier>
<poNumber>GU12533</poNumber>
<stockDetailReceived>
<stockDetail>
<productCode>test1</productCode>
<altProductCode/>
<productName>test</productName>
<quantity>2</quantity>
</stockDetail>
</stockDetailReceived>
</stockReceived>
</syn:stockReceivedRequest>
</soapenv:Body>
</soapenv:Envelope>
the code managing the request is;
[SoapDocumentMethod(Binding = "GoodsReceiptServiceBinding")]
[WebMethod(MessageName = "stockReceivedRequest")]
public stockReceivedResponseType GoodsReceiptService([XmlElementAttribute(Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "stockReceived")]stockReceived stockReceived)
// Get raw request body and process it out to the Logger
Stream receiveStream = HttpContext.Current.Request.InputStream;
RequestFactory.RequestIn(receiveStream, "GoodsReceiptService");
SRSServiceLayer srsServiceLayer = new SRSServiceLayer();
if (stockReceived != null)
return srsServiceLayer.StockRecieved(stockReceived);
else
stockReceivedResponseType response = new stockReceivedResponseType();
response.result = Result.ERROR;
response.errorMessages = EventFactory.GetEvent(107);
return response;
I have tried to make the method unqualified but I just get an error when compiling the code out as XmlElement cant be on a deceleration type.
can we either add syn: on to the stockRecievedRequest when it comes in or is there away to just not bother with it?
hope someone can help.
Aidan

Hi we have this;
/// <summary>
/// Stock Recieved
/// </summary>
[DataContract]
public class stockReceived
/// <summary>
/// Gets or sets the date recieved.
/// </summary>
/// <value>The date recieved.</value>
[DataMember(Name = "dateReceived", IsRequired = true, Order = 0)]
[XmlElementAttribute(IsNullable = true, Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "dateReceived")]
public string dateRecieved { get; set; }
/// <summary>
/// Gets or sets the time recieved.
/// </summary>
/// <value>The time recieved.</value>
[DataMember(Name = "timeReceived", IsRequired = false, Order = 1)]
[XmlElementAttribute(IsNullable = false, Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "timeReceived")]
public string timeRecieved { get; set; }
/// <summary>
/// Gets or sets the courier.
/// </summary>
/// <value>The courier.</value>
[DataMember(Name = "courier", IsRequired = false, Order = 2)]
[XmlElementAttribute(IsNullable = false, Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "courier")]
public string courier { get; set; }
/// <summary>
/// Gets or sets the purchase order number.
/// </summary>
/// <value>The purchase order number.</value>
[DataMember(Name = "poNumber", IsRequired = true, Order = 3)]
[XmlElementAttribute(IsNullable = true, Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "poNumber")]
public string poNumber { get; set; }
/// <summary>
/// Gets or sets the stock detail.
/// </summary>
/// <value>The stock detail.</value>
[DataMember(Name = "stockDetailReceived", IsRequired = false, Order = 4)]
[System.Xml.Serialization.XmlArrayAttribute(Form = System.Xml.Schema.XmlSchemaForm.Unqualified)]
[XmlArrayItemAttribute("stockDetail", IsNullable = true, Form = System.Xml.Schema.XmlSchemaForm.Unqualified)]
public stockDetail[] stockDetailReceived { get; set; }
but as you can see by the request we are expecting with the syn:stockReceivedRequest this is done by the web call
[SoapDocumentMethod(Binding = "GoodsReceiptServiceBinding")]
[WebMethod(MessageName = "stockReceivedRequest")]
public stockReceivedResponseType GoodsReceiptService([XmlElementAttribute(Form = System.Xml.Schema.XmlSchemaForm.Unqualified, ElementName = "stockReceived")]stockReceived stockReceived)
// Get raw request body and process it out to the Logger
Stream receiveStream = HttpContext.Current.Request.InputStream;
RequestFactory.RequestIn(receiveStream, "GoodsReceiptService");
SRSServiceLayer srsServiceLayer = new SRSServiceLayer();
if (stockReceived != null)
return srsServiceLayer.StockRecieved(stockReceived);
else
stockReceivedResponseType response = new stockReceivedResponseType();
response.result = Result.ERROR;
response.errorMessages = EventFactory.GetEvent(107);
return response;
its the 
[WebMethod(MessageName = "stockReceivedRequest")]
that is getting qualified.
regards
Aidan

Similar Messages

  • How to remove XML namespace in SOAP request

    Hello
    I would like to change one of our existing interfaces to use a SOAP communication channel rather than File. The file currently contains FIDCCP02 Idocs.
    I have created a new communication channel using SOAP 7.1 and generated a Java client. When I send a request to the endpoint from Java, PI returns a SOAP fault.
    Error
    The error in the monitor is 'No standard agreement found for ..'. I think this is because the file contains XML with a root element with no namespace, but the root element in the SOAP message does have a namespace.
    Example requests
    File message :
    <FIDCCP02 xmlns:ns2="http://dorsetcc.gov.uk/FIN_I26/Invoice/PremierFin" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    SOAP message :
    <ns2:FIDCCP02 xmlns:ns2="http://dorsetcc.gov.uk/FIN_I26/Invoice/PremierFin" xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    When I send a test request from RWB with no namespace it is successful.
    Attempt to remove namespace
    I have tried adding AF_Modules/XMLAnonymizerBean with no parameters as the first module on the SOAP communication channel, but this does not appear to make any difference. I have refreshed the cache.
    regards
    Steve

    Hello Iñaki
    Thanks for your reply.
    I had read the blog about the XMLAnonymizerBean. It looks very straightforward, and in theory should do just what I need.
    I've added the anonymizer bean as the first module as the SOAP message is asynchronous, and I want to remove the namespaces from the request.
    I want to exclude all namespaces so I haven't set any parameters.
    The SOAP channel in Communication Channel monitor has a status of 'Channel Started but inactive'. I cannot see any messages in the Processing Details for this channel, even though I have sent test messages from Java code and from RWB (the message from RWB without the namespace does reach the receiver). This makes me wonder if I have not configured the interface to use the new SOAP channel correctly, although I can see it in the Receiver Determination configuration overview.
    I can see the messages in SXMB_MONI but can't find which communication channel is being used by the sender.
    I'm using PI 7.1.
    regards
    Steve

  • XML Namespace in WebService Request/Response

    Hi all,
    I have a question regarding xml namespace usage in wsdl and the corresponding request/response messages.
    I have already browsed quite some articles about xml namespaces as well as some forum threads, but I am still not sure.
    I have the following part of a wsdl document (generated by Integration Directory), defining a targetnamespace.
    u2026
    <wsdl:types>
        <xsd:schema targetNamespace="http://www.dorma.com/sap/xi/finance"
                             xmlns="http://www.dorma.com/sap/xi/finance"
                             xmlns:xsd="http://www.w3.org/2001/XMLSchema">
            <xsd:element name="DebtorGetDetailResponse" type="Z_BAPI_DEBTOR_GETDETAIL_Response"></xsd:element>
            u2026
            <xsd:complexType name="Z_BAPI_DEBTOR_GETDETAIL_Response">
                <xsd:sequence>
                    <xsd:element name="DEBITOR_COMPANY_DETAIL" type="BAPI1007_5" minOccurs="0">
                    </xsd:element> u2026
                </xsd:sequence>
            </xsd:complexType>
            u2026
        </xsd:schema>
        u2026
    </wsdl:types>
    u2026
    In my understanding, all types defined in the schema section of a wsdl document will be in the targetnamespace, if defined.
    Therefore the element DEBITOR_COMPANY_DETAIL would be in the namesapce
    http://www.dorma.com/sap/xi/finance
    However, the ABAP proxy generates a response message like follows,
    where only the root element is in this namespace and the child elements are in the global namespace:
    <?xml version="1.0" encoding="utf-8"?>
    <ns1:DebtorGetDetailResponse xmlns:ns1="http://www.dorma.com/sap/xi/finance"
                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <DEBITOR_COMPANY_DETAIL>
            u2026
        </DEBITOR_COMPANY_DETAIL>
        u2026
    </ns1:DebtorGetDetailResponse>
    Do I have a wrong understand of the wsdl (xml schema) or is this an erroneous behavior?
    The problem is that some 3rd-party software web service module does not accept
    the response message as not complient with the respective wsdl document.
    Any input is appreciated.
    Thanks
    Hans
    Edited by: Hans-Jürgen Schwippert on Oct 1, 2008 12:02 PM

    I have the same problem. I am trying to connect to a webservice running on IBM websphere but it doesn't accept the xml in my request. It appears to be the same namespace issue.
    Did you ever find a solution for this?
    Is it a valid webservice call if you omit the namespace for an element or is this a bug in the Adaptive WS implementation?
    Web Dynpro web service model generated request:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Header>
    <sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/">
    <enableSession>true</enableSession>
    </sapsess:Session>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    look between these lines -
    <ns1:tamKontrolleraKontoLastAnrop xmlns:ns1="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
    <AnvandarNamn>30039647</AnvandarNamn>
    </ns1:tamKontrolleraKontoLastAnrop>
    look between these lines -
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    As you can see the tag
    <AnvandarNamn>30039647</AnvandarNamn>
    is missing a namespace.
    It should be
    <ns1:AnvandarNamn>30039647</ns1:AnvandarNamn>
    Using a third part tool called Soapui i generate this request that works:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tam="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
       <soapenv:Header/>
       <soapenv:Body>
          <tam:tamKontrolleraKontoLastAnrop>
             <tam:AnvandarNamn>30039647</tam:AnvandarNamn>
          </tam:tamKontrolleraKontoLastAnrop>
       </soapenv:Body>
    </soapenv:Envelope>

  • Empty namespaces in ws-request

    Hi,
    when i call my webservice from a BPEL-process on TP4, the request contains empty namespaces, which is not valid from my point of view:
    <AutorisationsNachweis xmlns:xihk="http://www.xihk.de/2008a/modell" xmlns="http://www.xihk.de/2008a/modell">
    <knr xmlns="">106</knr>
    <benutzername xmlns="">106JUNIT</benutzername>
    <kennwort xmlns="">xxx</kennwort>
    </AutorisationsNachweis>
    Is this a known bug? Has anyone encountered the same problem?
    regards,
    Thomas

    well - what is the wsdl/ schema specifiying - as elementForm? qualified or unqualified?
    cheers clemens

  • Problem with old namespace in WSDL file

    I have a problem with my WSDL file.  My scenario is SOAP to IDOC. 
    Originally the ESB data types were configured under namespace urn:test1:xxx  for development purposes.  When it came time to implement and test, we copied the data types from the old name space to a new namespace http://company.com:interface.
    After the new objects were created, all the old test objects were deleted, including the old namespace definition.  Now when I generate the WSDL file, the top part of the WSDL file looks correct, but toward the bottom, there are references to the old namespace.
    Does anyone know why these reference are appearing, and is there any way to correct this without deleting all my objects and rebuilding everything?
    Thanks in advance for any help.  Will award points for help.
    Terri

    Found the problem....the XML namespace in the Message type still contained the old namespace.  When this was changed to the new namespace, second target namespace was no longer generated.

  • I need an urgent help  remove namespace from proxyServie request body

    I have EFIBetalingOrdningMisligholdt proxyService that called IMMultiHaendelseModtag IMMultiHaendelseModtag business Service, but they have different xsd, so i am transforming EFIBetalingOrdningMisligholdt proxy service reuest xsd to
    IMMultiHaendelseModtag business service xsd.
    Bellow i have my xq file for the transformation.
    IMMultiHaendelseModtag Business Service request parameter should look like this.
    here is partial request to IMMultiHaendelseModtagBusinessService
    <soapenv:Body>
         <ns:IMMultiHændelseModtag_I      revision="string" xmlns:ns="http://skat.dk/begrebsmodel/2009/01/15/">
         <ns:Kontekst>
         <!--You may enter ANY elements at this point-->
         <AnyElement/>
         </ns:Kontekst>
    IMMultiHaendelseModtagBusinessService is called
    here is a partial of the transformed request
    Route to: "IMMultiHaendelseModtag"
         $outbound:
         <con:endpoint      name="BusinessService$dk.skat.efi.im$biz$IMMultiHaendelseModtag" xmlns:con="http://www.bea.com/wli/sb/context">
         <con:service>
         <con:operation>getIMMultiHændelseModtag</con:operation>
         </con:service>
         <con:transport>
         <con:mode>request-response</con:mode>
         <con:qualityOfService>best-effort</con:qualityOfService>
         <con:request      xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <tran:headers      xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
         <http:Content-Type>text/xml</http:Content-Type>
         <http:SOAPAction>
         "http://skat.dk/begrebsmodel/2009/01/15/getIMMultiHændelseModtag"
         </http:SOAPAction>
         </tran:headers>
         </con:request>
         </con:transport>
         <con:security>
         <con:doOutboundWss>false</con:doOutboundWss>
         </con:security>
         </con:endpoint>
         $body (request):
         <soapenv:Body      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
         <ns:EFIBetalingOrdningMisligholdt_I      revision="string" xmlns:ns="http://skat.dk/begrebsmodel/2009/01/15/">
         <ns:IMMultiHændelseModtag_I>
         <ns:HændelseSamling>
         <ns:EFIHændelseStruktur>
    but the problem this :
    <soapenv:Body      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
         <ns:EFIBetalingOrdningMisligholdt_I      revision="string" xmlns:ns="http://skat.dk/begrebsmodel/2009/01/15/">
    question.
    How can I transforme :<ns:IMMultiHændelseModtag_I      revision="string" xmlns:ns="http://skat.dk/begrebsmodel/2009/01/15/"> to <soapenv:Body      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
         <ns:EFIBetalingOrdningMisligholdt_I      revision="string" xmlns:ns="http://skat.dk/begrebsmodel/2009/01/15/"> ?
    declare namespace xf = "http://skat.dk/begrebsmodel/2009/01/15/";
    declare namespace ns0 = "http://skat.dk/begrebsmodel/2009/01/15/";
    declare function xf:test($eFIBetalingOrdningMisligholdt_I1 as element(ns0:EFIBetalingOrdningMisligholdt_I))
    as element(ns0:IMMultiHændelseModtag_I) {
    let $EFIBetalingOrdningMisligholdt_I := $eFIBetalingOrdningMisligholdt_I1
    return
    <ns0:IMMultiHændelseModtag_I>
    <ns0:HændelseSamling>
    <ns0:EFIHændelseStruktur>
    let $KundeStruktur := $EFIBetalingOrdningMisligholdt_I/ns0:BetalingsordningMisligholdListe/ns0:Kunde[1]/ns0:KundeStruktur
    return
    <ns0:KundeStruktur>
    <ns0:KundeNummer>{ data($KundeStruktur/ns0:KundeNummer) }</ns0:KundeNummer>
    <ns0:KundeType>{ data($KundeStruktur/ns0:KundeType) }</ns0:KundeType>
    for $VirksomhedCVRNummer in $KundeStruktur/ns0:VirksomhedCVRNummer
    return
    <ns0:VirksomhedCVRNummer>{ data($VirksomhedCVRNummer) }</ns0:VirksomhedCVRNummer>
    for $KundeNavn in $KundeStruktur/ns0:KundeNavn
    return
    <ns0:KundeNavn>{ data($KundeNavn) }</ns0:KundeNavn>
    for $DriftFormKode in $KundeStruktur/ns0:DriftFormKode
    return
    <ns0:DriftFormKode>{ data($DriftFormKode) }</ns0:DriftFormKode>
    for $EnkeltmandVirksomhedEjer in $KundeStruktur/ns0:EnkeltmandVirksomhedEjer
    return
    <ns0:EnkeltmandVirksomhedEjer>{ $EnkeltmandVirksomhedEjer/@* , $EnkeltmandVirksomhedEjer/node() }</ns0:EnkeltmandVirksomhedEjer>
    </ns0:KundeStruktur>
    <ns0:IndholdValg>
    <ns0:EFIBetalingOrdningMisligholdtStruktur>
    let $BetalingsOrdningliste := $EFIBetalingOrdningMisligholdt_I/ns0:BetalingsordningMisligholdListe/ns0:Kunde[1]/ns0:BetalingsOrdningliste
    return
    <ns0:BetalingsOrdningliste>
    for $MisligholdtBetalingsordning in $BetalingsOrdningliste/ns0:MisligholdtBetalingsordning
    return
    <ns0:MisligholdtBetalingsordning>
    <ns0:BetalingOrdningEFIIndsatsID>{ data($MisligholdtBetalingsordning/ns0:BetalingOrdningEFIIndsatsID) }</ns0:BetalingOrdningEFIIndsatsID>
    <ns0:BetalingOrdningID>{ data($MisligholdtBetalingsordning/ns0:BetalingOrdningID) }</ns0:BetalingOrdningID>
    <ns0:BetalingOrdningRateID>{ data($MisligholdtBetalingsordning/ns0:BetalingOrdningRateID) }</ns0:BetalingOrdningRateID>
    <ns0:BetalingOrdningRateSRBDato>{ data($MisligholdtBetalingsordning/ns0:BetalingOrdningRateSRBDato) }</ns0:BetalingOrdningRateSRBDato>
    <ns0:BetalingOrdningRateBeløbStruktur>{ $MisligholdtBetalingsordning/ns0:BetalingOrdningRateBeløbStruktur/@* , $MisligholdtBetalingsordning/ns0:BetalingOrdningRateBeløbStruktur/node() }</ns0:BetalingOrdningRateBeløbStruktur>
    </ns0:MisligholdtBetalingsordning>
    </ns0:BetalingsOrdningliste>
    </ns0:EFIBetalingOrdningMisligholdtStruktur>
    </ns0:IndholdValg>
    </ns0:EFIHændelseStruktur>
    </ns0:HændelseSamling>
    </ns0:IMMultiHændelseModtag_I>
    declare variable $eFIBetalingOrdningMisligholdt_I1 as element(ns0:EFIBetalingOrdningMisligholdt_I) external;
    xf:test($eFIBetalingOrdningMisligholdt_I1)
    I have called the business proxy alone it works.
    errors
    The invocation resulted in an error: .
         <soapenv:Envelope      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
         <soapenv:Body>
         <soapenv:Fault>
         <faultcode>soapenv:Server</faultcode>
         <faultstring>BEA-380000: Internal Server Error</faultstring>
         <detail>
         <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-380000</con:errorCode>
         <con:reason>Internal Server Error</con:reason>
         <con:location>
         <con:node>RouteNode1</con:node>
         <con:path>response-pipeline</con:path>
         </con:location>
         </con:fault>
         </detail>
         </soapenv:Fault>
         </soapenv:Body>
         </soapenv:Envelope>
         System Error Handler
    $fault:      
         <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
         <con:errorCode>BEA-380000</con:errorCode>
         <con:reason>Internal Server Error</con:reason>
         <con:location>
         <con:node>RouteNode1</con:node>
         <con:path>response-pipeline</con:path>
         </con:location>
         </con:fault>

    Thanks for answering.
    the situation is that I have to make a pass-trough proxyservice.
    That I have never done before.
    explanation:
    proxyservice A-calls business service B, B need password and user name, but proxyservice A does not have Process WS-Security Header to configured, so I have to create a pass-trough proxyService to call business Service B.
    What is the best way of doing that ?
    As I have read that to solve the problem one can set ./ctx:security/ctx:doOutboundWss to true, the only way I saw that was possible was by mean of xquery.
    I am trying to explaine the same situation here again:
    I have proxyService A that does not have :
    Process WS-Security Header in the configuration, that mean I can not set it in my proxy Configuration by way of normal proxy configuration.
    But A is calling a BS that need security, so I want to create a pass-trough proxyservice.
    in order to do that, I want to set ./ctx:security/ctx:doOutboundWss to true in the request
    how can I set ./ctx:security/ctx:doOutboundWss to true in xq ?
    Tks

  • Wsdl requests result in infinite loop response; sometimes

    I'm not sure this is the appropriate place to post this question so please redirect me if there is a better place.
    We have some web services deployed and after they have been running a while a request for the wsdl will result in the following response.
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://model.ws.acme.com" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsxsdns="http://model.ws.acme.com" xmlns:wsns="http://model.ws.acme.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://model.ws.acme.com" xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType><xs:complexType>
    where '<xs:complexType>' is repeated without end.
    We are using the following: tomcat 5.5, axis2 1.2 and java 1.5.
    I thought a request for the wsdl would simply return the file from the file system but I guess I'm wrong. Anyone know what really happens when the wsdl is requested? Any suggested reading? Anyone else ever seen this? Any other advice?
    Thanks for your kind assistance

    Sad, I see many questions and few answers. Open source is great when it works.

  • Can't import XSD (without Namespace) into WSDL

    Hi
    We are developing a BPEL process that takes a XML message - that adheres to the new XSD (has a namespace) - and steps the message (translates) down in to the old XML message - that adheres to the current production XSD (does not have a namespace).
    Our issue is that is seems that you cant import a XSD without a namespace into a WSDL using JCAPS 6. Is there a way around this as we dont want to update the old XSD to include a namespace, knowing that there will be alot of additional dev to upgrade our exisiting 4.5.3 components and the XSD will be decommisioned in the future.
    Any help would be greatly appreciated.
    Regards,

    Hi Arie,
    Thanks for your response.
    It actually happens with every .psd file regardless of size or specs.
    All the other programs in the CS6 master collection work fine, except for AE and PS.
    I tried the small file. Created a small file, 100 px by 100px 72dpi, just with a gradient background. Same thing, not enough memory to initialise PSL.
    I got the adobe cleaner, and re-installed on my system (again) .... same thing.
    As long as I open AE with doing ctrl-alt-shift every single time or export layers from PS individually I seem to be OK.
    The problem is far from solved, so I guess i just have to put up with workarounds.
    Thanks for taking the time to respond

  • XSD Namespace and WSDL Namespaces

    Hi,
    I have a wsdl in which I'm defining a xsd schema in the <wsdl:types> element. Can we have same targetnamespace for both (wsdl) and (xsd that is defined in wsdl <types> element) ?? Please clarify.
    Thanks
    Edited by: bpeltechie on Jul 5, 2012 2:17 PM

    Yes, you can have the same target name space for both wsdl and schema file. Tried with a helloworld.wsdl and helloworld.xsd its valid scenario.
    HelloWorldBPELProcess.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="HelloWorldBPELProcess"
    targetNamespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:client="http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*" schemaLocation="xsd/HelloWorldBPELProcess.xsd" />
    </schema>
    </wsdl:types>
    HelloWorldBPELProcess.xsd file.
    <?xml version="1.0" encoding="UTF-8"?>
    <schema attributeFormDefault="unqualified"
         elementFormDefault="qualified"
         targetNamespace="*http://xmlns.oracle.com/PIMtoRPASAmendment_jws/Helloworld/HelloWorldBPELProcess*"
         xmlns="http://www.w3.org/2001/XMLSchema">
         <element name="process">
              <complexType>
                   <sequence>
                        <element name="input" type="string"/>
                   </sequence>
              </complexType>
         </element>
    </schema>
    Thanks,
    Vijay
    Edited by: veejai24 on 05-Jul-2012 04:03

  • Name ans NameSpace from WSDL

    I have a WSDL in a string format, How can I extract the Name ans NameSpace from it?

    Hi,
    try to you SAX parser with a name space hanlder registered. Download the [Xerces |http://xerces.apache.org/] and look at the sample for parsing name space in the sample directory
    Regards,
    Alan Mehio
    London,UK

  • Different Namespaces in request and response of a webservice in BPEL

    Hello I have created  a  piece of code in BPEL in JDeveloper where i invoke a partner link. The namespaces of the request differs from the name space of response of the wsdl.I have tried to just change the namespace of output variables to the required one in the wsdl and xsd .But it results in errors.
    Can some one suggest me a way of doing this.
    Regards
    Sam.
    PS:I am new to BPEL

    This is my wsdl
    <?xml version="1.0" encoding="UTF-8"?><wsdl:definitions name="testprojectMS" targetNamespace="http://abcd.org/testprojectMS" xmlns:oldtns1="http://www.xyz.net" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://abcd.org/testprojectMS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mrm1="http://abcd.org/testprojectMS">
    <wsdl:types>
    <xsd:schema targetNamespace="http://abcd.org/testprojectMS" xmlns:mrm="http://abcd.org/testprojectMS">
    <xsd:import namespace="http://www.xyz.net" schemaLocation="testproject.xsd"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="testproject_in">
    <wsdl:part element="oldtns1:testprojectIn" name="testprojectIn"/>
    </wsdl:message>
    <wsdl:message name="testproject_out">
    <wsdl:part element="oldtns1:testprojectOut" name="testprojectOut"/>
    </wsdl:message>
    <wsdl:portType name="testprojectMSPortType">
    <wsdl:operation name="testproject">
    <wsdl:input message="tns:testproject_in" name="testproject_Input"/>
    <wsdl:output message="mrm1:testproject_out" name="testproject_Output"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="testprojectMSSOAP_HTTP_Binding" type="tns:testprojectMSPortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="testproject">
    <soap:operation soapAction=""/>
    <wsdl:input name="testproject_Input">
    <soap:body parts="testprojectIn" use="literal"/>
    </wsdl:input>
    <wsdl:output name="testproject_Output">
    <soap:body parts="testprojectOut" use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="testprojectService">
    <wsdl:port binding="tns:testprojectMSSOAP_HTTP_Binding" name="testprojectPort">
    <soap:address location="http://myhost/testprojectService"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    Please let me know where it went wromg

  • Webservice request namespace

    Hi there...
    How can i put a namespace in my request xml in flex. So, my
    going data is:
    <clientRequestwithReturn>
    <MoneyTransferRequest>
    <requestChannel>01</requestChannel>
    <fromAccountNo>0008830006000007</fromAccountNo>
    </MoneyTransferRequest>
    </clientRequestwithReturn>
    But i need to send :
    <xxx:clientRequestwithReturn xmlns:open="
    http://www.xxxxx.org/">
    <yyy:MoneyTransferRequest xmlns:mon="
    http://www.yyyyy.com/">
    <requestChannel>01</requestChannel>
    <fromAccountNo>0008830006000007</fromAccountNo>
    </mon:MoneyTransferRequest>
    </open:clientRequestwithReturn>
    So i need to put namespace info to my request object. How can
    i do it?

    I have the same problem. I am trying to connect to a webservice running on IBM websphere but it doesn't accept the xml in my request. It appears to be the same namespace issue.
    Did you ever find a solution for this?
    Is it a valid webservice call if you omit the namespace for an element or is this a bug in the Adaptive WS implementation?
    Web Dynpro web service model generated request:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Header>
    <sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/">
    <enableSession>true</enableSession>
    </sapsess:Session>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    look between these lines -
    <ns1:tamKontrolleraKontoLastAnrop xmlns:ns1="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
    <AnvandarNamn>30039647</AnvandarNamn>
    </ns1:tamKontrolleraKontoLastAnrop>
    look between these lines -
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    As you can see the tag
    <AnvandarNamn>30039647</AnvandarNamn>
    is missing a namespace.
    It should be
    <ns1:AnvandarNamn>30039647</ns1:AnvandarNamn>
    Using a third part tool called Soapui i generate this request that works:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tam="http://schemas.fora.se/modell/tam/1.0/TAM_Data">
       <soapenv:Header/>
       <soapenv:Body>
          <tam:tamKontrolleraKontoLastAnrop>
             <tam:AnvandarNamn>30039647</tam:AnvandarNamn>
          </tam:tamKontrolleraKontoLastAnrop>
       </soapenv:Body>
    </soapenv:Envelope>

  • Target Namespace in imported WSDL

    Hello All,
    I have an interface that sends data from SAP to 3rd party system.
    3rd party team gave us the WSDL and some XSD's of the interface they have on their system.
    Now, the problem - target namespace on that WSDL is more than 60 characters. Because of this PI 7.0 is unable to recognise XSD's which are external references on imported WSDL document.
    When i reduced the target namespace on the WSDL manually to less than 60 characters and uploaded WSDL again, external references are identified by PI.
    Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the future?
    Can I delete target namespace from WSDL and use the WSDL as target namespace is optional?
    Thanks
    Chandra
    Edited by: Chandra Sekhar H on Jul 19, 2010 10:45 AM

    Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the
    future?
    You can use the wsdl without any issue. If you need to know more: https://service.sap.com/sap/support/notes/901988
    Regards,
    Abhishek.

  • Calling SOAP Request from XML Spy

    I have published PLSQL web service at Oracle 10g AS.
    The web service runs at http://localhost:7201/reqProcess with processRequest as method being exposed.
    This web service takes the string as input and return XMLTYPE as out parameter.
    Now When I am trying to pass SOAP XML from XMLSPY to above url I am getting folloing errors.
    1) I get http error: couldnot post the file /reqProcess/ on server 'localhost' (500)
    2) I get SOAP Error as
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <SOAP-ENV:Fault>
                   <faultcode>SOAP-ENV:Client</faultcode>
                   <faultstring>No Deserializer found to deserialize a &apos;http://wsi.nat.zz.com/2005/06/StandardHeader/:m0:standardHeader&apos; using encoding style &apos;null&apos;. [java.lang.IllegalArgumentException]</faultstring>
                   <faultactor>/reqProcess</faultactor>
              </SOAP-ENV:Fault>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Please help..

    Hi Quwang ur help needed
    My requirement ...
    1) PLSQL as web service : I succesffuly deployed PLSQL Procedure as Web service at 10 10g. The PLSQL takes string (CLOB) as input convert that into XML and store in table and return XMLTYPE as output.
    When I am accesing PLSQL WS using browser I am able to send string (basically XML format) as a input and able to receive the result back (SOAP envelop)
    2)WS Invocation : After PLSQL WS published I need to pass the SOAP XML which is generated from XYX wsdl file to the PLSQL WS published above. For this req I was using XML Spy to test this. (In actual the clinet will be Sieble that will send SOAP XML to PLSQL WS).
    Initially I was generating the SOAP XML from XYZ.wsdl and was directly sending that to PLSQL URL. I was getting error as I described initially.
    Next I tried to generate the SOAP request from the PLSQL WS wsdl file and inside the parameter I am sending the SOAP XML as string to the IN paramater of PLSQL WS. This time I am getting some different errors. The first error is same as http error: couldnot post the file /balprocess/balprocess/operation?processRequest on server 'localhost' (500)
    and second error is SOAP fault as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <SOAP-ENV:Body>
              <SOAP-ENV:Fault>
                   <faultcode>SOAP-ENV:Server</faultcode>
                   <faultstring>java.sql.SQLException: ORA-31011: XML parsing failed
    ORA-19202: Error occurred in XML processing
    LPX-00210: expected &apos;<&apos; instead of &apos;"&apos;
    Error at line 1
    ORA-06512: at "SYS.XMLTYPE", line 0
    ORA-06512: at "SCOTT.BAL_A_PROCESS", line 16
    ORA-06512: at line 1
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)</faultstring>
                   <faultactor>/balprocess/balprocess</faultactor>
              </SOAP-ENV:Fault>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    For ur reference I am pasting the PLSQL WSDL file and the SOAP request xml that I am sending to PLSQL WS URL.
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="bal_a_process"
    targetNamespace="http://bal.request.process/bal_a_process.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://bal.request.process/bal_a_process.wsdl"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd1="http://bal.request.process/bal_a_process.xsd" >
    <documentation>
    WSDL for Service: bal_a_process, generated by Oracle WSDL toolkit (version: 1.1)
    </documentation>
    <types>
    <schema targetNamespace="http://bal.request.process/bal_a_process.xsd" xmlns:tns="http://bal.request.process/bal_a_process.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:dom="http://xmlns.oracle.com/2001/XMLSchema/DOM">
    <complexType name="bal_request_process_bal_a_processUser_processRequest_Out">
    <all>
    <element name="outresponsexmlOut" type="dom:org.w3c.dom.DocumentFragment"/>
    </all>
    </complexType>
    </schema>
    </types>
    <message name="processRequestOutput">
    <part name="return" type="xsd1:bal_request_process_bal_a_processUser_processRequest_Out"/>
    </message>
    <message name="processRequestInput">
    <part name="param0" type="xsd:string"/>
    </message>
    <portType name="bal_a_processPortType">
    <operation name="processRequest">
    <input message="tns:processRequestInput"/>
    <output message="tns:processRequestOutput"/>
    </operation>
    </portType>
    <binding name="bal_a_processBinding" type="tns:bal_a_processPortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <operation name="processRequest">
    <soap:operation soapAction="urn:bal-request-process-bal_a_process/processRequest"/>
    <input>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
    </input>
    <output>
    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:bal-request-process-bal_a_process"/>
    </output>
    </operation>
    </binding>
    <service name="bal_a_process">
    <port name="bal_a_processPort" binding="tns:bal_a_processBinding">
    <soap:address location="http://localhost:7200/balprocess/balprocess"/>
    </port>
    </service>
    </definitions>
    Request I am sending to PLSLQ WS URL
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <SOAP-ENV:Body>
              <processRequest xmlns:m="urn:bal-request-process-bal_a_process" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <param0 xsi:type="xsd:string">     "<a>"aaa"</a>"     </param0>
              </processRequest>
         </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    I above SOAP request XML i m testing "<a>"aaa"</a>" as XML string. but this is also getting failed. In actual this will be SOAP XML request from some other XYZ wsdl file.
    Quwang ur help needed urgently.
    Regards

  • Namespace and extention/inhertance

    I wonder if anybody have observed similar behaviour.
    Our process:
    1. write SLSB with request/response
    2. let the servicegen generate the web-service.xml
    We use inheritance (which translates to extention in wsdl) to provide some common elements for request/response:
    public class XRequest implements Serializable {
    private String application;
    private String transactionId;
    /* getters setters ommited ...*/
    public class SomeRequest extends XRequest {
    private String id;
    /* getters setters ommited ...*/
    The method signature looks like:
    public SomeResponse check(String sessionId, SomeRequest val1) throws java.rmi.RemoteException
    When SomeRequest and XRequest (SomeResponse/XResponse) are in the same package (same namespace in WSDL) it works.
    If SomeRequest and XRequest (SomeResponse/XResponse) are not in the same package, the fields from XRequest/XResponse are gone.
    When i fire up the test console, i noticed that all request elements somehow share the namespace.
    I wonder, if for whatever reason the inheritance/extends in wls implementation works only in single package ?
    Should i provide some serializers ? Am I missing something fundamental here ?
    For reference, we use "document wrapped" and 8.1SP5 (originally 8.1SP3)
    Pawel

    Take a look at these:
    http://www.w3.org/TR/REC-xml-names/
    http://www.w3.org/TR/xmlschema-1/
    http://www.w3.org/TR/xmlschema-2/
    Regards,
    AK~

Maybe you are looking for

  • HP LaserJet P1102w - Flashing Wireless Light

    My printer kept changing IP addresses thus I kept having to add a new printer to my wireless laptop. I wanted to stop this, so I went to the web interface of the printer (looked up the IP address of the printer it was finding on the network and typed

  • External Drive Not Working Properly

    I have a 30GB Lacie Drive I use to transfer data between my imac and my macbook (both are intel machines) - since upgrading to Snow Leopard, it no longer seems to be working properly. It lets me upload some smaller files onto it, but whenever i try t

  • Microsoft Office Outlook update takes almost an hour, Microsoft Office Outlook update takes almost an hour

    When I shut down my mac cmpletely, next day when I turn it on and try to open Microsoft Outlook for Mac, it takes like an hour just updating ID and updating messages. Why is this happening? Thanks, JC

  • Direct labour cost

    Hello all, I want to capture direct labour cost and raw material cost in COPA  where i can map the value field to capture it. Suggest.

  • Problems with Essentials 12 catalog.

    I have recently installed Essentials 12 on a new computer. I restored the old catalog from a backup file. This worked well. I then spent several hours importing new photos. I then tried to find an old catalog, without success. But now I can not get b