Handling Recursive include in XSD

Hi Experts,
I 'am trying to create a java client proxy for my WSDL. My XSD "includes" 3 other xsds that have recursive imports among them due to which the client proxy generation results in an infinite loop eventually leading to a StackOverFlowException. This happens in Axis 1.2 and jdeveloper as far as I 've tested. Though I heard the latest versions of these tools do support recursive include handling, I would like to get rid of this recursive include so that it can be used to generate client proxy in most available tools.
Here is my usecase:
TestEmployee.WSDL
<xsd:schema>
<xsd:import namespace="http://xmlns.oracle.com/apps/fnd/framework/svctoolbox/samplelib" schemaLocation="http://<host>/<path>/TestEmployeeService.xsd"/>
</xsd:schema>
TestEmployeeService.xsd:
=============================
<xsd:include schemaLocation=A.xsd/>
<xsd:include schemaLocation=B.xsd/>
<xsd:include schemaLocation=C.xsd/>
A.xsd
===================================
<xsd:include schemaLocation=C.xsd/>
B.xsd
===================================
<xsd:include schemaLocation=A.xsd>
<xsd:include schemaLocation=C.xsd>
C.xsd
=====================================
<xsd:include schemaLocation=B.xsd>
The xsd structures are such that the include can not be ignored. Any suggestions on how to break the loop in this recursion would be immensely helpful.
Thanks,
Ganapathi

Have a look at Matt Wrights Blog, where he covers something similar http://blogs.oracle.com/matt/
Cheers!

Similar Messages

Recursive node in xsd

Hello PI people.
I have a problem reguarding to a XSD file (standard DSML found here: [DSMLv2|http://www.oasis-open.org/committees/dsml/docs/DSMLv2.xsd]).
When I Import it as external definition to PI Integration builder it all works fine but if I undfold the message "Filter" the there is problem with the defintions for "not" and after one more fold on "and" or "or" the same problem is shown. It looks like PI understands the XSD but it just not permit recursive nodes?
Is it the XSD that dosent meet the PI standard or is it a internal thing in PI that needs to be activated to handle recursive nodes i XSD?
(When a message is mapped with this DSML all the error prone nodes are stripped..)
// Jesper

Hello Jesper,
You can refer to this document for supported XSD and WSDL:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72e4c
Once you open this excel document go to row 94 for Recursive Data Structures, it says it is supported but there is a reference to row 143 which says
Recursive data structure must be expanded in design-time manually to the desired depth
If what you are thinking is dynamic recursion, then it is not possible. You have to use Java Mapping/XSLT for that. Now as for the nodes not displaying, right-click on the node and then select expand recursive structure.
Hope this helps,
Mark

Error: recursive include directive

Hi,
I am trying to run iStore from my local box on jDeveloper. I am getting the below error message, anybody has ideas on how to fix it.
C:\jDeveloper\jdevhome\jdev\myhtml\OA_HTML\OAGlobal.jsp
Error: recursive include directive
I am on R12.1.1, and jDev version is 10.1.3.3.0. I installed it from patch # 6863618
Thanks.

Have you completed all the steps in these MOS docs?
How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12.x [ID 416708.1]
Configuring JDeveloper For Use With Oracle Applications 11i and R12 [ID 330236.1]
What Setup is Required to Create Custom JSP Pages to Run on the Ebusiness Suite 11i and R12+? [ID 884200.1]
Thanks,
Hussein

Problem with import tag in xsl files and include in xsd files

Hello,
I've been developing an application using JBoss as server. Then, i created an especific path for xsd and another path for xsl files. In both cases, i created a main file that include (xsd) or import (xsl) the other files. My problem is that i have to specify the exactly path where the imported xsl or the included xsd files are, even though they are in the same path as the main file. What i want to know is how i say that the other xsd and xsl files are in the same path that the main file that is importing them?
here's an example of my import and include declarations:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:import href="../server/jboss/deploy/application.ear/pack.jar/xsl/transformer1.xsl"/>
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          elementFormDefault="qualified">
     <xsd:include schemaLocation="../server/jboss/deploy/application.ear/pack.jar/xsd/schema1.xsd"/>
thanks for your help

yes, thats not the value returned of
URL url = this.getClass().
                    getResource("/xsl//transformer.xsl");the expression i posted is an string i'm using to test.... but i think it's not incorrect, because if the files i'm trying to open are not in the path, he throws the following exception:
java.io.FileNotFoundException: C:\cpqd\isp\tools\third-party\jboss\server\jbossISP1\deploy\cpqd-ispeng-EngEJB-3.3.0.0.ear\cpqd-ispinv-ServiceEJB.jar\xsl\isp_transformer_manufacturer.xsl
    at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80)
    at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89)
    at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
    at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xalan.processor.ProcessorInclude.parse(ProcessorInclude.java:323)
    at org.apache.xalan.processor.ProcessorInclude.startElement(ProcessorInclude.java:192)
    at org.apache.xalan.processor.StylesheetHandler.startElement(StylesheetHandler.java:668)
    at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
    at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
    at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:972)
    at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:788)
    at br.com.cpqd.oss.isp.service.adapter.FrameworkAdapter.createExternalData(FrameworkAdapter.java:131)
    at br.com.cpqd.oss.isp.service.message.ExternalDataMDBBean.onMessage(ExternalDataMDBBean.java:92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:458)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
    at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:62)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:284)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:150)
    at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:90)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
    at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:372)
    at org.jboss.ejb.Container.invoke(Container.java:709)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:928)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1205)
    at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:276)
    at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
    at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:159)
    at org.jboss.mq.SpySession.run(SpySession.java:351)
    at org.jboss.jms.asf.StdServerSession.run0(StdServerSession.java:200)
    at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
    at java.lang.Thread.run(Thread.java:534)and when the files are in the path, he throws the other exception... thats why i think the problem it's not the URL....

