Home » Language IDEs » ServerTools (WTP) » ibm contrib - jsp document editor (xml-syntax)
| | |
| Re: ibm contrib - jsp document editor (xml-syntax) [message #35896 is a reply to message #34206] |
Sun, 01 August 2004 23:45   |
Eclipse User |
|
|
|
On Thu, 29 Jul 2004 07:26:53 +0000 (UTC), martin <martin.kuhn@gmx.at>
wrote:
> My jsp documents has an extension "jspx".
> Now it seems that the jsp documents are treated as xml. What I have to do
> that the documents treated as jsp content.
>
There's no way to change this though current user interface. And, if you
really like hacking around,
you could change plugin extensions for JSP content type, and even "JSP
Editor", but that won't
"fix" the problem everywhere. One item we have to do for future code is
carry the Eclipse base 'contentType'
for JSP through out more code (e.g. validation, launching, and debugging).
BUT, I'd be interested to understand better why you needed to change file
extension. What was it you were expecting that didn't happen with regular
..jsp extension, but XML syntax used? JSP editor, on a .jsp file, should
detect that the file is in XML syntax if file begins with <?xml and if the
file contains jsp:root tag. Granted, there's bugs, but I'm wondering what
"features of XML" you were looking for that you weren't getting?
Thanks.
|
|
|
| Re: ibm contrib - jsp document editor (xml-syntax) [message #36637 is a reply to message #35896] |
Wed, 04 August 2004 02:46 |
| Eclipse User |
|
|
|
David Williams wrote:
> On Thu, 29 Jul 2004 07:26:53 +0000 (UTC), martin <martin.kuhn@gmx.at>
> wrote:
> > My jsp documents has an extension "jspx".
> > Now it seems that the jsp documents are treated as xml. What I have to do
> > that the documents treated as jsp content.
> >
> There's no way to change this though current user interface. And, if you
> really like hacking around,
> you could change plugin extensions for JSP content type, and even "JSP
> Editor", but that won't
> "fix" the problem everywhere. One item we have to do for future code is
> carry the Eclipse base 'contentType'
> for JSP through out more code (e.g. validation, launching, and debugging).
> BUT, I'd be interested to understand better why you needed to change file
> extension. What was it you were expecting that didn't happen with regular
> ..jsp extension, but XML syntax used? JSP editor, on a .jsp file, should
> detect that the file is in XML syntax if file begins with <?xml and if the
> file contains jsp:root tag. Granted, there's bugs, but I'm wondering what
> "features of XML" you were looking for that you weren't getting?
> Thanks.
According to the JSP Specification Version 2.0:
"JSP documents, that is, JSP pages that are delivered as XML documents, use
the extension .jspx by default."
So I named my documents with extension jspx. I have no other reason.
When I use jsp documents it would really nice to use an editor which knows
about the jsp taglibs I defined in my document and provide help to me
(provide code assist and so on). In my opinion a "plain" xml editor does
not know about taglibs for instance. So I can not see where the magic
should happen.
|
|
|
| Re: ibm contrib - jsp document editor (xml-syntax) [message #36739 is a reply to message #36637] |
Wed, 04 August 2004 03:23 |
| Eclipse User |
|
|
|
>
> When I use jsp documents it would really nice to use an editor which
> knows
> about the jsp taglibs I defined in my document and provide help to me
> (provide code assist and so on). In my opinion a "plain" xml editor does
> not know about taglibs for instance. So I can not see where the magic
> should happen.
>
Thanks Martin, I have a feeling we're not communicating well, if you
thought I was suggesting you use an xml editor.
As I mentioned, before any future formal release or milestone, if you are
the type that doesn't mind editing plugin.xml files, you can add your jspx
extension to the contentType defined in sse.model.jsp plugin.xml file (no
spaces), and to the editor defintion in sse.editor.jsp (spaces ok). That
should get the JSP editor working as you expected. Previously, I was
trying to say the should not *require* the jspx extension, if the file
was already in xml-syntax form. But if you do the plugin.xml editing, then
jspx should work too. I'm still curious, just from a "better understanding
users goals" point of view, why you wanted your jsp in xml syntax form
(and don't get me wrong, I think its great ... just wanted to understand
"use and requirements" better).
|
|
|
| Re: ibm contrib - jsp document editor (xml-syntax) [message #36875 is a reply to message #36739] |
Wed, 04 August 2004 08:17 |
| Eclipse User |
|
|
|
David Williams wrote:
> >
> > When I use jsp documents it would really nice to use an editor which
> > knows
> > about the jsp taglibs I defined in my document and provide help to me
> > (provide code assist and so on). In my opinion a "plain" xml editor does
> > not know about taglibs for instance. So I can not see where the magic
> > should happen.
> >
> Thanks Martin, I have a feeling we're not communicating well, if you
> thought I was suggesting you use an xml editor.
> As I mentioned, before any future formal release or milestone, if you are
> the type that doesn't mind editing plugin.xml files, you can add your jspx
> extension to the contentType defined in sse.model.jsp plugin.xml file (no
> spaces), and to the editor defintion in sse.editor.jsp (spaces ok). That
> should get the JSP editor working as you expected. Previously, I was
> trying to say the should not *require* the jspx extension, if the file
> was already in xml-syntax form. But if you do the plugin.xml editing, then
> jspx should work too. I'm still curious, just from a "better understanding
> users goals" point of view, why you wanted your jsp in xml syntax form
> (and don't get me wrong, I think its great ... just wanted to understand
> "use and requirements" better).
Why I write my jsp-files in xml syntax? Good question! I had the
requirement to generate some jsp-files. So I thougt it is easier to use
xml because there are many tools out there to produce xml in an easy way
(e.g. JDOM...).
Also I don't like the jsp-syntax. I mean it is more clear to write my jsp
in well-formed xml (and it's more aesthetical for me)
But, I regret it many times to do it in this way. There are no tools out
there to support jsp-documents and most of the documentation is for
old-style.
So I think about to switch to the "old-style" jsp syntax.
Furthermore I'm not a profi in writing web applications (mainly I did
swing programming last 3 years). There are things that I can not solve in
an jsp-document but in (good) old jsp-syntax this is no problem (at least
for me).
|
|
|
Goto Forum:
Current Time: Wed Jul 09 09:22:57 EDT 2025
Powered by FUDForum. Page generated in 1.12099 seconds |
Home