WebService - Unsupported Schema Namespace

Hi,
I am getting the below error when I try to call the web service. Any suggestions to resolve this problem will be a great help.
<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:VersionMismatch</faultcode>
<faultstring>Unsupported schema namespace: http://schemas.xmlsoap.org/ws/2002/12/secext</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
(400)Bad Request
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.j
ava:744)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.openq.crmondemand.ws.integrationevent.IntegrationEventWSStub.getE
vents(IntegrationEventWSStub.java:771)
at com.openq.webservices.batch.SiebelEventImporter.importEvents(SiebelEv
entImporter.java:61)
at com.openq.webservices.batch.SiebelEventLoaderMain.main(SiebelEventLoa
derMain.java:26)

Hello,
The following namespaces are supported by CRM On Demand:
■ Draft Namespaces:
■ wsse="http://schemas.xmlsoap.org/ws/2002/04/secext"
■ wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
■ Version 1.0 Namespace:
■ wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wsswssecurity-secext-1.0.xsd"
Thanks,
Sean

Similar Messages

Generating plsql webservices, output different namespaces not consistent

We've defined some database-packages which we want to publish as webservice. We use the option in jdeveloper to generate the plsql webservice.
If we look in the generated wsdl generated by user A, the wsdl gives namespaces like :
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://someurl/AlgemeenWS.wsdl/types/"
elementFormDefault="qualified" xmlns:tns="http://nl/fundeon/fundit/someurl/AlgemeenWS.wsdl/types/"if user B generates the same webservice it gives namespaces lile :
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://someurl/AlgemeenWS.wsdl"
elementFormDefault="qualified" xmlns:tns="http://nl/fundeon/fundit/someurl/AlgemeenWS.wsdl"Any idea how we can control this generated result?
update :
when we generate the classes, etc for the first time after selecting the program units to publish...it generates the correct wsdl.
when we repeat this step (second time of generation), we get the wrong namespace in the wsdl and the log gives us this warning :
WARNING: Ignoring target namespace for schema: "http://someurl/relatieWS/RelatieWS.wsdl", WSDL target namespace is used for the value types in the same package as Service Endpoint: "nl.packagename.relatieWS.RelatieWSUser_getadviseur_Out"

Hi Eric,
I experience exactly the same problem.
The first time the namespace contains 'types', regenerating the webservice afterwards omits the 'types' part.
This has some very awkward effects as the webservice envelop and any proxies are affected by this bug.
I have tried with both 10.1.3.1 & 10.1.3.2, both have the same problems.
I am looking into regenerations of the webservice using ant tasks, there might be a bug in JDeveloper itself.. who knows...
perhaps someone from oracle can comment / test this and open up a ticket for resolving....
Fred Dullemond

Unable to locate Spring NamespaceHandler for XML schema namespace

I am not sure if this is the best practice approach but this is the problem I am ruining into. Below, I explain what I am doing:
1) What I am doing:
=============
Based on the oracle incubator example (http://coherence.oracle.com/display/INCUBATOR/Processing+Pattern+Examples); I am running a server and submitting tasks through a proxy application that submits them to ProcessingPatternConfigurator; let's call my task processReport.
a) my processReport is using spring and ibatis together, I created a utility static class to obtain a spring context and retrieves beans using the following lines ( see exhibit "A1 and A2" below).
b) when my task calls the context and that spring loads, it is failing with the error show in exhibit "B".
I suspect I am missing a lib? I googled the error and searched you site but could find a meaningful discussion on it. I guess my question is if this is not the best approach, how do I integrated with spring initializing beans and setting up ibatis framwork, providing beans and database access through Ibatis for each task ruining on the grid (processReport).
thanks
A1) processReport (submitted in the grid) uses this line
AbstractXmlApplicationContext ctx = (AbstractXmlApplicationContext) AmrContextUtil.getInstance();
          System.out.println("Classpath loaded. Executing Report...");
          ReportProcessor repProcessor = (ReportProcessor) ctx.getBean("reportProcessor");
A2) Here is the AmrContextUtil:
import org.springframework.context.support.AbstractApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;
public final class AmrContextUtil {
     private static AbstractApplicationContext ctx = null;
     public AmrContextUtil() {
          super();
     public final static synchronized AbstractApplicationContext getInstance(){
          if (ctx == null){
               ctx = new ClassPathXmlApplicationContext("classpath:config/applicationContext.xml");
               setCtx(ctx);
          return ctx;
     public final static synchronized AbstractApplicationContext getCtx() {
          return ctx;
     public final static synchronized void setCtx(AbstractApplicationContext ctx) {
          AmrContextUtil.ctx = ctx;
B) Here is the error reported by the server:
2010-02-10 15:42:28.312/57.986 Oracle Coherence GE 3.5.2/463 <Warning> (thread=GridExecutor:Thread-2
, member=1): TaskRunner - Failed to process 0x00000126B99E5524AC1F007AAB1587BBCFEC5E6637E1DED6CCB984
03D6AADF4D due to:org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:config/reports-application.xml] Offending resource: class path resource [config/applicationContext.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Unexpected failure during bean definition parsing
Offending resource: class path resource [config/reports-application.xml] Bean 'reportSqlMapConfig'; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: *Configuration problem: Unable to locate Spring NamespaceHandler for XML schema namespace [http://www.springframework.org/schema/util]*
*Offending resource: class path resource [config/reports-application.xml] Bean 'reportSqlMapConfig'*
-> Property 'resourceMap'
c)Here is my application-context.xml offending line:
<bean id="reportSqlMapConfig"
class="com.xx.report.generator.ReportSqlMapConfig">
<property name="resourceMap">
<map>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.FPA"/>
</key>
<value>classpath:config/diehardReportSqlMapConfig.xml</value>
</entry>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.FCN"/>
</key>
<value>classpath:config/falconReportSqlMapConfig.xml</value>
</entry>
<entry>
<key>
<util:constant static-field="com.xx.report.domain.ReportType.ODS"/>
</key>
<value>classpath:config/odsReportSqlMapConfig.xml</value>
</entry>
</map>
</property>
</bean>

My guess is that something is broken in the configuration of the cacheServer and its not finding
all of the dependencies that your process pattern application needs. Probably the best way
to debug this stuff is to define a static main in your runnable task which will make the call
to the run() method and invoke it as the main class using the identical settings (classpath,
run directory) that you are using to launch the Coherence cache server.
Regards,
Bob

Validating attributes with a non-schema namespace

Hey,
Just wondering if anyone could possibly help me with the following.
Under 3.3.2 (http://www.w3.org/TR/xmlschema-1/#declare-element) it says that the definition of "element" can have "any attributes with non-schema namespace" .
If I have a schema (a.xsd) and import another schema (b.xsd):
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
                   xmlns:b="http://www.foo.com"
                   elementFormDefault="qualified"
                   attributeFormDefault="unqualified">
     <xs:import namespace="http://www.foo.com"; schemaLocation="b.xsd"/>
    <xs:element name="someName" b:validAttribute="invalidValue"/>
</xs:schema>Is there a way to ensure that b:validAttribute is validated when I use SchemaFactory#newSchema(StreamSource)?
I've been hunting around and it just seems to ignore it / always let it pass regardless of the value.
The w3 XMLSchema.xsd uses processContents="lax" for the xs:anyAttribute, so as I understand it, it should be validated it if it finds b.xsd (which it does)?
As a side note, it also allows b:invalidAttribute="foo" which I'd also like to catch..
Any help would be much appreciated!
Cheers,
Meph.

If you take your schema and validate it against the schema for schemas from the W3C site then I am sure the 'b:validAttribute' will be validated.
But I have no idea whether the SchemaFactory will process schemas that way (i.e. by validating them against the schema for schemas).

Parser doesn't recognize schema namespace

I've got the following bit of code:
                org.apache.xerces.parsers.DOMParser parser = new org.apache.xerces.parsers.DOMParser();
                parser.setFeature("http://xml.org/sax/features/namespaces", true);
                parser.setFeature("http://apache.org/xml/features/validation/schema", true);
                parser.setFeature( "http://xml.org/sax/features/validation", true);
                ErrorHandler handler = new MyErrorHandler();
                parser.setErrorHandler(handler);
                parser.parse(name);The schema file I want it to parse (and validate) is below. Its a simple example taken from the w3schools web site. I have almost no doubt the file is a valid schema file.
<?xml version="1.0"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.w3schools.com"
xmlns="http://www.w3schools.com"
elementFormDefault="qualified">
<xs:element name="note">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="to" type="xs:string"/>
        <xs:element name="from" type="xs:string"/>
        <xs:element name="heading" type="xs:string"/>
        <xs:element name="body" type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
</xs:schema>Below are the first few errors generated. The real head scratcher is having no clue about the URI I gave it, and then suggesting the SAME one as what I really should use. Getting these parsers setup to do validation has been a major pain. Anyone know what I left out?
Error at 5 : org.xml.sax.SAXParseException: General Schema Error: Grammar with uri: http://www.w3.org/2001/XMLSchema , can not be found; schema namespace may be wrong: Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace or the instance document's namespace may not match the targetNamespace of the schema.
Error at 5 : org.xml.sax.SAXParseException: Element type "xs:schema" must be declared.
Error at 7 : org.xml.sax.SAXParseException: Element type "xs:element" must be declared.

Thanks for the replies, but I don't think we are quite connecting. I do eventually want to be able to validate an XML file against a schema (which I can't do either), but first I want to be able to validate the schema file itself; i.e. to confirm that the schema I designed is a valid schema file. As I understand it, it should be possible to tell the parser that the schema to validate against is the "schema for writing schemas", http://www.w3.org/Schema/schema.xsd (or whatever it is). That's where I'm getting stuck, that the parser doesn't recognize the elements for actually defining a schema.

Clientgen error: Schema namespace error

Hi
I am trying to generate a client jar using weblogic 8.1 for a webservice deployed using AXIS and I get the following error:
generate-client:
[clientgen] Generating client jar for http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService?wsdl ...
[clientgen] weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http://ttdvd12.ebiz.verizon.com
:8080/baais_wrelay/services/VOIPService']:impl:ArrayOf_xsd_string perhaps due to the lack of an import statement for n
amespace http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService
[clientgen] at weblogic.xml.schema.model.XSDSchema.getSchemaForName(XSDSchema.java:1062)
[clientgen] at weblogic.xml.schema.model.XSDSchema.lookupTopLevelObjectImpl(XSDSchema.java:893)
[clientgen] at weblogic.xml.schema.model.XSDSchema.lookupTypeImpl(XSDSchema.java:881)
This seems to be a weblogic specific problem as it seems to work with AXIS client.Appreciate help in resolving this issue.
Here is the WSDL:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions targetNamespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xmlsoap" xmlns:impl="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns:intf="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="urn:cem_dictionary.dictionary.cem.beans.wrelay" xmlns:tns2="urn:ngvs_dictionary.dictionary.ngvs.beans.wrelay" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <wsdl:types>
          <schema targetNamespace="urn:cem_dictionary.dictionary.cem.beans.wrelay" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="ErrRsp">
                    <sequence>
                         <element name="opcode" nillable="true" type="xsd:int"/>
                         <element name="statusCode" nillable="true" type="xsd:int"/>
                         <element name="statusDesc" nillable="true" type="xsd:string"/>
                         <element name="tid" nillable="true" type="xsd:int"/>
                    </sequence>
               </complexType>
          </schema>
          <schema targetNamespace="urn:ngvs_dictionary.dictionary.ngvs.beans.wrelay" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="ValidateGwyRsp">
                    <sequence>
                         <element name="statusCode" nillable="true" type="xsd:int"/>
                         <element name="statusDesc" nillable="true" type="xsd:string"/>
                         <element name="trunkGwyName" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="ValidateGwyQry">
                    <sequence>
                         <element name="custName" nillable="true" type="xsd:string"/>
                         <element name="lataNumber" nillable="true" type="xsd:int"/>
                         <element name="trunkGwyName" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="ValidateEnprIdQry">
                    <sequence>
                         <element name="altEnprIdCnt" nillable="true" type="xsd:int"/>
                         <element name="custName" nillable="true" type="xsd:string"/>
                         <element name="enprId" nillable="true" type="xsd:string"/>
                         <element name="lataNumber" nillable="true" type="xsd:int"/>
                    </sequence>
               </complexType>
               <complexType name="ValidateEnprIdRsp">
                    <sequence>
                         <element name="altEnprId" nillable="true" type="impl:ArrayOf_xsd_string"/>
                         <element name="custName" nillable="true" type="xsd:string"/>
                         <element name="lataNumber" nillable="true" type="xsd:int"/>
                         <element name="statusCode" nillable="true" type="xsd:int"/>
                         <element name="statusDesc" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
          </schema>
          <schema targetNamespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="ArrayOf_xsd_string">
                    <complexContent>
                         <restriction base="soapenc:Array">
                              <attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:string[]"/>
                         </restriction>
                    </complexContent>
               </complexType>
          </schema>
     </wsdl:types>
     <wsdl:message name="sendValidateEnprIdQryResponse">
          <wsdl:part name="sendValidateEnprIdQryReturn" type="xsd:boolean"/>
          <wsdl:part name="arg2" type="tns2:ValidateEnprIdRsp"/>
          <wsdl:part name="arg3" type="tns1:ErrRsp"/>
     </wsdl:message>
     <wsdl:message name="sendValidateEnprIdQryRequest">
          <wsdl:part name="arg1" type="tns2:ValidateEnprIdQry"/>
     </wsdl:message>
     <wsdl:message name="sendValidateGwyQryResponse">
          <wsdl:part name="sendValidateGwyQryReturn" type="xsd:boolean"/>
          <wsdl:part name="arg2" type="tns2:ValidateGwyRsp"/>
          <wsdl:part name="arg3" type="tns1:ErrRsp"/>
     </wsdl:message>
     <wsdl:message name="sendValidateGwyQryRequest">
          <wsdl:part name="arg1" type="tns2:ValidateGwyQry"/>
     </wsdl:message>
     <wsdl:portType name="VOIPService">
          <wsdl:operation name="sendValidateGwyQry" parameterOrder="arg1 arg2 arg3">
               <wsdl:input message="impl:sendValidateGwyQryRequest" name="sendValidateGwyQryRequest"/>
               <wsdl:output message="impl:sendValidateGwyQryResponse" name="sendValidateGwyQryResponse"/>
          </wsdl:operation>
          <wsdl:operation name="sendValidateEnprIdQry" parameterOrder="arg1 arg2 arg3">
               <wsdl:input message="impl:sendValidateEnprIdQryRequest" name="sendValidateEnprIdQryRequest"/>
               <wsdl:output message="impl:sendValidateEnprIdQryResponse" name="sendValidateEnprIdQryResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="VOIPServiceSoapBinding" type="impl:VOIPService">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="sendValidateGwyQry">
               <wsdlsoap:operation soapAction=""/>
               <wsdl:input name="sendValidateGwyQryRequest">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
               </wsdl:input>
               <wsdl:output name="sendValidateGwyQryResponse">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
               </wsdl:output>
          </wsdl:operation>
          <wsdl:operation name="sendValidateEnprIdQry">
               <wsdlsoap:operation soapAction=""/>
               <wsdl:input name="sendValidateEnprIdQryRequest">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
               </wsdl:input>
               <wsdl:output name="sendValidateEnprIdQryResponse">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService" use="encoded"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="VOIPServiceService">
          <wsdl:port binding="impl:VOIPServiceSoapBinding" name="VOIPService">
               <wsdlsoap:address location="http://ttdvd12.ebiz.verizon.com:8080/baais_wrelay/services/VOIPService"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
Thanks
Girish

I am briging some vendor information from R3 system to XI thru IDOC. The IDOC Type is "CREMAS.CREMAS01".
I am able to import this into Integration Repository in XI. XI is translating this into XML.
Now insted of creating data types manually, I would like to export this XML into XSD and import into the data type.
When importing this XSD into data type I am getting this error message.

Schema Namespace Scope

Is there a way to set the scope that JAXB uses when marshalling? I found that the marshaller inserts a xmlns attribute on each element that needs that particular namespace. Instead, I want my instance documrnents to have the xmlns namespace prefix attribute in the root element declaration. This way, the remote namespace location and prefix is only declared once instead of repeatedly defining it for each complex element inherited from the remote namespace. My schema includes the identification of the remote namespace and prefix and also has an import line to identify the namespace and a specific schema to import from the namespace.
Here is the schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:xmlns:UGS.MDB" xmlns:cmnLib="urn:xmlns:UGS.CMN" xmlns="urn:xmlns:UGS.MDB" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:import namespace="urn:xmlns:UGS.CMN" schemaLocation="Common.xsd"/>
     <xs:include schemaLocation="MdbCommon.xsd"/>
     <xs:element name="MdbClientIDQueryResponse">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="CmnQueryDialog"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>
Here is the resulting XML instance document from the Marshaller:
<?xml version="1.0" encoding="UTF-8"?>
<MdbClientIDQueryResponse xmlns="urn:xmlns:UGS.MDB" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:xmlns:UGS.MDB MdbClientIDQueryResponse.xsd">
     <CmnQueryDialog>
          <cmnLib:Security xmlns:cmnLib="urn:xmlns:UGS.CMN">
               <cmnLib:Classification>UNCLASSIFIED</cmnLib:Classification>
               <cmnLib:Handling>String</cmnLib:Handling>
          </cmnLib:Security>
          <cmnLib:Power xmlns:cmnLib="urn:xmlns:UGS.CMN">
               <cmnLib:Current>Low</cmnLib:Current>
               <cmnLib:Remaining>4 hours</cmnLib:Remaining>
          </cmnLib:Power>
          <ClientID>alphatango25</ClientID>
     </CmnQueryDialog>
</MdbClientIDQueryResponse>
Here is what I want the XML instance document to look like:
<?xml version="1.0" encoding="UTF-8"?>
<MdbClientIDQueryResponse xmlns="urn:xmlns:UGS.MDB" xmlns:cmnLib="urn:xmlns:UGS.CMN" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:xmlns:UGS.MDB MdbClientIDQueryResponse.xsd">
     <CmnQueryDialog>
          <cmnLib:Security>
               <cmnLib:Classification>UNCLASSIFIED</cmnLib:Classification>
               <cmnLib:Handling>String</cmnLib:Handling>
          </cmnLib:Security>
          <cmnLib:Power>
               <cmnLib:Current>Low</cmnLib:Current>
<cmnLib:Remaining>4 hours</cmnLib:Remaining>
          </cmnLib:Power>
          <ClientID>alphatango25</ClientID>
     </CmnQueryDialog>
</MdbClientIDQueryResponse>

I also faced the same problems and have the solution. If you unmarshal the object to an outputstream using JAXB, then JAXB has no idea what the current scope is. So, create your xml file using either a SAX XMLEventWriter or a StAX XMLSreamWriter. JAXB 2 allows you to marshal your object to either of these writers. These writers know not to bother rebinding the default namespace and this removes the problem.
Other answers on this thread are very unhelpful. There's nothing wrong with wanting to keep xml readable. Why should my xml be littered with unnecessary namespace declarations. Removing these has cut down my file sizes by several Mb.

Error publishing plsql webservice (xml schema mapping and/or serializer)

Hi guys,
I'm with a problem when publishing plsql webservices from JDeveloper 11.
The scenario is something like this:
1) I have a connection with a database 9i, and the objects (packages, object types, etc) are all in there.
2) In this case, i can publish the package spec using the option "Publish as JAX-RPC Web Service" normally.
3) A database 11g was created, and i compiled the objects in this environment.
4) Then i've created a new connection with a database 11g.
5) In this case, when i'll publish the webservice, the error occurs: "The following types used by the program unit do not have an XML Schema mapping and/or serializer specified: REC_DMP_REMESSA"
I have no idea in how to solve this case. Someone can help?
Thank in advance.
Best Regards,
Gustavo

Duplicate of https://forums.oracle.com/thread/2610823
Timo

HL7 schema modification error with imported schema namespace

I have created a variant of one of the out of the box HL7 schemas. The changes were made to the related Segments schema. I have a custom namespace identified on both the "master" schema and one on the modified schema which is being
imported into the "master". I have verified that the namespace of the imported schema matches the namespace identified in the import statement of the master schema. However, I am getting the following error and I'm not sure how to proceed.
There was a failure executing the receive pipeline: "MyProject, MyProject.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=318a75bd6cda7207" Source: "BTAHL7 2.X Disassembler" Receive Port: "rp_ReceiveHL7" URI: "10.26.146.39:11001"
Reason: The namespace attribute 'http://MyProject/2XHL7/MDM/Segments_23' of an import should be the same value as the targetNamespace 'http://microsoft.com/HealthCare/HL7/2X/2.3/Segments' of the imported schema.

Indeed, however, the namespace of the import is same as the value of the imported schema, but the namespace of neither schema is http://microsoft.com/HealthCare/HL7/2X/2.3/Segments,
since I changed it when I made the modification. That namespace does not exist in my project, nor does it exist locally, so i'm not sure where this error message is trying to lead me.

WebService invocation - variable @namespace errro

Hi,
I am getting the below error. (Variable @namespace is not
defined)
I do not know webservices, I am just trying to access a WSDL
file from
flex. Can you please let me know why Flex shows this error?
On which
element is it expecting a namespace. The WSDL file I am using
already
has a targetNamespace.
Even if I do not call any methods from the webservice, I get
this error.
Even if I do only following it give me error. i.e it is
probably
tyring to invoke the webservice and check it.
<mx:WebService id="webService" wsdl="
http://someurl?wsdl">
<mx:operation name="getData"
result="resultHandler(event);"
fault="mx.controls.Alert.show(event.fault.faultString);"
/>
</mx:WebService>
Thanks in advance.
Regards,
Neha
ReferenceError: Error #1065: Variable @namespace is not
defined.
at
mx.rpc.xml::SchemaLoader/schemaImports()[E:\dev\3.0.x\frameworks\projects\rpc\sr\
c\mx\rpc\xml\SchemaLoader.as:102]
at
mx.rpc.wsdl::WSDLLoader/schemaImports()[E:\dev\3.0.x\frameworks\projects\rpc\src\
\mx\rpc\wsdl\WSDLLoader.as:253]
at
mx.rpc.wsdl::WSDLLoader/resultHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\
\mx\rpc\wsdl\WSDLLoader.as:162]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcE\
vent()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:168]
at
mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::resultHandle\
r()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:191]
at
mx.rpc::Responder/result()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\Respo\
nder.as:41]
at
mx.rpc::AsyncRequest/acknowledge()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\r\
pc\AsyncRequest.as:74]
at
DirectHTTPMessageResponder/completeHandler()[E:\dev\3.0.x\frameworks\projects\rp\
c\src\mx\messaging\channels\DirectHTTPChannel.as:381]

I got the same error. How did you solve your problem? By the way, on your post:
var operation:Operation = request.getOperation("getData") as Operation;
What's the definition of request? Thanks.

Extracting XML from webservice result with Namespaces using E4X

Hi,
I need to extract some data from proprietary Web Service (to be fed to HierarchicalData for dataProvider of ADG).
So I made service.returnType=’e4x’;
In that case it returns data as XML.
I need to get useful data from it after Snapshot:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header xmlns:msdwHdr="http://xml.msdw.com/ns/appmw/soap/1.0/header">
<msdw:RequestID xmlns:msdw="http://xml.msdw.com/ns/appmw/soap/1.0/header">restsoap#1390182244050#197728273958044232</msdw:RequestID>
<msdwHdr:FinalMessage>true</msdwHdr:FinalMessage>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ADSSnapshotResponse xmlns="http://xml.ms.com/ns/appmw/dataserver/1.0">
<Snapshot seqNo="0">
<BASE_ELEMENT_NAME BASE_ELEMENT_NAME="4.11.2.0">
Using E4X, like:
var root:XML = event.result as XML; //good!
var xmlRoot1:XMLList = root['SOAP-ENV:Body'].ADSSnapshotResponse.Snapshot.BASE_ELEMENT_NAME;
it does return XMLList (tried different variants), but debugger shows nothing at all inside that XMLList.
var root1:XMLList = root.children(); // that returns valid XMLList with 2 XML elements inside
But all other data I could not get if I use any E4X:
Can I skip Envelope, going to Body as one of its children? suppose I can...
a) root.SOAP-ENV:Body would give compilation errors because of ‘-‘, ‘:’
b) root.Body gives blank XMLList
c) root.Body[0] returns NULL
Any idea how to extract the load from ADS Response (envelope)?
What can I do regarding XML Namespaces in E4X ?
If I set service.returnType="xml" it returns data as XMLNode's.
But I prefer to use E4X if possible.
Please help!
TIA,
Oleg.
P.S.: using Flex 4.5.1 with Flex3 ADG.

not an implementable option for us and cost prohibitive.

N80ie login prob on webservice "unsupported conten...

I sent a link to my phone for plaxo mobile, and from there I can login successfully. Subsequently I saved the link as a bookmark, and whenver I try to log in from the bookmark, I get an error message "unsupported content type." From the original email I can still login successfully, but never from the bookmark.
From Y!go I'm finding that I can't login either, it claims another application is using the Internet, please stop the other application, but there is no other app. using the internet.

i get "unsupported content type" if I try to visit wap sites with the S60 browser. Visiting normal web sites is fine.
No issues with Y!go2 on the N80 for meMessage Edited by iggy23 on 30-Apr-200704:05 PM
Currently using E71, looking at options

Change namespace in generated WebService

Hello experts,
i have to provide a webservice with three methods for an external Client.
So i created three functions in a function group. From the function group i autocreated my webservice with the wizzard. I changed the external/internal mapping properly, activate the webservice and create with soamanager a service and an endpoint and so on...
When i create a client with the autogenerated WSDL from the WebService, i can call and reach the autogenerated Webservice from this client.
The problem is: The external client cant reach our webservice. We have solved all problems with firewalls and certificates. The remaining problem is the namespace. The external clients request (we cant change it and have to provide a suitable webservice) with the namespace "urn:extnamespace" cant reach our servicepoint (error "service >extnamespace:Connect< not supported") :
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:extnamespace="urn:extnamespace">
<SOAP-ENV:Body>
<extnamespace:Connect>
    <token>123456</token>
