THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Note |
|---|
When deploying to WebLogic, some developers report problems with the framework locating resources, especially with Velocity. For more about WebLogic and Velocity, see the Velocity website. |
| Info |
|---|
To deploy to WebLogic, the common approach is to create and deploy an unexpanded WAR to the WebLogic deployment directory. With WL 8.x, the deployment directory is typically at |
Adding an action-velocity.properties Configuration File
...
- In the
action.propertiesfile (usually kept in the
WEB-INF/classesdirectory)
...
- , add an entry that specifies a Velocity configuation file.
Code Block title action.properties action.velocity.configfile =
...
action-velocity.properties
...
- Create the corresponding Velocity properties file ("action-velocity.properties"
...
- ), preferablly in the same location as the
action.propertiesfile.
- Copy into the Velocity properties file the contents of the
velocity.propertiesfile that is
...
- the the SAF
velocity-dep.jar
...
- .
- In your new
...
action-velocity.properties
...
- file, find
...
- he section titled
...
- "
T E M P L A T E L O A D E R S", and change this section
...
- as so:
| Code Block |
|---|
> =========================================== > resource.loader =class > > class file.resource.loader.description = Velocity File Resource Loader > file.resource.loader.class = > org.apache.velocity.runtime.resource.loader.FileResourceLoader > file.resource.loader.path = . > file.resource.loader.cache = false > file.resource.loader.modificationCheckInterval =2 > > 2 class.resource.loader.class = > org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader > class.resource.loader.cache = true > =========================================== > > ... which straightens out the class resource loading problems (for us > at least). > > hope this helps, > james |
...
|
- Redeploy a fresh WAR to WebLogic.