[GLASSFISH-8615] service-name-pattern does not work in handlers.xml Created: 30/Jun/09  Updated: 06/Jan/11

Status: Open
Project: glassfish
Component/s: web_services
Affects Version/s: v2.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: razvan_petrescu Assignee: Bhakti Mehta
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 8,615
Status Whiteboard:

v3_exclude, v2.1.1_exclude


I have created a simple WS Handler and installed using handlers.xml. Everything
works fine, until I've tried to restrict a handler chain to a specific service,
when the namespace information is lost. Here is the content of handlers.xml:

<handler-chain name="defaultChain">
<service-name-pattern xmlns:ns1="http://test/">

And here is the Webservices.xml I got from GF admin console after deployment:
(notice: <service-name-pattern>


<?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"
<wsdl-service xmlns:ns1="http://test/">ns1:TestService</wsdl-service>
<wsdl-port xmlns:ns1="http://test/">ns1:TestPort</wsdl-port>


I've tested the same test case on the previous version of Glassfish and it works

Comment by razvan_petrescu [ 30/Jun/09 ]

Found something - it works if the handlers.xml file contains this:
<service-name-pattern xmlns:ns1="http://test/">ns1:*Service</service-name-pattern>

instead of

<service-name-pattern xmlns:ns1="http://test/">

Should these newlines matter in an XML file ???

Comment by razvan_petrescu [ 21/Jul/09 ]

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.

Comment by razvan_petrescu [ 21/Jul/09 ]

Changed user, because I got no feedback in a month on a sensitive issue

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Bhakti Mehta [ 17/Sep/09 ]

Added keyword

Comment by Ed Bratt [ 15/Oct/09 ]

Will not fix in v2.1.1

Generated at Mon Mar 27 10:17:29 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.