db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-873) OSGi bundle activator not JSR169 compliant
Date Thu, 20 Nov 2008 01:09:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-873:
-------------------------------------

    Attachment: EmbeddedActivator.class
                DERBY-873_notforcommit.diff

Based on Dan's suggestions I made some a stab. However, I don't have Knoplerfish or anything
else installed, so this is a completely untested patch (except that it doesn't give build
errors). 

I'll need to go through figuring out how to test this, but just in case someone who is all
set up is interested in doing - for testing purposes only! - a jar -uvf I've included the
class EmbeddedActovator.class - it'll need the directory structure created (org/apache/derby/osgi).


> OSGi bundle activator not JSR169 compliant
> ------------------------------------------
>
>                 Key: DERBY-873
>                 URL: https://issues.apache.org/jira/browse/DERBY-873
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions: 10.0.2.0
>            Reporter: Byron K. Appelt
>            Priority: Minor
>         Attachments: DERBY-873_notforcommit.diff, EmbeddedActivator.class
>
>
> EmbeddedActivator contains references to java.sql.DriverManager which is not included
in JSR169.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message