Forum Stats

  • 3,840,393 Users
  • 2,262,599 Discussions
  • 7,901,261 Comments

Discussions

Eclipse WTP JSF indexing not working after disabling AppXray

BonanzaOne
BonanzaOne Member Posts: 18
edited Feb 20, 2016 1:22PM in Enterprise Pack for Eclipse

When AppXray is disabled the Eclipse no longer index Managed Beans.

Please fix it so AppXray is disabled without affecting the operation of Eclipse WTP JSF indexing. We developers wanna have the option to use it (since the Oracle plugin have bugs that are not being resolved, like the annotated managed bean suggestions).

Steps to reproduce

  1. Disable AppXray: Window -> Preferences -> Oracle -> AppXray -> check the "Disable AppXray" checkbox
  2. Restart Eclipse.
  3. Create a new "Dynamic Web Project": New -> Project... -> Dynamic Web Project
  4. Apply JSF 2.0 Facet to the project.
  5. Create an annotated Managed Bean.
  6. Create a new facelet (page with JSF template, it can be a JSP file)
  7. Try to bind the annotated Managed Bean to the Facelet. The editor will not suggest any beans.

Tested with Mars 4.1 and OEPE 8.4.0.201510191754. All up to date.

disableapp.png

Tagged:

Answers

  • dvohra21
    dvohra21 Member Posts: 14,628 Gold Crown
    edited Jan 2, 2016 10:41AM

    And does the managed bean get listed when AppXray is enabled?  What are the disadvantages to having the AppXray enabled?

  • BonanzaOne
    BonanzaOne Member Posts: 18
    edited Feb 17, 2016 9:24PM

    Dvohra

    Beans are listed, but the content assist does not detects it.

    Since September/2015, I am dealing with this other thread , were I am unable to properly develop JSF application using OEPE plugin, since the plugin has it's content assist broken for some reason.

    If I had the option to use WTP JSF content assist this would be different, but disabling AppXRay seems to have no effect.

    The disadvantage of having AppXray enabled is that content assist is not working. Developers should be able to choose which Facelet/Web page editor they would use, regardless of the Java EE Server we would develop to.

    WTP plugin works just fine for content assiting, is it really necessary to override it with another thing?

    Just separate WebLogic AS deployment and Facelets page editing, they offer different capabilities.

  • dvohra21
    dvohra21 Member Posts: 14,628 Gold Crown
    edited Feb 20, 2016 1:22PM

    JSF 2.0 Facet is applied.

    @ManagedBean annotation is set.

    Should list the managed beans in code assist. Could be a bug.

This discussion has been closed.