</extnamespace:Connect>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
From our test- client we use successfully this with the namespace "urn:sap-com:document:sap:rfc:functions"::
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:extnamespace="urn:sap-com:document:sap:rfc:functions">
<SOAP-ENV:Body>
<extnamespace:Connect>
    <token>123456</token>
</extnamespace:Connect>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The wizzard have automaticaly generated the namespace "urn:sap-com:document:sap:rfc:functions". The external Client use another namespace. We have no option to change the external client or request of it. We need to provide a suitable WebService which use the same namespace.
We found no possibility to say the generation wizzard to use another namespace. Also we found no possibility with soamanager to change it. When we change the namespace in XSLT-Transformation with STRANS and call the WebService from our test client, we get allways the error "service >extnamespace:Connect< not supported".
The following links seems to be good on first sight, but dont help us:
[Changing SOAP Namespace for Web Service;
[service.sap.com/notes]   sap note 853824
If there is no way to change the namespace, we have to create the webservice manually. Is there a suitable example for this job available?
Greetings & thank you very much for your help!
Edited by: JosipI on Dec 17, 2010 3:16 PM

We have created a server interface in XI with the wsdl excepted by the external client. Then created a server proxy with this interface in our sap system. Then we have implemented the generated methodes by calling existing functions. It works fine.
Thanks a lot!
Edited by: JosipI on Dec 23, 2010 1:24 PM
Edited by: JosipI on Dec 23, 2010 1:25 PM

Resolve xml namespace while importing xml schema

Hi All,
I am using ALSB 2.6 on windows platform. I have created a xml schema resource in a project folder. XML schema resource location is "/ANUP/TEST/SCHEMA". The target namespace for this schema is "http://test/schema/audit/properties.xsd". The XML schema file name is Properties.xsd.
I want to import this schema structure into an xquery which is the in project folder "/ANUP/TEST". My statement in xquery is:
xquery version "1.0";
import schema namespace ns6="http://test/schema/audit/properties.xsd" at "/ANUP/TEST/SCHEMA/Properties.xsd";
declare function getCustomer() as element(ns6:dummyParent){
let $anup := "anup"
return <ns6:dummyParent>
<ns6:dummy1>anup</ns6:dummy1>
<ns6:dummy2>tripathi</ns6:dummy2 >
<ns6:dummy3>anup</ns6:dummy3>
</ns6:dummyParent>
getCustomer()
When I try to save this xquery, I get the error ::
An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource "/ANUP/TEST/SCHEMA/Properties.xsd": {1}.
I tried to change the values instead of "/ANUP/TEST/SCHEMA/Properties.xsd" in import schema namespace statement and found out that if I put Properties.xsd in "C:\ANUP\TEST\SCHEMA", it works.
Can somebody tell me how can I change this clause after "at" keyword so that I can browse to the XMl schema which has been imported into ALSB and part of project folder?
Thanks:
Anup

I have the same is issue in Oracle OSB 11g. Does anyone have any idea how to import an xml-schema inside an XQuery, when the schema is present in the OSB-project (and not on filesystem or hosted on some URL).
import schema namespace ns="http://someNamespace.com" at "/path/to/schema/in/OSB/schema.xsd";
The above format gives the error "An error occurred compiling the XQuery resource: line ##, column ##: {err}FODC0002: Error retrieving resource"

Efficient reverse proxy for Schema based BizTalk webservices

I've got a few webservices hosted on BizTalk I'm wanting to expose with a reverse proxy.
Checking through this article it seems there is some disconnect.
http://msdn.microsoft.com/en-us/magazine/cc748658.aspx
The article outlines how to do this with a webservice generated from an orchestration. But I created my webservices from schemas. The structure of my asmx.cs doesn't appear to be the same. See Figure 8 in the article.
When I try to do
AZDHS_AIE_Internal.AIE objWebServiceMethodCall new AZDHS_AIE_Internal.AIE();
objWebServiceMethodCall.Url = "real URL goes here";
There is no Url member inside the instance of AIE that is created. It is the proper class which contains the web methods, so I was surprised to not see it there.
Anyone else tried to get this scenario working before? I'm not finding much resources for schema based webservices, only orchestration based ones.

Alright, got it working.
Here the short story of how to get this working. Make a copy of the generated webservice solution from BizTalk. In it you'll see there is a
DataTypes.cs class.
Next, you'll generate a proxy class of the target webservice using the visual studio command line wsdl tool (wsdl http://url/svc.asmx?wsdl). Make sure this class is named differently than the actual webservice is since that is the same
name you've got in the BizTalk generated webservice solution.
In the new proxy class replace the return and parameter types in the web methods to be the corresponding types in the
DataTypes.cs class.
In the BizTalk webservice code go to your web method where it currently puts the received message into the messagebox database. There you will create a new instance of the new proxy class and call the corresponding web method, which now has the same type
definition in both the proxy class and the BizTalk generated class.
And that's all. Build and deploy to a server anywhere with access to the actual BizTalk server and your calls will bounce off the webserver and go to BizTalk.

WebService - Unsupported Schema Namespace

Similar Messages

Maybe you are looking for