You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2007/04/26 00:20:15 UTC
[jira] Created: (VELOCITY-541) only possible to use one
StringResourceLoader per application
only possible to use one StringResourceLoader per application
-------------------------------------------------------------
Key: VELOCITY-541
URL: https://issues.apache.org/jira/browse/VELOCITY-541
Project: Velocity
Issue Type: Bug
Components: Engine
Affects Versions: 1.5
Reporter: Nathan Bubna
Assigned To: Nathan Bubna
Fix For: 1.6
When multiple StringResourceLoaders are initialized, the later ones are blowing up. StringResourceLoader uses a static RepositoryFactory. Unfortunately, this means that you can really only have one StringResourceLoader per classloader. This poses significant issues for anyone using multiple engines w/StringResourceLoader and could be come a major issue if any other frameworks or components adopt use of the StringResourceLoader (e.g. i'm planning to use this for a VelocityViewTag in Tools 2.x). They'll stomp all over each other in many ways. This is bad. :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-541) only possible to use one
StringResourceLoader per application
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491850 ]
Nathan Bubna commented on VELOCITY-541:
---------------------------------------
I meant to add this info in my resolving comment....
Checked in change to revision 532549 to:
Completely revamp how repositories are created and stored to allow for
1) multiple StringResourceLoaders per application
2) StringResourceRepository(s) to be stored statically or in application attributes
3) named StringResourceRepository(s) to avoid namespace collisions
4) ability to clear out static repositories to plug possible memory leak
The existing StringResourceLoaderTestCase passes without alteration, and a new set of tests for the repository changes was added as StringResourceLoaderRepositoryTestCase.
> only possible to use one StringResourceLoader per application
> -------------------------------------------------------------
>
> Key: VELOCITY-541
> URL: https://issues.apache.org/jira/browse/VELOCITY-541
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.5
> Reporter: Nathan Bubna
> Assigned To: Nathan Bubna
> Fix For: 1.6
>
>
> When multiple StringResourceLoaders are initialized, the later ones are blowing up. StringResourceLoader uses a static RepositoryFactory. Unfortunately, this means that you can really only have one StringResourceLoader per classloader. This poses significant issues for anyone using multiple engines w/StringResourceLoader and could be come a major issue if any other frameworks or components adopt use of the StringResourceLoader (e.g. i'm planning to use this for a VelocityViewTag in Tools 2.x). They'll stomp all over each other in many ways. This is bad. :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Resolved: (VELOCITY-541) only possible to use one
StringResourceLoader per application
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-541.
-----------------------------------
Resolution: Fixed
revision 532549:
> only possible to use one StringResourceLoader per application
> -------------------------------------------------------------
>
> Key: VELOCITY-541
> URL: https://issues.apache.org/jira/browse/VELOCITY-541
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.5
> Reporter: Nathan Bubna
> Assigned To: Nathan Bubna
> Fix For: 1.6
>
>
> When multiple StringResourceLoaders are initialized, the later ones are blowing up. StringResourceLoader uses a static RepositoryFactory. Unfortunately, this means that you can really only have one StringResourceLoader per classloader. This poses significant issues for anyone using multiple engines w/StringResourceLoader and could be come a major issue if any other frameworks or components adopt use of the StringResourceLoader (e.g. i'm planning to use this for a VelocityViewTag in Tools 2.x). They'll stomp all over each other in many ways. This is bad. :(
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org