- oXygen-user - www.oxygenxml.com

Error with DocBook XInclude
by T Reaves 13 Apr '05

13 Apr '05

Hello. When I simply transform the existing DocBook XInclude example wit DocBook HTML I get the following error three times in Oxygen W No template matches xi:include in article. null and the output to my browser looks like Table of Contents Welcome to the Docbook Welcome to the Docbook <xi:include></xi:include><xi:include></xi:include><xi:include></xi: include> Am I missing something?

2 1

feature request: ignore certain files
by Lars Huttar 12 Apr '05

12 Apr '05

(Sorry, I sent this first from the wrong email address.) Dear Oxygen people, First a note of encouragement... I recently talked a coworker into trying the Oxygen XSLT tracer. Soon after that, I heard from our boss that she finds it really useful. (She was already an Oxygen user, but didn't know how to start the XSLT tracer.) Also, this past week our boss ordered two additional copies of Oxygen for our team. Several of us are learning XSLT, and I had told him how much it helps to be able to see what's going on when you're not confident of how XSLT works. I told him you could get an XSLT tracer with Oxygen for under $100, or go with XMLSpy Professional for $500. That made it a no-brainer. :-) Now the feature request: In Oxygen projects, I usually "Link to external folders". That works just right for me, but it also brings in certain files I don't want to clutter up my Project pane... like my .svn folders and *.bak files. Can there be a setting to let us specify filename patterns that the Project pane will ignore? Thanks, Lars

3 2

small enhancements
by Paul Hermans 06 Apr '05

06 Apr '05

a) XPath Is it only possible to test absolute paths starting from the root node? I would like to select nodes in the tree view and test relative paths form there. b) Schema editing If simple types are restricted it would be nice to get only the facets applicable to the base type that has been used for the restriction. Regards, Paul

3 2

StackOverflowError
by Ray Miller 24 Mar '05

24 Mar '05

jre=1.5.0_02 dtd=4.4b2 xsl=1.68.1 ide =oXygen-5.1 xinclude=oXygen-5.1 os=fc2 fop=saxon-6.5.3 Implementing xincludes; when html transforming from root document everything is OK; when initiating html transformation from a nested xinclude document the following oXygen fatal error is generated via a popup dialog box: StackOverflowError Problem occurs from both single file and chunk modes. Added following jvm parms to oxygen.sh to no avail: -Xms256m -Xmx384m -Xss2m Same problem with Xalan fop. Advice please -- Ray Miller

2 1

DocBook question
by T Reaves 21 Mar '05

21 Mar '05

When will support for 5.0 and/or NG be added? I'm trying to code against 5.0, and am getting errors that I should. The very basic example of an article from the 5.0 book produces the following: F A '(' character or an element type is required in the declaration of element type "entry". soextblx.dtd file:/Developer/Applications/Oxygen/frameworks/ docbook/dtd/soextblx.dtd 316:33 Thanks.

3 2

Oxygen Problems
by Matthew Riches 17 Mar '05

17 Mar '05

I am not sure if this falls exclusively within the remit of Oxygen or not, so apologies if it is not an Oxygen Problem I Have a WSDL and XSD in oxygen that test and verify without error. If However I copy the files to my server and run them, then I get an error. "java.io.IOException: Type {http://www.w3.org/2000/10/XMLSchema}uriReference <http://www.w3.org/2000/10/XMLSchema%7duriReference> is referenced but not defined." I don't understand why this is, but as it is in the standard files, I think I'm limited to what I can do. Is this a fault of the way I am using oxygen, or my apache system, or does oxygen just not check / test everything fully? Matt ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

2 1

More Oxygen Problems
by Matthew Riches 17 Mar '05

17 Mar '05

OK, using the latest version of software, I have a problem with stylesheets. If I use <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/TR/WD-xsl"> I get an error stating that a version is required. It is plainly there! However, if I use <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> then it works fine Do I need to use the earlier version to get the errors to disappear? Matt ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

2 1

Re: [oXygen-user] Problem Debugging WSDL
by Radu Coravu 15 Mar '05

15 Mar '05

Dear Matthew, The snippet from the schema file seems to be alright. The problem is in the wsdl file. I think the sample you sent might be replaced with: "<?xml version="1.0"?> <definitions name="logingateway" targetNamespace="http://localhost/test3.wsdl" xmlns:gwns="http://localhost/test3.wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:becta="http://localhost/bdefinitions" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"> <import namespace="http://localhost/bdefinitions" schemaLocation="http://10.0.250.144/bdefinitions.xsd"/> <import namespace="http://schemas.xmlsoap.org/wsdl/soap/" schemaLocation="http://10.0.250.144/soap.xsd"/>  <message name="loginuser"> <part name="loginname" type="xsd:string"/> <part name="password" type="xsd:string"/> <part name="site" type="becta:guidtype"/> </message>" These are the major differences from your file: --The "xsd:import" tags are replaced by "import" ones. The wsdl files have their own import statements. So prefixing the import statement with "xsd" is wrong. --The namespace attribute's value should be "http://localhost/bdefinitions" and not "http://localhost/bdefinitions.xsd". That's because it should be equal exactly with the target namespace declaration from the schema. --For the same reason the "xmlns:becta="http://localhost/bdefinitions.xsd"" attribute in the "definitions" tag should be "xmlns:becta="http://localhost/bdefinitions"" --The "type" attribute in the message part named "site" should change value from "b:guidtype" to "becta:guidtype" because the "b" prefix is not mapped to any namespace. For further information on wsdl you can read the following specification: "http://www.w3.org/TR/wsdl" Please try this and get back if you run into any more trouble. Regards, Radu. Matthew Riches wrote: >Thanks for your help. I just can't get it to work. I can see what you >are saying, but no matter what way I try to implement it I get different >errors thrown up. > >Some code samples > >In my xsd (called bdefinitions.xsd) >[code] ><xs:schema targetNamespace="http://localhost/bdefinitions" >elementFormDefault="qualified" > xmlns="http://localhost/bdefinitions.xsd" >xmlns:mstns="http://tempuri.org/XMLSchema.xsd" > xmlns:xs="http://www.w3.org/2001/XMLSchema"> > ><xs:simpleType name="guidtype"> > <xs:restriction base="xs:string" > > <xs:length value="34" /> > </xs:restriction> ></xs:simpleType> > >In my wsdl (called test3.wsdl) >[code] ><?xml version="1.0"?> > > <definitions name="logingateway" > targetNamespace="http://localhost/test3.wsdl" > xmlns:gwns="http://localhost/test3.wsdl" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:becta="http://localhost/bdefinitions.xsd" > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns="http://schemas.xmlsoap.org/wsdl/"> > > <xsd:import namespace="http://localhost/bdefinitions.xsd" >schemaLocation="http://10.0.250.144/bdefinitions.xsd"/> > <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/soap/" >schemaLocation="http://10.0.250.144/soap.xsd"/> > >  > <message name="loginuser"> > <part name="loginname" type="xsd:string"/> > <part name="password" type="xsd:string"/> > <part name="site" type="b:guidtype"/> > </message> > > >Unfortunately, I am not an xml guru, as I'm sure you can tell, Im just >trying to fill in some gaps in our knowledge temporarily > >-----Original Message----- >From: Radu Coravu [mailto:radu_coravu@sync.ro] >Sent: 15 March 2005 07:11 >To: Matthew Riches >Cc: oxygen-user(a)oxygenxml.com >Subject: Re: [oXygen-user] Problem Debugging WSDL > >Hello Matthew, > >Things should be pretty simple. >Let's say the target namespace of the schema in which the simple type is > >defined is : "http://test". >Then, in the wsdl file in the "types" section you should have something >like this: > >"<schema xmlns="http://www.w3.org/2001/XMLSchema" >targetNamespace="http://test"> > <include schemaLocation="a.xsd"/> > </schema>" > >The type will then be used like: >" <message name="someMessage"> > <part name="from" type="test:guidtype"/> ></message>" > >Of course you need to add the attribute ' xmlns:test="http://test" ' to > >the "definitions" tag. >There are other ways to use the types defined in the schema but this >seems to me the easiest one. > >If you are looking for something else maybe some more details about what > >you are trying to achieve and the way in which you try to include/import > >the schema file in the wsdl may be useful. >Also maybe some code snippets from the wsdl file would be useful. > >Regards, Radu. > >Matthew Riches wrote: > > > >>Thanks, that's solved a lot of banging heads on keyboards... >> >>Another quick question if I may? >> >>I have a type defined in an xsd such that >>[code] >> <xs:simpleType name="guidtype"> >> <xs:restriction base="xs:string" > >> <xs:length value="34" /> >> </xs:restriction> >> </xs:simpleType> >> >>And the file is imported into my wsdl (I have checked all the case this >>time) >> >>But no matter what, I get an error message saying that it cannot solve >>type guidtype from namespace <the namespace> to a local definition. >> >>I am certain that this is not a capitalisation issue, so any more hints >>on how to deal with this message would be appreciated. >>Matt >> >> >> >> >>********************************************************************** >>This email and any files transmitted with it are confidential and >>intended solely for the use of the individual or entity to whom they >>are addressed. If you have received this email in error please notify >>the system manager. >>This footnote also confirms that this email message has been swept by >>MIMEsweeper for the presence of computer viruses. >>www.mimesweeper.com >>********************************************************************** >> >> >> >> >> >> > > > > > > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. >This footnote also confirms that this email message has been swept by >MIMEsweeper for the presence of computer viruses. >www.mimesweeper.com >********************************************************************** > > > >

1 0

Re: [oXygen-user] Problem Debugging WSDL
by Radu Coravu 15 Mar '05

15 Mar '05

Hello Matthew, Things should be pretty simple. Let's say the target namespace of the schema in which the simple type is defined is : "http://test". Then, in the wsdl file in the "types" section you should have something like this: "<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://test"> <include schemaLocation="a.xsd"/> </schema>" The type will then be used like: " <message name="someMessage"> <part name="from" type="test:guidtype"/> </message>" Of course you need to add the attribute ' xmlns:test="http://test" ' to the "definitions" tag. There are other ways to use the types defined in the schema but this seems to me the easiest one. If you are looking for something else maybe some more details about what you are trying to achieve and the way in which you try to include/import the schema file in the wsdl may be useful. Also maybe some code snippets from the wsdl file would be useful. Regards, Radu. Matthew Riches wrote: >Thanks, that's solved a lot of banging heads on keyboards... > >Another quick question if I may? > >I have a type defined in an xsd such that >[code] > <xs:simpleType name="guidtype"> > <xs:restriction base="xs:string" > > <xs:length value="34" /> > </xs:restriction> > </xs:simpleType> > >And the file is imported into my wsdl (I have checked all the case this >time) > >But no matter what, I get an error message saying that it cannot solve >type guidtype from namespace <the namespace> to a local definition. > >I am certain that this is not a capitalisation issue, so any more hints >on how to deal with this message would be appreciated. >Matt > > > > >********************************************************************** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. >This footnote also confirms that this email message has been swept by >MIMEsweeper for the presence of computer viruses. >www.mimesweeper.com >********************************************************************** > > > >

1 0

Problem Debugging WSDL
by Matthew Riches 11 Mar '05

11 Mar '05

I am running off my localhost, and am getting errors such as "Could not solve name 'string' from namespace {http://www.w3.org/2000/10/XMLSchema} to a defined schema element. null" I assumed that this is because my local pc cannot access the included schema as they are based on the web, so I copied them all down to the hard drive, and replaced all the addresses, but I am still getting the error. Anything Else I should be looking at? Matt ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************

2 1