QName vs NCName

Hi Everyone,
I hope I'm not posting this in the wrong forum. I have a 3 questions regarding QName and NCName in an XML document:
1. In an XML document, if an element belongs to a namespace, can I still include it as NCName if its name does not clash with a name from the default namespace.
2. As far as XML elements are concerned, do only elements belonging to default namespace can be included as NCNames? I guess the answer to this question also depends on the answer to the first question. Meaning if I can include an element that does not belong to the default namespace without the prefix associated with its namespace, then that would mean that it is possible to include that name as NCNames.
3. Since we never colonize attribute names, then attribute names are always NCNames. Is this correct?
Thanks for your time and response,
Mehrdad

Thanks for your reply. You are quiet correct in your assumption that I still don't quiet understand issues regarding namespaces. Your reply definitely answered my question regarding including attributes using QName;
To make my other question more clear, I will use the following example:
<?xml version="1.0"?>
<!DOCTYPE root SYSTEM "root.dtd">
<root
xmlns:h="http://www.w3.org/TR/html4/"
xmlns:f="http://www.w3schools.com/furniture">
<h:table>
<h:tr>
<h:td>Apples</h:td>
<h:td>Bananas</h:td>
</h:tr>
</h:table>
<f:table>
<f:name>African Coffee Table</f:name>
<f:width>80</f:width>
<f:length>120</f:length>
</f:table>
*<wood>*
*<type>redwood</type>*
*</wood>*
</root>
Suppose the the element <wood> Note that the element <wood> is supposed to be in the http://www.w3schools.com/furniture namespace, but I have included it without a namespace prefix. Would this invalidate the xml document?
Maybe you can confirm/clarify this for me as well. I think I had the wrong assuption about NCNames and thought that only elements belonging to the default namesapce can be included as NCNames. However, right now, I think that any element regardless of whether they belong to the default namespace or not, can be included as either NCNames or QName.
Thanks again for taking the time to respond to me.

