Found the issue - nothing to do with CXF dependencies at all, rt.jar wasn't
'accessible' so code completion didn't work and I thought it was a
dependency problem.
It seems that starting a bare bones maven project without archetype
configures the project vs a specific J2SE version in STS. You need to
configure Build Path, Libraries, and change the execution environment to the
workspace default. (sonatype maven plugin 0.12).
Thanks both.
-----Original Message-----
From: Glen Mazza
Sent: Wednesday, August 03, 2011 4:57 PM
To: users@cxf.apache.org
Subject: Re: Maven dependency for javax.jws.WebService
I don't think you want to include the CXF simple frontend dependency; my
Java-first tutorial is using the other two dependencies along with the
@WebService annotation:
http://www.jroller.com/gmazza/entry/java_first_web_service
Glen
On 08/03/2011 11:44 AM, David G wrote:
Hi,
I’m trying to create a bare-bones service from scratch using Maven but can’t
seem to get the jax-ws API from the CXF dependencies. Without it I can’t
add the @WebService dependency.
What is the most appropriate CXF artifact to use to pick this up
(transitively would be fine)? Here is what I have at the moment:
<properties>
<cxf.version>2.4.1</cxf.version>
</properties>
<dependencies>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-simple</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-transports-http</artifactId>
<version>${cxf.version}</version>
</dependency>
</dependencies>
Thanks
--
Glen Mazza
Talend - http://www.talend.com/ai
Blog - http://www.jroller.com/gmazza
Twitter - glenmazza