Bug 104785 - Need to support encoding spec'd in web.xml
Summary: Need to support encoding spec'd in web.xml
Status: CLOSED DUPLICATE of bug 83798
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: Future   Edit
Assignee: jst.jsp-triaged CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords:
Depends on: 183309
Blocks: 124288
  Show dependency tree
 
Reported: 2005-07-22 09:27 EDT by David Williams CLA
Modified: 2010-04-27 11:30 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2005-07-22 09:27:49 EDT 
in the 
jsp-property-group

as in 

</jsp-config>
<jsp-property-group>
  <url-pattern>*.jsp</url-pattern>
  <page-encoding>koi8-r</page-encoding>
</jsp-property-group>
</jsp-config>
Comment 1 David Williams CLA 2005-07-23 14:42:47 EDT 
moving to P2, since part of JSP 2.0, and there has been newsgroup post
expressing the need for this. Though ... will have to figure out exactly how
(without sacrificing or interfering with content specified encodings).
Comment 2 Andrej Zachar CLA 2006-09-22 04:16:09 EDT 
Go to eclipse -> window -> Preferences -> Content Types -> JSP and change default encoding to your.
Inherit means that it takes it from here!
I think this is a useability bug of eclipse.
I hope it helps you.
Comment 3 Nitin Dahyabhai CLA 2007-04-19 01:27:44 EDT 
Deferring to 3.0.  Eclipse 3.3 lacks any way for us to insert this in the content type determination.
Comment 4 David Williams CLA 2008-05-15 08:48:53 EDT 
I'm assuming this will have to be done next release, so changing to 'future'.
Comment 5 Ian Tewksbury CLA 2010-01-20 09:24:04 EST 
After 5 years this seems to me a feature we will not be supporting and there is the workaround described by comment #2.  I vote for close.
Comment 6 Nick Sandonato CLA 2010-04-27 11:30:24 EDT 

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