You are viewing a plain text version of this content. The canonical link for it is here.
Posted to graffito-dev@incubator.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2006/09/06 11:26:22 UTC
[jira] Created: (GRFT-100) Support custom class loader for mapped
classes
Support custom class loader for mapped classes
----------------------------------------------
Key: GRFT-100
URL: http://issues.apache.org/jira/browse/GRFT-100
Project: Graffito
Issue Type: Improvement
Components: JCR-Mapping
Affects Versions: 1.0-a1-dev
Reporter: Felix Meschberger
Currently, the ReflectionUtils.forName(String) method provides a class loading service, which just uses the class loader of the ReflectionUtils class itself to load classes. Many classes use the ReflectionUtils.forName(String) method, but some use the direct Class.forName(String) method.
Loading classes using Class.forName usually works very well in "simple" applications without much class loader ado. In certain environments, e.g. OSGi frameworks, classloaders are heavily used to separate parts of the application from other parts. In such environments, loading classes must be carefully crafted and using Class.forName(String) may not be adequate.
To come around this limitation a bit, I propose to add functionality to the ReflectionUtils class to inject a custom class loader to be used.
--
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] Resolved: (GRFT-100) Support custom class loader for mapped
classes
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-100?page=all ]
Christophe Lombart resolved GRFT-100.
-------------------------------------
Fix Version/s: 1.0-a1-dev
Resolution: Fixed
Patch applied - thanks !
> Support custom class loader for mapped classes
> ----------------------------------------------
>
> Key: GRFT-100
> URL: http://issues.apache.org/jira/browse/GRFT-100
> Project: Graffito
> Issue Type: Improvement
> Components: JCR-Mapping
> Affects Versions: 1.0-a1-dev
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Fix For: 1.0-a1-dev
>
> Attachments: ClassLoading.fm20060906.patch
>
>
> Currently, the ReflectionUtils.forName(String) method provides a class loading service, which just uses the class loader of the ReflectionUtils class itself to load classes. Many classes use the ReflectionUtils.forName(String) method, but some use the direct Class.forName(String) method.
> Loading classes using Class.forName usually works very well in "simple" applications without much class loader ado. In certain environments, e.g. OSGi frameworks, classloaders are heavily used to separate parts of the application from other parts. In such environments, loading classes must be carefully crafted and using Class.forName(String) may not be adequate.
> To come around this limitation a bit, I propose to add functionality to the ReflectionUtils class to inject a custom class loader to be used.
--
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] Closed: (GRFT-100) Support custom class loader for mapped
classes
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-100?page=all ]
Felix Meschberger closed GRFT-100.
----------------------------------
Verified. Thanks alot.
> Support custom class loader for mapped classes
> ----------------------------------------------
>
> Key: GRFT-100
> URL: http://issues.apache.org/jira/browse/GRFT-100
> Project: Graffito
> Issue Type: Improvement
> Components: JCR-Mapping
> Affects Versions: 1.0-a1-dev
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Fix For: 1.0-a1-dev
>
> Attachments: ClassLoading.fm20060906.patch
>
>
> Currently, the ReflectionUtils.forName(String) method provides a class loading service, which just uses the class loader of the ReflectionUtils class itself to load classes. Many classes use the ReflectionUtils.forName(String) method, but some use the direct Class.forName(String) method.
> Loading classes using Class.forName usually works very well in "simple" applications without much class loader ado. In certain environments, e.g. OSGi frameworks, classloaders are heavily used to separate parts of the application from other parts. In such environments, loading classes must be carefully crafted and using Class.forName(String) may not be adequate.
> To come around this limitation a bit, I propose to add functionality to the ReflectionUtils class to inject a custom class loader to be used.
--
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: (GRFT-100) Support custom class loader for mapped
classes
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-100?page=all ]
Christophe Lombart reassigned GRFT-100:
---------------------------------------
Assignee: Christophe Lombart
> Support custom class loader for mapped classes
> ----------------------------------------------
>
> Key: GRFT-100
> URL: http://issues.apache.org/jira/browse/GRFT-100
> Project: Graffito
> Issue Type: Improvement
> Components: JCR-Mapping
> Affects Versions: 1.0-a1-dev
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Attachments: ClassLoading.fm20060906.patch
>
>
> Currently, the ReflectionUtils.forName(String) method provides a class loading service, which just uses the class loader of the ReflectionUtils class itself to load classes. Many classes use the ReflectionUtils.forName(String) method, but some use the direct Class.forName(String) method.
> Loading classes using Class.forName usually works very well in "simple" applications without much class loader ado. In certain environments, e.g. OSGi frameworks, classloaders are heavily used to separate parts of the application from other parts. In such environments, loading classes must be carefully crafted and using Class.forName(String) may not be adequate.
> To come around this limitation a bit, I propose to add functionality to the ReflectionUtils class to inject a custom class loader to be used.
--
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: (GRFT-100) Support custom class loader for mapped
classes
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-100?page=all ]
Felix Meschberger updated GRFT-100:
-----------------------------------
Attachment: ClassLoading.fm20060906.patch
Patch to always use ReflectionUtils.forName(String) and to support setting the class loader
> Support custom class loader for mapped classes
> ----------------------------------------------
>
> Key: GRFT-100
> URL: http://issues.apache.org/jira/browse/GRFT-100
> Project: Graffito
> Issue Type: Improvement
> Components: JCR-Mapping
> Affects Versions: 1.0-a1-dev
> Reporter: Felix Meschberger
> Attachments: ClassLoading.fm20060906.patch
>
>
> Currently, the ReflectionUtils.forName(String) method provides a class loading service, which just uses the class loader of the ReflectionUtils class itself to load classes. Many classes use the ReflectionUtils.forName(String) method, but some use the direct Class.forName(String) method.
> Loading classes using Class.forName usually works very well in "simple" applications without much class loader ado. In certain environments, e.g. OSGi frameworks, classloaders are heavily used to separate parts of the application from other parts. In such environments, loading classes must be carefully crafted and using Class.forName(String) may not be adequate.
> To come around this limitation a bit, I propose to add functionality to the ReflectionUtils class to inject a custom class loader to be used.
--
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