Is JSP on ANYONE'S RADAR?

JetBrainers, JSP is in a decrepid state, and hasn't gotten attention
since I can last remember, and I have good memory! The issues below all
have SCRs.

1- variables show red when the variable is created in another jsp and
the jsp where the variable is used is being 'included'. This used to
work in 3.0.5. Can we please fix soon?

2- Pasting code in HTML and JSP screws up the whole layout, even if the
layout copied was clean.

3- JSP tag opening and closing, and tag error location are not done
properly.

4- Color coding is off, commented out java scriptlets still show like
live highlighted code.

5- We used to be able to optimize imports if I remember correctly. That
doesn't do anything anymore.

6- The refactoring menu was supposed to be turned off when in a JSP
page, it's not.

7- Debugging is in the dumpster.

And these are my issues alone, I am SURE there are other people with
more issues they've submitted that have gotten NO attention at all! I
was told a while back that the person taking care of XML and JSP
was/were on vacation. They can't still be there; Can they?

Please please someone PLEASE devote just 1 week to this and get it all
done! at the speed you guys work, I don't see how this could all take a
week to fix! PLEASE!

Thanks
R

35 comments
Comment actions Permalink

Rayz wrote:

+100

Here is an attached image of something REALLY basic that should be working.

The page has an include with all the Import statements in it, so they
can be shared across many JSPs. yet look at how many Classes show up in
red and get a suggestion to add the import!

This is the state JSP is in, and this is just the top of the heap, it's
not even going deep in the issues.

Yet here we are with a pretty scrolling, and adding refactoring feature
after refactoring feature, tweaking the UI like there's no tomorrow,
adding gimicks here and there.

I used to be able to participate a lot more in the growth and direction
of the product, but my work is in web apps, jsp, servlets etc... not in
gui, generics or aspects. So I wish that I could produce more info, and
I wish I could produce more bugs and report them, but when the basics
are not getting fixed it's getting pretty discouraging.

Still, IDEA is better than anything else, even with this embarrasment we
call JSP/HTML/XML support... sigh...

Thanks
R



Attachment(s):
jsp-problems.JPG
0
Comment actions Permalink

Sorry one more note about the image:

Note how the include is in green? So my imports should work.

Also since I do have this setup as a webapp, notice how the other
imports are in red? The dir is correct, it works in 3.0.5.

R

0
Comment actions Permalink

I'm in the same boat mate .....

It doesn't recognise imported classes and it doesn't recognise tag libraries or file inclusions.

Doesn't recognise much of anything really.

0
Comment actions Permalink

And according to Aurora page:

"Ctrl-B on JSP custom tags navigates to tag definition"

is working!

Which is kind of like picking out a nice shower curtain, before you've built your bathroom ....

0
Comment actions Permalink

And even with everything broken, I would still edit JSP in IDEA.......
except that it is ridiculously anti-performant (eg type char in to page --
watch CPU go to 100% for 10 secs during which time IDE stops responding).

I can't take the punishment anymore.

"Robert S. Sfeir" <no_mail@jetbrains.com> wrote in message
news:bm6ec5$mj2$1@is.intellij.net...

JetBrainers, JSP is in a decrepid state, and hasn't gotten attention
since I can last remember, and I have good memory! The issues below all
have SCRs.

>

1- variables show red when the variable is created in another jsp and
the jsp where the variable is used is being 'included'. This used to
work in 3.0.5. Can we please fix soon?

>

2- Pasting code in HTML and JSP screws up the whole layout, even if the
layout copied was clean.

>

3- JSP tag opening and closing, and tag error location are not done
properly.

>

4- Color coding is off, commented out java scriptlets still show like
live highlighted code.

>

5- We used to be able to optimize imports if I remember correctly. That
doesn't do anything anymore.

>

6- The refactoring menu was supposed to be turned off when in a JSP
page, it's not.

>

7- Debugging is in the dumpster.

>

And these are my issues alone, I am SURE there are other people with
more issues they've submitted that have gotten NO attention at all! I
was told a while back that the person taking care of XML and JSP
was/were on vacation. They can't still be there; Can they?

>

Please please someone PLEASE devote just 1 week to this and get it all
done! at the speed you guys work, I don't see how this could all take a
week to fix! PLEASE!

>

Thanks
R

>


0
Comment actions Permalink

I'd be mostly interested in IDEA finally supporting JSP2.0 & EL - it's out due this quarter, so people will want to use it extensively. Currently webapp-support is completely broken as soon as your web.xml is using Servlet2.4 XSD..

0
Comment actions Permalink

Yann Cebron wrote:

I'd be mostly interested in IDEA finally supporting JSP2.0 & EL - it's out due this quarter, so people will want to use it extensively. Currently webapp-support is completely broken as soon as your web.xml is using Servlet2.4 XSD..

Yeah while I would like to see that, I'd be satisfied with a working JSP
architecture, and then they can add 2.0 support and everything else in
4.01 or what ever next build will also have Aspects.

What ever it is, I really need some help from the JetBrainers, or
JetBrains Project managers to push this to the top of the list. I've
been taking the pain with others, but it's becoming unbarable. So I use
3.0.5, but that is pointless most of the time since I don't get to
report the bugs which exist in 9xx builds... it's the chicken and the
egg thing. Do you use 3.x and not complain, or do you use 9xx series
and keep raising a stink so things get fixed.

R

0
Comment actions Permalink

Have just done a quick test, and the imports seem to work properly if the
name of the included file ends with one of the extensions defined for JSP
files (IDE Settings > File Types). So I guess the workaround is to either
rename your include files to give them the necessary extension, or to add
".inc" to the list of JSP file extensions.

You are right about JSP support being flaky though. I get
NullPointerExceptions etc. quite frequently while I'm using it. Although I
must admit I haven't been taking the time to submit bug reports for it, so
I'm as much to blame as anyone for allowing it to continue in this state.
Still, it definitely needs some work. Time to get busy submitting those
SCRs, I guess.

Vil.


Robert S. Sfeir wrote:

Here is an attached image of something REALLY basic that should be working.

The page has an include with all the Import statements in it, so they
can be shared across many JSPs. yet look at how many Classes show up in
red and get a suggestion to add the import!

--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

0
Comment actions Permalink

If you don't like the EAP I suggest you stop complaining and use 3.0. First people complained about stability, then JSP, and there's been a lot more complaining about other things in the EAP. IntelliJ is giving you a development version of a several hundred dollar IDE for free so you can test it, and when they want you to test the JSP features you think are broken, they will fix them. I don't think you are in any position to tell them what to do.

0
Comment actions Permalink

Thanks for the workaround, it helps for sure. I don't know why I didn't
think of it, too much to do maybe. This sure helps, but if a file is
included in a jsp page, IDEA ought to assume that there COULD be JSP
code in it and see if there are tags. If not just move on.

R

Vilya Harvey wrote:

Have just done a quick test, and the imports seem to work properly if
the name of the included file ends with one of the extensions defined
for JSP files (IDE Settings > File Types). So I guess the workaround is
to either rename your include files to give them the necessary
extension, or to add ".inc" to the list of JSP file extensions.

You are right about JSP support being flaky though. I get
NullPointerExceptions etc. quite frequently while I'm using it. Although
I must admit I haven't been taking the time to submit bug reports for
it, so I'm as much to blame as anyone for allowing it to continue in
this state. Still, it definitely needs some work. Time to get busy
submitting those SCRs, I guess.

Vil.


Robert S. Sfeir wrote:

>> Here is an attached image of something REALLY basic that should be
>> working.
>>
>> The page has an include with all the Import statements in it, so they
>> can be shared across many JSPs. yet look at how many Classes show up
>> in red and get a suggestion to add the import!

0
Comment actions Permalink

I would also like to see some more focus on JSP development with Aurora.
About 30% of my total work is with JSP pages and there have been numerous
issues with editing JSPs. I understand its still beta but I just hope that
JSPs get some attention before this goes final.

--Grant

"Robert S. Sfeir" <no_mail@jetbrains.com> wrote in message
news:bm6ec5$mj2$1@is.intellij.net...

JetBrainers, JSP is in a decrepid state, and hasn't gotten attention
since I can last remember, and I have good memory! The issues below all
have SCRs.

>

1- variables show red when the variable is created in another jsp and
the jsp where the variable is used is being 'included'. This used to
work in 3.0.5. Can we please fix soon?

>

2- Pasting code in HTML and JSP screws up the whole layout, even if the
layout copied was clean.

>

3- JSP tag opening and closing, and tag error location are not done
properly.

>

4- Color coding is off, commented out java scriptlets still show like
live highlighted code.

>

5- We used to be able to optimize imports if I remember correctly. That
doesn't do anything anymore.

>

6- The refactoring menu was supposed to be turned off when in a JSP
page, it's not.

>

7- Debugging is in the dumpster.

>

And these are my issues alone, I am SURE there are other people with
more issues they've submitted that have gotten NO attention at all! I
was told a while back that the person taking care of XML and JSP
was/were on vacation. They can't still be there; Can they?

>

Please please someone PLEASE devote just 1 week to this and get it all
done! at the speed you guys work, I don't see how this could all take a
week to fix! PLEASE!

>

Thanks
R

>


0
Comment actions Permalink

Keith Lea wrote:

If you don't like the EAP I suggest you stop complaining and use 3.0. First people complained about stability, then JSP, and there's been a lot more complaining about other things in the EAP. IntelliJ is giving you a development version of a several hundred dollar IDE for free so you can test it, and when they want you to test the JSP features you think are broken, they will fix them. I don't think you are in any position to tell them what to do.

hehe ok. what ever, read my other posts... I'm not complaining, I would
just like them to bring it up higher since it's affecting a lot of people.

take a chill pill. I'm not biting on more flames.

R

0
Comment actions Permalink

"If you don't like the EAP I suggest you stop complaining and use 3.0."

What an absurd statement. This is akin to the line "If you don't like this country, then get the hell out!" The answer to both statements, of course, is to ignore the jibe and CONTINUE to complain -- after all, that's the only way to make things better.

0
Comment actions Permalink

I think complaining about free services is definitely not the only way to make things better. There are many ways for you to help IDEA improve. Aside from that, do you think the IDEA developers don't know that JSP features don't work? Do you think they did it on purpose? Do you think they aren't working hard on the EAP to fix these problems? Do you think that if they wanted more JSP feedback, they would fix JSP so you could use it and file bugs on it?

I'm sick of hearing people complaining on these forums, and I think we owe more to the developers than to complain about the quality of the EAP. The EAP isn't a country, and you don't have family, friends, and a job that you would have to leave behind if you went back to 3.0.5. IntelliJ is developing a software product, and they kindly (unlike most developers) release it so we can test the new features. The EAP isn't a right, and I think such pointless whining is treating it as such.

0
Comment actions Permalink

You condescend to call it "whining" but I believe complaining has a useful effect. There's no reason to get fascist on us and demand conformity and silence. If I don't like something I'm going damn well complain. And if others don't like something, I hope they complain too. Complaints are discourse to IntelliJ. It's never personal, and it's often helpful to promote dialog with the users. How can that be interpreted as anything other than beneficial for IntelliJ and us all?

0
Comment actions Permalink

I believe that an occasional 'wake-up call' should be acceptable if some people feel that a certain issue is not taken care of. Besides, the goal of EAP is giving feedback about what doesn't work (ie. complaining). If you can't stand that, perhaps you shouldn't visit this forum (or skip the posts that anger you).

That said, I do believe that complaints should be civil. I've seen some unacceptable complaints before, but I consider the complaint that started this thread to be within the limits (although it could use a little less SHOUTING and a bit more consideration for the JetBrainers).

-- Make love, not war.

0
Comment actions Permalink

Kirk Woll wrote:

You condescend to call it "whining" but I believe complaining has a useful effect. There's no reason to get fascist on us and demand conformity and silence. If I don't like something I'm going damn well complain. And if others don't like something, I hope they complain too. Complaints are discourse to IntelliJ. It's never personal, and it's often helpful to promote dialog with the users. How can that be interpreted as anything other than beneficial for IntelliJ and us all?

Thanks, and I was not whining, I was only asking them to move it higher
on the list.

I didn't say I would stop using it. I didn't say I wasn't using 3.0.x.
I didn't say the stability sucks. I just said with everything else
being worked on, I felt that JSP issues were being ignored, and was
begging for a Program Manager to move it up. Get of the rant Keith. If
there are more JSP issues that need to be brought to their attentions
which you know of, list them. If you don't, get back to finding the
bugs that matter to you.

I'm going to harp on the bugs that matter to me because when the next
rev of idea is released, and these things aren't quite working right, I
will only blame myself for it because I didn't push the issue and bring
it up to their attention.

To answer your question about "Don't you think they know"... No they
don't always know everything. As a matter of fact I just submitted a
JSR 45 support feature request with Tomcat 5 support, and that wasn't on
the list originally and was told it was added and that bug is now open.
Had I followed your advice we would have had a chance of not having
this kind of support, and hence more frustration.

Park it and be productive, which is what I was trying to do in the first
place.

R

0
Comment actions Permalink

Wouter Zelle wrote:

I believe that an occasional 'wake-up call' should be acceptable if some people feel that a certain issue is not taken care of. Besides, the goal of EAP is giving feedback about what doesn't work (ie. complaining). If you can't stand that, perhaps you shouldn't visit this forum (or skip the posts that anger you).

That said, I do believe that complaints should be civil. I've seen some unacceptable complaints before, but I consider the complaint that started this thread to be within the limits (although it could use a little less SHOUTING and a bit more consideration for the JetBrainers).

-- Make love, not war.

Hey it wasn't shouting it was begging out loud :)

R

0
Comment actions Permalink

My advice is to stop posting complaints on the forums when the bugs are already in the database. I think everyone should post tracker requests/bugs for anything they find and can think of.

0
Comment actions Permalink

It would be nice if there were a new consolidation-type SCR in ITN where
all these bugs could be seen as a bundle so we could have a full view of
the extent of JSP problems (or other sets of related issues). I added an
ITN feature request for such functionality:
http://www.intellij.net/tracker/itn/viewSCR?publicId=655

Jon

0
Comment actions Permalink

Actually, complaining and yelling loudly does work. How else can you explain aspectJ support?

0
Comment actions Permalink

On Sat, 11 Oct 2003 22:09:32 +0000, Hani Suleiman wrote:

Actually, complaining and yelling loudly does work. How else can you
explain aspectJ support?


Same way we can explain AspectJ support -REMOVED- from IntelliJ 4.0.

In some ways, I think its a shame to have it removed, after the work
that's been done to put it in their.

--
"It's all in the heat of the moment, it's all in the pain..." Devy.
Mark Derricutt @ mark@talios.com @ talios.blog-city.com

0
Comment actions Permalink

I presume you are referring to this post from Dmitry Lomov?

+after some consideration we decided not to announce AspectJ support as an official feature of Aurora release of IDEA.

The reason for this decision is time constraints: currently we are implementing support for two novel Java language features - AspectJ and Generics, and we figure that we cannot perfect both to meet our usual quality standards (and your high expectations) and release soon at the same+

So how do you figure this means that they dropped it because we complained?

0
Comment actions Permalink

Kirk Woll wrote:

I presume you are referring to this post from Dmitry Lomov?

+after some consideration we decided not to announce AspectJ support as an official feature of Aurora release of IDEA.

The reason for this decision is time constraints: currently we are implementing support for two novel Java language features - AspectJ and Generics, and we figure that we cannot perfect both to meet our usual quality standards (and your high expectations) and release soon at the same+

So how do you figure this means that they dropped it because we complained?

Hey no hijacking my thread! :) Start your own! :)

R

0
Comment actions Permalink

On Sun, 12 Oct 2003 01:52:46 +0000, Kirk Woll wrote:

So how do you figure this means that they dropped it because we
complained?


No figuring really, just wild speculation. My logic flows that if
everyone was raving about AspectJ and no-one complaining, then it quite
likely would have been included.

--
"It's all in the heat of the moment, it's all in the pain..." Devy.
Mark Derricutt @ mark@talios.com @ talios.blog-city.com

0
Comment actions Permalink

I for one, think the JSP support has been getting better with Aurora. I
remember when just opening a JSP would send errors scrolling through the
window. It is also better and recognizing that a variable has been declared
in an enclosing JSP. Still not perfect, but definately better. JSTL
support is a little better. At least it knows what the tag attributes are.

However, with that said ....

My shop is a JBuilder/IntelliJ shop. Everyone was offered JBuilder Ent.
The informed among us (the website developers) all fought and won the right
to have IntelliJ. So, needless to say, I am on pins and needles waiting for
JSP 2.0 support in IntelliJ.




"Robert S. Sfeir" <no_mail@jetbrains.com> wrote in message
news:bm6ec5$mj2$1@is.intellij.net...

JetBrainers, JSP is in a decrepid state, and hasn't gotten attention
since I can last remember, and I have good memory! The issues below all
have SCRs.

>

1- variables show red when the variable is created in another jsp and
the jsp where the variable is used is being 'included'. This used to
work in 3.0.5. Can we please fix soon?

>

2- Pasting code in HTML and JSP screws up the whole layout, even if the
layout copied was clean.

>

3- JSP tag opening and closing, and tag error location are not done
properly.

>

4- Color coding is off, commented out java scriptlets still show like
live highlighted code.

>

5- We used to be able to optimize imports if I remember correctly. That
doesn't do anything anymore.

>

6- The refactoring menu was supposed to be turned off when in a JSP
page, it's not.

>

7- Debugging is in the dumpster.

>

And these are my issues alone, I am SURE there are other people with
more issues they've submitted that have gotten NO attention at all! I
was told a while back that the person taking care of XML and JSP
was/were on vacation. They can't still be there; Can they?

>

Please please someone PLEASE devote just 1 week to this and get it all
done! at the speed you guys work, I don't see how this could all take a
week to fix! PLEASE!

>

Thanks
R

>


0
Comment actions Permalink

I for one, think the JSP support has been getting better with Aurora.

Mmm .. can't say I've noticed this, but YMMV.

I remember when just opening a JSP would send errors scrolling through the window.

I still get loads of exceptions while typing.

It is also better and recognizing that a variable has been declared

At least it knows what the tag attributes are.

What version are you using? I'm using Struts, and it has no idea about the Struts tags, even though it knows where the tlds are ...

0
Comment actions Permalink

Rayz wrote:

I for one, think the JSP support has been getting better with Aurora.

Mmm .. can't say I've noticed this, but YMMV.

I remember when just opening a JSP would send errors scrolling through the window.

I still get loads of exceptions while typing.

It is also better and recognizing that a variable has been declared

At least it knows what the tag attributes are.

What version are you using? I'm using Struts, and it has no idea about the Struts tags, even though it knows where the tlds are ...

Well it knows where the struts tags are in my case, but as soon as I
start typing them, I get exceptions, or if I don't finish typing the tag
I get an exception and I can't get rid of the exception until I quit
idea, remove the tag in a text editor, then go back in.

I've been using 3.0.5 a lot more since the end of last week, and the
difference between 3.0.5 JSP and 9xx series is tremendous. It's
actually a joy to use JSP in 3.0.5, it's just not usable in 9xx. The
simple joy of being able paste in JSP or HTML and not having it screw up
the alignment alone releaves stress. I'm kind of anal when it comes to
properly formatted code, so when pasting in JSP or HTML that just gets
completely left justified, is very frustrating and very time consuming
to clean up.

We are talking EAP here, so I don't expect it to work at all, I'd be
happy with it if it even worked a bit. My original post just wished
that those issues moved up a bit to the top of the cream so it does
become usable in the EAP, and we can test further issues. Without those
issues working at this point, I am unable to help testing 9xx series,
since I can't use it for production work. I can certainly tinker with
it when I'm watching tv, but that's really not testing functionality in
a real use case scenario.

Yes perhaps there have been improvements, but they've been burried by
the overwhelming issues that still remain.

R

0
Comment actions Permalink

FWIW, I'm using #915, and I generally don't have any issues with the JSP capabilities. I do Struts a lot, and I get ctrl-space completion for tag names, attributes, etc. I just set up Aurora for an existing project, and didn't have to do anything to get it to recognise the tlds or anything. I can Ctrl-B to the definition, etc etc. Can't reformat or optimise imports though.
Every now and then, it does get a little stuck on the continual-popup error box - usually when trying parse an imcomplete statement. That's a bt annoying, but having tried jbuilder and eclipse/solareclipse (numerous times), I know which I prefer!
I did notice a lot of complaints after 915 was released, which is why I've held off upgrading for the time being...

cheers,
Reg

0

Please sign in to leave a comment.