Hi Dan,
I noticed you are one of the developers of the jaxws-maven-plugin. I am
running into an issue and I wanted to run it by you. We are using JBoss4.2
with the JBossWS2.0.1GA (JAX-WS). In my POM I setup the JAX-WS dependencies
as follows:
<dependencies>
<!-- JAXB 2.1.5 API -->
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1.5</version>
<scope>provided</scope>
</dependency>
<!-- JAX-WS Annotations -->
<dependency>
<groupId>javax.jws</groupId>
<artifactId>jsr181-api</artifactId>
<version>1.0-MR1</version>
<scope>provided</scope>
</dependency>
<!-- JAX-WS 2.1.1 API -->
<dependency>
<groupId>javax.jws</groupId>
<artifactId>jaxws-api</artifactId>
<version>2.1.1</version>
<scope>provided</scope>
</dependency>
</dependencies>
Using the <scope>provided</scope> the JAR files are omitted from the
WEB-INF/lib directory (which is required by JBoss since it includes it's own
JAX-WS jars) and the webservice application deploys without a hitch on
JBoss4.2 with JBossWS2.0.1GA. My problem is I want to use the
jaxws-maven-plugin but it only works when the above mentioned dependencies
have either a scope of compile. Which adds the JAX-WS jars to the WEB/lib
directory of my WAR file and to my build classpath. Or, when I add the
jax-ws jar files to the endorsed directory of my JDK/JRE as such :
C:\Program Files\Java\jdk1.5.0_12\jre\lib\endorsed <directory>
Added jaxb-api.jar
Added jaxws-api.jar
Added jsr181-api.jar
Now the jaxws-maven-plugin works when I call a goal like package or install
with each execution running its set of jaxws-maven-plugin goals:
<build>
<finalName>${pom.artifactId}</finalName>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jaxws-maven-plugin</artifactId>
<executions>
<execution>
<id>SimpleWS</id>
<configuration>
<sei>com.heartlab.ws.services.SimpleWS</sei>
<!-- SOAP Version -->
<protocol>soap1.1</protocol>
<!-- <protocol>Xsoap1.2</protocol> -->
<!-- JAX-WS Version -->
<!-- <target>2.0</target> -->
<target>2.1</target>
<genWsdl>true</genWsdl>
<keep>true</keep>
<verbose>true</verbose>
</configuration>
<goals>
<goal>wsgen</goal>
<goal>wsimport</goal>
<goal>wsgen-test</goal>
</goals>
</execution>
<execution>
<id>HelloWS</id>
<configuration>
<sei>com.heartlab.ws.services.HelloWS</sei>
<!-- SOAP Version -->
<protocol>soap1.1</protocol>
<!-- <protocol>Xsoap1.2</protocol> -->
<!-- JAX-WS Version -->
<!-- <target>2.0</target> -->
<target>2.1</target>
<genWsdl>true</genWsdl>
<keep>true</keep>
<verbose>true</verbose>
</configuration>
<goals>
<goal>wsgen</goal>
</goals>
</execution>
</executions>
<!-- Specific version of JAXWS-Tools -->
<dependencies>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-tools</artifactId>
<version>2.1.1</version>
</dependencies>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-maven-plugin</artifactId>
<!-- Make this dynamic somehow to support multiple server
configurations -->
<configuration>
<jbossHome>${appserver.url}</jbossHome>
<port>${appserver.port}</port>
</configuration>
</plugin>
</plugins>
</build>
But when I attempt to run the goals independently i.e. 'mvn jaxws:wsgen -e'
I receive the following error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] One or more required plugin parameters are invalid/missing for
'jaxws:wsgen'
[0] inside the definition for plugin: 'jaxws-maven-plugin'specify the
following:
<configuration>
...
<sei>VALUE</sei>
</configuration>.
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring:
org.codehaus.mojo:jaxws-maven-plugin. Reason: Invalid or missing parameters
: [Mojo parameter [name: 'sei'; alias: 'null']] for mojo:
org.codehaus.mojo:jaxws-maven-plugin:1.6:wsgen
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:568)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginParameterException: Error
configuring: org.codehaus.mojo:jaxws-maven-plugin. Reason: Invalid or
missing param
eters: [Mojo parameter [name: 'sei'; alias: 'null']] for mojo:
org.codehaus.mojo:jaxws-maven-plugin:1.6:wsgen
at
org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters(DefaultPluginManager.java:907)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:612)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:421)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
Any ideas would be much appreciated!
Thanks,
Kyle
Dan Tran wrote:
>
> use multiple <execute>s
>
>
>
> On 9/19/07, Kyle.Bober <[EMAIL PROTECTED]> wrote:
>>
>> Is there a way to execute the generation of multiple WSDL files using
>> multiple jaxws-maven-plugin configurations via the jaxws-maven-plugin...
>> I
>> have yet to figure this out... Anyone out there have any success with
>> this?
>> --
>> View this message in context:
>> http://www.nabble.com/jaxws-maven-plugin-Multiple-SEI-%28Service-Endpoint-Implementations%29-tf4481299s177.html#a12778450
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> 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]
>
>
>
--
View this message in context:
http://www.nabble.com/jaxws-maven-plugin-Multiple-SEI-%28Service-Endpoint-Implementations%29-tf4481299s177.html#a12797391
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
