| Summary: | WebXmlUpdater - multiple method calls fail to update model | ||
|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Ian Trimble <ian.trimble> |
| Component: | Core | Assignee: | Ian Trimble <ian.trimble> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | dimitar.giormov, raghunathan.srinivasan |
| Version: | 3.3 | ||
| Target Milestone: | 3.2.3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 323185 | ||
| Bug Blocks: | |||
Please review if this is caused by the fix for bug 323185 (In reply to comment #1) > Please review if this is caused by the fix for bug 323185 If I reverse the patch for bug 323185, things work correctly. Hi the dependent bug was fixed. I have run your tests and they passed. Hopefully you can close the issue now. Fix for blocking bug has corrected the problem. |
When multiple WebXmlUpdater methods are called sequentially, only the first method will succeed. For example (where "updater" is an instance of WebXmlUpdater), this succeeds: updater.addServlet("Foo", "org.foo.Foo", "1"); but this successfully adds only the servlet and not the context parameter: updater.addServlet("Foo", "org.foo.Foo", "1"); updater.addContextParam("Bar", "Hmm", "Stuff"); This causes two failing tests in the core tests suite: - testAddContextParam, and - testAddServletMapping