[
https://issues.jboss.org/browse/JBIDE-7281?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen resolved JBIDE-7281.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since
it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or
create a new one mentioning/linking this jira for background information.
Thank you!
Wizards should not allow user to select unsupported JAX-WS spec
version
-----------------------------------------------------------------------
Key: JBIDE-7281
URL:
https://issues.jboss.org/browse/JBIDE-7281
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 3.2.0.Beta1
Reporter: Lukas Jungmann
Assignee: Feng Qian
Fix For: 3.3.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
-create a dynamic web project with target runtime set to JBossAS6-M5
-create a ws client there with JAX-WS spec set to 2.1 and finish the wizard
=> generated code is of JAX-WS version 2.2
default ws stack in JBossAS6-M5 does not seem to allow user to set JAX-WS spec version.
Even though the wsconsume's output says it is generating JAX-WS 2.1 code, it in fact
generates code of version 2.2
jlukas@lukas-laptop:~/latest/jboss-6.0.0.20100911-M5/bin$ ./wsconsume.sh --target=2.2 -o
/tmp/fff -k
http://footballpool.dataaccess.eu/data/info.wso?WSDL
Could not find log4j.xml configuration, logging to console.
WSConsume (CXF) does not allow to setup the JAX-WS specification target, using JAX-WS
2.1.
log4j:WARN No appenders could be found for logger
(org.apache.cxf.common.logging.LogUtils).
log4j:WARN Please initialize the log4j system properly.
Loading FrontEnd jaxws ...
Loading DataBinding jaxb ...
wsdl2java -compile -exsh false -d /tmp/fff -verbose -classdir /tmp/fff
-allowElementReferences
http://footballpool.dataaccess.eu/data/info.wso?WSDL
wsdl2java - Apache CXF 2.2.10
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira