Please describe the problem in detail.
What did you do actually. I tried to reproduce the issue with no success.

Questions:

- what project type do you use (web project, J2SE project)
- are you configuring handler on service side or client side ?
- what jdk version do you use ?
- have you tested Netbeans 6.8 Bata ?

Basically, what you need is to 
- create either LogicalHandler or MessageHandler subclass.
- use "Configure Handlers" action to attach handler to service (or client)

For me everything works fine.

Product Version: NetBeans IDE 6.7.1 (Build 200907230233)
Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15

SOAP client service:  
web project
JAX-WS 2.1 library
Protocol handler pointing to class which implements SOAPHandler<SOAPMessageContext>

SOAP server service:
web project
JAX-WS 2.1 library
**** IMPORTANT ****  JAXB Binding
Protocol handler which points to class which implements SOAPHandler<SOAPMessageContext>

I will try to create a generic simple test case.

I also have this problem.  I reproduce it easily using NB 6.7.1.   

I have a handler class that implements javax.xml.ws.handler.LogicalHandler.  I add it to my *web service client* (maybe it is client specific?), and then upon build/run get the error saying "could not find handler chain file..."

As a workaround, I can hand copy the xml file to the build directory...but this used to work.

meg

Cannot reproduce.

I'm using NetBeans IDE 7.2 (Build 201207171143) with all updates applied.

I'm also seeing this bug.
Steps:
- create maven based web application
- create web service WS1
- create web service client WS2 (this is a client generated from a WSDL file)
- create Web Service Message Handler
- under "Web Service References" you will have reference to WS2. Right click it and set this created Message Handler
- build
- try to deploy resulting WAR file

The problem is that files containig jws:handler-chain element are not copied to the web service client classes directories

Thank you for exact steps.
I'm able to reproduce.
The issue is specific to maven web project.
Ant based project works fine.
handler xml file is created in the package structure of the main WebServiceClient
service but its root is project directory.
As result it is not copied into the correct directory in the package.

I need a help from Maven experts.
The issue is a consequence of wired work "jaxws-maven-plugin".
pom.xml has a plugin :
<plugin>
    <groupId>org.jvnet.jax-ws-commons</groupId>
    <artifactId>jaxws-maven-plugin</artifactId>
    <version>2.2</version>

With execution:
                    <execution>
                        <goals>
                            <goal>wsimport</goal>
                        </goals>
                        <configuration>
                            <wsdlFiles>
                                <wsdlFile>StockService.wsdl</wsdlFile>
                            </wsdlFiles>
                            <wsdlLocation>file:/C:/tmp/StockService.wsdl</wsdlLocation>
                            <staleFile>${project.build.directory}/jaxws/stale/StockService.stale</staleFile>
                            <bindingDirectory>${basedir}/src/jaxws-bindings</bindingDirectory>
                            <bindingFiles>
                                <bindingFile>StockService_handler.xml</bindingFile>
                            </bindingFiles>                            
                        </configuration>
                        <id>wsimport-generate-StockService</id>
                        <phase>generate-sources</phase>
                    </execution>

wsimport (see f.e. http://mojo.codehaus.org/jaxws-maven-plugin/wsimport-mojo.html ) generates java class file sources which compiled into the target/classes folder inside project directory.
This is the value of the ${project.build.outputDirectory}.
The latter property value have to be used for handler xml file as well.
But it is not used.
There is "destDir" parameter plugin which could be used to set output directory.
If I use <destDir>${project.build.directory}</destDir> then handler xml is copied into the "target" folder directly with its package structure. So it works as expected. But it copies handler.xml file inside project directory (with its package structure)  if I use <destDir>${project.build.directory}/classes</destDir> ( which is default value for ${project.build.outputDirectory} ).
So it works as expected for any destDir option value except ${project.build.directory}/classes.
Is it a bug in the wsimport maven plugin or smth else ?

Created attachment 129608 [details]
wsdl file to test

I've attached wsdl file to test with.
Please evaluate.

I have no idea, sorry. Most likely has to do with inner workings of the plugin itself. Adding mgrebac@netbeans.org on CC, he appears to be one of the current developers of the plugin over at glassfish.

Adding Lukas, current plugin owner.

Works fine with updated maven-jaxws-plugin, version 2.3.
See bug 229913.

Likely, there was an issue with maven-jaxws-plugin, version 2.2