[MAGNOLIA-2049] Activation: failed from 3.0.5 to 3.5.4 Created: 07/Feb/08 Updated: 23/Jan/13 Resolved: 11/Jul/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.5.4 |
| Fix Version/s: | 3.6, 3.5.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Olivier Marti | Assignee: | Philipp Bärfuss |
| Resolution: | Workaround exists | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
When trying to activate a contentNode from magnolia version 3.0.5 to 3.5.4 an error occurs: ERROR org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[default] ApplicationDispatcher.java(invoke:687) 07.02.2008 17:33:37 Servlet.service() for servlet default threw exception Workaround:
|
| Comments |
| Comment by Magnolia International [ 08/Jul/08 ] |
|
We should provide a fix, an update task, and/or documentation for this. |
| Comment by Philipp Bracher [ 11/Jul/08 ] |
|
The current workaround is enough. |
| Comment by Magnolia International [ 15/Jul/08 ] |
|
Needs docu - will add to release notes. |