javaserverfaces
  1. javaserverfaces
  2. JAVASERVERFACES-1709

@Inject Support For Managed Beans (CDI Related)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.2
    • Fix Version/s: 2.1_gf31_m3
    • Component/s: None
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      1,709
    • Status Whiteboard:
      Hide

      importance_large size_medium

      Show
      importance_large size_medium

      Description

      JSF Managed beans need to support @Inject

      See: https://jira.jboss.org/browse/CDITCK-154

      1. 1709.txt
        1 kB
        rogerk
      2. changebundle.txt
        2 kB
        Ed Burns
      3. changebundle.txt
        43 kB
        rogerk

        Activity

        Hide
        rogerk added a comment -

        Created an attachment (id=1209)
        Changes - Revision 1

        Show
        rogerk added a comment - Created an attachment (id=1209) Changes - Revision 1
        Hide
        Ed Burns added a comment -

        Please edit build.properties.glassfish to indicate that V3.1 is now a valid value for container.name.
        There are comments in there for v2 and v3, put it in there.

        Should config.properties.patch really be committed?

        jsf-ri/build-tests.xml, why are you removing TestApplicationImpl_Config when you add TestInjection?

        Index: jsf-ri/systest-per-webapp/injection/src/java/com/sun/faces/systest/Foo.java, do we need this
        class?

        Index: jsf-ri/systest-per-webapp/injection/web/WEB-INF/web.xml

        If you're going to add a web.xml for a 3.1 only app, set the XSD stuff to Servlet 3.0.

        I don't like the way you're doing the exclusion business. Can you skip checking in jsf-ri/systest-per-
        webapp/build.xml and jsf-ri/systest-per-webapp/build-tests.xml but check in everything else.

        Show
        Ed Burns added a comment - Please edit build.properties.glassfish to indicate that V3.1 is now a valid value for container.name. There are comments in there for v2 and v3, put it in there. Should config.properties.patch really be committed? jsf-ri/build-tests.xml, why are you removing TestApplicationImpl_Config when you add TestInjection? Index: jsf-ri/systest-per-webapp/injection/src/java/com/sun/faces/systest/Foo.java, do we need this class? Index: jsf-ri/systest-per-webapp/injection/web/WEB-INF/web.xml If you're going to add a web.xml for a 3.1 only app, set the XSD stuff to Servlet 3.0. I don't like the way you're doing the exclusion business. Can you skip checking in jsf-ri/systest-per- webapp/build.xml and jsf-ri/systest-per-webapp/build-tests.xml but check in everything else.
        Hide
        Ed Burns added a comment -

        Created an attachment (id=1211)
        Modify systest-per-webapp to only include classes in package com.sun.faces.systest.model from the systest bundle.

        Show
        Ed Burns added a comment - Created an attachment (id=1211) Modify systest-per-webapp to only include classes in package com.sun.faces.systest.model from the systest bundle.
        Hide
        rogerk added a comment -

        Enabled injection test and tests pass fine.
        We will keep an eye on it.

        Show
        rogerk added a comment - Enabled injection test and tests pass fine. We will keep an eye on it.
        Hide
        Manfred Riem added a comment -

        Closing resolved issue out

        Show
        Manfred Riem added a comment - Closing resolved issue out

          People

          • Assignee:
            rogerk
            Reporter:
            rogerk
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: