Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: v2.1.1
    • Fix Version/s: None
    • Component/s: web_services
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      8,794
    • Status Whiteboard:
      Hide

      v3_exclude,V2.1.1exclude

      Show
      v3_exclude,V2.1.1exclude

      Description

      When you deploy a WebService and use a handlers.xml file, the namespace is not
      processed correctly.
      In the handlers.xml file I have this line:
      <service-name-pattern xmlns:ns1="urn:test">ns1:*Service</service-name-pattern>

      After deploy, the webservices.xml file contains this line:

      <service-name-pattern>

      {urn:test}

      *Service</service-name-pattern>.

      Meanwhile, the services are processed correctly:

      <wsdl-service xmlns:ns1="urn:test">ns1:TestService</wsdl-service>
      <wsdl-port xmlns:ns1="urn:test">ns1:TestPort</wsdl-port>

      I have used the same targetNamespace (urn:test) for this WebService, and also in
      handlers.xml.

      At startup, Glassfish also complains about this error:

      [#|2009-07-21T17:45:08.763+0300|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;Deployment
      descriptor file META-INF/webservices.xml in archive
      [test.jar].;16;74;cvc-pattern-valid: Value '

      {urn:test}

      *Service' is not
      facet-valid with respect to pattern
      '*|([\i-[:]][\c-[:]]?[\i-[:]][\c-[:]]*?' for type
      'qname-pattern'.;_RequestID=542a043f-b8df-4730-a7a1-49b68b50aec4;|"DPL8015:
      Invalid Deployment Descriptors in Deployment descriptor file
      META-INF/webservices.xml in archive [test.jar].
      Line 16 Column 74 – cvc-pattern-valid: Value '

      {urn:test}

      *Service' is not
      facet-valid with respect to pattern
      '*|([\i-[:]][\c-[:]]?[\i-[:]][\c-[:]]*?' for type 'qname-pattern'."|#]

      [#|2009-07-21T17:45:08.781+0300|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=10;_ThreadName=main;Deployment
      descriptor file META-INF/webservices.xml in archive
      [test.jar].;16;74;cvc-type.3.1.3: The value '

      {urn:test}

      *Service' of element
      'service-name-pattern' is not
      valid.;_RequestID=542a043f-b8df-4730-a7a1-49b68b50aec4;|"DPL8015: Invalid
      Deployment Descriptors in Deployment descriptor file META-INF/webservices.xml in
      archive [test.jar].
      Line 16 Column 74 – cvc-type.3.1.3: The value '

      {urn:test}

      *Service' of element
      'service-name-pattern' is not valid."|#]

      Here is the generated webservice.xml file:

      <?xml version="1.0" encoding="UTF-8" standalone="no"?>
      <webservices xmlns="http://java.sun.com/xml/ns/javaee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2"
      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
      http://www.ibm.com/webservices/xsd/javaee_web_services_1_2.xsd">
      <webservice-description>
      <display-name>TestService</display-name>
      <webservice-description-name>TestService</webservice-description-name>
      <port-component>
      <port-component-name>TestBean</port-component-name>
      <wsdl-service xmlns:ns1="urn:test">ns1:TestService</wsdl-service>
      <wsdl-port xmlns:ns1="urn:test">ns1:TestPort</wsdl-port>
      <service-endpoint-interface>test.TestBean</service-endpoint-interface>
      <service-impl-bean>
      <ejb-link>TestBean</ejb-link>
      </service-impl-bean>
      <handler-chains>
      <handler-chain>
      <service-name-pattern>

      {urn:test}

      *Service</service-name-pattern>
      <handler>
      <handler-name>TestHandler</handler-name>
      <handler-class>test.TestHandler</handler-class>
      </handler>
      </handler-chain>
      </handler-chains>
      </port-component>
      </webservice-description>
      </webservices>

        Activity

        Hide
        razvan_petrescu added a comment -

        Glassfish V3 is miles away of being production ready (with all the stuff already
        present in 2.1) so it should be fixed in the following releases of V2 branch.

        Show
        razvan_petrescu added a comment - Glassfish V3 is miles away of being production ready (with all the stuff already present in 2.1) so it should be fixed in the following releases of V2 branch.
        Hide
        Bhakti Mehta added a comment -

        Added the keyword

        Show
        Bhakti Mehta added a comment - Added the keyword
        Hide
        jagadesh added a comment -

        Will not be fixed for V2.1.1

        Show
        jagadesh added a comment - Will not be fixed for V2.1.1

          People

          • Assignee:
            Bhakti Mehta
            Reporter:
            razvan_petrescu
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: