-
The Expander (and possibly other CAM operations) fails if given a directory pathname that contains whitespace. Although the workaround is easy (only use directories without spaces), spaces are common in directories of some operating systems. At the very least, if this is not fixed soon, code behind the dialog should check for whitespace in the pathanme and display an error message. As it is now,
2009-11-03 16:58:03 UTC in JCAM Engine with XML Editor / Validator
-
Using File > Export > Export CAM to XSD and then picking the "WSDL" mode, the file that is created gets an extension of ".xsd" when it should be "*.wsdl". Oxygen complains that the file isn't a valid XSD (since it isn't). By renaming the file "*.wsdl", the file opens correctly in Oxygen and validates as a valid WSDL. Even though the detour is easy, this MUST be fixed in the next build.
2009-10-30 17:45:24 UTC in JCAM Engine with XML Editor / Validator
-
The evaluation report table can be a little difficult to interpret because the subtle single space indenting made it hard to tell
structure. Suggestions:
1) Alternate cell BG color (or other visual clue) when you finish
one complex type and start another. Thinking of the odd/even table
shading we often see with XSLT rendering.
2) Add a column for Representation Term and/or...
2009-10-16 16:50:37 UTC in JCAM Engine with XML Editor / Validator
-
David, you REALLY must document this oddity in the actual code. I was very tempted to change it to what I thought was correct rather than submit the original PR. Think in terms of someone else maintaining parts of your code.
2009-10-02 22:06:36 UTC in JCAM Engine with XML Editor / Validator
-
[Refer to CLOSED PR # 2091288 from a year ago.]
If after creating one CAM template form XML Schema, you try to create another CAM template from a different XSD, you will get a Java exception about "unbound namespace prefix". (See attachment). Even though the template eventually will be created, it is essentially useless because there are missing namespace declarations on individual elements.
2009-10-02 18:30:33 UTC in JCAM Engine with XML Editor / Validator
-
Sorry -- I should have clarified that attribute *values* are not renamed. I guess it's debatable what should happen. In a way, the values are data so shouldn't be changed. On the other hand, broken references such as as:Structure ID="ACTION_CODE" need to be considered.
2009-09-28 18:50:43 UTC in JCAM Engine with XML Editor / Validator
-
It turns out the ACTION_CODE example is broken if attributes aren't handled. as:Structure ID="ACTION_CODE" after renaming does not point to any existing node.
See attached example.
2009-09-28 18:43:24 UTC in JCAM Engine with XML Editor / Validator
-
Although the Renamer Tool correctly convert elements having uppercase names and possibly underscores to camelcase and expands pre-specified, configurable acronyms and abbreviations, it does not apply the same transformations to *attributes* in the input. This does not make much sense to me.
Note: I am documenting this as only converts element names, so please let me know if there is a code...
2009-09-28 16:44:55 UTC in JCAM Engine with XML Editor / Validator
-
The Renamer tool consults words-utils.xsl for custom term mapping, I believe in the following line, the comparison word should be "QUANTITY".
xsl:when test="upper-case($name)='QUATITY'">Quantity.
2009-09-25 18:02:14 UTC in JCAM Engine with XML Editor / Validator
-
Apparently, the newly opened Feature Request is # 2849398. We really need to make sure bug/feature cross references are added as comments espeically when closing a bug.
2009-09-10 16:28:19 UTC in JCAM Engine with XML Editor / Validator
