jsp2 again

Hi,

thanks for the jsp2 taglib problem solution but I still got 2 problems
within my jsp2 files.

1) <%@ taglib tagdir="/WEB-INF/tags" prefix="stags" %>

.tag files aren't supported?

2.) <jsp:attribute ...> within a Tag is marked red.

regards,
/thomas

23 comments

There is apparently no planned support for JSP2.0, I asked about that months ago with no reply.. too bad, the first and only JSP editor I want to use doesn't support the latest published standards :(

0

Yann Cebron wrote:

There is apparently no planned support for JSP2.0, I asked about that months ago with no reply.. too bad, the first and only JSP editor I want to use doesn't support the latest published standards :(

Says who? Have you guys checked the J2EE forum?

JSP2 is in fact working last I checked.


R

0

I'm pretty sure JSP tagfiles (*.tag) are not supported, and that's one of the biggest improvements in JSP2.0.

0

Yann Cebron wrote:

I'm pretty sure JSP tagfiles (*.tag) are not supported, and that's one of the biggest improvements in JSP2.0.

"Starting from 1127 we'll search TLDs in all web module libraries. But
please make sure that you properly configure libraries for deployment.

By the way we've discussed the default setting for module libraries.
Whether to include them into deployment. Because we do not have enough
statistics we decided to ask EAP. What do you do more often include or
exclude libraries from deployment?

Thanks,
IK "

You should try it again after 1129, they've fixed an issue which should
resolve your problem.

R

0

We exclude, but that is because we are a non-web shop and everything is
geared towards the applications instead. I like having the option.

--
Norris Shelton
Sun Certified Java Programmer


"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:bvbnmq$elv$1@is.intellij.net...

Yann Cebron wrote:

>

I'm pretty sure JSP tagfiles (*.tag) are not supported, and that's one

of the biggest improvements in JSP2.0.

"Starting from 1127 we'll search TLDs in all web module libraries. But
please make sure that you properly configure libraries for deployment.

>

By the way we've discussed the default setting for module libraries.
Whether to include them into deployment. Because we do not have enough
statistics we decided to ask EAP. What do you do more often include or
exclude libraries from deployment?

>

Thanks,
IK "

>

You should try it again after 1129, they've fixed an issue which should
resolve your problem.

>

R



0

Yann Cebron wrote:

There is apparently no planned support for JSP2.0, I asked about that months ago with no reply.. too bad, the first and only JSP editor I want to use doesn't support the latest published standards :(

2.0 requires to create a new framework which is not a good idea close to
release.

IK

--
Igor Kuralenok
Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0

Robert S. Sfeir wrote:

Yann Cebron wrote:

>> I'm pretty sure JSP tagfiles (*.tag) are not supported, and that's one
>> of the biggest improvements in JSP2.0.


"Starting from 1127 we'll search TLDs in all web module libraries. But
please make sure that you properly configure libraries for deployment.

By the way we've discussed the default setting for module libraries.
Whether to include them into deployment. Because we do not have enough
statistics we decided to ask EAP. What do you do more often include or
exclude libraries from deployment?

Thanks,
IK "

You should try it again after 1129, they've fixed an issue which should
resolve your problem.


I was talking about tld files. The problem here is to support .tag files
which is new in 2.0 and are not supported in 4.0 (with jspx and other
stuff). I hope some of these file types will be supported in 4.1.

IK

--
Igor Kuralenok
Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0

Igor Kuralenok (JetBrains) wrote:

Yann Cebron wrote:

>> There is apparently no planned support for JSP2.0, I asked about that
>> months ago with no reply.. too bad, the first and only JSP editor I
>> want to use doesn't support the latest published standards :(


2.0 requires to create a new framework which is not a good idea close to
release.


Please make sure this makes it to 4.1 feature list. It's a huge feature
that is needed since more and more people are using that.

Thanks
R

0

Robert S. Sfeir wrote:

Igor Kuralenok (JetBrains) wrote:

>> Yann Cebron wrote:
>>
>>> There is apparently no planned support for JSP2.0, I asked about that
>>> months ago with no reply.. too bad, the first and only JSP editor I
>>> want to use doesn't support the latest published standards :(
>>
>>
>> 2.0 requires to create a new framework which is not a good idea close
>> to release.


Please make sure this makes it to 4.1 feature list. It's a huge feature
that is needed since more and more people are using that.

As far as I know we don't plan to support at least jspx in 4.1 because
of time restrictions.

IK

--
Igor Kuralenok
Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0

Igor Kuralenok (JetBrains) wrote:

>

As far as I know we don't plan to support at least
jspx in 4.1 because
of time restrictions.


I can't believe this. I recently bought a personal license and I am very unhappy with this decesion to say the least.

Michael

0

Igor Kuralenok (JetBrains) wrote:

Robert S. Sfeir wrote:

>> Igor Kuralenok (JetBrains) wrote:
>>
>>> Yann Cebron wrote:
>>>
>>>> There is apparently no planned support for JSP2.0, I asked about
>>>> that months ago with no reply.. too bad, the first and only JSP
>>>> editor I want to use doesn't support the latest published standards :(
>>>
>>>
>>>
>>> 2.0 requires to create a new framework which is not a good idea close
>>> to release.
>>
>>
>>
>> Please make sure this makes it to 4.1 feature list. It's a huge
>> feature that is needed since more and more people are using that.


As far as I know we don't plan to support at least jspx in 4.1 because
of time restrictions.

IK


My concern is that once again AspectJ and Generics will take presedence
over JSP, when clearly the JSP community, and competition, is more
important. I'm not negating aspects, but gosh, it seems like JSP is a
little further ahead in the cue.

Further, HTML support needs to be improved, and refactorings need to be
introduced to JSP. No one does JSP refactoring, and it's IDEA's forte
to do refactorings, and I really feel this would put IDEA once again in
a position of envy by all other IDEs.

The issue, I think, is that new framework is needed to support all this,
I've heard that comment many times, but I think that it's time to bite
the bullet, before the bullet bites you, and add that framework and make
things work right for all J2EE aspects (no pun intended). The current
version is excellent, but it's excellent for the work done. If we were
to take a look at it in comparison to other IDEs, I'd say you're only
75% there. To demonstrate I will list off hand the things that others
do/ don't do, which you should do:

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the support (not via
user plugin, but yours, including Resin, Orion, and Jboss to start with)
4- JSF
5- Struts specific support (workflow, Struts file templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page cleanup, complete
code completion, page validation etc...)
7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it
9- Hot deployment, meaning when I change a jsp page, just deploy it
without asking me to hit ctrl+F9.

This is just to name a few things off the top of my head which would
make IDEA a more complete J2EE IDE. I'm sure others will have more to add.

Thanks
R

0

For me personally - I'd definitely like ALL of the features mentioned by
Robert below!!!


"Robert S. Sfeir" <robert@codepuccino.com> schrieb im Newsbeitrag
news:bvo7ra$6pd$1@is.intellij.net...

Igor Kuralenok (JetBrains) wrote:

Robert S. Sfeir wrote:

>
>> Igor Kuralenok (JetBrains) wrote:
>>
>>> Yann Cebron wrote:
>>>
>>>> There is apparently no planned support for JSP2.0, I asked about
>>>> that months ago with no reply.. too bad, the first and only JSP
>>>> editor I want to use doesn't support the latest published standards>>>
>>>
>>>
>>> 2.0 requires to create a new framework which is not a good idea close
>>> to release.
>>
>>
>>
>> Please make sure this makes it to 4.1 feature list. It's a huge
>> feature that is needed since more and more people are using that.
>

As far as I know we don't plan to support at least jspx in 4.1 because
of time restrictions.

>

IK

>

>

My concern is that once again AspectJ and Generics will take presedence
over JSP, when clearly the JSP community, and competition, is more
important. I'm not negating aspects, but gosh, it seems like JSP is a
little further ahead in the cue.

>

Further, HTML support needs to be improved, and refactorings need to be
introduced to JSP. No one does JSP refactoring, and it's IDEA's forte
to do refactorings, and I really feel this would put IDEA once again in
a position of envy by all other IDEs.

>

The issue, I think, is that new framework is needed to support all this,
I've heard that comment many times, but I think that it's time to bite
the bullet, before the bullet bites you, and add that framework and make
things work right for all J2EE aspects (no pun intended). The current
version is excellent, but it's excellent for the work done. If we were
to take a look at it in comparison to other IDEs, I'd say you're only
75% there. To demonstrate I will list off hand the things that others
do/ don't do, which you should do:

>

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the support (not via
user plugin, but yours, including Resin, Orion, and Jboss to start with)
4- JSF
5- Struts specific support (workflow, Struts file templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page cleanup, complete
code completion, page validation etc...)
7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it
9- Hot deployment, meaning when I change a jsp page, just deploy it
without asking me to hit ctrl+F9.

>

This is just to name a few things off the top of my head which would
make IDEA a more complete J2EE IDE. I'm sure others will have more to

add.
>

Thanks
R



0

I would like them all, also. However, JSP 2.0 is here now, JDK 1.5 is still
a ways off. First things first.

--
Norris Shelton
Sun Certified Java Programmer


"RK" <wendrador@web.de> wrote in message
news:bvo9tt$lo2$1@is.intellij.net...

For me personally - I'd definitely like ALL of the features mentioned by
Robert below!!!

>
>

"Robert S. Sfeir" <robert@codepuccino.com> schrieb im Newsbeitrag
news:bvo7ra$6pd$1@is.intellij.net...

Igor Kuralenok (JetBrains) wrote:

Robert S. Sfeir wrote:

>
>> Igor Kuralenok (JetBrains) wrote:
>>
>>> Yann Cebron wrote:
>>>
>>>> There is apparently no planned support for JSP2.0, I asked about
>>>> that months ago with no reply.. too bad, the first and only JSP
>>>> editor I want to use doesn't support the latest published standards

:(

>>>
>>>
>>>
>>> 2.0 requires to create a new framework which is not a good idea

close

>>> to release.
>>
>>
>>
>> Please make sure this makes it to 4.1 feature list. It's a huge
>> feature that is needed since more and more people are using that.
>

As far as I know we don't plan to support at least jspx in 4.1 because
of time restrictions.

>

IK

>

>

My concern is that once again AspectJ and Generics will take presedence
over JSP, when clearly the JSP community, and competition, is more
important. I'm not negating aspects, but gosh, it seems like JSP is a
little further ahead in the cue.

>

Further, HTML support needs to be improved, and refactorings need to be
introduced to JSP. No one does JSP refactoring, and it's IDEA's forte
to do refactorings, and I really feel this would put IDEA once again in
a position of envy by all other IDEs.

>

The issue, I think, is that new framework is needed to support all this,
I've heard that comment many times, but I think that it's time to bite
the bullet, before the bullet bites you, and add that framework and make
things work right for all J2EE aspects (no pun intended). The current
version is excellent, but it's excellent for the work done. If we were
to take a look at it in comparison to other IDEs, I'd say you're only
75% there. To demonstrate I will list off hand the things that others
do/ don't do, which you should do:

>

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the support (not via
user plugin, but yours, including Resin, Orion, and Jboss to start with)
4- JSF
5- Struts specific support (workflow, Struts file templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page cleanup, complete
code completion, page validation etc...)
7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it
9- Hot deployment, meaning when I change a jsp page, just deploy it
without asking me to hit ctrl+F9.

>

This is just to name a few things off the top of my head which would
make IDEA a more complete J2EE IDE. I'm sure others will have more to

add.
>

Thanks
R

>
>


0

Norris Shelton wrote:

I would like them all, also. However, JSP 2.0 is here now, JDK 1.5 is still
a ways off. First things first.


None of my features are JDK 1.5 dependant. They're base J2EE Impl I think.

R

0

Just to vote too in general for the great importance of good html and jsp support, greather than more exotic features for AspectJ and Generics. Html and jsps solutions are just too practical !

0

R,

I think that you are right on the money with your list of requests.
Are there feature requests in tracker for all of them?
They would get my votes.

Tim


"Robert S. Sfeir" <robert@codepuccino.com> wrote in message
news:bvo7ra$6pd$1@is.intellij.net...
>

My concern is that once again AspectJ and Generics will take presedence
over JSP, when clearly the JSP community, and competition, is more
important. I'm not negating aspects, but gosh, it seems like JSP is a
little further ahead in the cue.

>

Further, HTML support needs to be improved, and refactorings need to be
introduced to JSP. No one does JSP refactoring, and it's IDEA's forte
to do refactorings, and I really feel this would put IDEA once again in
a position of envy by all other IDEs.

>

The issue, I think, is that new framework is needed to support all this,
I've heard that comment many times, but I think that it's time to bite
the bullet, before the bullet bites you, and add that framework and make
things work right for all J2EE aspects (no pun intended). The current
version is excellent, but it's excellent for the work done. If we were
to take a look at it in comparison to other IDEs, I'd say you're only
75% there. To demonstrate I will list off hand the things that others
do/ don't do, which you should do:

>

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the support (not via
user plugin, but yours, including Resin, Orion, and Jboss to start with)
4- JSF
5- Struts specific support (workflow, Struts file templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page cleanup, complete
code completion, page validation etc...)
7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it
9- Hot deployment, meaning when I change a jsp page, just deploy it
without asking me to hit ctrl+F9.

>

This is just to name a few things off the top of my head which would
make IDEA a more complete J2EE IDE. I'm sure others will have more to

add.
>

Thanks
R



0

Tim Haley wrote:

R,

I think that you are right on the money with your list of requests.
Are there feature requests in tracker for all of them?
They would get my votes.

Tim


Yup, all over the place. This is not new :) We've just been waiting
because generally the excuse is that the framework is not in place to do
this kind of stuff. My feeling is: put this framework in place, delay
AspectJ, and I feel this needs to happen in the next dot release, not in
5.0 or 4.2 (which would be 6 months from now, if 4.1 is a 2-3 months
cycle). 6 Months from now, Eclipse would have caught up, and IDEA is
already behind JBuilder, JDeveloper(10g), CodeGuide, and MyEclipse when
it comes to most if not all of these features. (note: I am mentioning
features, not price, or ease of use or anything, just J2EE support features)

I think we waited for refactoring of the whole IDE framework to allow
IDEA to grow, there are clearly benefits, I think our wait would have
been in vain however, if a new J2EE framework can't be added to current
rebuilt IDE framework.

I'm confident JB is reading and considering our opinion, whether we can
sway their process in our direction or not remains to be seen.

R

P.S. I hope that JB doesn't torpedo, or is not delaying, this J2EE
framework in preference of Fabrique. That would be a real shame.

0

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the
support (not via
user plugin, but yours, including Resin, Orion, and
Jboss to start with)
4- JSF
5- Struts specific support (workflow, Struts file
templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page
cleanup, complete
code completion, page validation etc...)
7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it
9- Hot deployment, meaning when I change a jsp page,
just deploy it
without asking me to hit ctrl+F9.


Oh man, these things are all extremely important to me. If I had to choose just one feature out of those 9 though, I would definitely choose #1. JSP2 support. Including .tag files, and EL support. We NEED these things, as we are planning on moving to Tomcat5 in the near future and we will be taking advantage of these new features. It will make things VERY tough if IDEA doesn't support these features.

Do any other IDEs support these features currently?

0

Robert S. Sfeir wrote:


My concern is that once again AspectJ and Generics will take presedence
over JSP, when clearly the JSP community, and competition, is more
important. I'm not negating aspects, but gosh, it seems like JSP is a
little further ahead in the cue.

Further, HTML support needs to be improved, and refactorings need to be
introduced to JSP. No one does JSP refactoring, and it's IDEA's forte
to do refactorings, and I really feel this would put IDEA once again in
a position of envy by all other IDEs.


Agree, it would be great to have complete JSP 2.0 / EL refactoring support.


The issue, I think, is that new framework is needed to support all this,
I've heard that comment many times, but I think that it's time to bite
the bullet, before the bullet bites you, and add that framework and make
things work right for all J2EE aspects (no pun intended). The current
version is excellent, but it's excellent for the work done. If we were
to take a look at it in comparison to other IDEs, I'd say you're only
75% there. To demonstrate I will list off hand the things that others
do/ don't do, which you should do:

1- JSP 2
2- JSP refactoring
3- More App Server Support to the full extent of the support (not via
user plugin, but yours, including Resin, Orion, and Jboss to start with)
4- JSF


I'm not sure about this one. While the spec should be done soon, it's
not final at this point. I'd prefer work being done based on existing,
finalized standards (eg. Servlet 2.4/JSP 2.0) rather than the hottest,
newest thing.

(Can you point to any beta tools out there that really make IDE JSF
support shine?)

Apart from that, there have been some posts from JB staff indicating
that the new 'Fabrique' product will be pushed in this space.

5- Struts specific support (workflow, Struts file templates and project
templates, Validation of actions etc...)
6- HTML support (yes you do html, but we need page cleanup, complete
code completion, page validation etc...)


Perhaps more generic schema-bound XML editor support could facilitate
jspx and xhtml code completion and validation.

I currently use Eclipse for XML editing. There are two plugings that
provide RELAX NG/XSD validation and completion. (xmlbuddy and oxygen)
There are quality schemas for most of the xml formats I use: xslt,
xhtml, relaxng and the j2ee xml configuration goo.

7- CSS and JavaScript support and highlighting
8- Integrate the SQL Plugin and improve it


I don't see the need for this. There is a plethora of existing tools
that do the job, from sqlplus to Query Analyzer. Why does this belong in
the IDE? Could you explain?

9- Hot deployment, meaning when I change a jsp page, just deploy it
without asking me to hit ctrl+F9.

This is just to name a few things off the top of my head which would
make IDEA a more complete J2EE IDE. I'm sure others will have more to add.


Apart from the points mentioned, I agree 100%!

-J2SE 1.5 is rumoured to be released towards the end of this year. We
certainly won't be deploying on J2SE until somewhere 2005.
-> -1 for generics and any other 1.5 lang enchancements.

-While we may use some AOP goo in production apps, it won't be AspectJ.
I think the number of developers using this in production is very small.
-> -1 for aspectj

-The J2EE 1.4 web tier specs (servlet 2.4/jsp 2.0) are a great
improvement. App server support seems to be getting there quickly.
-> +1 for full Servlet 2.4/JSP 2.0 support.

-In my experience, most IBM/Webspere shops standarize on Eclipse/WSAD.
-> +1 for better J2EE integration with the cheaper containers: JBoss, Orion.

Regards,

-tt

0

Taras Tielkes wrote:

>> 1- JSP 2
>> 2- JSP refactoring
>> 3- More App Server Support to the full extent of the support (not via
>> user plugin, but yours, including Resin, Orion, and Jboss to start with)
>> 4- JSF


I'm not sure about this one. While the spec should be done soon, it's
not final at this point. I'd prefer work being done based on existing,
finalized standards (eg. Servlet 2.4/JSP 2.0) rather than the hottest,
newest thing.

(Can you point to any beta tools out there that really make IDE JSF
support shine?)


No, but my point was that if you're going to write the framework, take
all these things in consideration. I didn't ask that ALL these features
be implemented, just what I think is missing to make IDEA at the top of
the food chain again with J2EE. Yes JSF is in beta, but it should stop
them from looking at the spec and making sure that when it's final, they
don't hit yet another snag/excuse for why they can't add the support.


Apart from that, there have been some posts from JB staff indicating
that the new 'Fabrique' product will be pushed in this space.

>> 5- Struts specific support (workflow, Struts file templates and
>> project templates, Validation of actions etc...)
>> 6- HTML support (yes you do html, but we need page cleanup, complete
>> code completion, page validation etc...)


Perhaps more generic schema-bound XML editor support could facilitate
jspx and xhtml code completion and validation.


What ever way they do it, do it and do it right and complete. This
would include code cleanup, which JBuilder, CodeGuide, JDeveloper and
Eclipse all have; Even if in some form of plugin.

>> 7- CSS and JavaScript support and highlighting
>> 8- Integrate the SQL Plugin and improve it


I don't see the need for this. There is a plethora of existing tools
that do the job, from sqlplus to Query Analyzer. Why does this belong in
the IDE? Could you explain?


Because anytime you work with a webapp (be it Struts/Spring or EJB
driven) you need to work with SQL. Having an integrated SQL Plugin
provides completeness to the IDE. Currently you can download the SQL
Plugin, and it's wonderful, but from a less experinced user's point of
view, I think it would be greatly beneficial if IDEA just had that out
of the box... The other reason being... because the other IDEs have
it... not that everything the other IDEs have is a good thing to add,
don't get me wrong.

Apart from the points mentioned, I agree 100%!

-J2SE 1.5 is rumoured to be released towards the end of this year. We
certainly won't be deploying on J2SE until somewhere 2005.
-> -1 for generics and any other 1.5 lang enchancements.


Yup 1.5... lots of niceness, but not more important than this.

-While we may use some AOP goo in production apps, it won't be AspectJ.
I think the number of developers using this in production is very small.
-> -1 for aspectj


yeah -10


-The J2EE 1.4 web tier specs (servlet 2.4/jsp 2.0) are a great
improvement. App server support seems to be getting there quickly.
-> +1 for full Servlet 2.4/JSP 2.0 support.


Ditto, and I would make this a top priority. Write the framework, and
add this support/functionality to it, then start adding the other stuff
with every future dot release.


-In my experience, most IBM/Webspere shops standarize on Eclipse/WSAD.
-> +1 for better J2EE integration with the cheaper containers: JBoss,
Orion.


And Resin please :)

R

0

Just saw this post and wanted to whole heartedly agree. It's certainly a dissapointment that this release while good in parts seems to have lost it's way, the best IDE shouldn't leave me wishing for features in a technology as basic as JSP. AspectJ.. sigh.

0

agreed, I wish they had worked on supporting the latest J2EE standard, but I can live with it I guess.

Now I love 4.0 and in no way can ever imagine going back to 3.0 but to me personally most of the "major" features in this release don't really mean much to me. The wasted aspectj time, even if it is released in 4.1 doesnt impact my everyday work. Ditto on on the GUI tool and Ditto on WebLogic support unfortunately. oh well.

0

Please sign in to leave a comment.