Thursday Nov 05, 2009

Servlet [ActivationCoordinatorPortTypeImpl] and Servlet [RegistrationPortTypeImpl] have the same url pattern

Last Friday while I was creating a web service client application using Glassfish V3 and Netbeans 6.8, I had come across this problem/exception.

SEVERE: Servlet [CoordinatorPortTypeImpl] and Servlet [CompletionCoordinatorPortTypeImpl] have the same url pattern: [/WSATCoordinator]
SEVERE: Exception while deploying the app
java.lang.IllegalStateException: Servlet [CoordinatorPortTypeImpl] and Servlet
[CompletionCoordinatorPortTypeImpl] have the same url pattern:
[/WSATCoordinator]at org.glassfish.apf.AnnotationInfo@15c9b76
       at
com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:478)
       at
com.sun.enterprise.deployment.archivist.Archivist.readAnnotations(Archivist.java:420)
       at
com.sun.enterprise.deployment.archivist.WebArchivist.postAnnotationProcess(WebArchivist.java:309)
       at
com.sun.enterprise.deployment.archivist.WebArchivist.postAnnotationProcess(WebArchivist.java:81)
       at
com.sun.enterprise.deployment.archivist.Archivist.readRestDeploymentDescriptors(Archivist.java:397)
       at
com.sun.enterprise.deployment.archivist.Archivist.readDeploymentDescriptors(Archivist.java:373)
       at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:238)
       at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:247)
       at com.sun.enterprise.deployment.archivist.Archivist.open(Archivist.java:208)
       at
com.sun.enterprise.deployment.archivist.ApplicationFactory.openArchive(ApplicationFactory.java:148)
       at ...

Actually I wanted to use some subclass of WebServiceFeature in my client program,but netbeans wrongly imported internal api classes instead of actual classes like com.sun.xml.internal.ws.developer.BindingTypeFeature instead of com.sun.xml.ws.developer.BindingTypeFeature.(This was due to metro has apis that are not in api package, nor are separated from the big implementation bundle)

So  I started renaming the wrongly imported classes to actual classes,but Netbeans editor showed classpath problems. So in order to overcome the problem, I added webservices-osgi.jar to netbeans clients projects compile time  libraries.Then when I tried to deploy the application, GF V3 throwed the above exception.

I reported this to Fabian and he told me this problem was because we have the WS-AT servlet code in webservices-osgi.jar and that is clashing with the WS-AT servlet that already comes with glassfish and this may be resolved in the next releases of Metro.

So for now the workaround is to add webservices-osgi.jar to the projects compile time libraries with out packaging them to the final war file that we deploy as shown below.

Note: The package check box is not selected .

Even then if problem persists , clean your project and then run.

About

This is my personal blog.All the information here reflects my own thoughts and feelings and should not be taken as official information from Oracle.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today