JBossDeveloper

I was able to easily fix this by adjusting the ear file to the following. notice the lib/ before the jboss-seam.jar.

<application>
 <display-name>Seam Shell</display-name>

 <module>
 <web>
 <web-uri>tutorialWeb.war</web-uri>
 <context-root>/tutorial</context-root>
 </web>
 </module>
 <module>
 <java>lib/jboss-seam.jar</java>
 </module>
 <module>
 <ejb>tutorialEJB.jar</ejb>
 </module>
 <module>
 <java>lib/jbpm-3.1.1.jar</java>
 </module>
</application>

(to be clearer, its the application.xml file)

I did it, and it still says:

org.jboss.deployment.DeploymentException: Failed to find module file: lib/jboss-seam.jar

"karakal" wrote:
I have this error with Eclipse 3.2, Jboss 4.0.4GA, the newest version of Seam and seam-gen:

11:45:08,510 ERROR [MainDeployer] Could not initialise deployment: file:/home/lah/jboss-4.0.4.GA/server/default/deploy/sample.ear
org.jboss.deployment.DeploymentException: Failed to find module file: jboss-seam.jar

What is wrong here?

WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=sampleEJB.jar
java.lang.RuntimeException: Interceptor class not found: org.jboss.seam.ejb.SeamInterceptor

Hi, shundavid!

I just removed the entries for jboss-seam.jar and jbpm-xxx.jar from application.xml.

Make sure the two jar files appear in your EarContent directory (for some reason they first did not in my project).

There is also a configuration option in "properties (context menu)" --> "J2EE Module Dependencies" where you can remove the two.
Just play around with these two options, after some trials, I had success.
Good luck!

Also, in step #5 screenshot of build.properties it shows the variables entered in seam set-properties step. However, my build.properties only has the jboss.home property.

How do you get the other properties generated?
Can you manually add them? If so, do you have to rerun any steps?

You don't need to. The file shown there is the build.properties file in seam-gen, only used to create your project and, afterwards, actions etc. I was mislead by the open file, too.

The build.xml AND build.properties in your wtp-project will not be used and it cannot be used, because it is the build.xml for the "normal" project structure without wtp (with "view", "resources" , ... directories). There is not (yet) a build file for the WTP project structure, you have to rely on eclipse building and publishing your project.

So, I took a fresh start with seam-gen's tutorial this morning. I followed the tutorial steps; got the same jboss-seam.jar not found and followed japplicoon's suggestion with application.xml & properties. Here's what worked for me:

1. In sampleEJB > J2EE Module Dependencies select both jboss-seam.jar & jbpm-3.1.2.jar
2. In sample > EarContent>META-INF>application.xml, remove:

jboss-seam.jar


jbpm-3.1.2.jar

3. Deploy and look at the sample.ear. It should now contain the two JAR files mentioned above and be 1.38MB.


Now, the server starts up for me; however, when I go to http://localhost:8080/sample/ I get the following error:

09:17:17,859 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 59s:672ms
09:17:44,015 INFO [Events] no events.xml file found
09:17:44,250 INFO [STDOUT] SHELLFLOW METHOD HIT!!!
09:17:44,265 ERROR [ExceptionInterceptor] redirecting to debug page
java.lang.ClassCastException: org.jboss.seam.example.pageflow.SimpleFlow$$EnhancerByCGLIB$$66779c68
 at org.jboss.seam.core.Pageflow.instance(Pageflow.java:65)
 at org.jboss.seam.interceptors.ConversationInterceptor.beginNavigation(ConversationInterceptor.java:210)
 at org.jboss.seam.interceptors.ConversationInterceptor.beginConversation(ConversationInterceptor.java:196)
 at org.jboss.seam.interceptors.ConversationInterceptor.beginConversationIfNecessary(ConversationInterceptor.java:128)
 at org.jboss.seam.interceptors.ConversationInterceptor.endOrBeginLongRunningConversation(ConversationInterceptor.java:61)

Hi,hatcheck
I got same problems with you.And I did the same actions with yours,but with the first step i took it on the sampleWeb.When I run it,I didn't see any error message.Good luck

Calling WTP is a little bit flakey is like calling Ubuntu a little bit brown. I've actually given up on WTP's crummy "publish" mechanism and gone and written a shell script to jar up and deploy the ear by hand. And unlike WTP's mouse-only (afaict) interface for manual publish, I can just make the script an external tool launch configuration and bind it to a key.

Still, thanks for the info on doing it within eclipse.

The MyEclipse publish is pretty good.

The new documentation works perfect, Thanks!.

You guys look into fixing the Reverse Engineering demo too

Who was the guy that planned to write a build.xml for the WTP-structure? That would be the nicest way for me, since I really don't want to refactor the whole project back to the "seam-structure" ...
While upgrading Jboss I seem to have secured the jmx console such that the shutdown script needs username and password ... hmm, how to teach eclipse to use stop arguments? WTP IS confusing !