search

javalover520 / jsyntaxpane

Automatically exported from code.google.com/p/jsyntaxpane
0 stars 0 forks source link

SyntaxKits need to support alternate classloaders #125

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
When using jsyntaxpane in the context of OSGi, classloader issues arise.
OSGi does not take kindly to Class.forName as this circumvents the class
loader dependency heirarchy that OSGi builds for dependency management.

Without getting too deep into OSGi, the easiest solution is to allow for an
optional classloader to be passed into the constructors of all SyntaxKits
so that the base class (DefaultSyntaxKit) can optionally use this
classloader for creating components.

Original issue reported on code.google.com by c.ca...@gmail.com on 12 Nov 2009 at 2:30

GoogleCodeExporter commented 8 years ago 
This is a dupplicate of issue 177, that has a patch attached. 

https://code.google.com/p/jsyntaxpane/issues/detail?id=177

Original comment by martin.q...@ens-rennes.fr on 18 Aug 2013 at 12:13