You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2007/01/28 18:40:21 UTC
[jira] Moved: (TILES-42) JRun 4 server stop trigger NPE
[ https://issues.apache.org/struts/browse/TILES-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli moved SB-25 to TILES-42:
-----------------------------------------
Fix Version/s: (was: 2.0)
2.0.0
Component/s: (was: Tiles)
core
Affects Version/s: 2.0.0
Workflow: Struts (was: jira)
Key: TILES-42 (was: SB-25)
Project: Tiles (was: Sandbox)
> JRun 4 server stop trigger NPE
> ------------------------------
>
> Key: TILES-42
> URL: https://issues.apache.org/struts/browse/TILES-42
> Project: Tiles
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.0
> Environment: JRun 4, Win2k, Sun JDK 1.5.0
> Reporter: Zarick Lau
> Assigned To: Antonio Petrelli
> Fix For: 2.0.0
>
> Attachments: tiles-core-HEAD-jrun4-stop-npe.patch
>
>
> I have integrate standalone tiles in my project (for my company).
> When JRun 4 stop (or I trigger the hot-deploy to reload the webapp), it will throw a NullPointerException.
> After some study, the NPE should be cause by the absence of super.init(config) call in TilesServlet.java
> I'll attach my one-line patch. Hope useful...
> (BTW, what's the current status on standalone-tiles?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.