[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-dev
Subject:    [jira] Resolved: (VELOCITY-541) only possible to use one
From:       "Nathan Bubna (JIRA)" <dev () velocity ! apache ! org>
Date:       2007-04-26 0:15:15
Message-ID: 21485309.1177546515473.JavaMail.jira () brutus
[Download RAW message or body]


     [ 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


[prev in list] [next in list] [prev in thread] [next in thread]