Register XSD-Files which includes Other XSD-Files

Hallo
i have two XML-Schemata. One is included by the other.
Here is an example:
This is the XSD, which is included by the other (metadata.xsd):
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
     
     <xs:element name="metadata" type="metadataType">
          <xs:annotation>
               <xs:documentation>ROOT ELEMENT von Metadata</xs:documentation>
          </xs:annotation>
     </xs:element>
     
     <xs:complexType name="metadataType">
          <xs:sequence>
               <xs:element ref="identifier"/>
               <xs:element ref="category"/>
               <xs:element ref="creator"/>
               <xs:element ref="creation_date"/>
               <xs:element ref="publisher"/>
               <xs:element ref="language"/>
               <xs:element ref="title"/>
               <xs:element ref="basic_year"/>
               <xs:element ref="statistic"/>
This is the XSD, which include the other XSD (lexikon.xsd):
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="unqualified" attributeFormDefault="unqualified">
     
     <xs:include schemaLocation="metadata.xsd"/>
     
     <xs:element name="lexikon" type="lexikonType" xdb:defaultTable="LEXIKON">
          <xs:annotation>
               <xs:documentation>ROOT ELEMENT</xs:documentation>
          </xs:annotation>
     </xs:element>
     <xs:complexType name="lexikonType">
          <xs:sequence>
               <xs:element ref="metadata"/>
               <xs:element ref="lexikonEntries"/>
          </xs:sequence>
          <xs:attribute name="lexikonKat" type="xs:integer">
               <xs:annotation>
                    <xs:documentation>für spezielle UnterkategorienTypen zu den Lexikas</xs:documentation>
               </xs:annotation>
          </xs:attribute>
     </xs:complexType>
     
     
     
     
     <xs:element name="explicationTxt" type="explicationType"/>
     <xs:complexType name="explicationType">
          <xs:choice>
               <xs:element ref="verweis"/>
               <xs:element ref="txt"/>
               <xs:element ref="para"/>
