[Paul Ashford]

We are currently developing an IVR application using VXML. We are using struts for processing of the VXML. When I edit a JSP people file that is producing the VXML, the MyEclipse JSP editor puts warnings all over the place about unknown tags, with the first warning being

Unknown tag (vxml).

I even tried to put a DOCTYPE in for the VXML spec, and it still complained about all of the VXML tags.

JSPs can produce any type of file you like, it does not have to be HTML.
I can also think of using JSPs for creating dynamic XML documents for AJAX usage. Or what about WML?

So, in other words, the JSP editor should support the DOCTYPE tag, and validate against a DTD, or the xmlns (schema) attributes for validation of tags within the document.

[Scott Anderson]

Can you try Open With… > MyEclipse XML editor and see if that behaves better for you? Can you post a small example here for a JSP you think is giving improper error messages? Please be sure to include it in “code” blocks like this:

Code goes in here

[tmancill]

@support-scott wrote:

Can you try Open With… > MyEclipse XML editor and see if that behaves better for you? Can you post a small example here for a JSP you think is giving improper error messages? Please be sure to include it in “code” blocks like this:

Code goes in here

I’ve added the VoiceXML DTD to Preferences -> MyEclipse -> Editors -> XML -> XML Catalog and am having the same problem. Also, there doesn’t seem to be an option for Open With… > MyEclipse XML editor, only MyEclipse ‘Classic’ JSP Editor and MyEclipse JSP Designer. (I’m using 4.0, milestone 3). Could that be related?

Anyway, everytime I try to preview my post with valid VoiceXML code between code blocks (doesn’t matter if HTML is disabled or not), I get redirected to the main page (http://www.myeclipseide.com/index.php). The code is simple and fairly short, so I give up… Please contact me directly if you’d like a code snippit.

[Scott Anderson]

Also, there doesn’t seem to be an option for Open With… > MyEclipse XML editor, only MyEclipse ‘Classic’ JSP Editor and MyEclipse JSP Designer. (I’m using 4.0, milestone 3). Could that be related?

To add a new editor as an option for a particular file suffix, you need to add it to Window > Preferences > General > Editors > File Associations > *.jsp and click ‘Add…’ and select MyEclipse XML Editor.

Once you’ve done that, you should be able to use the XML editor directly to open any of your JSP files. As far as previewing goes, since that really shows static representation in a browser, and Voice XML is really all about dynamic representation, you’ll really have to deploy and run the application and then hit it with a browser to see anything meaningful in this particular application domain.

[tmancill]

Thank you for your reply, the process of selecting the MyEclipse XML editor worked fine. However, it’s still not validating the document against the DTD I added to the XML Catalog. Shouldn’t it key off the Public-ID in the DOCTYPE tag?

BTW, I’m not looking for preview or anything like that to work, just for the editor to validate the tags against the VoiceXML DTD.

[surfpnk]

Has there been any progress in getting VXML to validate properly without all those warnings? I installed 4.0.3 GA today, tried the MyEclipse XML Editor, but still no change, I’m seeing the exact same issues as the other posters.

We work with IVR apps and VXML on a daily basis, and it’d be nice to see those warning go away some day! Thanks.

[stef_s]

Hello,

as of 4.1.1 nothing has changed. Will there be any development to validate jsp files against different DTDs or XML schemas? Everytime i open an vxml file the editor needs several seconds to show all these yellow error signs 🙁

[cruelfate]

I totally concur with the aim of this post as I’m having the same fustration. I too edit JSPs that produce VoiceXML. In my opinion, there shouldn’t necessarily be a fixed association between file extension, document type, and generated content type. JSPs can produce XML, HTML, XTML, plain text, CSVs .. etc.

When I open a tag in the editor (“<“), I’m looking for MyEclipse to offer syntactically valid VoiceXML elements as specified in VoiceXML DTD included in the source file, as well as offer a subset of the usual JSP tool bag: specifically Struts, JSTL and custom taglibs, as specified in by the taglib directives. I typically have struts-bean and struts-logic plus a custom taglib for doing VoiceXML stuff. (The HTML-specific taglibs are, of course, useless for VoiceXML).

Here’s what I’ve got in my environment: I’ve added an XML catalog entry thusly:

URI:           http://www.w3.org/TR/voicexml20/vxml.dtd
Key Type:    URI
Key:        -//W3C//DTD VOICEXML 2.0//EN

And I’ve got a Web project with the following JSP source (foo.jsp):

<?xml version="1.0"?>
<!DOCTYPE vxml PUBLIC "-//W3C//DTD VOICEXML 2.0//EN"
"http://www.w3.org/TR/voicexml20/vxml.dtd">
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic" %>
<vxml xmlns="http://www.w3.org/2001/vxml" version="2.0">

</vxml>

.. MyEclipse behaves in a sub-optimal fashion because:
(1) The editor does not suggest any VXML tags when I open/start a tag (“<“). The editor does suggest the taglib tags (including custom taglibs if I stick those in) and <jsp:> tags, but that is all.
(2) I get a yellow marker on the line with the VXML tag:

Unknown tag (vxml)

which I assume can’t be good.
(3) If I right-click in the document and run the MyEclipse validator, it dutifully reports without errors:

Validation of resource /IVR/web/foo.jsp is complete.

which seems to be at odds with item (2).

It seems to matter not whether the catalog key type (above) is System, Public or URI.

If you fix item 1, I won’t care about items 2 and 3 🙂

Changing the file extension to something other than .jsp is a red herring. Using .jspx is wrong because it is not a JSP with an XML syntax (that’s a discussion for another day).

Bottom line: Why can’t this thing work for other markup (VXML, WML or whatever the DTD says) like it does for HTML ?

[Riyad Kalla]

Guys,
Can you download Eclipse 3.2RC7 and MyEclipse 5.0 Milestone 1 (or 2 by the time you read this, we are hoping to get it out ASAP). I just tested this locally and with your code snippet above (Without the XML catalog entry) I am getting autocomplete for all the taglibs as well as tags like “meta” that as far as I can tell are from the Voice DTD. Also I don’t see *any* html completion popping up in the JSP page (table, p, img, etc.)

So I think it’s working… but please give it a try. I just tried with our internal build of 5.0 Milestone 2.

[cruelfate]

Sorry for not reponding sooner, but I hadn’t had a chance to try this until today as I hadn’t been working for my IVR client in a while.

I’m using Build id=”20060810-5.0.1-GA”. Things were initially promising. The editor indeed suggested appropriate VXML elements for anything inserted as a child of the vxml element BUT as soon as I entered a form element (a valid VXML element), it was back to HTML land – and no VXML tags. Apparently, HTML nature is still in scope being triggered by the common element, “form“.

Is there some way to turn off MyEclipse instisting on HTML in JSPs? How about an annotation? I suppose I’d even settle for a project-wide switch, though I do have projects with both VXML and HTML content.

Anyway, Here’s a code sample with a little more to play with:

<?xml version="1.0"?>
<!DOCTYPE vxml PUBLIC "-//W3C//DTD VOICEXML 2.0//EN"
"http://www.w3.org/TR/voicexml20/vxml.dtd">
<vxml xmlns="http://www.w3.org/2001/vxml" version="2.0">
    <form>

        <!-- try to enter a VoiceXML "field" here -->

        <field name="answer" type="boolean">
            <prompt>yes or no?</prompt>
            <filled>
                <if cond="answer">
                    <prompt>wrong!</prompt>
                    <clear />
                </if>
            </filled>
            <noinput>say something</noinput>
            <nomatch>there are only two choices.<reprompt/></nomatch>
        </field>
    </form>
</vxml>

[Riyad Kalla]

Proper XHTML support is on our TODO list, and I think that this falls into this category (properly recognizign and processing the DTD).

Can’t you use the XML editor on this file to work around the problem or is the lack of HTML tags in the XML editor the issue?

[surfpnk]

I’ve confirmed the problems that cruelfate is seeing with build “20070302-5.1.1-GA”, using his code sample. Once the <form> element is added, the IDE suggests only HTML and not VXML elements.

In addition, the <form> line is underlined yellow and suggests “Invalid location of tag (form)”, when, of course, it is quite properly located. No warning icon, though.

I have to say, things are getting closer; at least I don’t stare at as many yellow triangle warning icons as I used to.

[Riyad Kalla]

We had some more changes in 5.5M2, but not many. WE still don’t have full XHTML support there yet, but with Facelets being a high priority, it’ll get done soon.

[athanikar]

I have used Struts for number of application. I waould like to use it with VXML as I am implementing IVR Application.

Could you hguys pls point to some infromation on this. I am using JBoss, Struts and VXML as interaction piece.

Any help would be appreciated.

Thanks, 🙂 🙁

[athanikar]

Sorry for the double post. I am using MyEclipse version

Version: 5.1.1 GA
Build id: 20070302-5.1.1-GA

Thanks,

[Author]

Posts