|
| Re: JSP as a second class citizen [message #171734 is a reply to message #171703] |
Tue, 20 June 2006 21:55   |
Eclipse User |
|
|
|
Originally posted by: dserodio.gmail.com
Zohar wrote:
> Hi,
> I've noticed that when working with JSPs, I don't have all of eclipse's
> services available. For example, when I search for references to a method
> (in the entire workspace), I don't get references in JSPs where the method
> is invoked. Another example is when changing a method's name through
> refactoring - the method's references in JSPs are not updated.
> Is this intentional?
I've posted questions like this before, and the answer I got was along
the lines of "scriptlets are bad, you shouldn't be using scriptlets".
HTH,
Daniel Serodio
|
|
|
|
|
| Re: JSP as a second class citizen [message #171758 is a reply to message #171750] |
Wed, 21 June 2006 08:05 |
| Eclipse User |
|
|
|
Originally posted by: mikael.staldal.ingen-reklam-univits.com
Zohar wrote:
>> I've posted questions like this before, and the answer I got was
>> along the lines of "scriptlets are bad, you shouldn't be using
>> scriptlets".
> Why are they so bad and what is the alternative to using them?
Scriptlets in JSP are bad because it's messy to mix HTML and Java code
in the same file, and because of the risk of including business logic
in the presentation layer.
The alternative, if you use JSP, is to use taglibs. Another alternative
is to not use JSP at all, use some other presentation layer template
technology instead, e.g. Velocity (http://jakarta.apache.org/velocity/)
or LSP (http://sourceforge.net/projects/lspx).
(This is not an Eclipse issue, it's a general Java web app design issue.)
|
|
|
| Re: JSP as a second class citizen [message #172188 is a reply to message #171703] |
Fri, 23 June 2006 05:21 |
|
Zohar wrote:
> I've noticed that when working with JSPs, I don't have all of eclipse's
> services available. For example, when I search for references to a method
> (in the entire workspace), I don't get references in JSPs where the method
> is invoked. Another example is when changing a method's name through
> refactoring - the method's references in JSPs are not updated.
> Is this intentional?
Not at all. If you're finding that there are problems, ensure that
all of your JSP files have been saved to disk. If you still have
problems, please open a bug report against the JSP component (see
below) and include exactly which WTP build you are using. Please
try it with at least 1.0.2 or higher.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Web%20To ols&component=jst.jsp
--
- Nitin
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
Powered by
FUDForum. Page generated in 0.03369 seconds
] 
Search
Help
Register
Login
Home
