Archive deployment and seam component scanner problem ?

[powerware]

Hi,

I use
JBoss 4.0.3SP1
Postgresql 8.1
Seam beta1

I want to deploy an ear with

1 war archive
2 ejb3 archive
1 par archive

i put in every archive a seam.properties file in the log the scanner is scanning every archive.

but no component is retrieved.

When i put al the archive (2 ejb3 and 1 par) in the war archive all
component are retrieved

With beta 2 (cvs) the problem is the same.

What can possible be wrong with this setting.
I read that must be possible to use several archive.

Sergio

[matthew.edwards]

When I first started with Seam I tried using a par archive. I could never get it to work. Gavin said that it didn't look like the par archive was going to be a standard, so I just stopped using them.

I think the question is: can classes included in one ejb3/par archive access classes in another ejb3/par archive? Is there any difference in having more than one ejb3 archive?

[cesarizurieta]

I have no problems with this file structure:

app.ear
|-app.war
| |-...
|-app.jar
| |-...
|-app.ejb3
| |-seam.properties
| |-com/mycompany/SeamComponent1.class
| |-...
|-app.par
 |-seam.properties
 |-com/mycompany/SeamComponent2.class
 |-...

All components are correctly scanned.

[cesarizurieta]

One more thing. You need to define the ejb3s and the par in the application.xml like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
 "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
 "http://java.sun.com/dtd/application_1_3.dtd">
<application>
 <display-name>myapp</display-name>
 <module>
 <ejb>app.par</ejb>
 </module>
 <module>
 <ejb>app.ejb3</ejb>
 </module>
 <module>
 <web>
 <web-uri>app.war</web-uri>
 <context-root>/myapp</context-root>
 </web>
 </module>
</application>

[powerware]

My structure is the same .

i all archive which have seam components i included the emtpy seam.properties.

In my application.xml i included the archives and they are processed by JBoss.

I see in the log that seam is scanning the ejb3 and par archive

but it doesn't active my seam component.

Any clue ?

[liebner]

Any news on this one?

Same problem I run to, and everything is the greatest and latest :-)

When scanning my ejb3 file I only get these results:

14:24:47,859 INFO [Component] Component: org.jboss.seam.debug.contexts, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.debug.Contexts
14:24:47,875 INFO [Scanner] scanning: /C:/Programme/Java/jboss-4.0.4beta/server/default/tmp/deploy/tmp20806ServiceDictionary.ear-contents/ServiceDictionary.ejb3
14:24:47,937 INFO [Initialization] done initializing Seam

Nothing is bound and this all my jsf actions are going down the drain. I see that everything is fine for the booking example, but i can't see a difference.

Help greatly appreciated,
Stefan

[gavin.king]

Guys, we can't help with any problem we can't reproduce. Either

(1) If you think there is a bug in the scanner code, submit a simple runnable EAR to JIRA

(2) Figure out what is different between your code and the booking example

[amarinis]

I had a similar problem and found that the issue was that I included the jboss-seam.jar file in my WEB-INF/lib directory.

I removed the jar file from this directory and added the jboss-seam.jar file to the root folder of the ejb archive together with the seam.properties.

[gavin.king]

yes, its best to deploy the seam jar in the ejb3 jar or in the ear