[ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12358358 ]
Kathey Marsden commented on DERBY-289: -------------------------------------- Dan had mentioned in a thread on a different topic: "In addition most of the packages in derby.jar are now sealed, which means that classes in a sealed package must be loaded from the same jar." I think this might be a problem for the code sharing proposal which relies on the ability of one jar to be able to load the class from the other jar if the other jar is loaded first. It seems we would get an error if the package was sealed. > Enable code sharing between Derby client and engine > --------------------------------------------------- > > Key: DERBY-289 > URL: http://issues.apache.org/jira/browse/DERBY-289 > Project: Derby > Type: Improvement > Components: Network Client > Versions: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.1.0 > Environment: N/A > Reporter: David Van Couvering > Assignee: David Van Couvering > Priority: Minor > Fix For: 10.2.0.0 > Attachments: DERBY-289.diff > > Right now, there is no way for the Derby network client to share code with > the Derby engine. We should have a separate jar file, e.g. derby_common.jar, > that contains shared code and is used by both the client and the engine. -- 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
