PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3226

*** shadow/3226 Wed Aug 22 07:47:58 2001
--- shadow/3226.tmp.14313       Wed Aug 22 08:05:19 2001
***************
*** 2,9 ****
  | Identity Constrain Error:   identity constraint "KeyRef@xxxxxx" has a keyr |
  +----------------------------------------------------------------------------+
  |        Bug #: 3226                        Product: Xerces-J                |
! |       Status: NEW                         Version: 1.4.2                   |
! |   Resolution:                            Platform: PC                      |
  |     Severity: Major                    OS/Version: Windows NT/2K           |
  |     Priority: Other                     Component: Schema-Structures       |
  +----------------------------------------------------------------------------+
--- 2,9 ----
  | Identity Constrain Error:   identity constraint "KeyRef@xxxxxx" has a keyr |
  +----------------------------------------------------------------------------+
  |        Bug #: 3226                        Product: Xerces-J                |
! |       Status: RESOLVED                    Version: 1.4.2                   |
! |   Resolution: INVALID                    Platform: PC                      |
  |     Severity: Major                    OS/Version: Windows NT/2K           |
  |     Priority: Other                     Component: Schema-Structures       |
  +----------------------------------------------------------------------------+
***************
*** 27,30 ****
  A work around for this bug can be accomplished by moving the 'dummy2' keyref 
  element from the 'regions' element to the parent element 'purchaseReport' and 
  modifying the 'selector' elements 'xpath' attribute to 
! xpath="r:regions/r:zip/r:part".
--- 27,35 ----
  A work around for this bug can be accomplished by moving the 'dummy2' keyref 
  element from the 'regions' element to the parent element 'purchaseReport' and 
  modifying the 'selector' elements 'xpath' attribute to 
! xpath="r:regions/r:zip/r:part".
! 
! ------- Additional Comments From [EMAIL PROTECTED]  2001-08-22 08:05 -------
! This example from the Primer is in error; it conflicts with the algorithm 
! presented in the Schema Structures spec.  If you need more details, there was a 
! thread on the schema-dev list discussing this point.  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to