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/10/06 13:16:19 UTC
[jira] Created: (GRFT-108) Digester fails to load descriptor
classes when using different class loaders
Digester fails to load descriptor classes when using different class loaders
----------------------------------------------------------------------------
Key: GRFT-108
URL: http://issues.apache.org/jira/browse/GRFT-108
Project: Graffito
Issue Type: Improvement
Affects Versions: 1.0-a1-dev
Environment: Graffito SVN checkout Rev. 448648
Reporter: Felix Meschberger
With issue GRFT-100 a patch has been applied to the ReflectionUtils class to support custom class loaders for mapped classes. There is a similar issue regarding the loading of class descriptors using Digester: If the Digester is loaded by a different class loader than the jcr mapping library, the digester cannot load the descriptor classes.
The Digester class provides a setClassLoader() method which allows for setting a custom class loader. As the classes to be loaded are part of the jcr mapping library, the class loader of the DigesterDescriptorReader class, which uses the Digester to load class descriptions, should be set on the digester.
--
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-108) Digester fails to load descriptor classes
when using different class loaders
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-108?page=all ]
Felix Meschberger closed GRFT-108.
----------------------------------
Verified. Thanks alot.
> Digester fails to load descriptor classes when using different class loaders
> ----------------------------------------------------------------------------
>
> Key: GRFT-108
> URL: http://issues.apache.org/jira/browse/GRFT-108
> Project: Graffito
> Issue Type: Improvement
> Affects Versions: 1.0-a1-dev
> Environment: Graffito SVN checkout Rev. 448648
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Attachments: GRFT-108.fm.20061006.diff
>
>
> With issue GRFT-100 a patch has been applied to the ReflectionUtils class to support custom class loaders for mapped classes. There is a similar issue regarding the loading of class descriptors using Digester: If the Digester is loaded by a different class loader than the jcr mapping library, the digester cannot load the descriptor classes.
> The Digester class provides a setClassLoader() method which allows for setting a custom class loader. As the classes to be loaded are part of the jcr mapping library, the class loader of the DigesterDescriptorReader class, which uses the Digester to load class descriptions, should be set on the digester.
--
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-108) Digester fails to load descriptor
classes when using different class loaders
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-108?page=all ]
Christophe Lombart resolved GRFT-108.
-------------------------------------
Resolution: Fixed
Patch applied thanks
> Digester fails to load descriptor classes when using different class loaders
> ----------------------------------------------------------------------------
>
> Key: GRFT-108
> URL: http://issues.apache.org/jira/browse/GRFT-108
> Project: Graffito
> Issue Type: Improvement
> Affects Versions: 1.0-a1-dev
> Environment: Graffito SVN checkout Rev. 448648
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Attachments: GRFT-108.fm.20061006.diff
>
>
> With issue GRFT-100 a patch has been applied to the ReflectionUtils class to support custom class loaders for mapped classes. There is a similar issue regarding the loading of class descriptors using Digester: If the Digester is loaded by a different class loader than the jcr mapping library, the digester cannot load the descriptor classes.
> The Digester class provides a setClassLoader() method which allows for setting a custom class loader. As the classes to be loaded are part of the jcr mapping library, the class loader of the DigesterDescriptorReader class, which uses the Digester to load class descriptions, should be set on the digester.
--
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-108) Digester fails to load descriptor
classes when using different class loaders
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-108?page=all ]
Felix Meschberger updated GRFT-108:
-----------------------------------
Attachment: GRFT-108.fm.20061006.diff
Patch implementing setting the class loader to be used by the Digester instance.
> Digester fails to load descriptor classes when using different class loaders
> ----------------------------------------------------------------------------
>
> Key: GRFT-108
> URL: http://issues.apache.org/jira/browse/GRFT-108
> Project: Graffito
> Issue Type: Improvement
> Affects Versions: 1.0-a1-dev
> Environment: Graffito SVN checkout Rev. 448648
> Reporter: Felix Meschberger
> Attachments: GRFT-108.fm.20061006.diff
>
>
> With issue GRFT-100 a patch has been applied to the ReflectionUtils class to support custom class loaders for mapped classes. There is a similar issue regarding the loading of class descriptors using Digester: If the Digester is loaded by a different class loader than the jcr mapping library, the digester cannot load the descriptor classes.
> The Digester class provides a setClassLoader() method which allows for setting a custom class loader. As the classes to be loaded are part of the jcr mapping library, the class loader of the DigesterDescriptorReader class, which uses the Digester to load class descriptions, should be set on the digester.
--
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-108) Digester fails to load descriptor
classes when using different class loaders
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-108?page=all ]
Christophe Lombart reassigned GRFT-108:
---------------------------------------
Assignee: Christophe Lombart
> Digester fails to load descriptor classes when using different class loaders
> ----------------------------------------------------------------------------
>
> Key: GRFT-108
> URL: http://issues.apache.org/jira/browse/GRFT-108
> Project: Graffito
> Issue Type: Improvement
> Affects Versions: 1.0-a1-dev
> Environment: Graffito SVN checkout Rev. 448648
> Reporter: Felix Meschberger
> Assigned To: Christophe Lombart
> Attachments: GRFT-108.fm.20061006.diff
>
>
> With issue GRFT-100 a patch has been applied to the ReflectionUtils class to support custom class loaders for mapped classes. There is a similar issue regarding the loading of class descriptors using Digester: If the Digester is loaded by a different class loader than the jcr mapping library, the digester cannot load the descriptor classes.
> The Digester class provides a setClassLoader() method which allows for setting a custom class loader. As the classes to be loaded are part of the jcr mapping library, the class loader of the DigesterDescriptorReader class, which uses the Digester to load class descriptions, should be set on the digester.
--
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