Back in March 2010 I wrote about our JBossWS Maven plugin for running JAXWS tools (wsconsume and wsprovide). The plugin allows embedding tools' invocation into user Maven projects, so that given a wsdl contract you can e.g. automatically generate stub classes and interfaces for a ws endpoint you want to implement or for an endpoint you want to build a client for.
Yesterday I cut a micro 1.1.1.Final release of the plugin (org.jboss.ws.plugins:maven-jaxws-tools-plugin), which is available on the usual JBoss Maven repository. You're welcome to go and try it.
On that purpose, I've written a small sample project showing how a user project can actually use the wsconsume plugin. It's available on the wiki, have a look and see how easy it's to use it! :-)
JBossWS 5.4.0.FInal is released !
I am pleased to annouce JBossWS 5.4.0 Final is out. In this release we upgraded many components as usual and brings Elytron client configur...
-
After some micro bug fix releases on the 5.1 stream, JBossWS 5.2.0.Final has eventually been released . The latest versions brings a lot o...
-
JBoss Application Server 7 is highly configurable and allows for running different profiles , including one or more subsystems . The optio...
-
One of the goals I committed to when I joined the JBoss Web Services project back in 2007 was to improve the JBossWS tooling offer and poss...
4 comments:
I can't get wsconsume to work using EAP 6.0.1 (using jbossws cxf stack that comes w/ the eap repo:
org.jboss.ws.cxf
jbossws-cxf-client
4.0.6.GA-redhat-2
provided
Complains about gnu-getopt not found. I see it in the eap repo but only as "-redhat-x" instead of just version 1.0.13. For some reason it won't take the public one and requires that this version 1.0.13 must be downloaded only from eap repo. Any suggestions? I have similar ticket w/ redhat on the issue.
Daniel,
sorry for the late processing of your comment. Can you let me know the ticket you opened at Red Hat for the issue and / or post on the JBossWS user forum with more details on the issue / error you get? I'd like to understand if this is something that can be worked around with maven exclusions / inclusions and if it's reproducible in the testsuite for EAP. Btw, is this still a problem with EAP 6.1 or greater?
I've never had so much trouble getting a Maven plugin to work. Dependency hell!
1.1.1.Final is the only version of this plugin I could find in the Maven Nexus repository. Sadly I get an error running it (missing dependencies).
~ Jono,
you can see the available versions on Nexus repo at https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/ws/plugins/maven-jaxws-tools-plugin/ .
Regarding the error you're getting, can you provide any detail?
Alessio
Post a Comment