Hi, First I want to thank you for the feedback during the beta testing of oXygen 11. I am pleased to let you know that we just made oXygen version 11 final release available from our website http://www.oxygenxml.com The complete list of new additions in version 11 and details can be read at http://www.oxygenxml.com/index.html#new-version Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
Dear Oxygen folks: I try to renew my maintenance each year. I just renewed my version 10.x support at the end of June. Buying a new edition seems just a bit over the top just three months later. Do you offer any credit? Mark
The announcement says the following: "Your existing license covers the upgrade to version 11. Please note that you do not need a new license key because oXygen 11 works with your version 10 license key." Has that proven not to be the case? (I haven't downloaded the upgrade yet.) -----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Mark Wilson Sent: Friday, October 09, 2009 1:59 PM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] [ann] oXygen XML Editor version 11 Dear Oxygen folks: I try to renew my maintenance each year. I just renewed my version 10.x support at the end of June. Buying a new edition seems just a bit over the top just three months later. Do you offer any credit? Mark _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
My v10 license key works fine in v11. John On Oct 9, 2009, at 2:10 PM, Jesse Pelton wrote:
The announcement says the following: "Your existing license covers the upgrade to version 11. Please note that you do not need a new license key because oXygen 11 works with your version 10 license key." Has that proven not to be the case? (I haven't downloaded the upgrade yet.)
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Mark Wilson Sent: Friday, October 09, 2009 1:59 PM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] [ann] oXygen XML Editor version 11
Dear Oxygen folks: I try to renew my maintenance each year. I just renewed my version 10.x support at the end of June. Buying a new edition seems just a bit over the top just three months later. Do you offer any credit? Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi, We introduced the maintenance information in the license key, thus a license key for version 10 that contains also maintenance will work automatically with version 11. A license key for version 10 without maintenance on the other hand will not work with version 11. In any case, if you received a notification message that says that the version 10 license key works with version 11 then that means we sent you a version 10 license key containing the maintenance information and it will work with version 11. For obtaining information regarding orders and current license status see http://www.oxygenxml.com/order_history.html or you can write to support@oxygenxml.com. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com John Madden wrote:
My v10 license key works fine in v11.
John On Oct 9, 2009, at 2:10 PM, Jesse Pelton wrote:
The announcement says the following: "Your existing license covers the upgrade to version 11. Please note that you do not need a new license key because oXygen 11 works with your version 10 license key." Has that proven not to be the case? (I haven't downloaded the upgrade yet.)
-----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Mark Wilson Sent: Friday, October 09, 2009 1:59 PM To: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] [ann] oXygen XML Editor version 11
Dear Oxygen folks: I try to renew my maintenance each year. I just renewed my version 10.x support at the end of June. Buying a new edition seems just a bit over the top just three months later. Do you offer any credit? Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
First off, let me say how happy I am with oXygen 11 overall. I am especially tickled to have XPath content completion in Schematron. That said (you knew there was a "but" coming, didn't you? :-), some of the changes to the components are causing me at least confusion, if not headaches. This is primarily because I have gotten into the (bad?) habit of using oXygen's versions of some components from my commandline rather installing them myself. oNVDL ----- Summary question: should I use oxygen/lib/jing.jar or the oNVDL from http://www.oxygenxml.com/InstData/onvdl/onvdl-20070517.zip? I used to use onvdl.jar as a commandline RELAX NG and Schematron 1.5 validator (and, rarely, as an NVDL validator :-). I did this with commands like java -jar /Applications/oxygen/lib/onvdl.jar -c schema.rnc file.xml java -jar /Applications/oxygen/lib/onvdl.jar schema.rng file.xml java -jar /Applications/oxygen/lib/onvdl.jar schema.sch file.xml I don't remember exactly why I switched from using `jing` (20030619) to oNVDL sometime ago -- but I considered some fix or improvement George had made as important. This worked fine at least in oXygen 10, and maybe earlier. When I installed oXygen 11, though, I found that "the NVDL implementation from oNVDL was moved to jing-trang". There is no `jing-trang`, so I presume this means `jing` and `trang`. Does this mean that oNVDL has been superseded, and I should use `jing` for my commandline RELAXNG and Schematron 1.5 (and rarely NVDL) validation, or that I should download oNVDL separately and use it? Saxon 9 ----- - Summary problem: "License file saxon-license.lic not found" when using oXygen's Saxon from commandline I like to use a Saxon .jar file from oxygen/lib/ as my commandline XSLT 2 processor. I started doing this with Saxon 8 in oXygen 8 or 9, I think. As the names of the Saxon JAR files sometimes changed between releases of oXygen, I would occasionally have to look in oxygen/lib/ at the various *.jar files to figure out which was the right one to use, and change my `saxon` shell script front-end accordingly. This time, when installing the new oXygen broke my `saxon` front end, I dove into oxygen/lib/ and found only 2 possible choices: `saxon.jar` and `saxon9ee.jar`. It didn't take long to figure out that the former is Saxon 6, so I used the latter (remember, this is for XSLT 2 processing). This instantly caused a "License file saxon-license.lic not found" error. On a quick web-search I found that the amazing Michael Kay had already answered this: I was using the `java -jar` command syntax and had to switch to the `java -cp [CP] net.sf.saxon.Transform -sa` format. Well, this instantly caused a "you're not licensed to use SA processing" error, which persisted until I had that "doh!" moment of realizing that the -sa switch meant schema-aware. But removing that switch puts me right back to the "License file saxon-license.lic not found".
Hi Syd, I integrated all the development from oNVDL, including the NVDL implementation in the jing-trang project http://code.google.com/p/jing-trang/ So, I forked Jing as oNVDL, I added fixes and NVDL support in oNVDL and I merged those changed back to Jing. You can use jing.jar instead onvdl.jar. oXygen version 11 comes with Saxon Enterprise Edition (former Saxon SA) version 9.2, saxon9ee.jar. That does not seem to have a command line switch to enable using it as Home Edition (which is the successor of Saxon B). The saxon9ee.jar contains the Saxon HE code and thus oXygen does not need a separate jar to support Saxon HE. I am afraid there is not much we can do about that, you may ask Mike Kay to add a command line switch to enable using Saxon HE from saxon9ee.jar. Specifically with version 11.0 you can use the old Saxon 9.1 that is placed in lib/xproc/calabash as we ship that as well being needed by Calabash but this will change in 11.1 as Norm Walsh updates Calabash to use Saxon 9.2. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Syd Bauman wrote:
First off, let me say how happy I am with oXygen 11 overall. I am especially tickled to have XPath content completion in Schematron.
That said (you knew there was a "but" coming, didn't you? :-), some of the changes to the components are causing me at least confusion, if not headaches. This is primarily because I have gotten into the (bad?) habit of using oXygen's versions of some components from my commandline rather installing them myself.
oNVDL ----- Summary question: should I use oxygen/lib/jing.jar or the oNVDL from http://www.oxygenxml.com/InstData/onvdl/onvdl-20070517.zip?
I used to use onvdl.jar as a commandline RELAX NG and Schematron 1.5 validator (and, rarely, as an NVDL validator :-). I did this with commands like java -jar /Applications/oxygen/lib/onvdl.jar -c schema.rnc file.xml java -jar /Applications/oxygen/lib/onvdl.jar schema.rng file.xml java -jar /Applications/oxygen/lib/onvdl.jar schema.sch file.xml
I don't remember exactly why I switched from using `jing` (20030619) to oNVDL sometime ago -- but I considered some fix or improvement George had made as important. This worked fine at least in oXygen 10, and maybe earlier.
When I installed oXygen 11, though, I found that "the NVDL implementation from oNVDL was moved to jing-trang". There is no `jing-trang`, so I presume this means `jing` and `trang`. Does this mean that oNVDL has been superseded, and I should use `jing` for my commandline RELAXNG and Schematron 1.5 (and rarely NVDL) validation, or that I should download oNVDL separately and use it?
Saxon 9 ----- - Summary problem: "License file saxon-license.lic not found" when using oXygen's Saxon from commandline
I like to use a Saxon .jar file from oxygen/lib/ as my commandline XSLT 2 processor. I started doing this with Saxon 8 in oXygen 8 or 9, I think. As the names of the Saxon JAR files sometimes changed between releases of oXygen, I would occasionally have to look in oxygen/lib/ at the various *.jar files to figure out which was the right one to use, and change my `saxon` shell script front-end accordingly.
This time, when installing the new oXygen broke my `saxon` front end, I dove into oxygen/lib/ and found only 2 possible choices: `saxon.jar` and `saxon9ee.jar`. It didn't take long to figure out that the former is Saxon 6, so I used the latter (remember, this is for XSLT 2 processing).
This instantly caused a "License file saxon-license.lic not found" error. On a quick web-search I found that the amazing Michael Kay had already answered this: I was using the `java -jar` command syntax and had to switch to the `java -cp [CP] net.sf.saxon.Transform -sa` format. Well, this instantly caused a "you're not licensed to use SA processing" error, which persisted until I had that "doh!" moment of realizing that the -sa switch meant schema-aware. But removing that switch puts me right back to the "License file saxon-license.lic not found". _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Thanks for the information, George. I've now switched to using /Applications/oxygen/lib/jing.jar, and have downloaded and installed a separate copy of Saxon 9 (home edition). Thanks again.
I integrated all the development from oNVDL, including the NVDL implementation in the jing-trang project http://code.google.com/p/jing-trang/ So, I forked Jing as oNVDL, I added fixes and NVDL support in oNVDL and I merged those changed back to Jing. You can use jing.jar instead onvdl.jar.
oXygen version 11 comes with Saxon Enterprise Edition (former Saxon SA) version 9.2, saxon9ee.jar. That does not seem to have a command line switch to enable using it as Home Edition (which is the successor of Saxon B). The saxon9ee.jar contains the Saxon HE code and thus oXygen does not need a separate jar to support Saxon HE. I am afraid there is not much we can do about that, you may ask Mike Kay to add a command line switch to enable using Saxon HE from saxon9ee.jar.
Specifically with version 11.0 you can use the old Saxon 9.1 that is placed in lib/xproc/calabash as we ship that as well being needed by Calabash but this will change in 11.1 as Norm Walsh updates Calabash to use Saxon 9.2.
participants (5)
-
George Cristian Bina -
Jesse Pelton -
John Madden -
Mark Wilson -
Syd Bauman