xslt is broken

Please help. Idea cannot work with xsl documents. I've been looking for the
schema resource but I can't find it. If anyone knows where I can download
it please let me know thanks.

Rodrigo Gomez


15 comments
Comment actions Permalink

Well I think Jetbrains needs to include the dtd to the xslt definition. I think it is stupid not to. I'm lost and can't figure out where the dtd is. In a desperate attempt I looked at xml spy and stole their dtd and use that.

I also have been a loyal user of slickedit and they too include out of the box support for xsl. So I expect jetBRAINS to honor their name and bundle the dam dtds. Once I fiddle and dance around this stupid barrier, I was able to do a bit of xsl editing. The support so far is good. All the key bindings work, auto completion and all the good stuff that makes IDEA rock but it can be improved. There needs to be a way to include documentation so that quick-doc (ctrl-q) works.

Another mole is that idea hightlights unknow tags as red. Is there a way to tell idea to ignore them? Look at the picture. I know I can use the xsl:element, but I know in the future I will edit someones else's code and they might not use xsl:element. So it is important to have idea ignore those tags.

Please make IDEA a better editor for xsl.

Thank you.

Rodrigo Gomez


Please help. Idea cannot work with xsl documents. I've been looking
for the schema resource but I can't find it. If anyone knows where I
can download it please let me know thanks.

>

Rodrigo Gomez

>



Attachment(s):
xsl.JPG
0
Comment actions Permalink

XSL-T support is there. The schema is bundled.
Maybe you have noticed that error-highlighting is done on
non-xsl-elements. Instead your own, unknown elements are highlighted.

For me it worked flawlessy. Provide the source of your file instead of
an screenshot. Otherwise it's not possible to reproduce your problem.


Rodrigo Gomez schrieb:

Well I think Jetbrains needs to include the dtd to the xslt definition. I think it is stupid not to. I'm lost and can't figure out where the dtd is. In a desperate attempt I looked at xml spy and stole their dtd and use that.

I also have been a loyal user of slickedit and they too include out of the box support for xsl. So I expect jetBRAINS to honor their name and bundle the dam dtds. Once I fiddle and dance around this stupid barrier, I was able to do a bit of xsl editing. The support so far is good. All the key bindings work, auto completion and all the good stuff that makes IDEA rock but it can be improved. There needs to be a way to include documentation so that quick-doc (ctrl-q) works.

Another mole is that idea hightlights unknow tags as red. Is there a way to tell idea to ignore them? Look at the picture. I know I can use the xsl:element, but I know in the future I will edit someones else's code and they might not use xsl:element. So it is important to have idea ignore those tags.

Please make IDEA a better editor for xsl.

Thank you.

Rodrigo Gomez



>>Please help. Idea cannot work with xsl documents. I've been looking
>>for the schema resource but I can't find it. If anyone knows where I
>>can download it please let me know thanks.
>>
>>Rodrigo Gomez
>>
>>
>> -


>>

0
Comment actions Permalink

I know idea highlights unknowns elements. The problem, is how do you define
them? If you can't define them, can't we tell idea to ignore them?

XSL-T support is there. The schema is bundled.
Maybe you have noticed that error-highlighting is done on
non-xsl-elements. Instead your own, unknown elements are highlighted.
For me it worked flawlessy. Provide the source of your file instead of
an screenshot. Otherwise it's not possible to reproduce your problem.

Rodrigo Gomez schrieb:

>> Well I think Jetbrains needs to include the dtd to the xslt
>> definition. I think it is stupid not to. I'm lost and can't figure
>> out where the dtd is. In a desperate attempt I looked at xml spy and
>> stole their dtd and use that.
>>
>> I also have been a loyal user of slickedit and they too include out
>> of the box support for xsl. So I expect jetBRAINS to honor their name
>> and bundle the dam dtds. Once I fiddle and dance around this stupid
>> barrier, I was able to do a bit of xsl editing. The support so far is
>> good. All the key bindings work, auto completion and all the good
>> stuff that makes IDEA rock but it can be improved. There needs to be
>> a way to include documentation so that quick-doc (ctrl-q) works.
>>
>> Another mole is that idea hightlights unknow tags as red. Is there a
>> way to tell idea to ignore them? Look at the picture. I know I can
>> use the xsl:element, but I know in the future I will edit someones
>> else's code and they might not use xsl:element. So it is important to
>> have idea ignore those tags.
>>
>> Please make IDEA a better editor for xsl.
>>
>> Thank you.
>>
>> Rodrigo Gomez
>>
>>> Please help. Idea cannot work with xsl documents. I've been looking
>>> for the schema resource but I can't find it. If anyone knows where I
>>> can download it please let me know thanks.
>>>
>>> Rodrigo Gomez
>>>
>>> -


>>> -


>>>


0
Comment actions Permalink

I just looked and could not find the the schema. Where is it? I don't think
it is bundle. My point is that Idea should work out of the box. If you look
in this newsgroup, you will see this complaint has come up before.

XSL-T support is there. The schema is bundled.
Maybe you have noticed that error-highlighting is done on
non-xsl-elements. Instead your own, unknown elements are highlighted.
For me it worked flawlessy. Provide the source of your file instead of
an screenshot. Otherwise it's not possible to reproduce your problem.

Rodrigo Gomez schrieb:

>> Well I think Jetbrains needs to include the dtd to the xslt
>> definition. I think it is stupid not to. I'm lost and can't figure
>> out where the dtd is. In a desperate attempt I looked at xml spy and
>> stole their dtd and use that.
>>
>> I also have been a loyal user of slickedit and they too include out
>> of the box support for xsl. So I expect jetBRAINS to honor their name
>> and bundle the dam dtds. Once I fiddle and dance around this stupid
>> barrier, I was able to do a bit of xsl editing. The support so far is
>> good. All the key bindings work, auto completion and all the good
>> stuff that makes IDEA rock but it can be improved. There needs to be
>> a way to include documentation so that quick-doc (ctrl-q) works.
>>
>> Another mole is that idea hightlights unknow tags as red. Is there a
>> way to tell idea to ignore them? Look at the picture. I know I can
>> use the xsl:element, but I know in the future I will edit someones
>> else's code and they might not use xsl:element. So it is important to
>> have idea ignore those tags.
>>
>> Please make IDEA a better editor for xsl.
>>
>> Thank you.
>>
>> Rodrigo Gomez
>>
>>> Please help. Idea cannot work with xsl documents. I've been looking
>>> for the schema resource but I can't find it. If anyone knows where I
>>> can download it please let me know thanks.
>>>
>>> Rodrigo Gomez
>>>
>>> -


>>> -


>>>


0
Comment actions Permalink

Have you tried XPathView + XSLT-Support plugin? It helps a lot for XSL editing.
The last thing where IntelliJ sucks is that reformat code trims body of <xsl:text>, </xsl:text>

0
Comment actions Permalink

Rodrigo Gomez wrote:

I just looked and could not find the the schema. Where is it? I don't
think it is bundle. My point is that Idea should work out of the box. If
you look in this newsgroup, you will see this complaint has come up before.


There is a schema bundled with the XPathView + XSLT-Support plugin you have installed. You
can press ctrl-b on an XSLT element to open and view it.

Telling from the screenshot why the elements are highlighted in red is a bit hard. There
might be a conflict with another schema (you said you installed a DTD from XML Spy on your
own). This might be the cause because a DTD is not designed for template-like documents,
i.e. documents that embed and mix different XML dialects: XSLT and your own one in this
case. It might also be the case that this has been disabled in the plugin's settings.
Please check it's configuration.

The schema that is bundled with the plugin however allows elements from foreign namespaces
("literal result elements") inside XSLT elements. However, you have to explicitly declare
the namespace for those elements, otherwise IDEA will again flag an error.

If you're experiencing other problems, please post a reproducible testcase to the plugins
forum or email it to me and I'll take a look at it.

HTH,
Sascha

0
Comment actions Permalink

Thanks for info. I'll check it out and get back to you soon.

Rodrigo Gomez wrote:

>> I just looked and could not find the the schema. Where is it? I don't
>> think it is bundle. My point is that Idea should work out of the box.
>> If you look in this newsgroup, you will see this complaint has come
>> up before.
>>

There is a schema bundled with the XPathView + XSLT-Support plugin you
have installed. You can press ctrl-b on an XSLT element to open and
view it.

Telling from the screenshot why the elements are highlighted in red is
a bit hard. There might be a conflict with another schema (you said
you installed a DTD from XML Spy on your own). This might be the cause
because a DTD is not designed for template-like documents, i.e.
documents that embed and mix different XML dialects: XSLT and your own
one in this case. It might also be the case that this has been
disabled in the plugin's settings. Please check it's configuration.

The schema that is bundled with the plugin however allows elements
from foreign namespaces ("literal result elements") inside XSLT
elements. However, you have to explicitly declare the namespace for
those elements, otherwise IDEA will again flag an error.

If you're experiencing other problems, please post a reproducible
testcase to the plugins forum or email it to me and I'll take a look
at it.

HTH,
Sascha



0
Comment actions Permalink

I have the xpath view plugin but not the xslt-support. Is the xslt-support
plugin available for 5.0?

Have you tried XPathView + XSLT-Support plugin? It helps a lot for XSL
editing. The last thing where IntelliJ sucks is that reformat code
trims body of <xsl:text>, </xsl:text>



0
Comment actions Permalink

I have the xpath view plugin but not the xslt-support. Is the xslt-support plugin available for 5.0?


"XPathView + XSLT-Support" is the actual name of the plugin. The plugin manager
unfortunately doesn't display this in the "available"-list. You'll find the full name in
the "installed"-list though.

Sascha

0
Comment actions Permalink

"XPathView + XSLT-Support" is the actual name of the plugin. The
plugin manager unfortunately doesn't display this in the
"available"-list. You'll find the full name in the "installed"-list
though.


That's odd -- I don't see this in either list in the plugin manager. Nor
do I see anything that looks promising in idea3496.zip. Any ideas where
to get it? It sounds very useful.

--Mike


0
Comment actions Permalink

Michael Werle wrote:
>> "XPathView + XSLT-Support" is the actual name of the plugin. The
>> plugin manager unfortunately doesn't display this in the
>> "available"-list. You'll find the full name in the "installed"-list
>> though.


That's odd -- I don't see this in either list in the plugin manager.
Nor do I see anything that looks promising in idea3496.zip. Any ideas
where to get it? It sounds very useful.


Sorry, I wasn't clear enough: The XPathView plugin has been extended to provide XSLT
support, hence the name was changed from "XPathView" to "XPathView + XSLT-Support".
However, the Plugin Manager still shows it with the old name in the list of available
plugins. Once you downloaded and installed it, you'll find it in the list of your locally
installed plugins with the full name. I'll see what can be done to make it display the
correct name in the other list as well.

Sascha

0
Comment actions Permalink

Rodrigo Gomez wrote on 28/09/05 12:53:

Please make IDEA a better editor for xsl.



I was just thinking a funky plugin could also improve XSLT stuff here.

Say you open an XSLT file, right click in the editor and select a new
"Apply on file..." which problems for an XML file. This then opens a
toolwindow ( or an editor split with a virtual file ) that is a live
rendering of the XSLT file against a chosen XML file.

This would quite rock :)

0
Comment actions Permalink

Mark Derricutt wrote:

Say you open an XSLT file, right click in the editor and select a new
"Apply on file..." which problems for an XML file. This then opens a
toolwindow ( or an editor split with a virtual file ) that is a live
rendering of the XSLT file against a chosen XML file.


I've been thinking about a new run-configuration type that can be created to either run a
stylesheet against a chosen XML document or the currently selected one and displaying the
result in the run-toolwindow (with possibly different tabs for stderr/stdout and the
actual stylesheet output). Do you think that would be useful?

Sascha

0
Comment actions Permalink

This would be great.

Mark Derricutt wrote:

>> Say you open an XSLT file, right click in the editor and select a new
>> "Apply on file..." which problems for an XML file. This then opens a
>> toolwindow ( or an editor split with a virtual file ) that is a live
>> rendering of the XSLT file against a chosen XML file.
>>

I've been thinking about a new run-configuration type that can be
created to either run a stylesheet against a chosen XML document or
the currently selected one and displaying the result in the
run-toolwindow (with possibly different tabs for stderr/stdout and the
actual stylesheet output). Do you think that would be useful?

Sascha



0
Comment actions Permalink

Rodrigo Gomez wrote:

There needs to be a way to include documentation so that quick-doc (ctrl-q) works.


Check out the latest version of the plugin. It comes with bundled documentation from W3C
for elements and functions, and a lot more ;)

Sascha

0

Please sign in to leave a comment.