Both documents have i copied to a webdav-folder. Now i want register the documents.
BEGIN
DBMS_XMLSchema.registerSchema(
schemaurl=>'http://190.1.1.148:8080/home/DEV/xsd/lexikon.xsd',
schemadoc=>sys.UriFactory.getUri('/home/DEV/xsd/lexikon.xsd'));
END;
The following error-message is displayed:
ERROR at line 1:
ORA-31000: Resource 'metadata.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 166
ORA-06512: at line 2
I made the XSD-Files by XMLSpy. The Documents are well-formated and valid.
When i make a new XML-File based ONLY (of course) on lexikon.xsd everything works fine with XMLSpy.
How must i register these documents? Is it possible? Or can´t i register XSD-Files which includes others?
Thank you very much
cu
Heidi

Heidi,
register the metadata.xsd first inthe same way and then register the lixikon.xsd.
it should work.

How could Adobe Form handle multiple Include Text

Hi all,
In abap program, I have declared a global structure *t166k and pass it to adobe form. However, the the passing parameter *t166k need to based on the looping xt166k as shown below. If this is the case, how could I handle such multiple include text?
Thanks in advance.
    loop at xt166k where tdid ne 'F17'.
      move xt166k to t166k.
      case t166k-tdobject.
        when 'EKKO'.
          t166k-txnam(10)   = ekko-ebeln.
        when 'LFA1'.
          t166k-txnam(10)   = ekko-lifnr.
        when 'LFM1'.
          t166k-txnam(10)   = ekko-lifnr.
          t166k-txnam+10(4) = ekko-ekorg.
      endcase.
      perform get_header_text.
    endloop.
form get_header_text.
if t166u-druvo = '1'.
    *t166k = t166k.
endform.                    " GET_HEADER_TEXT
In Adobe Form
General
Name     GV_HEADER_TEXT
Description     Header Text
Status     Inactive
Text
Text Type     Include Text
Include Text
Text Name     T166K-TXNAM
Text Object     T166K-TDOBJECT
Text ID     T166K-TDID
Text Language     FORM_LANGU

Are you using a custom driver program?
If yes, then loop the function module with the number of copies you have.
the copy name should be a variable which should be passed to the form in the loop change the value of the copy control accordingly.
Please let me know, if you see any issues.
Thanks,
Rakesh

How can I remove *standalone="yes"* and include xmlns:xsd and xsi in root

Using JAXB 2.1 for the first time. Was wondering how I would remove standalone="yes" from <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> And also how can I add xmlns:xsd="http://www.w3.org/2001/XMLSchema" and to the root element xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

JAXBContext jaxbContext = JAXBContext.newInstance( "com.a.b" );
Marshaller marshaller = jaxbContext.createMarshaller();
marshaller.setSchema(schema);
ObjectFactory factory = new ObjectFactory();
A a = factory.createA();
JAXBElement<A> root = factory.createRoot(a);

Unknown host exception in Workshop 4 Weblogic including a XSD in a WSDL

Hi All,
Im facing a bug in W4W as it throws unknownhostexception when im including a LOCAL schema in a WSDL.
Im using Linux (Ubuntu). In windows, this bugs does not happen.
Is it a known bug? Is there a patch for it?
Thanks in advance!,
Daniel
Edited by danielamadei at 10/11/2007 6:15 AM

Hi,
I have exactly the same kind of issue.
I'm working with:
BEA version: 9.2.2
build id: 952826
I've imported a WSDL file from my file system into a package, right click on the WSDL file and then choosed "Web Service/Generate web service..."
Workshop starts working and stops with the following error "UnknowHostException: opt" (FYI: I've installed WorkShop in /opt/bea)
Doing exactly the same thing on Windows works.
Jean-Marc
Stack trace generated trying to generate a WebControl from the WSDL file (I guess this is the same kind of exception):
com.bea.wlw.controls.service.ui.except.TypesAnalysisFailedException: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.net.UnknownHostException: opt
at com.bea.wlw.controls.service.ui.util.ProcessServiceInfo.run(ProcessServiceInfo.java:100)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.net.UnknownHostException: opt
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:362)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:352)
at weblogic.wsee.wsdl.WsdlImport.parse(WsdlImport.java:93)
at weblogic.wsee.wsdl.WsdlDefinitions.parseChild(WsdlDefinitions.java:462)
at weblogic.wsee.wsdl.WsdlExtensible.parse(WsdlExtensible.java:98)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)
at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:362)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:50)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:73)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:38)
at com.bea.wlw.controls.service.ui.util.WsdlAnalyzer.load(WsdlAnalyzer.java:27)
at com.bea.wlw.controls.service.ui.util.WsdlAnalyzer.analyzeWsdl(WsdlAnalyzer.java:21)
at com.bea.wlw.controls.service.ui.util.ProcessServiceInfo.run(ProcessServiceInfo.java:93)
... 1 more
Caused by: java.net.UnknownHostException: opt
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.NetworkClient.openServer(NetworkClient.java:118)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:488)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:475)
at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:270)
at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:352)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:149)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:59)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
... 14 more
Edited by desmo999r at 11/12/2007 10:49 AM
Edited by desmo999r at 11/12/2007 10:56 AM

Ant autotype does not seem to recognize xsd:include

Hi
I am currently using WebLogic 7.0. I was trying to use ant autotype to generate
java classes based on a schema. I ran into a problem that the autotype does not
seem to include the other schema files listed with xsd:include. I could only get
around the problem by literally copy and paste the complex types definition into
the calling schema file. Below are the two schemas that illustrate the problem.
x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd results in a
unresolve type with autotype. Problem only goes away if EmployeeBean definition
is listed in x.xsd.
Any help is much appreciated.
==========================================================
x.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema xmlns:ofx="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://ofx.net/v3.0">
<xsd:include schemaLocation="y.xsd" />
<xsd:complexType name="Company">
<xsd:sequence>
<xsd:element name="XYZ" type="ofx:EmployeeBean" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==========================================================
y.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema targetNamespace="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ofx="http://ofx.net/v3.0">
<xsd:complexType name="EmployeeBean">
     <xsd:sequence>
     <xsd:element name="name"
          type="xsd:string"
          nillable="true"
          minOccurs="1"
          maxOccurs="1">
     </xsd:element>
     <xsd:element name="id"
          type="xsd:int"
          minOccurs="1"
          maxOccurs="1">
     </xsd:element>
     </xsd:sequence>
</xsd:complexType>
</xsd:schema>
=============================================================

Actually imports will work in most cases, though some bug fixes have
been made since and will show up in future releases.
--Scott
In article <[email protected]>,
Bruce Stephens <[email protected]> wrote:
Hello,
At the moment, we handle wsdl imports as done by SOAPBuilders Round
3, but not schema imports. Look for this in the upcoming release;
Contact Michael Bamford ([email protected]) if you would like
to be on the Beta.
Thanks,
Bruce
Sooleng Lau wrote:
Thank you for the response and info. What about schema import, is
it handled by weblogic 7.0 at the moment ? What is the upcoming
release, is it WebLogic 7.1 ?
Thank you.
Soo Leng
Bruce Stephens <[email protected]> wrote:
Hello,
Schema include is a known problem that will be corrected in the upcoming
release.
The workaround at this point is the cut and paste :-( you described.
Bruce
Sooleng Lau wrote:
Hi
I am currently using WebLogic 7.0. I was trying to use ant autotypeto generate
java classes based on a schema. I ran into a problem that the autotypedoes not
seem to include the other schema files listed with xsd:include. I couldonly get
around the problem by literally copy and paste the complex types definitioninto
the calling schema file. Below are the two schemas that illustratethe problem.
x.xsd includes y.xsd but however the EmployeeBean listed in y.xsd resultsin a
unresolve type with autotype. Problem only goes away if EmployeeBeandefinition
is listed in x.xsd.
Any help is much appreciated.
==========================================================
x.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema xmlns:ofx="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://ofx.net/v3.0">
<xsd:include schemaLocation="y.xsd" />
<xsd:complexType name="Company">
<xsd:sequence>
<xsd:element name="XYZ" type="ofx:EmployeeBean" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==========================================================
y.xsd
==========================================================
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<xsd:schema targetNamespace="http://ofx.net/v3.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ofx="http://ofx.net/v3.0">
<xsd:complexType name="EmployeeBean">
<xsd:sequence>
<xsd:element name="name"
type="xsd:string"
nillable="true"
minOccurs="1"
maxOccurs="1">
</xsd:element>
<xsd:element name="id"
type="xsd:int"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
=============================================================

Problems including XSD File

Hello,
i am trying to import a .xsd file into my wsdl file which I need as a partner link in my bpel process. I include the .xsd file in the following way: <xsd:include schemaLocation="../NPSSchema.xsd" />, but if I try to start the whole system I get this failure message:
ERROR: Successful execution of Deploy: D:\Masterstudium\Internetapplikationen\Assignment2\Assignment2ProcessApp/dist/Assignment2ProcessApp.zip
WARNING: (JBIMA0404) Deployment of service assembly Assignment2ProcessApp succeeded partially; some service units failed to deploy.
* Component: sun-http-binding
ERROR: (SOAPBC_DEPLOY_2) HTTPBC-E00201: Deployment failed. javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/wsdl:types/xs:schema): faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced at ''../NPSSchema.xsd'', relative to ''file:/C:/Users/stefan/.personalDomain/personalDomain/jbi/service-assemblies/Assignment2ProcessApp/Assignment2ProcessApp-sun-http-binding/sun-http-binding/Assignment2/numberportingservice.wsdl''.: java.io.FileNotFoundException: This file was not found: file:/C:/Users/stefan/.personalDomain/personalDomain/jbi/service-assemblies/Assignment2ProcessApp/Assignment2ProcessApp-sun-http-binding/sun-http-binding/NPSSchema.xsd
The .xsd file exists, I have really no idea why it doesn't work. Could anybody help??
Thanks a lot!
Steve

Hey,
Can you try this? open BEPL-Structure Panel >>Expand Schemas>>import Schema>> you will get any URL in this point your .xsd file.
And Also copy the .xsd file in your project folder.
Thanks,
Ariraj S
Edited by: arirajs on Dec 16, 2008 6:59 AM

Can we generate XSD URLs of an App directly without parsing WSDL

Hi,
I am from ATG-applcore team, having a query related to webservices XSD URI and MBean server
I have a Model project that has webservices created for application modules and deployed in Weblogic server.
I am able to get list of all webservice URIs of this App from MBeanServer.
Also i have a list of XML schemas used by these WSDLs in a flat file.
Can I get XSD URIs directly some how, without crawling through the WSDL URIs recursively untill all XSDs are found ?
Please suggest a way to get/generate XSD URIs, given WSDL links, XSD names, MBean server handle.
In my test App, I observed that by appending ?XSD=xsdName to end of one of the WSDL URI, gives a working link to the XML schema.
This link works even though the WSDL does not import that XSD.
http://hostName/context-root/WSDL1?XSD=XSD1.xsd
http://hostName/context-root/WSDL1?XSD=XSD2.xsd
http://hostName/context-root/WSDL1?XSD=XSDN.xsd
My project:
I am having two Web services Dff1RefService.wsdl and Kff1Ref1Service.wsdl as part of an EAR, deployed in Weblogic server.
Dff1RefService.xsd and Kff1Ref1Service.xsd are the corresponding imported XML schemas.
Links:
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Dff1RefService?WSDL*
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Dff1RefService?XSD=Dff1RefService.xsd*
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Kff1Ref1Service?WSDL*
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Kff1Ref1Service?XSD=Kff1Ref1Service.xsd*
Now the below links also work
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Kff1Ref1Service?XSD=Dff1RefService.xsd*
http://10.229.171.91:7102/FlexUI-Demo-Model-context-root/*Dff1RefService?XSD=Kff1Ref1Service.xsd*
This woks even though Kff1Ref1Service.wsdl does not import Dff1RefService.xsd.
Is this behavior valid for all cases, or this a one-off case seen in my App?
Please suggest a way to get/generate XSD URIs given - WSDL links, XSD names, MBean server handle.
Thanks,
vikranth

