Welcome toVigges Developer Community-Open, Learning,Share
Ask a Question
Welcome To Ask or Share your Answers For Others

Categories

jsf - Properties of new tags using composite component are not displayed by Eclipse auto complete shortcurt

0 votes
942 views
in Technique[技术] by (71.8m points)

jsf - Properties of new tags using composite component are not displayed by Eclipse auto complete shortcurt

I have developed composite components using JSF 2.0 in Eclipse. I've been putting my XHTML tag files inside resources folder.

When I hit ctrl + space in keyboard, the property of the tag are not displayed.

I found some tips told to install "Jboss tools" but didn't work.

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
          "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:cc="http://xmlns.jcp.org/jsf/composite"
      xmlns:h="http://xmlns.jcp.org/jsf/html"
      xmlns:f="http://xmlns.jcp.org/jsf/core"
      xmlns:p="http://primefaces.org/ui">

    <cc:interface>
        <cc:attribute name="value"/>
        <cc:attribute name="label"/>
        <cc:attribute name="masculino" default="true"/>
    </cc:interface>

    <cc:implementation>
        <p:selectOneMenu value="#{cc.attrs.value}" label="#{cc.attrs.label}">
            <f:selectItem itemValue="#{null}"
                          itemLabel="#{cc.attrs.masculino ? lbl['LABEL.TODOS'] : lbl['LABEL.TODAS']}" />
            <f:selectItem itemValue="true" itemLabel="#{lbl['LABEL.SIM']}" />
            <f:selectItem itemValue="false" itemLabel="#{lbl['LABEL.NAO']}" />
        </p:selectOneMenu>                                  
    </cc:implementation>

</html>

Above is one example of one tag created.

Thanks

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

JSF 2.x Facelets support is integrated in "Eclipse IDE for Enterprise Java Developers" (note the Enterprise, thus not "Eclipse IDE for Java Developers"), since Eclipse Helios (version 3.6, released June 2010). You need to ensure that the JavaServer Faces facet is enabled in Project Facets section of project's properties and is set to a minimum of version 2.0.

enter image description here

This is usually configureable during in new Dynamic Web Project wizard, but when importing non-Eclipse projects or creating non-Dynamic Web Project projects (e.g. Maven archetypes), then you need to manually check/add it.

Once integrated, JSF tag autocomplete is by default available on java.sun.com XML namespace.

enter image description here

The new xmlns.jcp.org namespace isn't recognized by default (currently tested Eclipse version is Luna SR2).

enter image description here

The new xmlns.jcp.org namespace will only work if you've added a physical JSF 2.2 implementation to build path in flavor of a full fledged Java EE container having JSF 2.2 in its modules, integrated via a decent server plugin and set as Targeted Runtimes in project's properties, or a concrete JSF 2.2 implementation JAR file in /WEB-INF/lib in case of Tomcat and clones (or by adding it as a Maven dependency).

enter image description here

It only still doesn't recognize composites in the new XML namespace. When changing back to java.sun.com, code completion of composite component tags is back, but code completion of attributes on those tags is not available.

enter image description here

Then I installed JBoss Tools 4.2.3 for Eclipse Luna and enabled the JBoss Tools Knowledge Base in project's properties.

enter image description here

After closing and reopening the Facelet (so JBoss builtin HTML editor gets opened; you can set/configure the editor used by rightclick, Open With), and switching to the Source tab (please don't use Visual editor, this is a disaster), I finally got code completion of attribtues on composite components.

enter image description here

Only the xmlns.jcp.org still didn't work. It's an Eclipse specific issue and probably already fixed in Mars or newer. You can always hide the composite namespace behind a custom XML namespace as below:

/WEB-INF/my.taglib.xml

<?xml version="1.0" encoding="UTF-8"?>
<facelet-taglib
    xmlns="http://xmlns.jcp.org/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-facelettaglibrary_2_2.xsd"
    version="2.2"
>
    <namespace>http://example.com/my</namespace>
    <composite-library-name>components</composite-library-name>
</facelet-taglib>

/WEB-INF/web.xml

<context-param>
    <param-name>javax.faces.FACELETS_LIBRARIES</param-name>
    <param-value>/WEB-INF/my.taglib.xml</param-value>
</context-param>

enter image description here

So, summarized:

  • Enable JSF project facet in project's properties for code completion on composite tags.
  • Install JBoss Tools for code completion on attribtues in composite tags.
  • Enable JBoss Tools Knowledge base in project's properties.
  • Have a physical JSF 2.2 impl JAR in buildpath for xmlns.jcp.org support on standard tags.
  • Use java.sun.com XML namespace domain or a custom taglib (or a newer Eclipse version) on composite tags.

与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
Welcome to Vigges Developer Community for programmer and developer-Open, Learning and Share

Just Browsing Browsing

2.1m questions

2.1m answers

63 comments

56.6k users

Most popular tags

Snow Theme by Q2A Market
Powered by Question2Answer
...