[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Richard Opalka updated JBAS-8403: --------------------------------- Attachment: jaxws-jbws3123.ear Providing archive to reproduce the problem. Just copy this archive to deploy directory and enter the following URL to your favourite browser http://localhost:8080/jaxws-jbws3123-web/ServletTest The issue is considered fixed if you'll get 'hello' message on the page ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Richard Opalka updated JBAS-8403: --------------------------------- Summary: <service-ref> element specified in jboss-web.xml is ignored for annotation driven servlets (was: <service-ref> element specified in jboss-web.xml is ignored) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat commented on JBAS-8403: -------------------------------------- org.jboss.web.deployers.WarAnnotationMetaDataDeployer produces a WebMetaData (equivalent to web.xml) that is attached as different names depending on where they come from (look at the class to get a better idea). It does not produce a JBossWebMetaData. Note: There is no fragment involved here. Are you sure the @WebServiceRef and other annotations are processed correctly ? Normally, there's no difference in metadata between the "real" servlet metadata from web.xml and the servlet metadata from the annotation. Things then all get merged together in MergedJBossWebMetaDataDeployer, which produces the final JBossWebMetaData that you should use. So another option is that you may not be using the right metadata object to create your web services ? Right when deploying, I can see the non working version: 15:28:21,057 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] Creating Service {http://Echo.org}EchoService from WSDL: vfs:/home/remm/Work/jbossas-6/build/target/jboss-6.0.0-SNAPSHOT/server/all/deploy/jaxws-jbws3123.ear/jaxws-jbws3123-web.war/WEB-INF/wsdl/EchoService.wsdl And the working one: 15:31:32,833 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] Creating Service {http://Echo.org}EchoService from WSDL: http://localhost:8080/jaxws-jbws3123-ejb/EchoBean?WSDL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat commented on JBAS-8403: -------------------------------------- Your WS metadata should be in attachment key "annotated."+WebMetaData.class.getName()+":classes". I suppose it's there since the web service works. However, either the overriding (done in MergedJBossWebMetaDataDeployer) does not work, or the web service is created from metadata somewhere else. BTW, JBoss Web is doing nothing at all in this stuff, but the problem could be in AS server module, or metadata, or maybe the web service is created from some other metadata somewhere else. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Richard Opalka commented on JBAS-8403: -------------------------------------- I confirm that if there's now web.xml in .war then JBossWebAppParsingDeployer isn't executed at all (although there's jboss-web.xml provided) :( I was playing little bit with JBossWebAppParsingDeployer inputs (no success). This deployer should be executed even if there's no web.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat commented on JBAS-8403: -------------------------------------- No success either dropping the setInput(WebAppMetaData) (or making it addInput(WebAppMetaData)) from JBossWebAppParsingDeployer, it then causes weird problems. I agree that JBossWebAppParsingDeployer should run even if there is no WebAppMetaData, those are two distinct descriptors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat updated JBAS-8403: --------------------------------- Priority: Critical (was: Blocker) Moving down to critical, since it is very easy to work around (if you configure jboss-web.xml, make sure you add a web.xml with <web-app /> if there's none. Still no real idea on how to fix the issue, straightforward solutions failed so far. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Richard Opalka reassigned JBAS-8403: ------------------------------------ Assignee: Richard Opalka (was: Remy Maucherat) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8403?page=com.atlassian.jira.plugin.sy... ] Remy Maucherat commented on JBAS-8403: -------------------------------------- Nice, that filter on .war would allow removing the setInput(WebMetaData) that was causing the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira