[
https://issues.jboss.org/browse/WFLY-3851?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on WFLY-3851:
---------------------------------------
AFAICS, the ear that's generated by the build contains a bunch of libraries, including
the jaxws RI. If that's done on purpose (that is, you don't want to use the jboss
webservices stack), you should have a descriptor for disabling the webservices subsystem,
unless you have completely disabled it in your server configuration.
In any case, complete this jira description explaining what is not working while it
should, which error message you get if any, etc. Thanks.
WildFly 8.1 + JAX-WS and attaching Spring dependency
----------------------------------------------------
Key: WFLY-3851
URL:
https://issues.jboss.org/browse/WFLY-3851
Project: WildFly
Issue Type: Task
Components: EE
Affects Versions: 8.1.0.Final
Environment: Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
WildFly 8.1.0 Final
Spring 3.1.1
JAX-WS RI 2.2.8
Windows 7
Reporter: Dmitriy Shishmakov
Assignee: Alessio Soldano
I was made a prototype project 'maven-ws-prototype' for showing a trouble WildFly
8.1 with Spring 3.1.
This maven EAR project is contains 2 WebServices. I attached Spring dependencies In
'war' submodule. I don't use them in java classes.
Project has been successfully deployed into JBoss 7.1.1 but didn't deployed in
WildFly 8.1.
GitHub:
https://github.com/DmitriySh/maven-ws-prototype
If everything ok links might be invoke.
http://localhost:8080/jboss7-war/CalculatorImpl?wsdl
http://localhost:8080/jboss7-ejb/RandomGeneratorImpl/RandomGeneratorServi...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)