Skip to main content

Java.net Maven 2 repo problems

4 replies [Last post]
davidmatheson
Offline
Joined: 2007-06-26
Points: 0

Hey, all. I have a Maven 2 project which is complaining that it can't get to jaxws-rt.jar in http://download.java.net/maven/2/com/sun/xml/ws/. Sure enough, I go to that directory and the only thing there is a "policy" directory. Am I using the wrong package (com.sun.xml.ws)? Is something wrong with the repo? Any help would be appreciated.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davidmatheson
Offline
Joined: 2007-06-26
Points: 0

Slowly progressing... Added jsr181-api-1.0-MR1.jar to the plugin dependency, as well as the project dependency. The jaxws-maven-plugin documentation states that it "(r)equires dependency resolution of artifacts in scope: runtime". Why is this? I don't want jsr181-api-1.0-MR1.jar in the WEB-INF/lib directory, so I should be able to label these as "provided", but it throws an error. I am new to Maven, does the "provided" scope mean something different? I thought it meant, "I need this library to compile, but I don't need to deploy it".

davidmatheson
Offline
Joined: 2007-06-26
Points: 0

Ok, so I added the Maven 1 repository along side the Maven 2 repository, and told it to use the Maven 1 layout, and some things got resolved. The next thing is that jaxws-maven-plugin bombs out when I try to do a wsimport on a WSDL I'm using. The error is at the end of the post. What dependency do I have to add for javax.jws.WebParam?

java.lang.NoClassDefFoundError: javax/jws/WebParam$Mode
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.getParameterOrder(WSDLModeler.java:2554)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processLiteralSOAPOperation(WSDLModeler.java:766)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processSOAPOperation(WSDLModeler.java:703)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processPort(WSDLModeler.java:471)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.processService(WSDLModeler.java:251)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:221)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:133)
at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:182)
at org.codehaus.mojo.jaxws.WsImportMojo.wsImport(WsImportMojo.java:274)
at org.codehaus.mojo.jaxws.WsImportMojo.processWsdlViaUrls(WsImportMojo.java:261)
at org.codehaus.mojo.jaxws.WsImportMojo.execute(WsImportMojo.java:189)
at org.codehaus.mojo.jaxws.MainWsImportMojo.execute(MainWsImportMojo.java:15)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
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:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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)

whitfordny
Offline
Joined: 2006-09-24
Points: 0

Can somebody elaborate as to why artifacts are available only on the Maven1 repository instead of the Maven2 repository? Most people are using Maven2 these days -- I would expect that it would be where the latest and greatest artifacts would reside, but the Maven1 repo seems to have an abundance of jars...

bbonner
Offline
Joined: 2003-06-13
Points: 0

Yes, it' seems silly. I'm trying to find the JSF 1.2 and EL 1.2 jars and apis but they're only in the maven/1/ repo. I posted a msg to Ed Burns.