glassfish
  1. glassfish
  2. GLASSFISH-5008

Java EE SE populates invalid value for "name" attribute

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 9.1peur2
    • Fix Version/s: not determined
    • Component/s: jbi
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      5,008

      Description

      Java EE SE populates invalid value for "name" attribute.

      In the attached project EJB WS throws TestFault

      JBI bridge wraps the fault in the following message (Message from the log). As
      per JBI spec page 41

      name attribute, which corresponds to the optional name attribute of the
      wsdl:input, wsdl:output, or wsdl:fault corresponding to the normalized message.
      If this attribute is not provided, the WSDL 1.1 default naming rules apply.

      Message from the log
      -------------------------
      [#|2008-05-12T12:05:22.546-0700|FINEST|sun-appserver9.1|com.sun.jbi.engine.bpel.BPELSEInOutThread|_ThreadID=23;_ThreadName=BPELSEInOutThread4;ClassName=com.sun.jbi.engine.bpel.BPELSEInOutThread;MethodName=processResponse;_RequestID=19408d7f-edd7-48ed-a27c-77a433f435f9;|I18N:
      BPJBI-3003: Received in-out message fault for M Ex
      15501183692268-18621-134299119222650245 content is <?xml version="1.0"
      encoding="UTF-8"?><jbi:message
      xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"
      xmlns:msgns="http://j2ee.netbeans.org/wsdl/EJBWSFromWSDL" name="comment"
      type="msgns:testFault" version="1.0"><jbi:part><comment:comment
      xmlns="http://xml.netbeans.org/examples/PurchaseOrder"
      xmlns:comment="http://xml.netbeans.org/examples/PurchaseOrder">Error from
      EJB</comment:comment></jbi:part></jbi:message>|#]

        Activity

        Hide
        mpottlapelli added a comment -

        Created an attachment (id=1493)
        project to reprodcue the issue

        Show
        mpottlapelli added a comment - Created an attachment (id=1493) project to reprodcue the issue
        Hide
        mpottlapelli added a comment -

        Why P2?

        User can not implement a fault handler in a Business process for named fault
        thrown from EJB WS when the EJB WS service is consumed.

        Only workaround available is to name fault and associated message part's element
        name to be exact same. Its scope is limited and does not work for existing WSDLs
        as these names would not match

        Show
        mpottlapelli added a comment - Why P2? User can not implement a fault handler in a Business process for named fault thrown from EJB WS when the EJB WS service is consumed. Only workaround available is to name fault and associated message part's element name to be exact same. Its scope is limited and does not work for existing WSDLs as these names would not match
        Hide
        harpreet added a comment -

        Changing miletstone from v3 to 9.1.1.

        Show
        harpreet added a comment - Changing miletstone from v3 to 9.1.1.
        Hide
        sanandal added a comment -

        "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
        release whose primary release driver is SailFin.
        This issue will be scrubbed after this release and will be given the right
        priority for the next release."

        Show
        sanandal added a comment - "Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1 release whose primary release driver is SailFin. This issue will be scrubbed after this release and will be given the right priority for the next release."
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

          People

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

            Dates

            • Created:
              Updated: