worrying about reflection "security" in a library is pointless. any
real security needs to be accomplished using server isolation, and/or
data access/encryption
On Feb 23, 2007, at 1:11 PM, Daniel John Debrunner (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-811?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12475439 ]
Daniel John Debrunner commented on LUCENE-811:
----------------------------------------------
Doesn't making such methods public mean they can be called trough
reflection?
Public API inconsistency
------------------------
Key: LUCENE-811
URL: https://issues.apache.org/jira/browse/LUCENE-811
Project: Lucene - Java
Issue Type: Bug
Components: Index
Affects Versions: 2.1
Environment: 2.1.0 release
Reporter: Andrzej Bialecki
Assigned To: Michael McCandless
Priority: Minor
Attachments: LUCENE-811.patch
org.apache.lucene.index.SegmentInfos is public, and contains
public methods (which is good for expert-level index manipulation
tools such as Luke). However, SegmentInfo class has package
visibility. This leads to a strange result that it's possible to
read SegmentInfos, but it's not possible to access its details
(SegmentInfos.info(int)) from a user application.
The solution is to make SegmentInfo class public.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
