Foren

Home » Liferay Portal » English » 3. Development

Kombinierte Ansicht Flache Ansicht Baumansicht
Threads [ Zurück | Nächste ]
toggle
Ajith Mathews C
build-wsdd goal not able to find classes in service archetype project
30. April 2012 20:37
Antwort

Ajith Mathews C

Rang: New Member

Nachrichten: 1

Eintrittsdatum: 13. April 2012

Neue Beiträge

Hi,

I have a project called as manager which is using the liferay service builder archetype. So basically this would contain the manager-portlet & manager-portlet-service modules. I am able to build the service using the goals liferay:build-service. This goal does not generate the wsdd file. I found that there is another goal used for creating the wsdd file, which is com.liferay.maven.plugins:liferay-maven-plugin:6.1.0:build-wsdd.

I am getting an exception, stating that its not able to find the class file for xyz. The xyz.java class is part of the manager-portlet-service module. I tried including the service jar into the portlet project dependencies section.

Any suggestions on how to make the .class available of the service module available to portlet project? service module generates a jar file as its output.
Ramon Garcia
RE: build-wsdd goal not able to find classes in service archetype project
23. Oktober 2012 04:28
Antwort

Ramon Garcia

Rang: New Member

Nachrichten: 11

Eintrittsdatum: 11. Februar 2010

Neue Beiträge

Hi,

I have the same problem... anyone know how to solve it??

Thks.
Amit Doshi
RE: build-wsdd goal not able to find classes in service archetype project
13. Februar 2013 01:37
Antwort

Amit Doshi

Rang: Liferay Master

Nachrichten: 543

Eintrittsdatum: 29. Dezember 2010

Neue Beiträge

Hi Guys,

I am facing same issue in maven based project.

Have you guys found any soulution for this?

Thanks & Regards,
Amit Doshi
Ramon Garcia
RE: build-wsdd goal not able to find classes in service archetype project
13. Februar 2013 23:07
Antwort

Ramon Garcia

Rang: New Member

Nachrichten: 11

Eintrittsdatum: 11. Februar 2010

Neue Beiträge

Hi... for resolve it...
The problem is when you run the generate-wsdd, in the service module, it can't find the serviceBuilder impl classes... to resolve it "easily" I do:
1. - "Copy impl classes from module project to service module"
2. - Do Package
3. - Generate wsdd
4. - Remove impl classes from service module
5 - Do package ... install...
With theses simple steps ... I solved the problem ... I hope you find it useful!
Amit Doshi
RE: build-wsdd goal not able to find classes in service archetype project
14. Februar 2013 05:18
Antwort

Amit Doshi

Rang: Liferay Master

Nachrichten: 543

Eintrittsdatum: 29. Dezember 2010

Neue Beiträge

Thanks for the quick reply Ramon.

I stuck at point

3- Generate wsdd.

I tried this command mvn liferay:build-wsdd -DserverConfigFileName=fileC://server-config.wsdd -DserviceFileName=C://service.xml -X

It gives me below error.

 1
 2
 3Loading jar:file:/C:/Documents%20and%20Settings/amit.doshi/.m2/repository/com/liferay/portal/portal-impl/6.1.20/portal-impl-6.1.20.jar!/portal.properties
 4[INFO] ------------------------------------------------------------------------
 5[INFO] BUILD FAILURE
 6[INFO] ------------------------------------------------------------------------
 7[INFO] Total time: 9.016s
 8[INFO] Finished at: Thu Feb 14 18:47:07 IST 2013
 9[INFO] Final Memory: 8M/34M
10[INFO] ------------------------------------------------------------------------
11[ERROR] Failed to execute goal com.liferay.maven.plugins:liferay-maven-plugin:6.1.20:build-wsdd (default-cli) on project mexico-application-portlet-service: fileC:\server-config.wsdd (The filename, directory name, or volume label syntax is incorrect) -> [Help 1]
12org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.liferay.maven.plugins:liferay-maven-plugin:6.1.20:build-wsdd (default-cli) on project mexico-application-portlet-service: fileC:\server-config.wsdd (The filename, directory name, or volume label syntax is incorrect)
13        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
14        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
15        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
16        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
17        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
18        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
19        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
20        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
21        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
22        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451)
23        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188)
24        at org.apache.maven.cli.MavenCli.main(MavenCli.java:134)
25        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
26        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
27        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
28        at java.lang.reflect.Method.invoke(Method.java:597)
29        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
30        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
31        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
32        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
33Caused by: org.apache.maven.plugin.MojoExecutionException: fileC:\server-config.wsdd (The filename, directory name, or volume label syntax is incorrect)
34        at com.liferay.maven.plugins.AbstractLiferayMojo.execute(AbstractLiferayMojo.java:72)
35        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
36        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
37        ... 19 more
38Caused by: java.io.FileNotFoundException: fileC:\server-config.wsdd (The filename, directory name, or volume label syntax is incorrect)
39        at java.io.FileOutputStream.open(Native Method)
40        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
41        at com.liferay.portal.util.FileImpl.write(FileImpl.java:789)
42        at com.liferay.portal.util.FileImpl.write(FileImpl.java:768)
43        at com.liferay.portal.util.FileImpl.write(FileImpl.java:764)
44        at com.liferay.portal.util.FileImpl.write(FileImpl.java:805)
45        at com.liferay.portal.kernel.util.FileUtil.write(FileUtil.java:328)
46        at com.liferay.portal.tools.WSDDBuilder.build(WSDDBuilder.java:60)
47        at com.liferay.maven.plugins.WSDDBuilderMojo.doExecute(WSDDBuilderMojo.java:33)


It would it be great help. if you attach your pom.xml and also the command that you used to generate wsdd.

Thanks & Regards,
Amit Doshi
Ramon Garcia
RE: build-wsdd goal not able to find classes in service archetype project
18. Februar 2013 04:52
Antwort

Ramon Garcia

Rang: New Member

Nachrichten: 11

Eintrittsdatum: 11. Februar 2010

Neue Beiträge

Hi Amit,

Can you try:
mvn liferay:build-wsdd
Executing it inside the portlet project?
I do it without the use of the params...
Hope it helps...
Alexey Kakunin
RE: build-wsdd goal not able to find classes in service archetype project
11. März 2013 10:02
Antwort

Alexey Kakunin

Rang: Expert

Nachrichten: 370

Eintrittsdatum: 7. Juli 2008

Neue Beiträge

Hi!

I've added bug for this problem into JIRA: http://issues.liferay.com/browse/MAVEN-69?focusedCommentId=278393#comment-278393

But after investigating how class-loader working in plugin (at least in 6.1.1-SNAPSHOT version) - I found what portlet/target/classes is added into classpath, so, to make build-wsdd working we just need compile generated classes.

To do it we can call mvn target after liferay:build-service but before liferay:build-wsdd

==
Alexey Kakunin
EmDev Limited
Amit Doshi
RE: build-wsdd goal not able to find classes in service archetype project
13. März 2013 00:09
Antwort

Amit Doshi

Rang: Liferay Master

Nachrichten: 543

Eintrittsdatum: 29. Dezember 2010

Neue Beiträge

Hi Alexey,

Thanks for creating the ticket. I am also facing same issue.

As my project is going through tough times and I can't able to find the solution for it . So, I have to migrate it into ANT as I am not so good in MAVEN.

I will give a try as per your above comment and check it whether it is working or not.

Thanks & Regards,
Amit Doshi
Ron J
RE: build-wsdd goal not able to find classes in service archetype project
19. Juni 2014 02:30
Antwort

Ron J

Rang: Junior Member

Nachrichten: 42

Eintrittsdatum: 18. November 2012

Neue Beiträge

Alexey Kakunin:
Hi!

I've added bug for this problem into JIRA: http://issues.liferay.com/browse/MAVEN-69?focusedCommentId=278393#comment-278393

But after investigating how class-loader working in plugin (at least in 6.1.1-SNAPSHOT version) - I found what portlet/target/classes is added into classpath, so, to make build-wsdd working we just need compile generated classes.

To do it we can call mvn target after liferay:build-service but before liferay:build-wsdd

==
Alexey Kakunin
EmDev Limited



This fix worked for me on the first build-wsdd but after making mods to the services and rerunning build-service I cannot get build-wsdd to work anymore. Has anyone experienced this?