Logged ER 8675884 against weblogic team, got a reply that no magic algorithm exists to get list of all XSDs.
A sample aglo is given in the bug page, that basically traverses through the wsdl-xsd hierarchy and collects all XSD URI.

WSDL - s:any handling & string to structure

Hi,
We have a WSDL supplied to us by a partner, generated by Visual Studio. Helpfully it doesnt actually declare or include the XSD structures within the Type definitions. There are 2 scenarios (examples below) that I need to deal with.
1) They declare the xml as a string so this will need to be converted to a structure and passed to an appropriate MI. (in the BPE so that errors are handled).
2) They declare the structure as <s:any /> which is valid WSDL but not so helpful to XI as it doesnt know what to do with it.
If I define TheRequest and TheResponse from the WSDL in a Mapping then I can only see as far as TheRequestXML and TheResponseXML, no deeper. I can see no Node operation to map 1 field to a whole structure.
It would be possible to do this in XSLT or a Java Mapping but that seems like the wrong way of going about this as it cant be that uncommon an occurance.
The XSD does not have any visibility of the methods in the WSDL (TheRequest / TheRequestXML etc).
I can work around this by hacking the WSDL to include & use the types in the XSD explicitly, but that again seems wrong.
Namespace is defined
xmlns:s="http://www.w3.org/2001/XMLSchema"
<wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://www.somewhere.com/">
      <s:element name="TheRequest">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="TheRequestXML" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="TheResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="TheResponseXML">
              <s:complexType mixed="true">
                <s:sequence>
                  <s:any />
                </s:sequence>
              </s:complexType>
            </s:element>
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
</wsdl:types>
Thanks
James

The message structure is defined in 2 parts:
WSDL
+--> XSD
When someone calls the Soap Sender and sends over some data (a SOAP message) and this contains a structure like:
<some method>
<some top level soap / wsdl node>
.... importing or including
<some top level xsd node>
   <rest of structure>
The maps then map any of the above nodes as the MI's use the top level soap methods. The problem is that unless the WSDL explicitly defines the Type from the XSD (rather than using s:any or just sticking it in a string) then the fields are not visible to any maps.
I agree it's not ideal, but hey I didnt design the WSDL
I just want to know how to handle these 2 scenarios and map the s:any and string to the (known) XSD structure so it may be used as normal in a further map.
Cheers
James

XSD embedded in XML file

I am receiving a file from one of our partners.
The file contains both the xsd definition and then the xml content.
Is XI able to read and process this? I have been unable to get the file accepted as a valid input.
If so, what do I need to have set up in the message type for the inbound file.
Also, the partner has stated that the format may change (hence the reason for including the xsd).
Is XI able to handle a changing message definition like this?
Thanks in advance.
C

Hi Chris,
the question is what you mean with 'is XI able to handle'. By default XI does not look into the message content at all. Hence, changing the structure of that format will not harm.
Knowing the structure of the message is important in one of the following cases:
1. You want to generate a proxy for the message (ABAP or java). I assume you do not want to do this.
2. You want to access data in the message via xpath. This is normally done for defining content-dependend conditions (used e.g. in routing) but may also be used in business processes.
If you do this it has to be assured that the xpath remains stable. That means that at least the path to the data you extract via this xpath does not change.
3. You want to define a mapping. If you use the graphical mapping tool you have to provide the structure of the message you want to map (either by providing an XSD definition or by providing a sample message). If the structure of the message is changed there are good chances that such a Message Mapping will no longer work.
(This depends on the kind of changes that have been applied.)
If you do your mapping via java, XSLT, or ABAP again XI does not mind when the structure changes. Anyway, I can hardly imagine how you can program your mapping such that it automatically adapts to changing message structures.
Greetings
Stephan
Message was edited by: Stephan Naundorf

Missing Template Handler is missing in action.

After a bit of struggle I found out how to input a missing
template
handler into our aged 4.5 Unix ColdFusion server. I was able
to have it
server up the custom 404error.htm file developed by our web
department.
And this worked, sort of.
The problem was that this HTML file makes use of Apache
 directives which, of course, ColdFusion does
