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

Bug 92480

Summary:	JSP Fragments need content properties page
Product:	[WebTools] WTP Source Editing	Reporter:	David Williams <david_williams>
Component:	jst.jsp	Assignee:	Amy Wu <for.work.things>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P2	CC:	jljlmatu
Version:	1.0	Keywords:	Documentation
Target Milestone:	1.5 M5
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	124288

Description David Williams

2005-04-23 02:07:58 EDT

In the course of refactoring, etc., I believe we've completely disabled 
the "content properties" page for JSP files. This is required for 
users of JSP fragments to be able to specify what content model (doc type) 
applies to that JSP Fragment. And .. this is needed for content assist and 
source page validation to work correctly.

Comment 1 David Williams

2005-04-23 02:08:35 EDT

Marking as P2 to remember to give attention during M5.

Comment 2 David Williams

2005-04-25 23:06:22 EDT

Changing severity to "normal" since "importance" should be reflected by priority, 
not severity (though is very important, to provide content assist, for xhtml
type fragments).

Comment 3 David Williams

2005-07-20 00:43:10 EDT

Status: this will not be in 0.7, but will give attention for release 1.0. 
Implication is that while editing JSP fragments, content assist and 
validation can not be customized to non-default content models (since, 
typically, the page directive attribute or doctype can not be repeated in a
fragment).

Comment 4 David Williams

2005-07-20 22:25:28 EDT

Technically an enhancement, I guess, even though will seem to be a bug to
end-users. 

Modifying only for bugzilla book keeping.

Comment 5 Amy Wu

2006-02-02 16:02:41 EST

*** Bug 107101 has been marked as a duplicate of this bug. ***

Comment 6 David Williams

2006-02-18 13:00:33 EST

Amy, as you work on this, please keep in mind we *might* want to change some package names. 

I noticed today that 
 org.eclipse.wst.sse.internal.contentproperties 
is in "sse.core" and thus should (likely) be named 
 org.eclipse.wst.sse.core.internal.contentproperties

I'm not sure what the final long term correct naming is, but just wanted 
to remind you to consider these "out of place" names. [which are out of place
just due to previous release refactorings].

Comment 7 Amy Wu

2006-02-24 19:45:39 EST

This has been fixed and released in this week's IBuild.  Please see:
http://www.eclipse.org/webtools/wst/components/sse/designs/WebContentSettings.html
for more info.

Comment 8 Amy Wu

2006-06-15 14:59:13 EDT

closing since reporter verified.  thanks.