[ http://issues.apache.org/jira/browse/DERBY-1891?page=all ]
Myrna van Lunteren updated DERBY-1891:
--------------------------------------
Attachment: DERBY-1891_tr_20060926.diff
DERBY-1891_doctr_20060926.diff
Attaching 2 patches, DERBY-1891_tr_20060926.diff for the source trunk and
DERBY-1891_doctr_20060926.diff for the doc trunk.
The only changes are that the string 'secktn' in the messages 58009.C.19 and
XN002.U have been changed to SECTKN.
The source built without problem. The ref.html built without problem. the
ref.monohtml and ref.pdf builds were succesfful, but show some problems that
persisted when I reverted the change to file src/ref/rrefexcept71493.dita, so I
think those are unrelated:
[fop] [ERROR] Error in column-number property value '':
org.apache.fop.fo.expr.PropertyException: No conversion defined
I've not run any tests except from the build & looking at the produced html.
> error 58009.C.19 refers to non-existent codepoint secktn - needs correcting
> ----------------------------------------------------------------------------
>
> Key: DERBY-1891
> URL: http://issues.apache.org/jira/browse/DERBY-1891
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.0.2.1, 10.3.0.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.2.0
>
> Attachments: DERBY-1891_doctr_20060926.diff,
> DERBY-1891_tr_20060926.diff
>
>
> error 58009.C.19=Network protocol exception: secktn was not returned. The
> connection has been terminated.
> This is NET_SECTKN_NOT_RETURNED in
> org.apache.derby.drda.client.net.NetConnection.java
> I searched in the drda specs but I could not find SECKTN, but I *did* find
> SECTKN.
> So...I think the error message should get changed to SECTKN.
> The same non-existent codepoint seems to be referred to in: XN002.U=secktn
> was not returned.
> This affects the following:
> - English messages .properties file(s)
> - Brazilian messages .properties file(s)
> - documentation for SQLStates.
> I didn't find any masters with this.
> It should probably go into 10.2.1, although it's not important enough to hold
> up a release. Targeting for 10.2.2 for now.
> Myrna
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
