Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 355150

Summary:	ModelProviderManager is not providing model with content of web.xml that is in the second web root
Product:	[WebTools] WTP Java EE Tools	Reporter:	Ian Trimble <ian.trimble>
Component:	jst.j2ee	Assignee:	Roberto Sanchez Herrera <shr31223>
Status:	RESOLVED DUPLICATE	QA Contact:	Chuck Bridgham <cbridgha>
Severity:	blocker
Priority:	P3	CC:	ccc
Version:	3.2.4
Target Milestone:	3.2.5
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	353834

Description Ian Trimble

2011-08-18 15:22:53 EDT

ModelProviderManager is not providing model with content of web.xml that is in the second web root. That is, there are multiple "web roots" configured via the org.eclipse.wst.common.component file, and the web.xml in the second root listed is not being read into the model provided via ModelProviderManager.

This is blocking work on bug 353834, since we rely on the ModelProviderManager to get the web model. This visibly manifests itself in the "Deployment Descriptor" explorer node, which will show no content when such a project is opened.

Comment 1 Carl Anderson

2011-08-22 19:01:45 EDT

Roberto, I know you just "fixed" this- can you ensure that the work you did fixes Ian's scenario?

Comment 2 Roberto Sanchez Herrera

2011-08-23 13:38:47 EDT

Ian, Carl,
The fix that Carl mentions was committed to 3.2.5 using bug 121460. See comment #12 for more details. 

I tested the following scenario using WTP 3.2.5:

1. I created a dynamic web 3.0 project with Deployment descriptor
2. I created a new folder in the web project and added it using the deployment assembly page as root folder to .component file.
3. I added a servlet to the deployment descriptor (I was able to see the servlet in the deployment descriptor node)
4. I edited manually the .component file so the new entry was first, and restarted eclipse. 
5. I was still able to see the servlet in the deployment descriptor node
6. I opened the workspace using WTP 3.2.4, and I could not see the servlet (error that Ian mentions)

So, it looks like the changes in WTP 3.2.5 fixes the simple scenario reported here.  

Ian, can you confirm if the patch in bug 121460 will work for you?

Comment 3 Ian Trimble

2011-08-23 20:10:28 EDT

I will look at my specific scenario ASAP. Thanks for following up on this bug.

Comment 4 Ian Trimble

2011-08-24 14:27:30 EDT

As far as I am concerned, this approach provides an adequate solution. I'm hoping that the users who logged Bug 353834 can make use of the attribute in the component file to make their particular scenario functional.

Thanks again,
 - Ian

Comment 5 Roberto Sanchez Herrera

2011-08-25 10:29:09 EDT

Thanks Ian for checking. I'm resolving this bug as duplicated of 121460

*** This bug has been marked as a duplicate of bug 121460 ***