Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9455

Errors due to unsatisfied JSF constraints should be handled more gracefully

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.3.0.M3
    • 3.3.0.M2
    • maven
    • Hide
      • create a new maven project
      • in the archetype selection, choose appfuse-light-jsf-archetype 2.1.0
      • click next and fill in the project details
      • click on finish, 2 error popup are displayed, just saying "One or more constraints have not been satisfied"
      • There should be error markers instead, saying :
      • "JavaServer Faces 2.0 can not be installed : One or more constraints have not been satisfied."
      • "JavaServer Faces 2.0 requires Dynamic Web Module 2.5 or newer."
      Show
      create a new maven project in the archetype selection, choose appfuse-light-jsf-archetype 2.1.0 click next and fill in the project details click on finish, 2 error popup are displayed, just saying "One or more constraints have not been satisfied" There should be error markers instead, saying : "JavaServer Faces 2.0 can not be installed : One or more constraints have not been satisfied." "JavaServer Faces 2.0 requires Dynamic Web Module 2.5 or newer."

      While testing appfuse-light-jsf-archetype:2.1.0, Error popups show up during project creation.
      The problem is the archetype depends on JSF 2.0 but uses web.xml version 2.4.
      JavaEE6 spec requires servlet version >= 2.5 to use JSF 2.0, and WTP is very strict about that.

      Instead of displaying an error popup, it'd be more appropriate to add error markers :

      • "JavaServer Faces 2.0 can not be installed : One or more constraints have not been satisfied."
      • "JavaServer Faces 2.0 requires Dynamic Web Module 2.5 or newer."

              fbricon@redhat.com Fred Bricon
              fbricon@redhat.com Fred Bricon
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: