Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2168

contradication in requirement of defining property names in Activation Spec and Resource Adapter?s configuration property names.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • JBossAS-4.0.2 Final
    • JCA service
    • None
    • Compatibility/Configuration

      details about the bug - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3891659#3891659

      Problem noticed in Jboss 4.0.2
      ------------------------------------
      There seems to be a contradication in requirement of defining property names in Activation Spec and Resource Adapter?s configuration property names.

      It requires the Resource Adapterrs Config Parameter name to start with capital letter

      Example:

      <config-property-name>MaxInstancesPerProcessType</config-property-name>

      The Method implementation in the Resource Adapter would look like

      getMaxInstancesPerProcessType()

      If property name has starting letter with lower case property name
      It complains that method not found.
      Example:
      <config-property-name>maxInstancesPerProcessType</config-property-name>
      <== Note starting letter "m" is lower case.

      Where as for MDB Activation Spec , it requires the Activation Config Parameter name to start with small letter

      Example:
      <activation-config-property-name> projectInfo</activation-config-property-name>

      The method implementation in the Activation Spec would look like

      getProjectInfo()

      If Activation Config has starting letter Upper case property name
      It complains that method not found.

      Example when JBOSS complains:
      <activation-config-property-name> ProjectInfo</activation-config-property-name>
      <== Not "P" is uppercase

      J2EE Spec says it needs to be Java Bean Complaint.

      This problem is not happening in Jboss 4.0.0

      Somebody please clarify if this is a bug in JBoss or an expected behaviour..

            Unassigned Unassigned
            sreenive Sreenivasan Genipudi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: