- oXygen-user - www.oxygenxml.com

oXygen as a Eclipse HTML Editor
by Miller, Ray (Centech) 17 Nov '06

17 Nov '06

oxygen-7.2.0 (eclipse-3.2.1 plugin) Wish to utilize oXygen as my default HTML editor (currently utilize as default javascript editor). How can I configure oXygen to validate against strict and loose dtds; no success in previous attempts. Ray

2 1

RE: [oXygen-user] congratulations on 8.0
by Miller, Ray (Centech) 17 Nov '06

17 Nov '06

What is the oXygen-8.0 upgrade policy and requirements (costs, license-reissue, etc)? Ray

2 1

rc8 and Berkeley XML DB
by Paul Hermans 16 Nov '06

16 Nov '06

Context: Berkeley DB connection. I have a collection. In this collection I have two types of files: 1) having a normal name such as "a1.xml" 2) having a URI as name, example "http://www.pcce.be/egb/artefact#KF.objecten.111 <https://office.amplexor.com/exchweb/bin/redir.asp?URL=http://www.pcce.be/eg…>" Trying to open files of type 2 (right-click in the database explorer) leads to an i/o error message. Paul

2 1

Errors using Oxygen 8.0RC1 with eXist in Eclipse
by Daniel E. Renfer 13 Nov '06

13 Nov '06

Hello, I am getting a few errors when trying to test the new RC of oXygen in Eclipse. I've tested this on both my development install of Eclipse and eXist under Ubuntu Edgy Eft, and with a fresh install of Eclipse/eXist under Windows XP. When I try to configure an eXist db in the Oxygen DB perspective, I get "ERROR: org/apache/commons/httpclient/HttpClient" I don't always get this error. I've been able to get the listing of collections from time to time. I tested this with the standalone Oxygen after I was able to get the listing under XP, because I didn't realize at the time that Oxygen refuses to open any file that's not *.xml (very annoying btw) I was able to open and save /db/system/users.xml, but when I went back into Eclipse to see if I could open that file, I saw the same httpclient error that I originally saw on Ubuntu. When I first tried to upgrade from the 7.2 plugin to the 8.0RC1 plugin under Ubuntu (with other existing plugins) I started getting errors that the view could not be displayed, and that I should check the log. I'm not quite sure where this log would be, but I found a few messages related to Oxygen in ~/workspace/.metadata/.log as well as some more recent ones related to Aptana. I'm not sure if it's a conflict with Aptana and Oxygen, or if Aptana was just screwing up on it's own. I removed Aptana and a few (but not all) of the errors went away. I also removed all Oxygen plugins and re-installed, which took care of a few more errors. On a few occasions, I got notification that the resource was locked, and was asked if it should try to re-lock it. This may or may not be because all during this time I was running eXist from within Tomcat from within Eclipse. I ended up re-starting many times and the server didn't always get shut down properly every time. This was why I decided to reboot and try it under XP with fresh everything. (Eclipse, workspace, Oxygen plugin, eXist 1.1.1 running under jetty) I'm using the latest JDK in all instances. Are these bugs with Oxygen, or am I doing things wrong? Does it screw it up if you try to include jars in addition to the 3 required? What if they're named differently? Thank you for making a great editor. I hope these issues can be resolved. Daniel E. Renfer http://kronkltd.net/

2 2

Problem switching from trial key to commercial key in diff files program
by Busch Paul 09 Nov '06

09 Nov '06

Hi all, approximately a month ago I installed oXygen 7.2 and acquired a trial license. When the trial period neared its end a counter indicating the days left began to show up at start up. I purchased a professional license and pasted the key at the appropriate place. Everything went fine. The counter ceased to show. Only when starting the (definitely second to nothing) diff files program standalone the counter would still appear indicating the days left on the trial license. I looked for a way to tell the diff files program about my newly acquired license key, but there seemed to be no way to do that. A reinstall didn't help either as the uninstall procedure does not seem to purge license keys. I decided to wait what would happen when the trial license would finally expire which happened today. The diff files program told me that the trial period was over and gave me the opportunity to paste my key. So in the end everything turned to good account but I don't think that's the way it should work. I thought I'd let you know so other users can be spared the experience. And if anyone knows advice on how to reliably purge a (trial) license key without formatting the hard disk I'd gratefully take it. Best regards. Paul

5 6

oXygen 8.0rc
by George Cristian Bina 09 Nov '06

09 Nov '06

Dear all, After a few month of work we are a few days away from a new oXygen release, version 8.0. Before that we thought to run it through you to have the opportunity to discover and eliminate eventual problems that went undetected by our automated and manual tests. So please try it out and let us know as soon as possible if you find any issues. Below you can find - a license key for v8 - links to an all platforms distribution for the standalone version and to the Eclipse plugin version - a description of the new features. License key for v8 ================== --- start license key --- Registration_Name=oXygen user Company= Category=Enterprise Component=XML-Editor, XSLT-Debugger Version=8, 8 Number_of_Licenses=1 Date=11-08-2006 Duration=30 SGN=MCwCFF26WnwlVHf0JtYaezzSEN652X22AhRa4DA39cyszAlAzCS1tiBYtaSCSw\=\= --- end license key --- Installation kits ================= All platforms distribution -------------------------- http://www.oxygenxml.com/update/Oxygen8.0_RC1/All/oxygen.tar.gz Eclipse plugin distribution - update site URL --------------------------------------------- http://www.oxygenxml.com/update/Oxygen8.0_RC1/Eclipse/site.xml New in version 8 ================ Editor Capabilities =================== XML Grid Editor The <oXygen/>'s grid editor allows you to edit repetitive XML content in a special layout similar to a spreadsheet application, without the need to interact with tags and markup. Support for Saving/Loading the Editor Layout. Predefined Layouts. You can save the current editor layout (what views and toolbars are visible and their position) and reuse it later, or even share it with your team. <oXygen/> has several predefined layouts, ranging from the Basic Layout - containing only the project and the outliner to the Advanced Layout - containing all the views. There are also available XML Schema development and XSLT development layouts showing only the specialized views and toolbars. Accurate XML Error Reporting Many of the XML Schema and DTD related errors are reported with accurate location information. For instance an error referring to the invalid value of an attribute will highlight exactly that value in the text. Accurate XPath Result Elements Locations Selecting a result of an XPath query highlights the XML source region corresponding exactly to the result element. Configurable Initial Directory of the File Open Dialog The initial directory of the file open dialog can be either the directory of the last opened file or the directory of the current edited file. Associate XSLT Stylesheet Action This action allows you to insert an xml-stylesheet processing instruction in the current XML document to associate it with an XSLT stylesheet. Many of the web browsers have XSLT support and can perform the XSLT transformation and display the result. Open in Browser Action This action opens the current document with the application configured as default browser. Improved Support for Schemas with Embedded Schematron Rules You can associate the edited document with an XML Schema or Relax NG schema having embedded Schematron rules in one step. Preserve the Line Separator This new option is useful when you are editing files originating from different operating systems and you need to preserve their line separator. Improved Database Support ========================= XML Database Perspective Using the Database perspective you can browse the tables or collections from the databases, execute XQuery or SQL queries, inspect or modify data, specify XML Schemas for the XML fields and collections. The database support includes many of the popular servers, operating either as native XML storage: Tamino, XHive, MarkLogic, TigerLogic, eXist, Berkeley or mixed, as relational and XML at the same time: DB2, SQLServer, Oracle. Support for Berkeley XML DB The support for Berkeley XML DB includes: resource management, resource editing, XQuery. Support for IBM DB2 Pure XML The support for IBM DB2 Pure XML database includes: multiple server connections, resource management, XML Schema registration, XQuery and SQL execution, table data editing. Support for eXist The support for eXist XML Database includes: multiple server connections, resource management, resource editing, XQuery. Support for MarkLogic The support for MarkLogic includes: multiple server connections, XQuery execution. Support for Microsoft SQLServer 2005 The support for Microsoft SQLServer 2005 database includes: multiple server connections, resource management, XML Schema registration, XQuery and SQL execution, table data editing. Support for Oracle 10g R2 The support for Oracle 10g R2 database includes: multiple server connections, resource management, XML Schema registration, XQuery and SQL execution, table data editing. Support for RainingData TigerLogic XDMS The support for the RainingData TigerLogic XDMS includes: multiple server connections, XQuery execution. Support for SoftwareAG Tamino The support for SoftwareAG Tamino includes: multiple server connections, resource management, Tamino Schema registration, XQuery execution, resource and schema editing. Support for XHive XML Database The support for XHive XML Database includes: multiple server connections, resource management, resource editing. Transformation and XSLT/XPath ============================= Flexible Input Configuration for Transformation Scenarios You can specify both the transformation XML source and the stylesheet locations. It is not required anymore the edited document to be one of the transformation XML source or stylesheet. This allows editing a module and invoking a transformation on the master files. Project Level Transformation Scenarios The transformation scenarios can be stored in the project file. This simplifies the scenario management by attaching only the relevant scenarios to a project. More, you can pass over to your teammates a set of pre-configured project scenarios. Validation Engine Detection for XSLT and XQuery The edited XQuery or XSL file is validated using the engine specified in the transformation scenario. If no transformation scenario is defined then the default validation engine from the options is used. Open Transformation Result in Editor A new option was added to the transformation scenario to allow opening the transformation result in <oXygen/>. XSLT/XPath Function Signature/Arguments Helper <oXygen/> helps editing complex XPath expressions by presenting a tooltip with the function signature above the function name and highlighting the current argument. This support is available when editing expressions in the XPath Toolbar and the XPath Builder, and also when editing XSL stylesheets and XQuery files. Subversion Client ================= Open a File or Folder from the Project into the Subversion Client The Subversion Client automatically checks the status of the selected resource allowing you to immediately commit or update it. Compare Images in the Subversion Client You can compare side by side different revisions of image files. Support for Creating Subversion Patches You can create patches in the unified diff format between two revisions or between your working copy and a revision. Filters for the Subversion Working Copy You can choose to hide from the Working Copy file browser the files that are ignored or scheduled for deletion. Schema Support ============== NVDL Editor You can edit Namespace-based Validation Dispatching Language scripts taking advantage of continuous validation support and context sensitive content completion. Validation against NVDL Scripts <oXygen/> distributes a NVDL implementation allowing the validation of XML documents against NVDL scripts. The support includes validation on demand, continuous validation, validation with external schema, batch validation from the project, etc. Content Completion Based on NVDL Scripts The content completion is able now to use an NVDL script to offer proposals; this makes possible editing documents with complex structure, that contain multiple languages defined by different schemata, for instance XHTML with embedded XForms. Mapping from XML Schema Logical Diagram to Text It is possible to locate in the source the definition of a component presented in the logical diagram. This action is available in the contextual menu or by double-clicking the diagram component. Enable/Disable Schema Diagram and Related Views You can change the <oXygen/> Schema editing layout by choosing to hide or to show the schema diagram and the schema components view. Project ======= Project Level Options You can specify almost all of the <oXygen/> settings at project level. This makes possible to pass along with the project XML Catalogs settings, transformation scenarios, formatting options, validation options, editor layout, etc. Component Updates ================= Updated the Xerces-J Parser to Version 2.8.1 The Xerces-J XML parser was updated to the latest version: 2.8.1. Updated Saxon8B from Saxonica to Version 8.8 Saxon 8B XSLT/XQuery processor was updated to the latest version: 8.8. <oXygen/> supports also the Saxon8SA 8.8 processor (that requires a separate license from Saxonica). Added the DocBook 5.0 RELAX NG Schemas The DocBook 5.0 RELAX NG schemas were added to the <oXygen/> distribution. Other ===== Support for the Secure FTP (SFTP) Protocol <oXygen/> can browse, open and save documents using the Secure FTP (SFTP) protocol. Better Integration of the XML Instance Generator The XML Instance Generator tool can be started directly from the XML Schema diagram with the parameters already configured based on the selected element. Best Regards, George --------------------------------------------------------------------- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com

1 0

XPath-validation in non-XSLT-files
by Theun Fleer 30 Oct '06

30 Oct '06

Hello, When editing XLST-files in oXygen7.2 on WinXP the XPath-expressions in the "select" and "match" attributes can be validated. When typing an incorrect XPath-expression, a wavy yellow line is shown, and an error description at the bottom of the screen; "content completion" is also an option. We are currently editing non-XSLT-files: a custom XML format with a custom namespace in which we must edit a lot of long XPath-expressions. We would like the same validation options as in the XLST-files... is this possible, and how? Kind regards, and keep up the good work! Theun Fleer Daidalos BV, The Netherlands Drs. T. Fleer Consultant GSM: +31 (0)6 40 58 50 27 Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 www.daidalos.nl KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend.

2 1

Xerces command line parsing?
by Andrew Rouner 17 Oct '06

17 Oct '06

Hello, I am looking for the right syntax and method to be able to batch-parse XML files from the command line using Xerces. I need to use Xerces as I am attempting to replicate parsing using oXygen (which has Xerces as its default parser). If anyone can send along the syntax for doing this or can point me to a resource that can help, I'd very much appreciate it. I previously used xmllint/LIBXML to do command line parsing of my TEI files, which worked well for files calling on the TEI xlite DTD. I am now dealing with files that use the full TEI and must rely on the xml catalog, i.e.: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TEI.2 PUBLIC "-//TEI P4//DTD Main Document Type//EN" "tei2.dtd" [ <!ENTITY % TEI.XML 'INCLUDE'> <!ENTITY % TEI.mixed 'INCLUDE'> <!ENTITY % TEI.drama 'INCLUDE'> <!ENTITY % TEI.corpus 'INCLUDE'> <!ENTITY % TEI.prose 'INCLUDE'> <!ENTITY % TEI.figures 'INCLUDE'> <!ENTITY % TEI.linking 'INCLUDE'> <!ENTITY % TEI.transcr 'INCLUDE'> <!ENTITY % TEI.names.dates 'INCLUDE'> <!ENTITY % TEI.spoken 'INCLUDE'> <!ENTITY % TEI.header 'INCLUDE'> <!ENTITY % ISOlat1 SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-lat1.ent'> %ISOlat1; <!ENTITY % ISOlat2 SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-lat2.ent'> %ISOlat2; <!ENTITY % ISOnum SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-num.ent'> %ISOnum; <!ENTITY % ISOpub SYSTEM 'http://www.tei-c.org/Entity_Sets/Unicode/iso-pub.ent'> %ISOpub; ]> I need to use Xerces, because I find that the default parser in oXygen (which is Xerces) can successfully parse these files (and LIBXML does not work for files using the full TEI due to problems with the DTD). My best understanding (which may be completely off) is that to use Xerces as an XML parser in the command line, what I am essentially doing, is using the syntax to run an XML file through an XSL stylesheet (on the assumption that the source file has to validate to run successfully. I have modified a previous stylesheet that processes all TEI elements found in these documents, and I use this syntax: java com.icl.saxon.StyleSheet -x org.apache.xerces.parsers.SAXParser source_file.xml stylesheet.xsl > /dev/null I am using Xerces as it comes with oXygen (and have not downloaded it separately). Since I am only really interested in parsing and not the output, I pipe it to /dev/null. I have the following in my bash profile for the PATH: CLASSPATH=$CLASSPATH:/Applications/oxygen/lib/saxon.jar:\ /Applications/oxygen/frameworks/docbook/xsl/extensions/saxon653.jar.ext:/App lications/oxygen/lib/xercesImpl.jar export CLASSPATH The above command WORKS, and will pick up SOME errors, but is clearly missing others. Does anyone have any more straightforward syntax for just PARSING with Xerces, or have any ideas why some errors (I have tested) are not being reported through this process? (One possibility is that it's just checking well-formedness, not validity, which I need to test further.) Thanks in advance for any help/suggestions. Andrew Andrew Rouner Digital Library Services Washington University Libraries St. Louis, MO EMAIL: arouner(a)wustl.edu > From: Oxygen XML Editor support <support(a)oxygenxml.com> > Date: Tue, 25 Jul 2006 12:47:23 +0300 > To: Andrew Rouner <arouner(a)wustl.edu> > Subject: Re: Differences in validators/ dtd problems? > > Dear Andrew Rouner, > > Thank you for contacting us. > The default parser used by oXygen is Xerces 2.8.0 (that is the latest > Xerces version). This looks at a first glance like a problem/bug in XMLLINT. > If you want to invoke Xerces to parse a document from command line then > you can do that though one of its sample applications: > http://xerces.apache.org/xerces2-j/samples.html > > Best Regards, > George > --------------------------------------------------------------------- > George Cristian Bina > <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger > http://www.oxygenxml.com > > >

2 1

Problem with Oxygen on Kubuntu Dapper Dake
by Thomas Zastrow 10 Oct '06

10 Oct '06

Hi there, I can't install Oxygen 7.2 on Kubuntu Dapper Dake. There is a Java-installation and the variables JAVA_HOME and JAVA are pointing to it. After starting oxygen.sh I get the error: zastrow@schleppi:~/downloads/progs$ ./oxygen.sh Starting Installer ... java.lang.NoClassDefFoundError: javax.swing.JOptionPane at java.lang.Class.initializeClass(libgcj.so.7) at com.install4j.runtime.installer.Installer.reportExeption(Unknown Source) at com.install4j.runtime.installer.Installer.main(Unknown Source) at java.lang.reflect.Method.invoke(libgcj.so.7) at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) at com.install4j.runtime.Launcher.main(Unknown Source) Best, Tom -- Thomas Zastrow Seminar fuer Sprachwissenschaft Universitaet Tuebingen http://www.sfs.uni-tuebingen.de/dialectometry/ Wilhelm Str. 19 D-72074 Tübingen Tel.: 07071/29-73968 Fax: 07071/29-5214

3 3

XML Schema validation broken in 7.2?
by Allison Bloodworth 10 Oct '06

10 Oct '06

Hi, Last week I upgraded (I think from Oxygen 7.1) to Oxygen 7.2 which is using Xerces 2.8.0 for schema validation. Suddenly XML instance documents that are definitely not valid are being called valid by Oxygen. I am using the red "checkmark" button for which the tool tip is "Validate Document". I am creating the files by opening a new document in Oxygen and attaching a schema that way. Documents with no content in the elements as well as documents that are just completely wrong are coming up as valid. When I validate using Xerces at the command line (java sax.Counter) I am getting the proper errors for these same documents. Additionally, I am getting the proper errors in Oxygen when I try to validate the schema itself. What could be going wrong? Allison Bloodworth Principal Administrative Analyst Technology Program Office University of California, Berkeley (415) 377-8243 abloodworth(a)berkeley.edu

2 1