Similar Messages

  • Dynamic XSLT Sort Routine to XML (NCName:* or QName was expected)

    I am trying to create a XSLT Stylesheet to perform dynamic sorts (via parameters) on XML data with the desired output being XML... I've declared everything static in my StyleSheet for debugging purposes:
    XML Document:
    <?xml version="1.0" encoding="UTF-8"?>
    <Content>
    <task:TASK id="25"
    src:col="/db/iconnect/MappingCenterCRM/default/TASK"
    src:key="25" xmlns:src="http://xml.apache.org/xindice/Query" xmlns:task="http://iconnect.com/schemas/task">
    <task:user_id>123</task:user_id>
    <task:long_description>This is my description...</task:long_description>
    <task:priority>1</task:priority>
    <task:status>Completed</task:status>
    </task:TASK>
    <task:TASK id="26"
    src:col="/db/iconnect/MappingCenterCRM/default/TASK"
    src:key="26" xmlns:src="http://xml.apache.org/xindice/Query" xmlns:task="http://iconnect.com/schemas/task">
    <task:user_id>123</task:user_id>
    <task:long_description>Another description...</task:long_description>
    <task:priority>1</task:priority>
    <task:status>New</task:status>
    </task:TASK>
    </Content>
    Here is my Stylesheet:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:task="http://iconnect.com/schemas/task" xmlns:src="http://xml.apache.org/xindice/Query">
    <xsl:output method="xml" />
    <xsl:param name="sortBy" select="task:long_description" />
    <xsl:param name="xPath" select="//Content/task:TASK" />
    <xsl:param name="orderByType" select="ascending" />
    <xsl:template match="$xPath | node()">
    <xsl:copy>
    <xsl:apply-templates>
    <xsl:sort select="$sortBy" order="ascending"/>
    </xsl:apply-templates>
    </xsl:copy>
    </xsl:template>
    </xsl:stylesheet>
    When I run in XMLSpy, I get the desired results, but when running using Xerces, I get the following error:
    javax.xml.transform.TransformerException: A node test that matches either NCName:* or QName was expected.

    I am trying to create a XSLT Stylesheet to perform dynamic sorts (via parameters) on XML data with the desired output being XML... I've declared everything static in my StyleSheet for debugging purposes:
    XML Document:
    <?xml version="1.0" encoding="UTF-8"?>
    <Content>
    <task:TASK id="25"
    src:col="/db/iconnect/MappingCenterCRM/default/TASK"
    src:key="25" xmlns:src="http://xml.apache.org/xindice/Query" xmlns:task="http://iconnect.com/schemas/task">
    <task:user_id>123</task:user_id>
    <task:long_description>This is my description...</task:long_description>
    <task:priority>1</task:priority>
    <task:status>Completed</task:status>
    </task:TASK>
    <task:TASK id="26"
    src:col="/db/iconnect/MappingCenterCRM/default/TASK"
    src:key="26" xmlns:src="http://xml.apache.org/xindice/Query" xmlns:task="http://iconnect.com/schemas/task">
    <task:user_id>123</task:user_id>
    <task:long_description>Another description...</task:long_description>
    <task:priority>1</task:priority>
    <task:status>New</task:status>
    </task:TASK>
    </Content>
    Here is my Stylesheet:
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:task="http://iconnect.com/schemas/task" xmlns:src="http://xml.apache.org/xindice/Query">
    <xsl:output method="xml" />
    <xsl:param name="sortBy" select="task:long_description" />
    <xsl:param name="xPath" select="//Content/task:TASK" />
    <xsl:param name="orderByType" select="ascending" />
    <xsl:template match="$xPath | node()">
    <xsl:copy>
    <xsl:apply-templates>
    <xsl:sort select="$sortBy" order="ascending"/>
    </xsl:apply-templates>
    </xsl:copy>
    </xsl:template>
    </xsl:stylesheet>
    When I run in XMLSpy, I get the desired results, but when running using Xerces, I get the following error:
    javax.xml.transform.TransformerException: A node test that matches either NCName:* or QName was expected.

  • QName error while calling a web service from Sourcing

    I need to call a web service from Sourcing script. The web service team has provided us the WSDL and I have generated the required stubs using wsimport and packaged the required java classes in a custom JAR. Now while calling a web method using this jar from my script, I am getting and exception. The exception message that I printed out was this:
    Caught exception e with msg Connection IO Exception. Check nested exception for details. (Connection
    IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
    java.lang.IllegalArgumentException: cannot create QName from "null" or "" String).)
    The same jar and same code works fine when called from a standalone java program.
    I am not using or creating QName anywhere in my script. The only place where QName is used is in the generated java class and there it is created from the correct namespace URL
    Can anyone please help me out in figuring out what is the issue?

    This is the stack trace of the error:
    #2.0 #2014 05 08 09:02:30:915#+00#Error#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#
    #BC-ESI-WS-JAV-RT#webservices_lib#C000CF8242BA4B800000002100002648#2174850000000005#sap.com/E-Sourcing-Server#com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding#VAC53324#89##D811EE96D68E11E3C9E0000000212F82#3cf7fe38d68f11e3c963000000212f82#3cf7fe38d68f11e3c963000000212f82#0#Thread[RequestHandler.RqThread: fullsave,5,Dedicated_Application_Thread]#Plain##
    Connection IO Exception. Check nested exception for details. (Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
        java.lang.IllegalArgumentException: cannot create QName from "null" or "" String).).
    [EXCEPTION]
    com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
        java.lang.IllegalArgumentException: cannot create QName from "null" or "" String).).
        at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.writeSOAPRequestMessage(SOAPTransportBinding.java:256)
        at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1318)
        at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:991)
        at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:945)
        at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
        at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)
        at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)
        at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)
        at $Proxy2539.grantOrganizationRoles(Unknown Source)
    I tested the same custom JAR, that is deployed in Sourcing, separately using a standalone java program and there it gave back the correct SOAP response

  • Problem with axis2 and QName class

    Hello,
    We have deployed AXIS2 library with a library project (J2EE server component) as it is specify by a SAP guide. We deployed the sda file correctly and we know how to reference this library in Portal Application and J2ee Module WEB or EJB.
    The problem is when we want to use internally javax.xml.namespace.QName is thrown an exception. This exception is shown bellow:
    java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
    at wpt.ConventerStub.populateAxisService(ConventerStub.java:52)
    at wpt.ConventerStub.<init>(ConventerStub.java:100)
    at wpt.ConventerStub.<init>(ConventerStub.java:89)
    at wpt.ConventerStub.<init>(ConventerStub.java:140)
    at wpt.ConventerStub.<init>(ConventerStub.java:132)
    at com.eadscasa.axis2.Axis2Converter.doContent(Axis2Converter.java:26)
    In the guide is said that we have to deploy a library project to avoid this problem but we still are getting it. I have realized that Qname class is a basic class into the JDK 1.4 and in different projects as AXIS2 making revision about this class.
    How can I deploy these libraries (jars) without dependencies with SAP Portal libraries?
    Is there any way to setup the classloader to avoid this error?
    In the documentation about this kind of project it is said that you cannot deploy libraries (*.jar) with the same name. I donu2019t know if it happens the same with the class.
    We have to develop web Services with Soap 1.2 specification, SAML etc and we need to develop this class because sap portal doesnu2019t support this kind o features.
    Regards,
    Daniel Urbano

    Hi,
    Firstly thanks for you reply. I generate the client with wsdl2java tool as it is mentioned in AXIS2 documentation and as you specified in your blog. After I follow the steps:
    Step 1 - Generating the Axis2.war
    Step 2 u2013 Modify the service *.aar file
    Step 3 u2013 Create the J2EE library
    Step 4 u2013 Create the J2EE application wrapping the web module axis2.war
    We know how to make the step 1,2 and 3 but there is a little mess in the last step. Donu2019t worry about this because we got the general idea in this document. According to the guide the main problem is to solve a classloading conflict because it only can be loaded the libraries once and you need the AXIS2 libraries for *.arr and for the axis2 engine to be able to manage this module. This problem it is solved making a J2EE library Project and putting a reference to this library in the module, applications or project, which have to use AXIS2 libraries.
    We have 3 different kind of projects that we can develop according to Sap Netweaver:
    J2EE Project:
    ·     Web Module Project: Resulting a war file.
    ·     Enterprise Application Project: Resulting a ear file
    ·     EJB Module Project: Resulting a war file.
    Portal Application
    ·     Portal Application Project: Resulting a par file.
    In any project mentioned upper we know how to deploy these with a reference to this library project that previously we deployed successfully in the portal. But the problem is when we are going to check this module running it the server give us an exception.
    java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
    at wpt.ConventerStub.populateAxisService(ConventerStub.java:52)
    at wpt.ConventerStub.(ConventerStub.java:132)
    at com.eadscasa.axis2.Axis2Converter.doContent(Axis2Converter.java:26)
    This exception is because exist classes into the axis2 libraries as javax.xml.namespace.Qname that are in SAP Portal libraries into the J2ee Server (JDK 1.4). This conflict is mentioned in the blog u201C360° View on enterprise SOAu201D where Michael Koegel, the author, says that if you want that AXIS2 libraries works you will have to work around with the dependencies of libraries.
    The main problem in this point it is that we donu2019t know how to resolve this dependencies and if it is possible that other module of SAP Portal wonu2019t work fine if we change the base libraries. AXIS2 has newer classes than SAP Portal and it is possible that we can break other SAP Portal functions. In this case if we can not get that AXIS2 and SAP Portal co-exist in the same server we will probably have to change our way to get the enterprise objectives.
    In order to resolve these dependencies we have found a SAP Note Number: 1138545. In this note it is said that we can setup the precedence class loader in the visual admin  into the deploy service. If you add your AXIS2 library at the beginning of StandardAplicationReferences variable in the deploy service, it is loaded the axis2 libraries first and it works the services but other portal functionality fails. This variable it is used to load the libraries precedence for all applications in the Server. If we could setup the class load precedence in a web module project or the system doesnu2019t take into account the server libraries for this module it will work perfectly.
    If you could specify more the last point of your manual, I will appreciate it.
    Regards,
    Daniel Urbano

  • Calling a CAF program via web service generates QName cannot be null error, but only for 1/5 of the same call in a parallel for loop.

    I'm calling 5 identical web service calls using a parallel for loop in BPM. Obviously the data in each slightly differs. Why would this call suspend the process and give the following errors:
    handleCommunicationError( ErrorContextData, Throwable, TransitionTicket ): A technical error occurred.
    Interface namespace = myNamespace
    Interface name = myService
    Operation name = myOperation
    Connectivity type = WS
    Application name = myAppName
    Reference name = 8bd95deb-8cf1-453d-94e5-0576bb385149
    Message Id = null
    WS style = DOC
    Start time of WS call = 2014-02-26 17:51:23.297
    Return time of WS call = 2014-02-26 17:51:23.412
    Principal name = SAP_BPM_Service
    Root error message = local part cannot be "null" when creating a QName
    Error message = Could not invoke service reference name 8bd95deb-8cf1-453d-94e5-0576bb385149, component name myComp application name myappname
    com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name 8bd95deb-8cf1-453d-94e5-0576bb385149, component name
    myCompname
    at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:341)
    at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:101)
    at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:101)
    at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:178)
    at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:657)
    at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:248)
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:78)
    at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:196)
    at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:163)
    at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
    at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:261)
    at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:152)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:337)
    at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:149)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
    Caused by: java.lang.IllegalArgumentException: Could not process message for operation myOperation in web service plugin module.
    at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:228)
    at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:314)
    ... 19 more
    Caused by: java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
    at javax.xml.namespace.QName.<init>(QName.java:246)
    at javax.xml.namespace.QName.<init>(QName.java:190)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceImpl.getInterfaceInvoker(DInterfaceImpl.java:126)
    at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASImpl.<init>(WSDASImpl.java:43)
    at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASFactoryImpl.createWSDAS(WSDASFactoryImpl.java:39)
    at com.sap.engine.services.sca.plugins.ws.tools.wsdas.WsdasFactoryWrapper.createWsdas(WsdasFactoryWrapper.java:30)
    at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.initWsdas(WebServiceImplementationInstance.java:256)
    at com.sap.
    Surely if it was the service group unassign then reassign issue then none of the calls would have worked?

    Hi David,
    While a random error is still an error it will be difficult for support to find a problem for an error which is not reproducible. It is always a faster resolution if you can determine how to provoke the error and provide those details. If we can reproduce an error on internal systems then we can fix the problem quickly and without having to access your system.
    regards, Nick

  • Web Dynpro Import Web Service Model - not a valid NCName

    Hi people,
    We are having a problem while importing a WSDL as an Adaptive Web Service Model in Web Dynpro (CE 7.2 SP03).
    The error is the following:
    "Definition of qualified base /schema/element[5]/complexType/sequence/element[4] is not correct. The value of property is not a valid NCName."
    We tried importing the same WSDL in other tools (XML Spy and SOAP UI). With these tools it could be read without errors and were able to successfully call the service.
    The point is, why the import fails in Web Dynpro if the WSDL can be read in other tools ? Can we do something in WD to import the WSDL that is supposed to be "not correct" ?
    Thanks in advance for your comments,
    Daniel

    Hi Pranav,
    I was facing this issue sometime back and i figured out that the ABAP proxy namespace in my case had a '/' in it, because of which the internal name of the service had a '/' character too.
    And this was unacceptable for the endpoint binding name in my case.
    Since it is occuring for you in case of the service name (i figured it out from attribute definations/services@name), check if the proxy name have a special character like '/'.
    Regards,
    Vivek

  • WebLogic Server 8.1 and Axis 1.2: LinkageError qname?

    I am trying to run Axis 1.2 inside WebLogic. It runs fine on JBoss, but I am getting strange errors in WebLogic 8.1 SP6.
    Happyaxis validation seems to be ok, but as soon as a WSDL needs to be generated I get the following exception: weblogic LinkageError loader constraints violated when linking javax.xml.namespace.QName
    I made sure that all the libraries are there and these are loaded from the lib folder of the WAR. One library in specific, qname.jar (that is related to the exception), was additionaly mentioned in the classpath before all other libraries but the exception still occurred.
    Is this problem familiar to someone?

    I too have had problems using WebLogic Builder to add the WebLogic Deployment Descriptors.
    I some places there are typos, others lack of Resource Reference Envionment tabs under Resources.
    Other times I have generated and saved the deployment descriptors, only to have them recreated the next time I go into WebLogic Builder again.
    Using the "Refresh Module" removes many of the CMP Fields and Primary Key fields in Persistence for some reason.
    Basically, WebLogic Builder is very unfriendly in porting jAppServer2004.

  • Error:1067 - Implicit coercion of a value of type QName to an unrelated type QName

    hi,
    I'm new in flex and my english not good. I'll try to explain
    my problem :(
    I have an application mxml and a component mxml. I imported a
    wsdl from .net webservice.
    In main mxml I added:
    <mx:Application .....
    xmlns:webservices="generated.webservices.*"/>
    and
    <webservices:xService id="m_service"/>
    there is no problem for this. But when I added into component
    mxml like this:
    <mx:Canvas.....
    xmlns:webservices2="generated.webservices.*"/>
    and
    <webservices2:xService id="m_service2"/>
    I'm getting the following error:
    error line sample: (and 633 similar lines in
    generated.webservices)
    responseMessage.wrappedQName = new QName("
    http://tempuri.org/","GetMemberListResponse");
    error:
    1067: Implicit coercion of a value of type QName to an
    unrelated type QName
    When I removed the <webservices2:xService
    id="m_service2"/> line from component mxml, I'm not getting an
    error.
    Flex 3.0 - sdk 4.0
    Thanx for your helps

    thanx your answer,
    I changed (like this:[WebService(Namespace = "
    http://Info.WebService/MyInfoService"))
    but it doesn't work. I still have same problem.
    It's really strange problem. When I used in application mxml,
    it's working. But when I used in component mxml, I'm getting error.
    I tested the web servise in other test application mxml with
    following code: (it's working excellent)
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="
    http://www.adobe.com/2006/mxml"
    layout="absolute" xmlns:webservices="generated.webservices.*"
    creationComplete="test12()">
    <mx:Script>
    <![CDATA[
    import mx.rpc.AsyncToken;
    private function test12():void
    m_service12.addgetFuelList_header(GetAuthHeader());
    m_service12.getFuelList();
    ]]>
    </mx:Script>
    <mx:Script source="***/ServiceAuthHeaderGetter.as"/>
    <webservices:TankInfoService id="m_service12"/>
    <mx:DataGrid
    dataProvider="{m_service12.getFuelList_lastResult}">
    </mx:DataGrid>
    </mx:Application>
    And finally I closed "Enable strict type checking" from
    project properties and the errors are disappeared.
    But now I got new problems with webservice :)
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference.
    I guess <webservices:TankInfoService id="m_service"/>
    is null.
    But why?
    in component mxml
    I added xmlns:webservices="generated.webservices.*" namespace
    and
    <webservices:TankInfoService id="m_service"/>
    my code is:
    m_service.addgetMemberList_header(GetAuthHeader());
    m_service.getMemberByUserPassword(this.txtUser.text,
    this.txtPassword.text);
    the error:
    TypeError: Error #1009: Cannot access a property or method
    of a null object reference.
    Any ideas???

  • DSP Web Service Data Source runtime error "Invalid xsi:type qname"

    I have created a DSP data service that uses a web service as a data source.
    The web service wraps an Oracle PL/SQL package and works when tested independantly of the DSP data service.
    When I test the DSP data service using the weblogic workshop test view I get the error below:
    weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
    (The full stack trace and the WSDL imported into DSP are at the bottom of this posting)
    I am new to DSP but I have created data services from the DSP tutorials succesfully before.
    This is the first data service I have tried to create which is not from a DSP tutorial.
    I dont really understand the error message.
    It appears to me that type EmpRecUser is being prefixed by the wrong name space. In the WSDL the namespace is 'tns:' in the error message the namespace is: 'ns0'.
    <element name="getEmpResponseElement">
    <complexType>
    <sequence>
    <element name="result" type="tns:EmpRecUser" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    I created the web service in Oracle J Developer from the tutorial URL below.
    http://www.oracle.com/technology/obe/obe1013jdev/10131/wsfromplsqlpackage/devwsfrom%20plsql.htm#p
    weblogic.xml.query.exceptions.XQueryDynamicException: {err}XQ0027: Validation failed: error: cvc-elt.4.2: Invalid xsi:type qname: 'ns0:EmpRecUser' in element getEmpResponseElement@http://hr/EmpWebService.wsdl/types/
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:169)
         at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
         at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
         at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
         at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
         at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
         at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
    Caused by: weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ValidationException: null
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans$ExceptionCollection.add(XMLValidatorForXMLBeans.java:340)
         at org.apache.xmlbeans.impl.validator.Validator.emitError(Validator.java:175)
         at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:207)
         at org.apache.xmlbeans.impl.validator.Validator.emitFieldError(Validator.java:193)
         at org.apache.xmlbeans.impl.validator.Validator.beginEvent(Validator.java:458)
         at org.apache.xmlbeans.impl.validator.Validator.nextEvent(Validator.java:246)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processBeginElementToken(XMLValidatorForXMLBeans.java:1205)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processToken(XMLValidatorForXMLBeans.java:1322)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.processTokensOnHold(XMLValidatorForXMLBeans.java:1349)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.gotBeginElementToken(XMLValidatorForXMLBeans.java:772)
         at weblogic.xml.query.schema.xmlbeans.XMLValidatorForXMLBeans.giveToken(XMLValidatorForXMLBeans.java:100)
         at weblogic.xml.query.schema.ValidatingIterator.fetchNext(ValidatingIterator.java:148)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at com.bea.ld.wrappers.ws.JAXRPCWebserviceIterator.fetchNext(JAXRPCWebserviceIterator.java:104)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
         at weblogic.xml.query.iterators.GenericIterator.hasNext(GenericIterator.java:134)
         at weblogic.xml.query.runtime.sequences.Subsequence.fetchNext(Subsequence.java:101)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.querycide.QueryAssassin.fetchNext(QueryAssassin.java:54)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at weblogic.xml.query.runtime.qname.InsertNamespaces.fetchNext(InsertNamespaces.java:238)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.runtime.core.QueryIterator.fetchNext(QueryIterator.java:127)
         at weblogic.xml.query.iterators.GenericIterator.next(GenericIterator.java:113)
         at weblogic.xml.query.xdbc.iterators.ItemIterator.fetchNext(ItemIterator.java:86)
         at weblogic.xml.query.iterators.GenericIterator.peekNext(GenericIterator.java:151)
         at weblogic.xml.query.xdbc.util.Serializer.processNamespaces(Serializer.java:340)
         at weblogic.xml.query.xdbc.util.Serializer.processElement(Serializer.java:262)
         at weblogic.xml.query.xdbc.util.Serializer.process(Serializer.java:206)
         at weblogic.xml.query.xdbc.util.Serializer.serializeItems(Serializer.java:152)
         at com.bea.ld.server.QueryInvocation.getResult(QueryInvocation.java:461)
    <definitions
    name="EmpWebService"
    targetNamespace="http://hr/EmpWebService.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://hr/EmpWebService.wsdl"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:tns0="http://hr/EmpWebService.wsdl/types/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    >
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hr/EmpWebService.wsdl/types/"
    elementFormDefault="qualified" xmlns:tns="http://hr/EmpWebService.wsdl/types/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
    <element name="getEmpElement">
    <complexType>
    <sequence>
    <element name="empNo" type="decimal" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <element name="getEmpResponseElement">
    <complexType>
    <sequence>
    <element name="result" type="tns:EmpRecUser" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <complexType name="EmpRecUser">
    <complexContent>
    <extension base="tns:EmpRecBase">
    <sequence>
    <element name="departmentId" type="decimal" nillable="true"/>
    <element name="managerId" type="decimal" nillable="true"/>
    <element name="hireDate" type="dateTime" nillable="true"/>
    <element name="jobId" type="string" nillable="true"/>
    <element name="employeeId" type="decimal" nillable="true"/>
    <element name="commissionPct" type="decimal" nillable="true"/>
    <element name="salary" type="decimal" nillable="true"/>
    <element name="lastName" type="string" nillable="true"/>
    </sequence>
    </extension>
    </complexContent>
    </complexType>
    <complexType name="EmpRecBase">
    <sequence/>
    </complexType>
    </schema>
    </types>
    <message name="EmpWebService_getEmp">
    <part name="parameters" element="tns0:getEmpElement"/>
    </message>
    <message name="EmpWebService_getEmpResponse">
    <part name="parameters" element="tns0:getEmpResponseElement"/>
    </message>
    <portType name="EmpWebService">
    <operation name="getEmp">
    <input message="tns:EmpWebService_getEmp"/>
    <output message="tns:EmpWebService_getEmpResponse"/>
    </operation>
    </portType>
    <binding name="EmpWebServiceSoapHttp" type="tns:EmpWebService">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="getEmp">
    <soap:operation soapAction="http://hr/EmpWebService.wsdl/getEmp"/>
    <input>
    <soap:body use="literal"/>
    </input>
    <output>
    <soap:body use="literal"/>
    </output>
    </operation>
    </binding>
    <service name="EmpWebService">
    <port name="EmpWebServiceSoapHttpPort" binding="tns:EmpWebServiceSoapHttp">
    <soap:address location="http://localhost:8888/PL_SQL_WS-GetEmployee-context-root/EmpWebServiceSoapHttpPort"/>
    </port>
    </service>
    </definitions>

    DSP validates the results from webservices. Whatever you tested the webservice with outside of DSP, probably does not.
    Can you capture the output of the webservice and attach it as well? You can capture the webservice response by running the wls server with the command-line property -Dweblogic.webservice.verbose=true
    Can you also open a case with customer support for this? I will not likely have much time to look at it.
    - Mike
    btw - the namespace prefixes are just place-holders that are defined with xmlns:prefix="some-uri". It is the namespace uri's that must be equivalent. If, in one case you have the definition xmlns:tns="myUri" and in another case xmlns:ns0="myUri" - then tns:EmpRecUser is equivalent to ns0:EmpRecUser.
    Perhaps in the webservice result there is no definition, or an incorrect definition for the namespace prefix ns0 - that would explain the complaint about the QName ns0:EmpRecUser. According to the wsdl, there should be a definition for ns0 as :
    xmlns:ns0="http://hr/EmpWebService.wsdl"
    in the webservice response.

  • Web Service call through XI returns SAP error( QName is 'xmlns'.....)

    Has any one come across this type of error.
    We are in XI 3.0 SP14 on AIX Platform.
    We are trying to get StockQuote Service working to test SOAP Adapter.
    Appreciate suggestions to resolution of the problem.
    Thanks
    Prasad
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: QName is 'xmlns', but URI is not 'http://www.w3.org/2000/xmlns/' in the qualified name, 'xmlns'</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi,
    I am also facing the same problem with SPS15(preview version)on MAXDB. But i am not using XI but instead sending SOAP Message over http (in a portal application). Kindly let me know the solutions if you know it.
    Regards,
    Satish

  • Schema qname collision issue

    I am trying to apply a BPEL orchestration (11g PS2) to receive and process an outbound msg from Salesforce. Salesforce provides the wsdl for the outbound msg that Salesforce sends to my service. Alone, this is not a problem. However, circumstances require that I do additional queries of Salesforce. The wsdl for these queries is separate. The problem I have is that the schemas for both wsdls (the schemas are in-line in both cases) share the same namespace for some schema definitions, resulting in duplicate qnames. In one case, the duplicate qnames represent distinctly different definitions (one is essentially a subset of the other). I naively hoped that I could get away with having both in the same composite (ordering them such that the last import trumps the first import in the case of common definitions while all other definitions are merged). It appears that one import only is applied. I can change which one is applied by reordering the imports in the composite - not quite what I had hoped for. My way around this problem has been to construct a sort of proxy composite to keep the two wsdls from 'touching'. Can anyone suggest a better way to handle this situation?
    Thanks,
    Cris

    1 set up a default tablespace for the target user
    2 Make sure the target user doesn't have the RESOURCE role and/or UNLIMITED TABLESPACE privilege.
    3 Make sure the target user has QUOTA on the default tablespace ONLY
    alter user quota unlimited on <target> quota 0 on <the rest>
    4 Import without importing indexes, those won't be relocated.
    5 Imp indexfile=<any file> ---> file with create index statements
    6 edit this file, adjusting tablespaces
    7 run it.
    Tablespaces can't be renamed in 9i.
    Sybrand Bakker
    Senior Oracle DBA

  • Axis QName prefix not working?

    I'm new to Axis nad I would like to change the default ns1 namespace prefix to something else when generating SOAP XML. I'm using version 1.4 and here is the code that I'm testing (just the Call section):
    Call call = (Call)service.createCall();
    call.initialize();
    call.setSOAPActionURI("urn:oasis:names:tc:SAML:1.1:protocol#Request");
    call.setTargetEndpointAddress(new java.net.URL(endpoint));
    call.setOperationName(new QName("urn:oasis:names:tc:SAML:1.1:protocol", "Request", "samlp"));
    call.addParameter("AssertionArtifact", XMLType.XSD_STRING, ParameterMode.IN);
    call.setReturnType(XMLType.XSD_STRING);
    String ret = (String) call.invoke(new Object[] { "rebh3eayWC2MccWP1R76" });As you can see in QName I give the prefix "samlp". This is what it generates:
    <?xml version="1.0" encoding="UTF-8"?>
       <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <soapenv:Body>
             <ns1:Request soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:oasis:names:tc:SAML:1.1:protocol">
                <AssertionArtifact xsi:type="xsd:string">rebh3eayWC2MccWP1R76</AssertionArtifact>
             </ns1:Request>
          </soapenv:Body>
       </soapenv:Envelope>It shows the default "ns1" instead of "samlp". Is there a way to add this prefix also to the "AssertionArtifact" tag?

    I'm new to Axis nad I would like to change the default ns1 namespace prefix to something else when generating SOAP XML. I'm using version 1.4 and here is the code that I'm testing (just the Call section):
    Call call = (Call)service.createCall();
    call.initialize();
    call.setSOAPActionURI("urn:oasis:names:tc:SAML:1.1:protocol#Request");
    call.setTargetEndpointAddress(new java.net.URL(endpoint));
    call.setOperationName(new QName("urn:oasis:names:tc:SAML:1.1:protocol", "Request", "samlp"));
    call.addParameter("AssertionArtifact", XMLType.XSD_STRING, ParameterMode.IN);
    call.setReturnType(XMLType.XSD_STRING);
    String ret = (String) call.invoke(new Object[] { "rebh3eayWC2MccWP1R76" });As you can see in QName I give the prefix "samlp". This is what it generates:
    <?xml version="1.0" encoding="UTF-8"?>
       <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <soapenv:Body>
             <ns1:Request soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:oasis:names:tc:SAML:1.1:protocol">
                <AssertionArtifact xsi:type="xsd:string">rebh3eayWC2MccWP1R76</AssertionArtifact>
             </ns1:Request>
          </soapenv:Body>
       </soapenv:Envelope>It shows the default "ns1" instead of "samlp". Is there a way to add this prefix also to the "AssertionArtifact" tag?

  • Incorrect value: Namespace prefix q1 of QName q1:RequestArray is undeclared

    Can someone please help me understand this error message?
    Incorrect value: Namespace prefix q1 of QName q1:RequestArray is undeclared
    Exception of class CX_SLIB
    I get this error when generating the Proxy Class.
    The URL of the Web Service WSDL is:
    https://addresscheck.melissadata.net/v2/SOAP/Service.svc?wsdl
    I found an OSS note which looked promising, but even after implementing the note I still get the error.
    OSS Note # 0001229799  -  "Workaround for kernel bug with xml namespace context"
    Thank you very much !
    -Chris

    Hope you would get everything from this link
    http://www.saphelp.com/ERP/archive/index.php?f-118.html
    regards
    nag

  • Handling XSD QName types in VC 7.1

    VC Experts,
    I'm trying to call one of the Service Registry web services (publishServiceDefinitions) but am having problems with correctly passing a value for an element with XSD type QName.  Following is a sample XML payload that works, which was generated from WSNavigator.  Notice element <qname> which has a qualified namespace.  I generated this from WSNavigator by entering the value "EricTestService" for the qname element.  This technique does not work in Visual Composer however.  The XML generated does not add the qualified namespace to the qname element.  Any help with this will be greatly appreciated.  Thanks.
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://sap.com/esi/uddi/sr/api/ws/">
       <soapenv:Header/>
       <soapenv:Body>
          <ws:publishServiceDefinitions>
             <definitions>
                <descriptions>
                   <text>Update4 Service published from SR API with WSNav</text>
                </descriptions>
                <documentation>http://itdoclib.intel.com/</documentation>
                <qname xmlns:pns="http://intel.com/EH-namespace">pns:EricTestService</qname>
                <serviceDefinitionKey>
                   <logicalKey>uddi:ed654420-c189-11dd-9663-0003ff2519d7</logicalKey>
                   <uddiKey>uddi:ed654420-c189-11dd-9663-0003ff2519d7</uddiKey>
                </serviceDefinitionKey>
                <technicalName>EH</technicalName>
                <wsdlURL>http://galaxy-desk:50000/index.html</wsdlURL>
             </definitions>
          </ws:publishServiceDefinitions>
       </soapenv:Body>
    </soapenv:Envelope>
    Regards,
    Brian

    Hi Brian,
    I've asked and Jarrod Williams from VC Solution Office came up with a work around for this issue:
    "As a workaround the user should enter the qname as follows, xmlns:pns='http://intel.com/EH-namespace'>pns: EricTestService"
    Hope this helps,
    Shay

  • XQuery using fn:QName in OSB

    Is fn:QName available to use in XQuery within the OSB? I tried but keep get the following error message...
    line 5, column 10: {err}XQ0017: "{http://www.w3.org/2004/07/xpath-functions}QName": unknown function (or number of arguments (2) is wrong)
    My xquery is below...
    declare variable $localname as xs:string external;
    declare variable $namespace as xs:string external;
    declare variable $cause as element()? external;
    element {fn:QName($namespace,$localname)} {
    <validation-error>{$cause}</validation-error>
    }

    The use case is to generate a qname by passing in a namespace and localname. We have different types of exceptions that have different namespaces and localnames but contain exactly the same content. The requirement is to create an xquery function that can be reused to create the exceptions by passing in the namespace and local name of the top level exception element.

Maybe you are looking for

  • Problem in transferring data from iPad 2 to iPad Air

    I just got a new iPad Air. I naturally wanted to transfer as much of the data as possible from my old iPad 2 (then to wipe the old iPad and pass it on). I read all the advice on line about changing. I did full and successful back ups of the iPad 2 to

  • BPM WorkSpace doesn't find my process

    Hi to all, i have a little problem with BPM workspace. I'm starting the Oracle BPM 10.3 Tutorial and i'm implementing the Expense Report Process. I created one participant, called Peter Jones and assign to him a Global Creation Activity in order to c

  • Temperature goes up with external monitor

    Hi, I'm using a 22" LCD monitor connected to my MacBook via DVI. And it's working pretty well. But the system temperature goes up whenever I plug in the monitor. When I don't have the monitor connected the idle temperature is about 40-45 degrees celc

  • GPS signal lost on Droid X - no reception

    I've had a working Droid X for just over 30 days and suddenly the GPS will not receive a signal and lock.  I have downloaded both GPS Status and GPS Test applications AFTER the issue started.  Both apps show that I am not seeing any satellites.  I've

  • CO Assessment Cycles

    Hi I have an assessment cycle created which got 1 sender cost center and 4 receiver cost centers. The  receiver cost centers belong to 2 different profit centers. Apart from that we have New GL activated as well When I execute the actual run for this