You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/07/20 01:39:13 UTC
[jira] Created: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
------------------------------------------------------------------------
Key: DERBY-1540
URL: http://issues.apache.org/jira/browse/DERBY-1540
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.2.0.0
Reporter: Daniel John Debrunner
The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
- Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
- document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
- a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
- a limitation of the default QueryObjectGenerator , cannot use with a security manager?
- a Derby test problem?
This is more of a tracking issue, with a dump of my thoughts.
--
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
Re: [jira] Created: (DERBY-1540) JDBC 4 EoD with default QueryObjectGenerator
fails with SecurityManager
Posted by Daniel John Debrunner <dj...@apache.org>.
Lance J. Andersen wrote:
> btw, did you try this with Beta2 of Mustang as i would be surprised if
> this fails as Rick worked with Amit on this earlier.
I haven't tried it at all. I was just going through the tests that
disable the security manager without a good reason or a bug number
attached. I don't have access to Beta2 of Mustang at the moment.
If the test passes with the security manager then that would be great
and the bug could be closed as invalid.
Dan.
Re: [jira] Created: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Lance J. Andersen" <La...@Sun.COM>.
btw, did you try this with Beta2 of Mustang as i would be surprised if
this fails as Rick worked with Amit on this earlier.
Lance J. Andersen wrote:
> Amit,
>
> Didn't u fix this already?
>
>
> Please see the attached
>
> Daniel John Debrunner (JIRA) wrote:
>> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
>> ------------------------------------------------------------------------
>>
>> Key: DERBY-1540
>> URL: http://issues.apache.org/jira/browse/DERBY-1540
>> Project: Derby
>> Issue Type: Bug
>> Components: JDBC
>> Affects Versions: 10.2.0.0
>> Reporter: Daniel John Debrunner
>>
>>
>> The test jdbc4/TestQueryObject runs without the security manager
>> because the default QueryObjectGenerator uses reflection.
>> See
>> trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
>>
>>
>> Seems like a bug, but not sure of its cause or solution: Could be one
>> (or none) of:
>>
>> - Make changes in Derby code, e.g. add privilege blocks but don't see
>> how this will solve anything as it's not Derby code that's calling
>> the reflection and I don't see any javadoc comments in JDBC 4.0 about
>> methods throwing SecurityExceptions.
>>
>> - document the privileges required to use the EoD features, though
>> not sure how we would document the ability to grant a privilege to
>> system (JDK) code. Are these privileges documented in the JDBC spec?
>>
>> - a bug in the Mustang beta, default query object not being treated
>> as system code, no priv blocks in it?
>>
>> - a limitation of the default QueryObjectGenerator , cannot use with
>> a security manager?
>>
>> - a Derby test problem?
>>
>> This is more of a tracking issue, with a dump of my thoughts.
>>
>>
>>
>
Re: [jira] Created: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Lance J. Andersen" <La...@Sun.COM>.
Amit,
Didn't u fix this already?
Please see the attached
Daniel John Debrunner (JIRA) wrote:
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: http://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
>
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
>
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
>
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
>
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
>
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
>
> - a Derby test problem?
>
> This is more of a tracking issue, with a dump of my thoughts.
>
>
>
[jira] Updated: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-1540:
---------------------------------
Fix Version/s: 10.2.2.1
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: https://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: derby-1540_v01.diff
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed DERBY-1540.
--------------------------------
Resolution: Fixed
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: https://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: derby-1540_v01.diff
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reopened DERBY-1540:
----------------------------------
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: https://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Fix For: 10.2.2.1
>
> Attachments: derby-1540_v01.diff
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas closed DERBY-1540.
--------------------------------
Resolution: Fixed
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: http://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Attachments: derby-1540_v01.diff
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
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
[jira] Updated: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas updated DERBY-1540:
---------------------------------
Attachment: derby-1540_v01.diff
This was a bug in the Mustang beta, which has been fixed. The attached patch (derby-1540_v01.diff) causes this test to run under the SecurityManager. I ran the jdbc40 suite against jar files. It passes cleanly under the embedded framework. In the DerbyNetClient framework the suite has the same errors which appear in the mainline. Touches the following file:
M java\testing\org\apache\derbyTesting\functionTests\tests\jdbc4\TestQueryObject_app.properties
Committed at subversion revision 425772.
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: http://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
> Attachments: derby-1540_v01.diff
>
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
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
[jira] Assigned: (DERBY-1540) JDBC 4 EoD with default
QueryObjectGenerator fails with SecurityManager
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas reassigned DERBY-1540:
------------------------------------
Assignee: Rick Hillegas
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ------------------------------------------------------------------------
>
> Key: DERBY-1540
> URL: http://issues.apache.org/jira/browse/DERBY-1540
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Rick Hillegas
>
> The test jdbc4/TestQueryObject runs without the security manager because the default QueryObjectGenerator uses reflection.
> See trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/TestQueryObject_app.properties
> Seems like a bug, but not sure of its cause or solution: Could be one (or none) of:
> - Make changes in Derby code, e.g. add privilege blocks but don't see how this will solve anything as it's not Derby code that's calling the reflection and I don't see any javadoc comments in JDBC 4.0 about methods throwing SecurityExceptions.
> - document the privileges required to use the EoD features, though not sure how we would document the ability to grant a privilege to system (JDK) code. Are these privileges documented in the JDBC spec?
> - a bug in the Mustang beta, default query object not being treated as system code, no priv blocks in it?
> - a limitation of the default QueryObjectGenerator , cannot use with a security manager?
> - a Derby test problem?
> This is more of a tracking issue, with a dump of my thoughts.
--
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