Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Component/s: Uncategorized
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Macintosh

    • Issuezilla Id:
      464

      Description

      If the value of

      • the {@link #eager}

        attribute is <code>true</code>, the runtime must

      • instantiate this class when the application starts. In this case,
      • <em>scope</em> is ignored if its value is "none", "request", or
      • "session", or is unspecified. In these cases, the value of
      • <em>scope</em> is assumed to be "application". Otherwise, any value
      • of <em>scope</em> supported by the implementation is allowed. Once
      • instantiated, the bean must be placed in the proper <em>scope</em>.
      • This instantiation and storing of the instance must happen before any
      • requests are serviced. If <em>eager</em> is unspecified or
      • <code>false</code>, the default "lazy" instantiation and scoped
      • storage of the managed bean happens.</p>
        *
      • <p>When the runtime processes this managed-bean, if a managed bean
      • exists whose name is equal to the derived <em>managed-bean-name</em>,
      • a {@link javax.faces.FacesException}

        must be thrown and the

      • application must not be placed in service.</p>
        *

        Activity

        Hide
        Ed Burns added a comment -

        ManagedProperty annotation

        • <p class="changed_added_2_0">The presence of this annotation on a
        • field of a class annotated with {@link ManagedBean}

          instructs the

        • system to inject a value into this field whenever the bean is
        • instantiated. The time of instantiation is dictated by the value of
        • the attributes on the usage of <code>ManagedBean</code> and by the
        • application logic itself. The value of the {@link #value}

          attribute

        • may be a literal <code>String</code> or a
        • <code>ValueExpression</code>. If the latter, the expression must not
        • be evaluated until the bean is instantiated. The value of the name
        • attribute is taken to be the <em>managed-property-name</em> for this
        • property. If not specified, the <em>managed-property-name</em> is
        • taken to be the name of the field to which this is attribute is
        • attached.</p>
          *
        • <p class="changed_added_2_0">If this annotation is present on a class
        • that does not have the <code>ManagedBean</code> annotation, the
        • implementation must take no action on this annotation.</p>
        Show
        Ed Burns added a comment - ManagedProperty annotation <p class="changed_added_2_0">The presence of this annotation on a field of a class annotated with {@link ManagedBean} instructs the system to inject a value into this field whenever the bean is instantiated. The time of instantiation is dictated by the value of the attributes on the usage of <code>ManagedBean</code> and by the application logic itself. The value of the {@link #value} attribute may be a literal <code>String</code> or a <code>ValueExpression</code>. If the latter, the expression must not be evaluated until the bean is instantiated. The value of the name attribute is taken to be the <em>managed-property-name</em> for this property. If not specified, the <em>managed-property-name</em> is taken to be the name of the field to which this is attribute is attached.</p> * <p class="changed_added_2_0">If this annotation is present on a class that does not have the <code>ManagedBean</code> annotation, the implementation must take no action on this annotation.</p>
        Hide
        kito75 added a comment -

        It seems strange to me that non-application scopes are ignored when eager=true.
        I'd prefer an exception to be thrown if you specify a non-application scope in
        that case.

        Show
        kito75 added a comment - It seems strange to me that non-application scopes are ignored when eager=true. I'd prefer an exception to be thrown if you specify a non-application scope in that case.
        Hide
        Ed Burns added a comment -

        Move to unscheduled target milestone

        Show
        Ed Burns added a comment - Move to unscheduled target milestone
        Hide
        Ed Burns added a comment -

        Prepare to delete "spec" subcomponent.

        Show
        Ed Burns added a comment - Prepare to delete "spec" subcomponent.
        Hide
        Ed Burns added a comment -

        push to CDI

        Show
        Ed Burns added a comment - push to CDI
        Hide
        Manfred Riem added a comment -

        Closing resolved issue out

        Show
        Manfred Riem added a comment - Closing resolved issue out

          People

          • Assignee:
            Ed Burns
            Reporter:
            Ed Burns
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: