- oXygen-user - www.oxygenxml.com

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

RE: [oXygen-user] Setting up catalog files for W3C XML Schemas
by John.Hockaday＠ga.gov.au 04 Mar '05

04 Mar '05

Sorin, Thanks for this information. I think that I may have corrupted my Oxygen default catalog. It looks like this: <?xml version="1.0"?> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <nextCatalog catalog="docbook/catalog.xml" /> <nextCatalog catalog="tei/dtd/teicatalog.xml" /> <nextCatalog catalog="xhtml/dtd/xhtmlcatalog.xml" /> <nextCatalog catalog="svg/dtd/svgcatalog.xml" /> <nextCatalog catalog="jsp/xsd/jspcatalog.xml"/> </catalog> However, when I try to validate this file I get the following error: http://www.w3.org/TR/xmlschema-1/#cvc-elt E cvc-elt.1: Cannot find the declaration of element 'catalog'. catalog.xml file:/C:/Program%20Files/Oxygen%205.0/frameworks/catalog.xml 2:1 Have I done something wrong? Thanks. John > -----Original Message----- > From: oxygen-user-bounces(a)oxygenxml.com > [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Sorin Ristache > Sent: Friday, 11 February 2005 6:58 PM > To: oxygen-user(a)oxygenxml.com > Subject: Re: [oXygen-user] Setting up catalog files for W3C > XML Schemas > > > Hello, > > You should not modify the default catalog provided by > <oXygen/>. It is > used for providing default support to document types like > Docbook, TEI, > XHTML, SVG, JSP, for example if you create new documents > starting from > templates provided by the action "New from templates". As you > can see in > the XML Catalog Preferences page you have only a checkbox for > instructing <oXygen/> to use the default catalog or not. The > text field > is not editable. > > To use an additional XML catalog you have to add it to the list of > catalogs from the same Preferences page by using the New button. The > locations from schemaLocation attributes of XML documents and > the system > IDs from DOCTYPE declarations will be searched first in the default > catalog if it is enabled and then in the catalogs from the list > displayed in the Preferences page in the order they are enumerated in > the list. > > Best regards, > > Sorin > > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com/ > > > John.Hockaday(a)ga.gov.au wrote: > > >Hi, > > > >I have downloaded the schemas from > http://schemas.opengis.net/ows/0.3.2/. > >The schemas refer to xlink which I already have on my system in > >e:/downloads/GML3.1/GML2004-10-29/xlink/xlinks.xsd. Rather > than change the > >schemaLocation in the ows19115subset.xsd file I thought that > I would use a > >catalog file to tell Oxygen 5.0 to find a local copy. > > > >The default catalog file in "Options => Preferences => XML > Catalog" is > >file:/C:/Program Files/Oxygen 5.0/frameworks/catalog.xml. I > edited this file > >by adding the following line: > > > > <nextCatalog catalog="e:/downloads/oxygencatalog.xml"/> > > > >and added the following lines in the > e:/downloads/oxygencatalog.xml" file: > > > ><?xml version="1.0" encoding="UTF-8"?> > ><catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> > > <rewriteURI > > uriStartString="http://www.w3.org/1999/xlink/" > > rewritePrefix="GML3.1/GML2004-10-29/xlink/"/> > ></catalog> > > > >If I open all the ows schemas into a project and then try to > validate the > >project I get the following error: > > > >http://www.w3.org/TR/xmlschema-1/#src-resolve E > src-resolve: Cannot resolve > >the name 'xlink:simpleLink' to a(n) 'attribute group' component. > >ows19115subset.xsd file:/E:/downloads/ows2/ows19115subset.xsd > >111:43 > > > >Yet the "simpleLink" attribute group is defined in > xlinks.xsd as follows: > > > > <attributeGroup name="simpleLink"> > > <attribute name="type" type="string" fixed="simple" > >form="qualified"/> > > <attribute ref="xlink:href" use="optional"/> > > <attribute ref="xlink:role" use="optional"/> > > <attribute ref="xlink:arcrole" use="optional"/> > > <attribute ref="xlink:title" use="optional"/> > > <attribute ref="xlink:show" use="optional"/> > > <attribute ref="xlink:actuate" use="optional"/> > > </attributeGroup> > > > >Am I not using the catalog file syntax properly or is there > a mismatch > >between the ows XSDs and xlink? > > > >Thanks. > > > > > >John Hockaday > >Geoscience Australia > >GPO Box 378 > >Canberra ACT 2601 > >(02) 6249 9735 > >http://www.ga.gov.au/ > >john.hockaday\(a)ga.gov.au > > > >_______________________________________________ > >oXygen-user mailing list > >oXygen-user(a)oxygenxml.com > >http://www.oxygenxml.com/mailman/listinfo/oxygen-user > > > > > _______________________________________________ > oXygen-user mailing list > oXygen-user(a)oxygenxml.com > http://www.oxygenxml.com/mailman/listinfo/oxygen-user >

2 1

New Review
by Kurt Cagle 21 Feb '05

21 Feb '05

A quick note to the Oxygen team - I've written a bit of a review for Oxygen 5.1, and thought you might be interested in knowing about it: http://www.understandingxml.com/archives/2005/02/a_breath_of_oxy.html -- Kurt Cagle http://www.understandingxml.com

1 0

Re: complex xpath
by David Sewell 18 Feb '05

18 Feb '05

On Sat, 22 Jan 2005 oxygen-user-request(a)oxygenxml.com wrote: > Date: Sat, 22 Jan 2005 18:23:02 +0200 > From: Sean Wheller <sean(a)enbaya.co.za> > Subject: [oXygen-user] complex xpath > > Using the following document as a study > http://www.gnome.org/~shaunm/doctable/doaproll.rdf > > My question is how to perform an XPath that will return all CVSRepository > nodes. I try //CVSRepository and get "XPath returned no results". > > Any hints should be documented and added to Oxygen Help. The problem is an XPath one and not an oXygen one. In your XML document, each "<Project>" element is assigned to a namespace without a prefix, making it impossible to find its subelements using XPath. Try adding this attribute to your root RDF element: xmlns:prj="http://www.gnome.org/~shaunm/faux-doap" then you can use the XPath expression //prj:CVSRepository and find the elements. DS -- David Sewell, Editorial and Technical Manager Electronic Imprint, The University of Virginia Press PO Box 400318, Charlottesville, VA 22904-4318 USA Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903 Email: dsewell(a)virginia.edu Tel: +1 434 924 9973

2 1