- oXygen-user - www.oxygenxml.com

Command-G and searching in OS X version of 6 beta
by David Sewell 13 May '05

13 May '05

[Lars Huttar wrote:] >Apparent bug in Oxygen 6 beta: >Today when I press Ctrl+F, a dialog window appears, with a titlebar >titled "Find/Replace"; but the rest of the dialog is blank (gray). >The only other decoration is the [x] in the upper-right corner. In the Mac OS X version of 6 beta, there is a keyboard shortcut for "Find Previous" (Shift-Command-G), but no shortcut for "Find Next". The expected Command-G shortcut for this is assigned to "Go to Last Modification". (In oXygen 5.1, Command-G = "Search Again".) The version 5.1 behavior should be restored -- Apple users expect Command-G to do "find next" in any application, thanks, David -- 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 Web: http://www.ei.virginia.edu/

2 1

oXygen beta 6 Visual Relax NG editor chokes on large schemas
by David Sewell 12 May '05

12 May '05

Probably a mistake, but the first document I opened with oXygen 6 beta was the Relax NG schema for the OASIS OpenDocument format: http://www.oasis-open.org/committees/download.php/11680/office-schema-1.0-c… That is a long (530KB) and complex schema, and on my system it made oXygen freeze for all practical purposes--extremely long wait times for screen rewrites, etc. (I'm running the standalone Mac OS X version on a dual G4 867MHz PowerMac). Is this something that optimization can help with before the final release? If not, is there a way to turn off the visual schema editor in the Preferences so that it won't start when a file is loaded? David -- 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 Web: http://www.ei.virginia.edu/

3 3

modified flag cleared by Undo (feedback on Oxygen 6.0 beta)
by Lars Huttar 12 May '05

12 May '05

Dear Oxygen people, One thing I would like to see in Oxygen is a feature that's present in many editors: when you open a file, make a change, and Undo that change, it would be nice to have the modification flag (shown by an asterisk) cleared. Regards, Lars

1 0

oXygen 6 beta
by George Cristian Bina 11 May '05

11 May '05

Hello everybody, The *best version of <oXygen/> ever* is ready for a first run :). We just uploaded a beta build of the new oXygen 6 at the URLs below [1]. Please give it a try and let us know your feedback. The first main new feature is the *schema visual diagram*. Strong points are: - support for both *XML Schemas* and *Relax NG schemas* - side by side source and diagram presentation - source and diagram are synchronized in *real time* (no background parsing) - print and save as image support Another important feature is the *diff and merge* support (available only from the standalone distributions). It is in fact a *complete diff and merge solution featuring - 6 diff algorithms (*XML Accurate*, *XML Fast*, *Syntax Aware*, *Line* level, *Word* level and *Character* level) - both *file and directory* comparison and merging - a nice GUI presentation of the diff results with *change guide lines* and *synchronized scrolling* - support for automatic selection of the diff algorithm - the possibility to *go into details* at word or character level on the found modifications - *editing* any of the documents directly in the diff GUI - easy invocation of the diff from the project panel and more. The third main feature is the import support from a number of external data sources like - any JDBC enabled database - comma, space, tab, semicolon separated text files - Excel sheets Of course there are a lot of other features, like XML Signature support (sign and verify), XML Canonicalization support, the possibility to define proxy namespace mappings for the XPath evaluations, support for the latest Saxon 8.4 for XSLT 2.0, improvements in the performance and in the user interaction and more. Enjoy, and do not forget to send us feedback ;) ! Hmm... I was about to forget that you need a v6 license key to use it, you can find it at the end of the message [2] [1] installation kits Windows (Includes Java VM) http://www.oxygenxml.com/InstDataRC60/Windows/VM/oxygen.exe Windows http://www.oxygenxml.com/InstDataRC60/Windows/NoVM/oxygen.exe Mac OS X http://www.oxygenxml.com/InstDataRC60/MacOSX/oxygen.tar.gz Linux http://www.oxygenxml.com/InstDataRC60/Linux/NoVM/oxygen.bin All (Linux, Unix,etc.) http://www.oxygenxml.com/InstDataRC60/All/oxygen.tar.gz Java Web Start distribution http://www.oxygenxml.com/InstDataRC60/Javawebstart/oxygenJWS.zip Eclipse 3.0 Plugin zip distribution http://www.oxygenxml.com/InstDataRC60/Eclipse/com.oxygenxml.editor_5.1.0.zip [2] license key --- START LICENSE KEY --- Registration_Name=oxygen-user-v6-beta Company= Category=Professional Component=XML-Editor, XSLT-Debugger Version=6, 6 Number_of_Licenses=1 Date=05-05-2005 Duration=31 SGN=MCwCFGM0LBedJ73PDzgnqtS2kuB0xR0iAhQXdXzbOrF7tkMGiWjM0HTqpva0tg\=\= --- END LICENSE KEY --- Best Regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

3 3

Beta 6
by Sean Wheller 10 May '05

10 May '05

Hi, Great job on beta 6. Just been playing with it a bit today. Especially interested in the comparison tools. Now the only thing missing is diff against a vcs. One quick way to implement this may be to work as a front end to cvs, svn, tla or baz. I think it would be safe to assume that any person wanting to make diffs would have one or more of these applications installed. It should therefor be possible to enable an Oxygen user to create a diff against the repository and view it before doing a commit. The next step from this is to implement the ability for a user to view patches, merge them and then commit them. What do you think? Can you get this in before release? -- Sean Wheller sean(a)enbaya.co.za http://www.enbaya.co.za

2 3

Feedback on oXygen V6 Beta
by Eliot Kimber 10 May '05

10 May '05

I'm in the middle of a project where we are developing XSLT 2 transforms and using complex XSD schemas, so the new features in V6 were quite welcome (we had been using Turbo XML for Schema viewing by oXygen for XSLT and schema editing--we get Turbo for free with our licenses of Epic Editor). I like the schema viewer but there are a few things that I think would make it more effective to work with (in rough order of priority) (this is for the full model view--I haven't fully explored the logical view, but it might address some of my comments below): 1. Ability to control collapsing of entire tree, e.g. "collapse children/expand children). When you're dealing with a large schema with lots of top-level elements and types and you want to focus on just one part it's tedious to collapse everything. It would probably help to also have the default be to have all the children of the root initially collapsed. Epic Editor's XML tree view has a neat feature that I've never seen anywhere else: if you triple click on a tree item it will collapse the children of that item--this makes it really quick to collapse a long list of children. 2. Option to view just the element/type hierarchy without all the details of reference, refinement, extension, etc. As it is, it can be a little difficult to navigate down through a hierarchy of element types because the tree can get pretty wide, so there's a lot of scrolling, especially if you've used long names for types (as I tend to do). One of the nice things about Turbo's view is that it is pretty quick to navigate down the tree. 3. Provide a "where used" view, that is, when you click on an element type, show what other element or type contexts it's allowed in, from which you can navigate to those types. 4. In the logcal model view, also synchronize with the source, including providing the option to open the containing XSD file if it's not already open. Things I really like: - The list of types, elements, and groups. Very handy for getting a view over how the schema is organized from a coding standpoint. - The synchronization of the tree view with the markup view. Really handy. Will save much time now spent doing searches for specific entries in the schema. - The showing of enumerations for element content. - For the logical model view, the grouping of types by their namespace. Cheers, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 9390 Research Blvd, #410 Austin, TX 78759 (512) 372-8155 ekimber(a)innodata-isogen.com www.innodata-isogen.com

2 1

[Feature Request] rename a file?
by T Reaves 07 May '05

07 May '05

I'd like the ability to rename a file in the context menu of the project browser window.

2 1

FOP and image width
by lists＠userdox.com 06 May '05

06 May '05

Hi, Thanks for all your assistance so far - its all part of the learning curve... I'm trying to ensure there are no content overflows when creating PDFs so that my memory usage problems don't return as my document increases in size. This means I am trying to create images of the correct size and specify their sizes in my xml/xsl files. I would like to have some of my images at page width, and others within the flow on indented text. My body text is set by: <xsl:param name="body.start.indent" select="'5.9cm'"/> All my tables are appearing as full page width (which is a different problem to be solved), but all my images are contained within the indented text region, approximately 9.7cm. This is too small for my entity relationship diagrams so I would like them to be at the full page width. I've followed the instructions at http://www.sagehill.net/docbookxsl/ImageSizing.html without success. Am I being too ambitious for FOP 0.20.5 or am I doing things the wrong way? Cheers, Geoff docbookxsl-1.68.1 oXygen 5.1 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

FOP and image problems - solved
by lists＠userdox.com 05 May '05

05 May '05

>>The error occurs when the FO processor is launched for the final step of >>the PDF transformation. Try to execute the same transformation scenario >>on a simple document - for example >>[oXygen-install-dir]/samples/docbook/sampleXInclude.xml. You get the >>same error, the PDF result is generated correctly ? >> >>Best regards, >>Sorin > > > Thanks for your help. I transformed the sampleXInclude.xml successfully. > Further testing shows that the problem is occuring with images (and FOP). I'll > do some more playing and post the results back here for the archive. > > Cheers, > > Geoff > > Hi, I've solved the problem - it was memory related. I increased the page file size on my WinXP laptop and then set the memory available to the built-in FOP in <oXygen /> to 1000MB => success http://xml.apache.org/fop/running.html#memory describes a few things that may help others with the same problem. Geoff ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

xfc rtf fo integration
by Raymond 04 May '05

04 May '05

Downloaded and installed xfc rtf fo processor. How does one integrate this fop into oXygen 5.1? Urgently need to generate a msWord compatible document. Raymond

2 1

Re: [oXygen-user] docbook validation - possibly related issue]
by lists＠userdox.com 29 Apr '05

29 Apr '05

>Hi, > >lists(a)userdox.com wrote: > >> Hi, >> >> After trying to find any errors with my xml files that have been giving me >> validation problems, I have now discovered that oXygen is refusing to >transform >> any of my documents to PDF - even when the documents are valid. The error >> message is: >> >> E|The process ended wide code : 1 The error was : Exception in thread "main" >> >> Transformation to html is successful. > >The error occurs when the FO processor is launched for the final step of >the PDF transformation. Try to execute the same transformation scenario >on a simple document - for example >[oXygen-install-dir]/samples/docbook/sampleXInclude.xml. You get the >same error, the PDF result is generated correctly ? > >Best regards, >Sorin Thanks for your help. I transformed the sampleXInclude.xml successfully. Further testing shows that the problem is occuring with images (and FOP). I'll do some more playing and post the results back here for the archive. Cheers, Geoff ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 1

docbook validation - possibly related issue
by lists＠userdox.com 28 Apr '05

28 Apr '05

Hi, After trying to find any errors with my xml files that have been giving me validation problems, I have now discovered that oXygen is refusing to transform any of my documents to PDF - even when the documents are valid. The error message is: E|The process ended wide code : 1 The error was : Exception in thread "main" Transformation to html is successful. I have JAI installed for FOP recognition of .PNG files (installed several weeks ago). oXygen 5.1 Apache Xerces-J 2.6.2 Apache Xalan Java 2.5.1 SAXON_6 6.5.3 SAXON_8B 8.1.1 Apache FOP 0.20.5 Jing 20030619 Trang 20030619 Apache NekoHTML 0.9.4 OASIS DocBook XML DTD 4.3 DocBook XSL 1.67.2 TEI DTD P4 TEI XSL 2.1 Any clues on what I can do here? Geoff ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 1

docbook validation
by lists＠userdox.com 28 Apr '05

28 Apr '05

Hi, I'm new to oXygen and this list so appologies if I break etiquette. I'm having some problems with validating docbook with XIncludes. If I validate my book I receive four errors: E|An element with the identifier "maintenance" must appear in the document.|cu_article_introduction.xml| E|An element with the identifier "figure.architecture" must appear in the document.|cu_article_maintenance.xml| E|An element with the identifier "figure.architecture" must appear in the document.|cu_article_using.xml| E|An element with the identifier "pkg.course_search_pkg" must appear in the document.|cu_article_rendering.xml| Within the file cu_article_maintenance.xml is the element <article id="maintenance">...</article> Within the file cu_article_introduction.xml is the element <figure id="figure.architecture">...</figure> Within the file cu_article_server_utilities.xml is the element <sect2 id="pkg.course_search_pkg">...</sect2> Once validation has completed I restart it without making any changes and I receive four validation errors - all of the same type - but some are different: E|An element with the identifier "using" must appear in the document.|cu_article_introduction.xml| E|An element with the identifier "figure.architecture" must appear in the document.|cu_article_maintenance.xml| E|An element with the identifier "figure.architecture" must appear in the document.|cu_article_using.xml| E|An element with the identifier "proc.display_unit_list_param" must appear in the document.|cu_article_rendering.xml| Within the file cu_article_using.xml is the element <article id="using">...</article> Within the file cu_article_introduction.xml is the element <figure id="figure.architecture">...</figure> Within the file cu_article_server_utilities.xml is the element <sect2 id="proc.display_unit_public_list_param">...</sect2> All elements that point to "maintenance" are <xref> All elements that point to "using" are <xref> All elements that point to "figure.architecture" are <xref> All elements that point to "proc.display_unit_public_list_param" are <link> All elements that point to "pkg.course_search_pkg" are <link> My entire book is: ====================================================== <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.docbook.org/xml/4.3/docbookx.dtd" [ <!ENTITY % xinclude SYSTEM "xinclude.mod"> %xinclude; ]> <book> <bookinfo> <title>Course and Unit System Guide</title> <corpauthor>Geoff Purchase </corpauthor> </bookinfo> <xi:include href="cu_article_introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_maintenance.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_using.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_client.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_transformations.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_rendering.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_requests.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_troubleshooting.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="cu_article_server_utilities.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> </book> ======================================================== Within cu_article_introduction.xml is this snippet: ========================================================== <figure id="figure.architecture"> <title>Course and Unit Architecture</title> <mediaobject> <imageobject> <imagedata fileref="tiers.png" format="PNG" /> </imageobject> </mediaobject> </figure> <sect2> <title>Tier 1 - Maintain and Manage Course and Unit</title> <para><xref linkend="figure.architecture" /> displays the three tiers of the Course and Unit system. Tier 1 covers all areas involved with maintaining and managing the Course and Unit database. For more information about maintaining and managing Course and Unit, refer to <xref linkend="maintenance" />.</para> </sect2> ================================================================ >From the oXygen Help|About: oXygen 5.1 Apache Xerces-J 2.6.2 Apache Xalan Java 2.5.1 SAXON_6 6.5.3 SAXON_8B 8.1.1 Apache FOP 0.20.5 Jing 20030619 Trang 20030619 Apache NekoHTML 0.9.4 OASIS DocBook XML DTD 4.3 DocBook XSL 1.67.2 TEI DTD P4 TEI XSL 2.1 I successfully transformed this book yesterday, and while I have made modifications to cu_article_introduction.xml, cu_article_maintenance.xml, and cu_article_using.xml since then, I have made no changes to cu_article_rendering.xml or cu_article_server_utilities.xml. I don't know if these problems are docbook or oxygen related, but I can't see any problems with the xml (a full one-month's experience). Any help coming my way is gratefully acepted. Thanks, Geoff ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

2 1

TOC with XInclude
by T Reaves 16 Apr '05

16 Apr '05

I'm trying to do a simple book where each chapter is it's own file. I then have another file that us xinclude to include the chapters. The problem is, when I transform, each chapter is given its own Table of Contents section. Any idea why this is happening?

2 3

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

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