DeltaXML Support Forums
| Not found what you where looking for? Try the advanced search | Go to page back123...789...91011next |
| DeltaXML Sync > Release Announcements | |||||
Posted:
12-December-2007 10:45 DeltaXML Sync 2.4 This releases incorporates includes a number of fixes and enhancements and also includes the new licensing/activation mechanism that is now included in the Core 4.5 release. Full details are in the release notes: http://www.deltaxml.com/sync/2.4/docs/release-notes.html#r2.4 A summary of the changes follows: * bug fix: certain attribute combinations would prevent dxu:attributes being the first child element * enhancement: support for units of sync granularity * enhancement: support for enhanced matchers as available in the DeltaXML Core comparator. Downloads and named-user/professional-server evaluations are available to registered users on the website. Enterprise customers with support contracts can request new version via the usual download mechanisms. As always, any comments and feedback is welcome. Thanks, Nigel | |||||
| DeltaXML Sync > Release Announcements | |||||
Posted:
12-December-2007 10:35 Release Announcements This forum topic is dedicated to announcements of new releases. | |||||
| DeltaXML Core > Release Announcements | |||||
Posted:
12-December-2007 10:33 DeltaXML Core version 4.5 The DeltaXML Core 4.5 release is now available. There are a couple of small enhancements, but the major change in this release is associated with the licensing/activation code. The previous code introduced in 4.3 and refined in 4.4 while generally correct and bug-free did activate or 'expose' a number of bugs/issues in various JVMs and API libraries. This release preserves the activation model and the different categories of license we previously introduced (named-user, professional-server and enterprise), but provides a new implementation which reduces our 'exposure' to platform bugs/limitations. One consequence of this change is that 4.5 license keys can no longer be used with version 4.4 and earlier releases. See the release notes for further details/links: http://www.deltaxml.com/core/4.5/docs/release-notes.html#r4.5 As usual, this release is available for registered users on our website (now with evaluations for named-user or professional-server keys) and to enterprise license customers with support contracts via their usual download mechanisms. Cheers, Nigel | |||||
| DeltaXML Core > Oracle Stored Procedures calling deltaxml core | |||||
Posted:
12-December-2007 16:47 Re: Oracle Stored Procedures calling deltaxml core - more info Hello, The evaluation activatoion keys from the website are for named-user licenses. This requires each 'user' who runs deltaxml.jar to have activated a license (the data is stored in java.util.prefs user-preference nodes). A few possibilities for why it doesn't work: - the oracle server process is running under a different user/uid than the user who did the activation - The oracle server/JVM doesn't support user preferences - You may be using a security manager which prohibits access to preferences data My initial guess would be the first possibility (I'm not familiar enough with Oracle to be certain about the others). The solution would be to use a server license/key. On our ToDo list is to add a facility to our website so that users can choose between named-user and server licenses for a 4 week evaluation. In the meantime, they are also available on request via email or our webforms. | |||||
| DeltaXML Core > Oracle Stored Procedures calling deltaxml core | |||||
Posted:
12-December-2007 19:11 Oracle Stored Procedures calling deltaxml core - more info Hi, Looks like I may be able to run deltaxmljar inside Oracle server but.... got following exception when I ran modified SimpleFiles example ( which ran ok outside Oracle) *** 2007-12-04 13:39:01.618 com.deltaxml.api.DeltaXMLProcessingException: No DeltaXMLCore license available, please activate a license. Possible problem with eval license validation!! | |||||
| DeltaXML Core > Oracle Stored Procedures calling deltaxml core | |||||
Posted:
12-December-2007 17:43 Oracle Stored Procedures calling deltaxml core Hi, Has anyone tried to load deltaxml.jar into Oracle 10g2? Does anyone know id there are any issues which would make them un-supported in Oracle JVM? I would like to embed this nice xml diff into Oracle server and have it accessible from server-side stored procedures. | |||||
| DeltaXML Core > Orderless comparison | |||||
Posted:
12-December-2007 23:30 Orderless keying - not compulsory Hello,
Keys are not required, however they do have two benefits with orderless comparison: - they give users more control over the matching process. - performance is improved because we don't have to look inside an element (subtree) to determine matching. This becomes more significant when there are lots of orderless siblings of the same type (element name).
If two corresponding elements have the same keys they are always matched. Conversely, if they have different keys, or one has a key while another doesn't, they will never match (and thus have delta='add' or delta='delete' status). When matching the children of 2 elements, we'll try keyed matching first - other matchers will then be applied to any keyless elements. What is significant in the orderless comparison is that the keys should be unique, so any data they are derived from should usually exhibit the same properties.
The orderless comparator will use another matching strategy. These can include the enhanced or 'fuzzy' matcher with document type data or the exact-subtree matcher. A final approach which is sometimes appropriate is the idea of persistent keys. If the 2nd file is in some way an edit or modification of the first (either a human edit or by some software) then is it possible for that edit process that changes/produces the 2nd file to preserve any deltaxml:key attributes? Or alternatively are there any placeholders (attributes, 'userData'/'annotation' elements or even comments) which can be used to hold the data (they can be converted to deltaxml:key and back again by input/output filters)? I'd be happy to take a look at an example of the structure (either XML instance data, or DTDs/schemas) to see if anything else may be appropriate (happy to do this on the forums - but could use email if you would prefer to keep the info off a public forum). Cheers, Nigel | |||||
| DeltaXML Core > Orderless comparison | |||||
Posted:
12-December-2007 12:18 Orderless comparison I am investigating various XML comparison libraries and have a particular interest in the problem of orderless content models. Reading the solution examples for orderless comparison suggests that there is still a need to generate a 'key' that may be generated from a combination of data in the actual XML instance. If that is the case then presumably this means that the data items chosen must be always be present and must themselves be unchanged in the 2 instances being compared ? I have a situation where a repeating content model contains no combination of data items that can be reliably used as key data (i.e. it may/may not be present and if so, one party may have changed that data), and there is no guarantee that the order will be maintained across instances, does DeltaXML provide any strategy to compare these structures ? | |||||
| DeltaXML Core > Excluding differences | |||||
Posted:
10-October-2007 17:06 Command-line example and techniques to ignore differences
Command line use is described in one of the README files included in the release. A simple example would be:
There are a number of ways of excluding differences that are not of interest: 1. Remove the uninteresting elements/data from the input files prior to comparison. Some example filtering techniques are described on our website: http://www.deltaxml.com/library/how-to-ignore-elements.html 2. Preprocessing/two-pass approaches which preserve data are also possible: http://www.deltaxml.com/library/how-to-treat-timestamps.html 3. Compare the original files and ignore the uninteresting differences in the delta. The structure of the delta generally matches the tree structure of the input data. It is possible to ignore uninteresting or further post process the changes which are important to you by matching them using XPath in the result. This could include a simple element name or a more detailed, contextual, XPath which includes more precise steps in the XML tree. For exmaple to ignore changes to the server-name element the following XSLT null/empty template could be used. The match statement specifies the XPath location of the uninteresting element:
| |||||
| DeltaXML Core > Excluding differences | |||||
Posted:
10-October-2007 16:43 Excluding differences The following question was emailed to DeltaXML and has been diverted/answered in this forum: I have some specific questions about your product, I list below to tell you want I am trying to do. For example, we have 1 config.xml file, that is across many systems and is different in most cases. I want to be about in a linux command line environment to compare each of these against a "gold copy" and have it tell me the differences. Also be able to exclude the differences that I don't care or want to know about for example "servername" or "location". Thanks! | |||||