Never mind. I just realized this is a silly question... since
say-hello.aar is not in web-inf/lib, it ain't gonna be in the runtime
classpath anyways. Will refactor my brain, and then my jar/aar approach.
Eoin
On Mon, 2011-05-23 at 14:41 -0400, Eoin O'Toole wrote:
> I have created a web application which contains an axis2 repository,
> which itself contains a web service (say-hello2.aar). say-hello2.aar
> contains a service.xml, and some stub classes which are generated from a
> wsdl.
>
> I include the generated say-hello2.aar in my web app, as follows:
>
> <dependency>
> <groupId>edu.mit.ist.es.etp-transcripts-web.ws-services</groupId>
> <artifactId>say-hello2</artifactId>
> <version>${project.version}</version>
> <type>aar</type>
> </dependency>
>
> All works well so far ( I can see the wsdl at
> http://localhost:8080/mywebapp/services/SayHello2?wsdl, and I can
> execute the web service skeleton code by navigating to
> http://localhost:8080/mywebapp/services/SayHello2/sayHello ).
>
> However..... I would like to use the generated source files within my
> web app (since I'm using these .aar files to delegate to business
> classes/spring beans in the app).
>
> But, when I try to do something like
> import edu.mit.transcripts.webservices.sayhello2.*;
> I get compile errors!!! (This package exists in the root of
> say-hello2.aar, but maven does not seem to be able to find classes or
> packages in say-hello2.aar at compile time).
>
> when I type mvn dependency:build-classpath the output shows that
> the .aar file in the repository is correct, and is being found. (The
> classes also show up in netbeans 7 dependency list....
>
> How do I get maven to look inside say-hello2.aar for the compile
> classpath?
>
> Thanks for any help.
>
> Eoin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
