Skip to main content

GlassFish fails to deploy a JAX-WS service thinking it is a JAXRPC service

2 replies [Last post]
abhi0123
Offline
Joined: 2010-10-06
Points: 0

I am trying to deploy a Servlet based endpoint using a webservices.xml in GlassFish 3.1.2.2. webservices.xml file could be used to augment or override existing JAX-WS annotations. However, GlassFish throws an error:
Service TimeService seems to be a JAXRPC based web service but without the mandatory WSDL and Mapping file. Deployment cannot proceed.

What surprises me is that several people have reported having this problem since GlassFish 2. However no one seems to have created a Jira and no one from the GlassFish Dev team has attempted to fix it.

Maven project attached. I have also created a JIRA bug report but in my experience, they are usually slow to respond.
http://java.net/jira/browse/GLASSFISH-19366

AttachmentSize
jaxws-servlet-container.zip4.01 KB

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Glen Mazza

Perhaps it's your project's structure? Links #2 and #3 here:
http://www.jroller.com/gmazza/entry/blog_article_index, both Mavenized
projects, work fine for Metro, at least on Tomcat.

HTH,
Glen

On 11/22/2012 04:17 PM, forums@java.net wrote:
> I am trying to deploy a Servlet based endpoint using a webservices.xml in
> GlassFish 3.1.2.2. webservices.xml file could be used to augment or
> override
> existing JAX-WS annotations. However, GlassFish throws an error: Service
> TimeService seems to be a JAXRPC based web service but without the
> mandatory
> WSDL and Mapping file. Deployment cannot proceed. What surprises me is
> that
> several people have reported having this problem since GlassFish 2.
> However
> no one seems to have created a Jira and no one from the GlassFish Dev
> team
> has attempted to fix it. Maven project attached.
>

abhi0123
Offline
Joined: 2010-10-06
Points: 0

forumguest wrote:
Perhaps it's your project's structure? Links #2 and #3 here:

There's nothing wrong with my project structure, it's a perfectly valid Maven project. If you see something wrong, I'll be very interested in knowing what it is. Otherwise, with all due respect, I don't need a link to another Web Service blog that has nothing in common with this particular problem.