JSP Structure view - HTML View

HTML View shows essentially the page with all jsp-specific tags/constructs
removed.
Being able to show generated HTML text will require executing the jsp page
inside web container, and I think it is just not feasible.

--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Norris Shelton" <nunya@nunya.net> wrote in message
news:dah353$9j4$1@is.intellij.net...

What is the purpose of this? My assumption was that it would show the
HTML that the page would generate. Some pages look like they may be OK,
but I have other pages that display nothing but a div node with a BR node.
Not very useful at the moment.

Unfortunately most JSP's out there are a nightmarish tag soup with very little good'ol HTML in it -- almost everything will be generated by JSP tags or decorated by sitemesh or something similar.

Keep it, thou. In my pages I can at least see the two or three content div's that compose the page ;)

True and too bad. As it is it's not going to provide much value. I
wouldn't recommend spending any more time on it unless the output from
executing the page was going to be used.

Alexey Kudravtsev (JetBrains) wrote:

>HTML View shows essentially the page with all jsp-specific tags/constructs
>removed.
>Being able to show generated HTML text will require executing the jsp page
>inside web container, and I think it is just not feasible.
>

>

In article <42CD3CBB.4060101@nunya.net>,
Norris Shelton <nunya@nunya.net> wrote:

True and too bad. As it is it's not going to provide much value. I

speak for yourself. I don't use scriptlets and I get full value from
jumping around a jsp page quickly.

That said, having page resolution would be a feat, but it would mean
that idea is processing the pages in the background without tomcat, so
it would need to have its own internal container, I don't see how else
this can be done.

R

That said, having page resolution would be a feat, but it would mean
that idea is processing the pages in the background without tomcat, so
it would need to have its own internal container, I don't see how else
this can be done.

By using Tomcat's Jasper Compiller? IMHO such a functionality would be
more proper for a plug-in (if the OpenAPI would allow it).

Ahmed.

Even if IDEA would actually compile and run a JSP page, some (or most) of the output may be dependant on the request state -- how would IDEA guess what's in the request?

Of course, all of this assumes that the JSP is generating HTML, which will not always be the
case.

Even (if even) we get nice looking page finally, what it has in common with
jsp file you edit? Where should we navigate from those tags?

<%
for (int i = 1; i < 5;i++) {
%>
<h<%=i%>>Hello!</h<%=i%>>
<%
}
%>

Isn't it more useful to navigate to <h/> in HTML structure rather have 5
<hn/> tags?

-

Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

In article <dajib2$7h0$1@is.intellij.net>,
Ahmed Mohombe <amohombe@yahoo.com> wrote:

That said, having page resolution would be a feat, but it would mean
that idea is processing the pages in the background without tomcat, so
it would need to have its own internal container, I don't see how else
this can be done.

By using Tomcat's Jasper Compiller? IMHO such a functionality would be
more proper for a plug-in (if the OpenAPI would allow it).

Wait that compiles the page and shoves a butt load of html in method
calls, you need to render the page to show all the elements... or did I
completely miss on this conversation?

R

In article <dajklt$gr9$2@is.intellij.net>,
Tim Haley <ymaraner@yahoo.com> wrote:

Of course, all of this assumes that the JSP is generating HTML, which will
not always be the
case.

Exactly, hence the custom tag problem as well.

R

I don't use scriptlets either. The problem is that a JSP page depends
on state. The editor has no idea what would be in the request and how
the underlying code would respond. The JSP View is very helpful. I
just don't get the value of the HTML View or the Java View. I see
neither of them providing much value to a typical JSP.

Robert S. Sfeir wrote:

>In article <42CD3CBB.4060101@nunya.net>,

Norris Shelton <nunya@nunya.net> wrote:

>

>
>>True and too bad. As it is it's not going to provide much value. I
>>
>>
>
>speak for yourself. I don't use scriptlets and I get full value from
>jumping around a jsp page quickly.
>
>That said, having page resolution would be a feat, but it would mean
>that idea is processing the pages in the background without tomcat, so
>it would need to have its own internal container, I don't see how else
>this can be done.
>
>R

>

well, I do a lot of client side coding and I see added value. (quick jumping to edit h1 tags, jumping to a form tag etc) + it helps me build xpath queries when targetting certain tags when context is bind to parent tag(s).