[
https://issues.apache.org/jira/browse/DERBY-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860709#action_12860709
]
Bryan Pendleton commented on DERBY-4623:
----------------------------------------
I can't reproduce the behavior you're seeing. The behavior that I see
on my system matches what is described at "Classpath and version issues" on:
http://db.apache.org/derby/docs/10.5/devguide/cdevstandardsxml.html
It's possible that part of the behavior that you were seeing is explained by
this note on that page:
The xalan.jar file automatically puts into the classpath the other
required jars that are in the same directory.
Can you post a short script showing the test you ran with the CLASSPATH?
That might help me understand your scenario better.
> "XML data type" page in ref needs some modifications
> ----------------------------------------------------
>
> Key: DERBY-4623
> URL: https://issues.apache.org/jira/browse/DERBY-4623
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0,
> 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0
> Reporter: C.S. Nirmal J. Fernando
> Assignee: C.S. Nirmal J. Fernando
> Priority: Trivial
> Attachments: DERBY-4623.diff, DERBY-4623.zip
>
>
> I think this page
> (http://db.apache.org/derby/docs/10.5/devguide/cdevstandardsxml.html ) need
> some more explanation on areas such as:
> 1) Setting paths of xercesImpl.jar and xalan.jar in the CLASSPATH
> 2) Command that user should use to start the Derby i.e. java
> org.apache.derby.tools.ij
> 3) Mention that user needed to create a table which contains XML data
> type column/s, because users might thought that they can retrieve XML data
> from an any table.
> 4) Mention the requirements that are needed when inserting values to a
> XML data typed column, i.e. need of XML keywords document & preserve
> whitespace, tags etc.
> 5) A small example which is clearly shows the creation, insertion &
> selection using XML data type.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
