Menu
▾
▴
xframe-xsddoc — Public mailing list about xsddoc
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(15) |
Feb
(8) |
Mar
(9) |
Apr
(27) |
May
(21) |
Jun
(33) |
Jul
(14) |
Aug
(20) |
Sep
(16) |
Oct
(6) |
Nov
(1) |
Dec
(14) |
| 2005 |
Jan
(4) |
Feb
(35) |
Mar
(25) |
Apr
(32) |
May
(55) |
Jun
(17) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(8) |
Nov
(2) |
Dec
|
| 2006 |
Jan
|
Feb
(16) |
Mar
|
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(19) |
Nov
(28) |
Dec
(13) |
| 2007 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(6) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2006-02-15 01:14:55
|
Feature Requests item #1238714, was opened at 2005-07-15 09:56 Message generated for change (Comment added) made by bforge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1238714&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: model Group: xsddoc-0.8-beta Status: Open Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: documentation of subtitution group affiliations Initial Comment: documentation of subtitution group affiliations ---------------------------------------------------------------------- >Comment By: bforge (bforge) Date: 2006-02-15 03:14 Message: Logged In: YES user_id=1355310 rejected. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1238714&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 01:08:54
|
Bugs item #1226673, was opened at 2005-06-24 03:05 Message generated for change (Comment added) made by bforge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1226673&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Patrick Klein (paklein) >Assigned to: bforge (bforge) Summary: enumeration values Initial Comment: Some older versions of xsddoc (pre-0.5 beta?) used to show all allowable values for an enumeration. These haven't been produced with more recent versions xsddoc, including 0.8. ---------------------------------------------------------------------- >Comment By: bforge (bforge) Date: 2006-02-15 03:08 Message: Logged In: YES user_id=1355310 We haven't got any reports from other users concerning this issue. We also cannot reproduce the problem with xnsdoc 1.0 ---------------------------------------------------------------------- Comment By: Patrick Klein (paklein) Date: 2005-07-05 19:55 Message: Logged In: YES user_id=507736 Attached is an example .xsd file. The output we get is here: https://tahoe.ca.sandia.gov/public/doc/xsddoc/noNamespace/index.php Thanks. ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-28 00:09 Message: Logged In: YES user_id=484961 Could you please provide an example? I fyou send as a sample schema file(s), we will try to find a fix for this problem. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1226673&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 01:05:24
|
Bugs item #1427822, was opened at 2006-02-08 21:47 Message generated for change (Settings changed) made by bforge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: unix Group: xsddoc-1.0 >Status: Closed >Resolution: Duplicate Priority: 7 Submitted By: Chris Webster (csunwebster) Assigned to: Kurt Riede (kriede) Summary: Ant task fails to run on Unix Initial Comment: The ant task is unable to run on unix machines. An error similar to: documentation: /homes/cay/XMLProject2/nbproject/build-impl.xml:43: net.sf.xframe.xsddoc.ProcessorException: /homes/cay/XMLProject2/homes/cay/XMLProject2/src/xml/newLoanApplication.xsd (No such file or directory) is generated. The problem is with FileUtil.getLocation as this method does not check for absolute path names on unix and thus appends a parent path incorrectly. ---------------------------------------------------------------------- Comment By: bforge (bforge) Date: 2006-02-15 03:03 Message: Logged In: YES user_id=1355310 Sounds like a duplicate to bug [1362775] Wrong Path for included Schema's. see https://sourceforge.net/tracker/index.php? func=detail&aid=1362775&group_id=48863&atid=454391 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 01:04:50
|
Bugs item #1362775, was opened at 2005-11-21 15:28 Message generated for change (Comment added) made by bforge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ant Group: xsddoc-1.0 Status: Open >Resolution: Fixed Priority: 5 Submitted By: Jentra (jentra) >Assigned to: bforge (bforge) Summary: Wrong Path for included Schema's Initial Comment: When specifying multiple schemas with the ant-task, the FilUtils-Class will build the path wrong. It appends the base dir, even, if the filename is absolute, which leads to wrong pathes. The atteached file will check if the filename is absolute and in this case will not prepend the basedir. ---------------------------------------------------------------------- >Comment By: bforge (bforge) Date: 2006-02-15 03:04 Message: Logged In: YES user_id=1355310 a possible fix is now available in CVS HEAD. May I ask you to test if the fixs works for you? ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2006-02-15 02:16 Message: Logged In: YES user_id=484961 did you forget to attach a patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 01:03:36
|
Bugs item #1427822, was opened at 2006-02-08 21:47 Message generated for change (Comment added) made by bforge You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: unix Group: xsddoc-1.0 Status: Open Resolution: None Priority: 7 Submitted By: Chris Webster (csunwebster) Assigned to: Kurt Riede (kriede) Summary: Ant task fails to run on Unix Initial Comment: The ant task is unable to run on unix machines. An error similar to: documentation: /homes/cay/XMLProject2/nbproject/build-impl.xml:43: net.sf.xframe.xsddoc.ProcessorException: /homes/cay/XMLProject2/homes/cay/XMLProject2/src/xml/newLoanApplication.xsd (No such file or directory) is generated. The problem is with FileUtil.getLocation as this method does not check for absolute path names on unix and thus appends a parent path incorrectly. ---------------------------------------------------------------------- >Comment By: bforge (bforge) Date: 2006-02-15 03:03 Message: Logged In: YES user_id=1355310 Sounds like a duplicate to bug [1362775] Wrong Path for included Schema's. see https://sourceforge.net/tracker/index.php? func=detail&aid=1362775&group_id=48863&atid=454391 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 00:40:25
|
Bugs item #1362791, was opened at 2005-11-21 14:49 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362791&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: all platforms >Group: xsddoc-1.0 Status: Open >Resolution: Fixed Priority: 5 Submitted By: Jentra (jentra) >Assigned to: bforge (bforge) Summary: Transformation fails for root element with ns in attributes Initial Comment: The transformation fails for schemas that use a namespaced attribute in the root element. Example: jxb:version <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" jxb:version="1.0" elementFormDefault="unqualified"> (for a full Example see http://www.ppart.de/apps/color/ColorTable.xsd Code lines affected: index-all.xsl line 68 overview-all.xsl line 68 schema-index.xsl line 78 The select statement '@*' will match all attributes regardless off the namespace: <xsl:template match="xs:schema">^M <doc:index-all href="./schema-summary.html">^M <xsl:for-each select="@*">^M <xsl:attribute name="{name()}"><xsl:value-of select="."/></xsl:attribute>^M </xsl:for-each>^M ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2006-02-15 01:40 Message: Logged In: YES user_id=484961 Thank you for this report. Changes for all three files are now available in CVS HEAD. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362791&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 00:16:08
|
Bugs item #1362775, was opened at 2005-11-21 14:28 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: ant >Group: xsddoc-1.0 Status: Open Resolution: None Priority: 5 Submitted By: Jentra (jentra) >Assigned to: Kurt Riede (kriede) Summary: Wrong Path for included Schema's Initial Comment: When specifying multiple schemas with the ant-task, the FilUtils-Class will build the path wrong. It appends the base dir, even, if the filename is absolute, which leads to wrong pathes. The atteached file will check if the filename is absolute and in this case will not prepend the basedir. ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2006-02-15 01:16 Message: Logged In: YES user_id=484961 did you forget to attach a patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-15 00:09:15
|
Bugs item #1423224, was opened at 2006-02-03 10:11 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1423224&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ant Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Kurt Riede (kriede) Summary: 2 byte chracter transform "%XX" Initial Comment: I use xsddoc 1.0 with Ant. I run xsddoc target. XML Schema includes 2 byte character(for example "ãã¹ ã(=test in English)"). HTML includes "%XX" which 2 byte chracter transformed. It is Output encoding and xsl encoding problem. I hope encoding setting add xsddoc Ant options And XSL Encoding is setting ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2006-02-15 01:09 Message: Logged In: YES user_id=484961 Could you please provide a simple example schema file that demonstrates the problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1423224&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-14 18:11:13
|
Bugs item #1426822, was opened at 2006-02-07 15:56 Message generated for change (Comment added) made by pswisnov You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1426822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-1.0 Status: Open Resolution: None >Priority: 7 Submitted By: Peter Wisnovsky (pswisnov) Assigned to: Kurt Riede (kriede) Summary: schemas reachable on multiple path break generator Initial Comment: I have a collection of schemas that are organized in the following way. - API includes every file - Entity contains base defs like Entity w/subclass PrimaryEntity w/subclass Named Primary Entity - Catalog includes Entity and contains catalog defs - Operational includes Catalog and Entity and contains operational defs including Project, a subclass of Named Primary Entity. I run xsddoc on API. What I see is that the documentation for a type in Operational shows a hierarchy that reaches into the entity types: good. However it shows the nodes in the path to anyType twice: bad. What I see is: anytype subtype entity (restriction) subtype primary entity (extension) subtype named primary entity (extension) subtype anytype <- !!!!GACK!!!! subtype entity (restriction) subtype primary entity (extension) subtype named primary entity (extension) subtype project (extension) Also the attributes of Entity appear 8 times in Project, the attributes of named primary entity appear 2. If I DON'T include entity.xsd in catalog.xsd, then it works for operational.xsd project, but then I don't see the HTML links from the catalog entities to their entity superclasses. ---------------------------------------------------------------------- >Comment By: Peter Wisnovsky (pswisnov) Date: 2006-02-14 10:11 Message: Logged In: YES user_id=1162080 Wondering if there is anything new here. I uploaded the schemas per your request. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1426822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-08 19:48:16
|
Bugs item #1427822, was opened at 2006-02-08 11:47 Message generated for change (Settings changed) made by csunwebster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: unix Group: xsddoc-1.0 Status: Open Resolution: None >Priority: 7 Submitted By: Chris Webster (csunwebster) Assigned to: Kurt Riede (kriede) Summary: Ant task fails to run on Unix Initial Comment: The ant task is unable to run on unix machines. An error similar to: documentation: /homes/cay/XMLProject2/nbproject/build-impl.xml:43: net.sf.xframe.xsddoc.ProcessorException: /homes/cay/XMLProject2/homes/cay/XMLProject2/src/xml/newLoanApplication.xsd (No such file or directory) is generated. The problem is with FileUtil.getLocation as this method does not check for absolute path names on unix and thus appends a parent path incorrectly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-08 19:47:07
|
Bugs item #1427822, was opened at 2006-02-08 11:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: unix Group: xsddoc-1.0 Status: Open Resolution: None Priority: 5 Submitted By: Chris Webster (csunwebster) Assigned to: Kurt Riede (kriede) Summary: Ant task fails to run on Unix Initial Comment: The ant task is unable to run on unix machines. An error similar to: documentation: /homes/cay/XMLProject2/nbproject/build-impl.xml:43: net.sf.xframe.xsddoc.ProcessorException: /homes/cay/XMLProject2/homes/cay/XMLProject2/src/xml/newLoanApplication.xsd (No such file or directory) is generated. The problem is with FileUtil.getLocation as this method does not check for absolute path names on unix and thus appends a parent path incorrectly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1427822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-07 23:56:30
|
Bugs item #1426822, was opened at 2006-02-07 15:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1426822&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-1.0 Status: Open Resolution: None Priority: 5 Submitted By: Peter Wisnovsky (pswisnov) Assigned to: Kurt Riede (kriede) Summary: schemas reachable on multiple path break generator Initial Comment: I have a collection of schemas that are organized in the following way. - API includes every file - Entity contains base defs like Entity w/subclass PrimaryEntity w/subclass Named Primary Entity - Catalog includes Entity and contains catalog defs - Operational includes Catalog and Entity and contains operational defs including Project, a subclass of Named Primary Entity. I run xsddoc on API. What I see is that the documentation for a type in Operational shows a hierarchy that reaches into the entity types: good. However it shows the nodes in the path to anyType twice: bad. What I see is: anytype subtype entity (restriction) subtype primary entity (extension) subtype named primary entity (extension) subtype anytype <- !!!!GACK!!!! subtype entity (restriction) subtype primary entity (extension) subtype named primary entity (extension) subtype project (extension) Also the attributes of Entity appear 8 times in Project, the attributes of named primary entity appear 2. If I DON'T include entity.xsd in catalog.xsd, then it works for operational.xsd project, but then I don't see the HTML links from the catalog entities to their entity superclasses. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1426822&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2006-02-03 09:11:12
|
Bugs item #1423224, was opened at 2006-02-03 01:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1423224&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ant Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Kurt Riede (kriede) Summary: 2 byte chracter transform "%XX" Initial Comment: I use xsddoc 1.0 with Ant. I run xsddoc target. XML Schema includes 2 byte character(for example "ãã¹ ã(=test in English)"). HTML includes "%XX" which 2 byte chracter transformed. It is Output encoding and xsl encoding problem. I hope encoding setting add xsddoc Ant options And XSL Encoding is setting ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1423224&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-11-21 13:49:31
|
Bugs item #1362791, was opened at 2005-11-21 13:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362791&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jentra (jentra) Assigned to: Nobody/Anonymous (nobody) Summary: Transformation fails for root element with ns in attributes Initial Comment: The transformation fails for schemas that use a namespaced attribute in the root element. Example: jxb:version <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jxb="http://java.sun.com/xml/ns/jaxb" jxb:version="1.0" elementFormDefault="unqualified"> (for a full Example see http://www.ppart.de/apps/color/ColorTable.xsd Code lines affected: index-all.xsl line 68 overview-all.xsl line 68 schema-index.xsl line 78 The select statement '@*' will match all attributes regardless off the namespace: <xsl:template match="xs:schema">^M <doc:index-all href="./schema-summary.html">^M <xsl:for-each select="@*">^M <xsl:attribute name="{name()}"><xsl:value-of select="."/></xsl:attribute>^M </xsl:for-each>^M ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362791&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-11-21 13:28:31
|
Bugs item #1362775, was opened at 2005-11-21 13:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jentra (jentra) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong Path for included Schema's Initial Comment: When specifying multiple schemas with the ant-task, the FilUtils-Class will build the path wrong. It appends the base dir, even, if the filename is absolute, which leads to wrong pathes. The atteached file will check if the filename is absolute and in this case will not prepend the basedir. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1362775&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-30 02:20:07
|
Bugs item #1228808, was opened at 06/27/05 23:58 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: Question about ant task when using FileSets Initial Comment: I had a problem using the ant task in the latest release (0.8-beta) with nested FileSets. It worked fine if I specified a single, specific file to convert, but it would never run against any of my files in the nested FileSets. I tracked it down to this code, which always returned null on my XML schema files: if (!root.getLocalName().equals("schema") || !root.getNamespaceURI().equals(Task.SCHEMA_NS)) { return null; } This was added during this commit: http://cvs.sourceforge.net/viewcvs.py/xframe/xsddoc/src/ net/sf/xframe/ xsddoc/Task.java?r1=1.21&r2=1.22 No matter what I did, I could not get any of my schema files to pass either of the tests in that if statement. I did verify that the FileSets were matching the files I wanted. After commenting out the test above everything worked out great. So, here's my question: what do I have to do to make this work? I'm including the top of one of my XSD files. These verify properly in XMLMind, they work with xsddoc, and they work fine with Castor. <?xml version="1.0" encoding="UTF-8"?> <!-- target package ::= org.opennms.netmgmt.xml.eventconf --> <schema targetNamespace="http://xmlns.opennms.org/xsd/eventc onf" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:this="http://xmlns.opennms.org/xsd/eventconf" xmlns:ns2="http://www.w3.org/1999/xhtml" xmlns:ns="http://www.w3.org/2001/XMLSchema" xmlns:hfp="http://www.w3.org/2001/XMLSchema- hasFacetAndProperty"> <annotation> <documentation>Version: $Id$</documentation> </annotation> <element name="events"> <complexType> ... snip ... Thanks, - djg ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 10/29/05 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 09/30/05 11:29 Message: Logged In: YES user_id=484961 fixed in CVS HEAD. Will be available in soon coming next release. Please check if current version is wotking for you. ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 09/28/05 14:54 Message: Logged In: YES user_id=1330069 I have submited a patch for Task.java (bug 1307377) that I believe will solve these problems, if they are in fact the same problems I was encountering (and they appear to be). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 09/28/05 04:16 Message: Logged In: NO same issues here. I cannot also get xsddoc to process a whole directory ( it generates an empty documentation frameset). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 09/24/05 04:52 Message: Logged In: NO You must simply set the DocumentBuilderFactory to be namespace aware. Add the statement factory.setNamespaceAware(true) in Task.getDocumentBuilder(). Regards /roman ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 08/16/05 10:57 Message: Logged In: YES user_id=484961 Hi Mark, thank you for your support. The best way to provide a patch is to attach the patch here: https://sourceforge.net/tracker/?group_id=48863&atid=454393 (Click on 'Submit New' and upload your patch-file) As far as I see, in both your cases, the default namespace of the schema is the XML-Schema-Namespace, and for this case the test is wrong. I mostly test with schema files where the XML-Namespace is bound to a prefix like xs: or xsd: and then the fileset is working. But however, I will check your patch and hope this will soon be fixed for the next release. Regards Kurt ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 08/16/05 07:38 Message: Logged In: YES user_id=1330069 Kurty, I have encountered the same problem and finally tracked down what I believe to be the cause. It appears the document builder factory is not being set to "namespace aware". In addition, the code path for processing the filesets is not using the internal convenience methods for getting a new document, so be sure to change that or it won't take advantage of the change you make to fix the "namespace aware" problem. The other problem I think has to be solved in conjunction is the one already noted in the Task.java file with respect to how the fileset root directories vary relative to the project directory. I fixed this by using a more absolute path approach to the problem in the addSchema method, eliminating the complexity of relative paths. I would be happy to supply my version of Task.java that seems to fix these issues. It works in my scenarios, but I have not necessarily tested it with every use case of fileset combinations. What is the best way to submit my changes so they can be considered? Regards, Mark ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 06/28/05 00:09 Message: Logged In: YES user_id=484961 Hi Gregor, I've crossposted this mail as a bug report. The above mentioned test was introduced to exclude files that donot represent a schema. We will analyse this. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-22 01:18:35
|
Bugs item #1333049, was opened at 2005-10-20 12:15 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1333049&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: all platforms >Group: xsddoc-1.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Kurt Riede (kriede) Summary: The "maven-xsddoc-plugin" project file is invalid Initial Comment: The following concerns all versions of "maven-xsddoc- plugin" up-to-and-including 1.0. The project file "project.xml" of the Maven plugin "maven- xsddoc-plugin" is invalid. This breaks compatiblity with Maven 1.1 whose parser of project files is less tolerant. The parsing error concerns the "<contributor>" section of the "project.xml" which defines an unrecognised tag: "id". Extract from "project.xml" in "maven-xsddoc-plugin": <!-- ... --> <contributor> <!-- ... --> <id>trippcr</id> <!-- TAG NOT RECOGNISED --> <!-- ... --> </contributor> <!-- ... --> Below is a trace of the error output by the Maven 1.1 "project.xml" parser: org.codehaus.plexus.util.xml.pull.XmlPullParserExceptio n: Unrecognised tag: 'id' (position: START_TAG seen ...<contributor>\r\n <id>... @101:11) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.par seContributor(Mav enXpp3Reader.java:444) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.par seModel(MavenXpp3 Reader.java:879) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.rea d(MavenXpp3Reader .java:1782) at org.apache.maven.project.Project.<init> (Project.java:122) at org.apache.maven.MavenUtils.getNonJellyProject (MavenUtils.java:185) at org.apache.maven.MavenUtils.getProject (MavenUtils.java:120) at org.apache.maven.plugin.JellyScriptHousing.getProject (JellyScriptHous ing.java:105) at org.apache.maven.plugin.PluginManager.installPlugin (PluginManager.jav a:915) at org.apache.maven.plugin.PluginManager.installPlugin (PluginManager.jav a:884) at org.apache.maven.plugin.PluginManager.processDepend encies(PluginManag er.java:458) at org.apache.maven.plugin.PluginManager.attainGoals (PluginManager.java: 664) at org.apache.maven.MavenSession.attainGoals (MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run (Forehead.java:551) at com.werken.forehead.Forehead.main (Forehead.java:581) ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2005-10-22 03:18 Message: Logged In: YES user_id=484961 Thank you for the report. We now have upgraded to Maven 1.1 and fixed this and some other the compatibility problems. Corrected versions are requested for upload to ibiblio. Best regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1333049&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-20 10:15:10
|
Bugs item #1333049, was opened at 2005-10-20 03:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1333049&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: The "maven-xsddoc-plugin" project file is invalid Initial Comment: The following concerns all versions of "maven-xsddoc- plugin" up-to-and-including 1.0. The project file "project.xml" of the Maven plugin "maven- xsddoc-plugin" is invalid. This breaks compatiblity with Maven 1.1 whose parser of project files is less tolerant. The parsing error concerns the "<contributor>" section of the "project.xml" which defines an unrecognised tag: "id". Extract from "project.xml" in "maven-xsddoc-plugin": <!-- ... --> <contributor> <!-- ... --> <id>trippcr</id> <!-- TAG NOT RECOGNISED --> <!-- ... --> </contributor> <!-- ... --> Below is a trace of the error output by the Maven 1.1 "project.xml" parser: org.codehaus.plexus.util.xml.pull.XmlPullParserExceptio n: Unrecognised tag: 'id' (position: START_TAG seen ...<contributor>\r\n <id>... @101:11) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.par seContributor(Mav enXpp3Reader.java:444) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.par seModel(MavenXpp3 Reader.java:879) at org.apache.maven.project.io.xpp3.MavenXpp3Reader.rea d(MavenXpp3Reader .java:1782) at org.apache.maven.project.Project.<init> (Project.java:122) at org.apache.maven.MavenUtils.getNonJellyProject (MavenUtils.java:185) at org.apache.maven.MavenUtils.getProject (MavenUtils.java:120) at org.apache.maven.plugin.JellyScriptHousing.getProject (JellyScriptHous ing.java:105) at org.apache.maven.plugin.PluginManager.installPlugin (PluginManager.jav a:915) at org.apache.maven.plugin.PluginManager.installPlugin (PluginManager.jav a:884) at org.apache.maven.plugin.PluginManager.processDepend encies(PluginManag er.java:458) at org.apache.maven.plugin.PluginManager.attainGoals (PluginManager.java: 664) at org.apache.maven.MavenSession.attainGoals (MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run (Forehead.java:551) at com.werken.forehead.Forehead.main (Forehead.java:581) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1333049&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-15 22:08:41
|
Patches item #1228804, was opened at 2005-06-28 08:41 Message generated for change (Settings changed) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454393&aid=1228804&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: Patch to xml2html.xsl to change end-of-sentence matching Initial Comment: I have attached a patch to xml2html.xsl to change end- of-sentence matching. Instead of matching on a single period ('.') and chopping off everything after when making pages like the overview page, it matches on a period followed by a space ('. ') after the text has been normalized. I wanted this because I have text like "XML Schema for the actiond-configuration.xml configuration file.", and I wanted all of this to be included in the overview page, not just "XML Schema for the actiond-configuration.". Does this seem like a sane thing to do? - djg ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-09-19 23:11 Message: Logged In: YES user_id=484961 Patch applied. Thanx to Gregor. ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-28 08:55 Message: Logged In: YES user_id=484961 Hi Gregor, sounds interesting. We'll check it. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454393&aid=1228804&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-15 20:55:02
|
Bugs item #1214556, was opened at 2005-06-04 00:24 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1214556&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Kurt Riede (kriede) Summary: xsddoc, java.lang.StackOverflowError Initial Comment: I am trying to generate XSD documentation for IBM Websphere 6.0 appdeployment.xsd I observed this error message: xsddoc caused an error: java.lang.StackOverflowError My environment: xsddoc-0.8-beta-full.zip java 1.5.0_02-b09 Windows XP ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2005-10-15 22:55 Message: Logged In: YES user_id=484961 Seems to be solved with upgrade to XalanJ 2.7.0 ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-09-20 00:21 Message: Logged In: YES user_id=484961 This problem seems to be reproducable by the following simle schema construct: <xs:element name="SameName" type="SameName"/> <xs:complexType name="SameName" base="xs:string"/> We are investigating this problem and trying to find a solution for the next release. Regards Kurt ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-04 11:04 Message: Logged In: YES user_id=484961 Please attach the schema, if the license allows it, or attach a simple schema that reproduces the problem. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1214556&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-15 20:07:48
|
Bugs item #1101707, was opened at 2005-01-13 16:27 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1101707&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.6-beta >Status: Closed >Resolution: Postponed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Kurt Riede (kriede) Summary: Enumeration name missing in enum documentation Initial Comment: Example: this type declaration <xsd:simpleType name="EarlyInvoicingMode" id="EarlyInvoicingMode"> <xsd:annotation> <xsd:documentation>Possible early invoicing modes of a shop. </xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:NCName"> <xsd:enumeration value='approved'> <xsd:annotation> <xsd:documentation> <p> Early invoicing is disabled for this shop.<br/> Invoices must be approved before they may be dispatched. </p> </xsd:documentation> </xsd:annotation> </xsd:enumeration> <xsd:enumeration value='disabled'> <xsd:annotation> <xsd:documentation> <p> Early invoicing is disabled for this shop.<br/> Invoices may be created after processing has been completed</p> </xsd:documentation> </xsd:annotation> </xsd:enumeration> </xsd:restriction> </xsd:simpleType> Produces this documentation ----------------------------------------- Possible early invoicing modes of a shop. Early invoicing is disabled for this shop. Invoices must be approved before they may be dispatched. Early invoicing is disabled for this shop. Invoices may be created after processing has been completed -------------------------------------------- This is not very helpful because the name of the documented enumeration is not visible ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2005-10-15 22:07 Message: Logged In: YES user_id=484961 converted to feature request [1327624] documentation of enumeration values: https://sourceforge.net/tracker/index.php? func=detail&aid=1327624&group_id=48863&atid=454394 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-01-25 17:43 Message: Logged In: NO I think that documentation without the information WHAT is documented is absolutely useless. I found this effect at the following places: 1.) when an enumeration is documented (as described) 2.) when attributes of a complex type are documented. The description of each attribute appears (also) in the genereal "Documentation" at the beginning of the page (before the documentation of the individual attributes). I think tha attribute documentation should only be visible at the attribute, but not repeated in teh global documentation. ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-01-14 18:00 Message: Logged In: YES user_id=484961 As far as I understand you, it would be nice to have the possible value together with the documentation. Similar things can happen in a lot of other schema constructs. So far we are following the XML Schema Infoset which specifies, that the documentation of a component is the summary of all nested documentation tags within a declaration. I agree with your suggestion that sometimes the context of the documentation is lost. I'll think about if it is possible and helpfull (also with a reasonable effort) to add some context information to the documentation section. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1101707&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-15 20:05:33
|
Feature Requests item #1327624, was opened at 2005-10-15 22:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1327624&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: model Group: xsddoc-0.8-beta Status: Open Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Nobody/Anonymous (nobody) Summary: documentation of enumeration values Initial Comment: see also bug report [ 1101707 ] Enumeration name missing in enum documentation: https://sourceforge.net/tracker/index.php? func=detail&aid=1101707&group_id=48863&atid=454391 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454394&aid=1327624&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-10-15 19:58:53
|
Bugs item #1228808, was opened at 2005-06-28 08:58 Message generated for change (Settings changed) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta >Status: Pending Resolution: Fixed Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: Question about ant task when using FileSets Initial Comment: I had a problem using the ant task in the latest release (0.8-beta) with nested FileSets. It worked fine if I specified a single, specific file to convert, but it would never run against any of my files in the nested FileSets. I tracked it down to this code, which always returned null on my XML schema files: if (!root.getLocalName().equals("schema") || !root.getNamespaceURI().equals(Task.SCHEMA_NS)) { return null; } This was added during this commit: http://cvs.sourceforge.net/viewcvs.py/xframe/xsddoc/src/ net/sf/xframe/ xsddoc/Task.java?r1=1.21&r2=1.22 No matter what I did, I could not get any of my schema files to pass either of the tests in that if statement. I did verify that the FileSets were matching the files I wanted. After commenting out the test above everything worked out great. So, here's my question: what do I have to do to make this work? I'm including the top of one of my XSD files. These verify properly in XMLMind, they work with xsddoc, and they work fine with Castor. <?xml version="1.0" encoding="UTF-8"?> <!-- target package ::= org.opennms.netmgmt.xml.eventconf --> <schema targetNamespace="http://xmlns.opennms.org/xsd/eventc onf" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:this="http://xmlns.opennms.org/xsd/eventconf" xmlns:ns2="http://www.w3.org/1999/xhtml" xmlns:ns="http://www.w3.org/2001/XMLSchema" xmlns:hfp="http://www.w3.org/2001/XMLSchema- hasFacetAndProperty"> <annotation> <documentation>Version: $Id$</documentation> </annotation> <element name="events"> <complexType> ... snip ... Thanks, - djg ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-09-30 20:29 Message: Logged In: YES user_id=484961 fixed in CVS HEAD. Will be available in soon coming next release. Please check if current version is wotking for you. ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-09-28 23:54 Message: Logged In: YES user_id=1330069 I have submited a patch for Task.java (bug 1307377) that I believe will solve these problems, if they are in fact the same problems I was encountering (and they appear to be). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-28 13:16 Message: Logged In: NO same issues here. I cannot also get xsddoc to process a whole directory ( it generates an empty documentation frameset). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-24 13:52 Message: Logged In: NO You must simply set the DocumentBuilderFactory to be namespace aware. Add the statement factory.setNamespaceAware(true) in Task.getDocumentBuilder(). Regards /roman ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-08-16 19:57 Message: Logged In: YES user_id=484961 Hi Mark, thank you for your support. The best way to provide a patch is to attach the patch here: https://sourceforge.net/tracker/?group_id=48863&atid=454393 (Click on 'Submit New' and upload your patch-file) As far as I see, in both your cases, the default namespace of the schema is the XML-Schema-Namespace, and for this case the test is wrong. I mostly test with schema files where the XML-Namespace is bound to a prefix like xs: or xsd: and then the fileset is working. But however, I will check your patch and hope this will soon be fixed for the next release. Regards Kurt ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-08-16 16:38 Message: Logged In: YES user_id=1330069 Kurty, I have encountered the same problem and finally tracked down what I believe to be the cause. It appears the document builder factory is not being set to "namespace aware". In addition, the code path for processing the filesets is not using the internal convenience methods for getting a new document, so be sure to change that or it won't take advantage of the change you make to fix the "namespace aware" problem. The other problem I think has to be solved in conjunction is the one already noted in the Task.java file with respect to how the fileset root directories vary relative to the project directory. I fixed this by using a more absolute path approach to the problem in the addSchema method, eliminating the complexity of relative paths. I would be happy to supply my version of Task.java that seems to fix these issues. It works in my scenarios, but I have not necessarily tested it with every use case of fileset combinations. What is the best way to submit my changes so they can be considered? Regards, Mark ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-28 09:09 Message: Logged In: YES user_id=484961 Hi Gregor, I've crossposted this mail as a bug report. The above mentioned test was introduced to exclude files that donot represent a schema. We will analyse this. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-09-30 18:36:32
|
Bugs item #1228808, was opened at 2005-06-28 08:58 Message generated for change (Comment added) made by kriede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta Status: Open >Resolution: Fixed Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: Question about ant task when using FileSets Initial Comment: I had a problem using the ant task in the latest release (0.8-beta) with nested FileSets. It worked fine if I specified a single, specific file to convert, but it would never run against any of my files in the nested FileSets. I tracked it down to this code, which always returned null on my XML schema files: if (!root.getLocalName().equals("schema") || !root.getNamespaceURI().equals(Task.SCHEMA_NS)) { return null; } This was added during this commit: http://cvs.sourceforge.net/viewcvs.py/xframe/xsddoc/src/ net/sf/xframe/ xsddoc/Task.java?r1=1.21&r2=1.22 No matter what I did, I could not get any of my schema files to pass either of the tests in that if statement. I did verify that the FileSets were matching the files I wanted. After commenting out the test above everything worked out great. So, here's my question: what do I have to do to make this work? I'm including the top of one of my XSD files. These verify properly in XMLMind, they work with xsddoc, and they work fine with Castor. <?xml version="1.0" encoding="UTF-8"?> <!-- target package ::= org.opennms.netmgmt.xml.eventconf --> <schema targetNamespace="http://xmlns.opennms.org/xsd/eventc onf" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:this="http://xmlns.opennms.org/xsd/eventconf" xmlns:ns2="http://www.w3.org/1999/xhtml" xmlns:ns="http://www.w3.org/2001/XMLSchema" xmlns:hfp="http://www.w3.org/2001/XMLSchema- hasFacetAndProperty"> <annotation> <documentation>Version: $Id$</documentation> </annotation> <element name="events"> <complexType> ... snip ... Thanks, - djg ---------------------------------------------------------------------- >Comment By: Kurt Riede (kriede) Date: 2005-09-30 20:29 Message: Logged In: YES user_id=484961 fixed in CVS HEAD. Will be available in soon coming next release. Please check if current version is wotking for you. ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-09-28 23:54 Message: Logged In: YES user_id=1330069 I have submited a patch for Task.java (bug 1307377) that I believe will solve these problems, if they are in fact the same problems I was encountering (and they appear to be). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-28 13:16 Message: Logged In: NO same issues here. I cannot also get xsddoc to process a whole directory ( it generates an empty documentation frameset). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-24 13:52 Message: Logged In: NO You must simply set the DocumentBuilderFactory to be namespace aware. Add the statement factory.setNamespaceAware(true) in Task.getDocumentBuilder(). Regards /roman ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-08-16 19:57 Message: Logged In: YES user_id=484961 Hi Mark, thank you for your support. The best way to provide a patch is to attach the patch here: https://sourceforge.net/tracker/?group_id=48863&atid=454393 (Click on 'Submit New' and upload your patch-file) As far as I see, in both your cases, the default namespace of the schema is the XML-Schema-Namespace, and for this case the test is wrong. I mostly test with schema files where the XML-Namespace is bound to a prefix like xs: or xsd: and then the fileset is working. But however, I will check your patch and hope this will soon be fixed for the next release. Regards Kurt ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-08-16 16:38 Message: Logged In: YES user_id=1330069 Kurty, I have encountered the same problem and finally tracked down what I believe to be the cause. It appears the document builder factory is not being set to "namespace aware". In addition, the code path for processing the filesets is not using the internal convenience methods for getting a new document, so be sure to change that or it won't take advantage of the change you make to fix the "namespace aware" problem. The other problem I think has to be solved in conjunction is the one already noted in the Task.java file with respect to how the fileset root directories vary relative to the project directory. I fixed this by using a more absolute path approach to the problem in the addSchema method, eliminating the complexity of relative paths. I would be happy to supply my version of Task.java that seems to fix these issues. It works in my scenarios, but I have not necessarily tested it with every use case of fileset combinations. What is the best way to submit my changes so they can be considered? Regards, Mark ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-28 09:09 Message: Logged In: YES user_id=484961 Hi Gregor, I've crossposted this mail as a bug report. The above mentioned test was introduced to exclude files that donot represent a schema. We will analyse this. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 |
|
From: SourceForge.net <no...@so...> - 2005-09-28 21:54:59
|
Bugs item #1228808, was opened at 2005-06-28 01:58 Message generated for change (Comment added) made by mrpatton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: all platforms Group: xsddoc-0.8-beta Status: Open Resolution: Accepted Priority: 5 Submitted By: Kurt Riede (kriede) Assigned to: Kurt Riede (kriede) Summary: Question about ant task when using FileSets Initial Comment: I had a problem using the ant task in the latest release (0.8-beta) with nested FileSets. It worked fine if I specified a single, specific file to convert, but it would never run against any of my files in the nested FileSets. I tracked it down to this code, which always returned null on my XML schema files: if (!root.getLocalName().equals("schema") || !root.getNamespaceURI().equals(Task.SCHEMA_NS)) { return null; } This was added during this commit: http://cvs.sourceforge.net/viewcvs.py/xframe/xsddoc/src/ net/sf/xframe/ xsddoc/Task.java?r1=1.21&r2=1.22 No matter what I did, I could not get any of my schema files to pass either of the tests in that if statement. I did verify that the FileSets were matching the files I wanted. After commenting out the test above everything worked out great. So, here's my question: what do I have to do to make this work? I'm including the top of one of my XSD files. These verify properly in XMLMind, they work with xsddoc, and they work fine with Castor. <?xml version="1.0" encoding="UTF-8"?> <!-- target package ::= org.opennms.netmgmt.xml.eventconf --> <schema targetNamespace="http://xmlns.opennms.org/xsd/eventc onf" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:this="http://xmlns.opennms.org/xsd/eventconf" xmlns:ns2="http://www.w3.org/1999/xhtml" xmlns:ns="http://www.w3.org/2001/XMLSchema" xmlns:hfp="http://www.w3.org/2001/XMLSchema- hasFacetAndProperty"> <annotation> <documentation>Version: $Id$</documentation> </annotation> <element name="events"> <complexType> ... snip ... Thanks, - djg ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-09-28 16:54 Message: Logged In: YES user_id=1330069 I have submited a patch for Task.java (bug 1307377) that I believe will solve these problems, if they are in fact the same problems I was encountering (and they appear to be). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-28 06:16 Message: Logged In: NO same issues here. I cannot also get xsddoc to process a whole directory ( it generates an empty documentation frameset). ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-09-24 06:52 Message: Logged In: NO You must simply set the DocumentBuilderFactory to be namespace aware. Add the statement factory.setNamespaceAware(true) in Task.getDocumentBuilder(). Regards /roman ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-08-16 12:57 Message: Logged In: YES user_id=484961 Hi Mark, thank you for your support. The best way to provide a patch is to attach the patch here: https://sourceforge.net/tracker/?group_id=48863&atid=454393 (Click on 'Submit New' and upload your patch-file) As far as I see, in both your cases, the default namespace of the schema is the XML-Schema-Namespace, and for this case the test is wrong. I mostly test with schema files where the XML-Namespace is bound to a prefix like xs: or xsd: and then the fileset is working. But however, I will check your patch and hope this will soon be fixed for the next release. Regards Kurt ---------------------------------------------------------------------- Comment By: mrpatton (mrpatton) Date: 2005-08-16 09:38 Message: Logged In: YES user_id=1330069 Kurty, I have encountered the same problem and finally tracked down what I believe to be the cause. It appears the document builder factory is not being set to "namespace aware". In addition, the code path for processing the filesets is not using the internal convenience methods for getting a new document, so be sure to change that or it won't take advantage of the change you make to fix the "namespace aware" problem. The other problem I think has to be solved in conjunction is the one already noted in the Task.java file with respect to how the fileset root directories vary relative to the project directory. I fixed this by using a more absolute path approach to the problem in the addSchema method, eliminating the complexity of relative paths. I would be happy to supply my version of Task.java that seems to fix these issues. It works in my scenarios, but I have not necessarily tested it with every use case of fileset combinations. What is the best way to submit my changes so they can be considered? Regards, Mark ---------------------------------------------------------------------- Comment By: Kurt Riede (kriede) Date: 2005-06-28 02:09 Message: Logged In: YES user_id=484961 Hi Gregor, I've crossposted this mail as a bug report. The above mentioned test was introduced to exclude files that donot represent a schema. We will analyse this. Regards Kurt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=454391&aid=1228808&group_id=48863 |
48 messages has been excluded from this view by a project administrator.