not understand.
So, I say no problem, I've dealt with this already before and
expanded
on some existing code that reads the html file and replaces
all these
virtual includes with the contents of the included file using
<cfile...>
tags and reFind() functions. This version even uses a Custom
Tag and
recursion to handle virtual includes inside of virtually
included files.
And this works great!
http://www.cdpr.ca.gov/errors/404error.cfm.
But when I then went into the ColdFusion administrator and
replaced the
HTML file path
'/rootDir/subDir/subDir/htdocs/errors/404error.htm'
with the corresponding CFML path
'/rootDir/subDir/subDir/htdocs/errors/404error.cfm' it stops
working.
ColdFusion starts to display the default ColdFusion 404 not
found error
rather then my specified Missing Template Handler.
What's wrong here? Why can't I server up a CFM file from the
exact same
place I can serve up an, albeit incomplete, HTML file?

User Since V1.5 wrote:
>
> I will be very happy if someone points out what I'm
missing.
>
Everything you have describe is true. The main point is that
sometimes
people do not want to and that there are reasons not to let
IIS handle
ColdFusion missing templates.
To be as clear as possible, if you have set IIS to check for
the
existence of a cfm file and then throw either a default or
custom HTTP
404 error page this will overwrite anything that could of or
would of
been done with a ColdFusion missing template page.
Sometimes this is a bad thing. For one example, there are
techniques
and development methodologies that build a 'template' or
'response'
completely in memory and a cfm file does not actually exist
in this
case. This is more advanced then many people work with but it
is
possible. In this case your having IIS check for the
existence of a
template would defeat the purpose. Another example is that a
server
wide missing template handler used by the ColdFusion server
can be
passed simple information about the error from ColdFusion,
this does not
happen with the IIS methodology.
So the missing template handler exists for cases where for
one reason or
another somebody does not want to have IIS checking for the
existence of
a cfm template before handing off the request to the
ColdFusion server.
As with many things in life, it is all about choices and what
works for
one person may not work for another.
A common difficulty with the missing template handler is that
it does
not necessarily live in the web server root. It has to live
in the Jrun
(aka Java) server web root which often is different then the
web server
root.
I.E. A common configuration may be this.
c:/inetpub/wwwroot 
c:/jrun/servers/cfusion/cfusion-ear/cfusion-war 
The latter is where the ColdFusion server wide missing
template hander
template file would have to live in this example
configuration.

Including schemas and Entity Resolver

I have a MasterSchema.xsd which includes 2 sub-schema's, schema1 and schema 2 using include schemaLocation as shown below
<?xml version = "1.0" encoding = "UTF-8"?><xsd:schema xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
elementFormDefault = "qualified">
<xsd:include schemaLocation = "schema1.xsd"/>
<xsd:include schemaLocation = "schema2.xsd"/>
</xsd:schema>
I am using the parser.setProperty to associate the MasterSchema.xsd with the instance. Like so,
parser.setProperty("http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation","MasterSchema.xsd");
I am registering an entity resolver with the parser and the entity resolver handler is an inner class. Shown below
parser.setEntityResolver(new EntityResolver() {
public InputSource resolveEntity(String publicId, String systemId)
if (systemId.endWith("MasterSchema.xsd") {
return new InputSource(("/absolute_path/MasterSchema.xsd");
} else if (systemId.endsWith("schema1.xsd")) {
return new InputSource(("/absolute_path/schema1.xsd");
} else if (systemId.endsWith("schema2.xsd")) {
return new InputSource("("/absolute_path/schema2.xsd");
} else {
return null;
The parser finds the MasterSchema.xsd but not the included schema1.xsd and schema2.xsd. Any ideas?
I am using the external-noNamespaceSchemaLocation instead of external-schemaLocation since I am not using any namespace.
Thanks
Mary.

I having the same problem, any resolution?
-alexander

Handling Recursive include in XSD

Similar Messages

Maybe you are looking for