[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12393273 ] sushmu commented on JBSEAM-2371: -------------------------------- The main problem is the library mismatch and classpath issues. A working maven example with the seam distribution would greatly help. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12395435 ] Siarhei Dudzin commented on JBSEAM-2371: ---------------------------------------- Please, use the following attachment (used for JBoss Tools): http://jira.jboss.org/jira/secure/attachment/12316955/test-project-JBIDE-... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12396294 ] Siarhei Dudzin commented on JBSEAM-2371: ---------------------------------------- Btw, it seems that integration tests partly seem to work with maven 2.0.8 (also jdk 1.5) only if I remove jboss embedded from test classpath! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12396657 ] Anne Chou commented on JBSEAM-2371: ----------------------------------- Removing the jboss embedded jars from the test classpath causes problems if deploying an EJB for testing. Using Maven 2.0.8 with surefire plugin 2.4 and TestNG 5.6 fails to find the DataSource at this line of the SeamTest code: EntityManagerFactory emf = Persistence.createEntityManagerFactory("test_database"); even though the persistence unit "test_database" is properly defined in persistence.xml and points to the DefaultDS. (Default bootstrap files deploy\hsqldb-ds.xml, embedded-jboss-beans.xml, etc. are all in the test classpath) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12396681 ] Anne Chou commented on JBSEAM-2371: ----------------------------------- That makes sense. But, just to clarify my last comment, removing the embedded jar from my test classpath caused exceptions because EJB3 is expecting the embedded container in order to deploy correctly. The DataSource error (above) occurs when running with the jboss-embedded-all.jar included in the test classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=all ] Pete Muir updated JBSEAM-2371: ------------------------------ Component/s: Build Test Harness -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12399029 ] Siarhei Dudzin commented on JBSEAM-2371: ---------------------------------------- Besides the JBoss Embedded problem, this issue also depends (this concerns mostly IDE support as SureFire plugin manages to put JBoss Embedded *-all jars in the right place) on resolutions of the following issues: http://jira.codehaus.org/browse/MNG-1412 - once this fixed the classpath will be much more predictable http://jira.codehaus.org/browse/MECLIPSE-294 introduced alphabetical sorting order for eclipse classpath (maven-eclipse-plugin allows to generate eclipse projects based on project pom.xml). To address MECLIPSE-294 when maven 2.0.9 comes out I've created http://jira.codehaus.org/browse/MECLIPSE-388 which should rollback MECLIPSE-294 to default dependencies ordering (which should be ok because maven 2.0.9 will have MNG-1412). Until then if you want to run integration tests in eclipse for projects created from maven you would need to manually re-order JBoss Embedded libraries and put all the '*-all' jars in the first place (or give them ugly names so that the alphabetical order puts them in the first place). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12399059 ] Siarhei Dudzin commented on JBSEAM-2371: ---------------------------------------- Actually a JBoss team (JBoss Build System) also identified classpath ordering issue (but probably for other reasons) at JBBUILD-417 which leads to http://jira.codehaus.org/browse/MNG-3197 which in turn duplicates MNG-1412 which I mentioned above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12410515 ] Hemant Saxena commented on JBSEAM-2371: --------------------------------------- I am able to successfully perform intregrated testing for seam components with jboss embedded container under my production mavenized project. Key to work is the separate inclusion of jboss-embedded dependency. Here are the details: We have parent POM and sub POMs structure in our project. In parent POM, include: ==================== Step1: <!-- JBoss Seam Test --> <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <version>5.7</version> <classifier>jdk15</classifier> </dependency> </dependencies> </dependencyManagement> Step2: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.4.2</version> </plugin> </plugins> </pluginManagement> In the ejb/POM: ============ Step1: <!-- TestNG --> <dependency> <groupId>org.testng</groupId> <artifactId>testng</artifactId> <scope>test</scope> <classifier>jdk15</classifier> </dependency> <dependency> <groupId>javax.el</groupId> <artifactId>el-api</artifactId> <scope>test</scope> </dependency> <!-- JBoss EJB3 Microcontainer for testing --> <dependency> <groupId>org.jboss.embedded</groupId> <artifactId>jboss-embedded-all</artifactId> <version>beta3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.embedded</groupId> <artifactId>jboss-embedded-all</artifactId> <version>beta3</version> <exclusions> <exclusion> <groupId>org.jboss.embedded</groupId> <artifactId>jboss-embedded</artifactId> </exclusion> <exclusion> <groupId>org.jboss.microcontainer</groupId> <artifactId>jboss-deployers-client-spi</artifactId> </exclusion> <exclusion> <groupId>org.jboss.microcontainer</groupId> <artifactId>jboss-deployers-core-spi</artifactId> </exclusion> </exclusions> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.embedded</groupId> <artifactId>hibernate-all</artifactId> <version>beta3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.embedded</groupId> <artifactId>thirdparty-all</artifactId> <version>beta3</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.embedded</groupId> <artifactId>jboss-embedded</artifactId> <version>beta3</version> <scope>test</scope> <exclusions> <exclusion> <groupId>org.jboss.microcontainer</groupId> <artifactId>jboss-deployers-client-spi</artifactId> </exclusion> </exclusions> </dependency> step2: <plugins> <plugin> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <configuration> <artifactItems> <artifactItem> <groupId>org.jboss.embedded</groupId> <artifactId>jboss-embedded-bootstrap</artifactId> <type>zip</type> <version>beta3</version> </artifactItem> </artifactItems> <outputDirectory>${project.build.testOutputDirectory}</outputDirectory> </configuration> <id>download-embedded-jboss-bootstrap</id> <phase>process-test-resources</phase> <goals> <goal>unpack</goal> </goals> </execution> <execution> <configuration> <artifactItems> <artifactItem> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <version>2.1</version> </artifactItem> </artifactItems> <outputDirectory>${project.build.testOutputDirectory}/endorsed</outputDirectory> </configuration> <id>download-jaxb-api</id> <phase>process-test-resources</phase> <goals> <goal>copy</goal> </goals> </execution> </executions> Step 3: </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <suiteXmlFiles> <suiteXmlFile>src/test/java/com/autotrader/adsinvmgr/testng.xml</suiteXmlFile> </suiteXmlFiles> <additionalClasspathElements> <additionalClasspathElement>${project.build.testOutputDirectory}/bootstrap</additionalClasspathElement> </additionalClasspathElements> <childDelegation>true</childDelegation> <useSystemClassLoader>true</useSystemClassLoader> <argLine>-Djava.endorsed.dirs=${project.build.testOutputDirectory}/endorsed -Dsun.lang.ClassLoader.allowArraySyntax=true</argLine> </configuration> </plugin> You dont need to do argLine inclusion if you are using jdk5. It only requires for jdk6. Then start writing your test cases under (src/test/java) as defined in Seam Docs ( extending SeamTest). PS: when surefire plugin execute testng, it has the following output folders defined for classpath: - ejb/target/classes - ejb/target/test-classes so files/folders like meta-inf/persistence.xml, seam.properties comes from ejb/classes. We dont need to add them seperately. Please feel free to contact me for template project or for any further questions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=all ] Hemant Saxena updated JBSEAM-2371: ---------------------------------- Attachment: maven-seam-microcontainer-testng-template.zip This is the snapshot of the working code which demonstrate mavenized project for seam, richfaces, reporting, surefire, testng, seam microcontainer and jboss embedded. This is loaded for reference on how to layout your poms. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12410590 ] Hemant Saxena commented on JBSEAM-2371: --------------------------------------- Attached is the reference snapshot of the our mavenized project. - It neatly describe the dependency artifact for seam, richfaces combo; and other required conf files - It neatly describe the dependency requires to invoke surefire --> which invoke testng -- which invoke SeamTest --> which bootstrap jboss embeddable container (this will provide JTA, JNDI and other stuff) and the seam microcontainer (this initialize seam components). What I understand that we (including me) were able to bootstrap seam microcontainer but wasnt able to bootstrap jboss embedded container along because of the dependencies issues. And thats the reason why JNDI env wasnt available and we werent able to deploy -ds.xml files which lead to non-instantiating EntityManager through Components.xml. The solution I gave in the earlier comment just exactly solve the dependency issues which lead to successful bootstrap of jboss embeddable container and seam was able to inject entitymanager into its components. I tried some basic navigation stuff and security stuff and it works. if you need more stuff to be loaded like navigation, jbpm and all , you need to get it copied to <project>/test-classes path inorder to get it picked up by seam microcontainer. Please refer to template project on how things has been laid out. I have not included the eclipse project files because that you can easily generate those by following command: $maven eclipse:eclipse or (using wtpversion version) $mvn -Dwtpversion=1.5 eclipse:eclipse -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12414728 ] Jason Grant commented on JBSEAM-2371: ------------------------------------- Just as a courtesy to those that follow, I'm not sure whether attachment #1 was ever tested. I'm working through it, and it is clearly not operational in the form submitted. So far, I've found the following: 1) The parent to the top-level pom was not shipped. Once can be made from the content of org.jboss.seam:root:pom:2.1.0.A1 2) The xxx group names are internally, inconsistent and require a fix. 3) The deploy module referenced from the top pom is not present. I am hoping that it is not required. 4) A seam.version property must be set. 5) I removed the coupling to oracle.ojbc14 6) Java does not compile due to absent import for SearchQueryCriterion I am still progressing with this, however these are the anomolies found so far. An operational submission would be most appreciated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12414733 ] Jason Grant commented on JBSEAM-2371: ------------------------------------- I've also tested attachment #2, even though some of the dependency versions seem old now. If I understand comment http://jira.jboss.org/jira/browse/JBSEAM-2371#action_12406363 Comment [2] suggests that TestNG tests should be working via 'mvn test' in the web pom. Doesn't work for me. I get the exception below. Hopefully, this is due to a misunderstanding on my part. Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: [Ljavax/el/ELResolver;; nested exception is java.lang.NoClassDefFoundError: [Ljavax/el/ELResolver; java.lang.NoClassDefFoundError: [Ljavax/el/ELResolver; at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.testng.internal.annotations.AnnotationHelper.findMethodsWithAnnotation(AnnotationHelper.java:197) at org.testng.internal.TestNGMethodFinder.getTestMethods(TestNGMethodFinder.java:47) at org.testng.TestClass.initMethods(TestClass.java:132) at org.testng.TestClass.init(TestClass.java:96) at org.testng.TestClass.<init>(TestClass.java:61) at org.testng.TestRunner.initMethods(TestRunner.java:288) at org.testng.TestRunner.init(TestRunner.java:212) at org.testng.TestRunner.init(TestRunner.java:184) at org.testng.TestRunner.<init>(TestRunner.java:121) at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:376) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:196) at org.testng.SuiteRunner.run(SuiteRunner.java:145) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:901) at org.testng.TestNG.runSuitesLocally(TestNG.java:863) at org.testng.TestNG.run(TestNG.java:613) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:136) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) 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:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Caused by: java.lang.ClassNotFoundException: javax.el.ELResolver at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12414774 ] Jason Grant commented on JBSEAM-2371: ------------------------------------- I am using maven 2.0.9 but will happily drop back to a prior edition if that will help. I get the same result under both Java 5 and 6. Yes, I certainly started with installs in the top dir, but had the same result. If I run 'mvn test' in the ejb dir, I get a successful build and test. Are there perhaps additional setup or configuration steps that are required? For example, I'm assuming no tomcat is required here, right? Also, I've just noticed the following properties in the bootstrap/conf dir, and cannot see them being set either in poms or via maven filters, etc.: jboss.embedded.bootstrap.resource.path jboss.server.data.dir jboss.bind.address jboss.home.dir To rule this out as a source of issues, I replaced them with absolute references to the correct local locations (i.e. within bootstrap dir), but the same exception (above) is produced. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=all ] Hemant Saxena updated JBSEAM-2371: ---------------------------------- Attachment: tech-stack-1.0.1.pom this is the parent pom for maven-seam-microcontainer-testng-template.zip. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12414932 ] Jason Grant commented on JBSEAM-2371: ------------------------------------- I've tried all combinations of Maven 2.0.8/2.0.9 and Java 1.5/1.6 but always the same exception during 'mvn install' Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: [Ljavax/el/ELResolver;; nested exception is java.lang.NoClassDefFoundError: [Ljavax/el/ELResolver; java.lang.NoClassDefFoundError: [Ljavax/el/ELResolver; Still investigating... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12414935 ] Jason Grant commented on JBSEAM-2371: ------------------------------------- In fact, I think the other pertinent thing about the extract above is that the embedded-all jar is the towards the end of the classpath despite it being listed first in the parent pom. As mentioned by Siarhei Dudzin maven 2.0.9 constructs the classpath differently, however the *-all.jar dependencies still appear towards the end of the classpath. I am trying to understand why this is the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12415078 ] Siarhei Dudzin commented on JBSEAM-2371: ---------------------------------------- Jason, El-api is in provided scope, it is also in provided scope in jboss-seam-2.0.1.GA.pom. Provided scope *is* used within test phase (http://maven.apache.org/guides/introduction/introduction-to-dependency-me...) and even propagated through transitive dependencies. So the scope is *not* the problem. I've cleaned up my local repository, made sure I have java 5 as runtime (java -version). After that I did 'mvn clean install' on top level. All tests passed! After that all artifacts supposed to be in my local repo, so just to make sure I've ran 'mvn test' from the web module and it passed! I simply can not break the build! I checked testproject-master/testproject-web/target/surefire-reports/TEST-TestSuite.xml and property surefire.test.class.path does contain el-api-1.0.jar which in turn does have the ELResolver. In this file I also see that all the jar's are sorted properly. This is what I get if I run 'mvn dependency:tree -Dverbose -Dincludes=javax.el' from the web module: [dependency:tree] testproject.group.testproject:testproject-web:war:1.0-SNAPSHOT \- org.jboss.seam:jboss-seam:jar:2.0.1.GA:provided (scope not updated to compile) \- org.jboss.el:jboss-el:jar:2.0.1.GA:provided \- javax.el:el-api:jar:1.0:provided It clearly shows how javax.el is resolved for the project. So it does seem to be your local problem. Although putting el-api in test scope fixes your problem, it's not the real problem! Because provided dependencies are used in test phase and they are also propagated as transient you *should* have had el-api in your test classpath. There are a number of possible reasons why you might have the problem: * you modified a pom and the dependency tree is now different * you have another project in your local repo with the same groupId/artifactId which somehow conflicts with any of the artifacts * you have custom settings.xml which define different repositories which might give you an artifact with different transitive dependencies There might be more but these are that popped up in my mind as I counted to 3 :) p.s. may be it is a good idea to post such kind of problems on forum? This JIRA issue is getting very long and maven tests aren't even officially supported yet! :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=all ] Jason Grant updated JBSEAM-2371: -------------------------------- Attachment: jg-seamtest-1.0.tgz I'm attaching jg-seamtest-1.0.tgz. It represents a self-contained demo of how to use SeamTest with Java 6, maven 2.0.9, Seam 2.1.0A1, and TestNG 5.8. I've done this by adapting Hemant's archive as follows: * The parent pom simply imports org.jboss.seam:root to get all seam dependency versions. This is a maven 2.0.9 feature, and permits use of libraries like seam whilst inheriting from something else. * The source code for EJBs and TestNG tests was taken from the Seam booking demo. * There is only one ejb module. In the test/resources dir, resides minimal webapp config that is purely used for testing in the embedded container. * I've stripped out all unnecessary content (e.g. reporting); I simply wanted to establish the minimum required to do a SeamTest. I will post to the forum also, since this may be of wider interest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12419140 ] Mariusz Smykula commented on JBSEAM-2371: ----------------------------------------- What is jboss-embedded-bootstrap.zip? How to make this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2371?page=comments#action_12419153 ] Mariusz Smykula commented on JBSEAM-2371: ----------------------------------------- Thanks for help, I have some problem with your demo project. {code}*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} jboss.jdbc:datasource=pentabidsDatasource,service=metadata -> jboss.jdbc:service=metadata{Create:** NOT FOUND **} -> jboss.jdbc:service=metadata{Start:** NOT FOUND **} *** CONTEXTS IN ERROR: Name -> Error jboss.jdbc:service=metadata -> ** NOT FOUND ** {/code} Btw, is this technique useful for testing in ear project with multiple linked ejb beans? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.pl... ] Anthony Whitford commented on JBSEAM-2371: ------------------------------------------ With 44 votes, I am surprised to see that this isn't scheduled for a sooner release. Maven support is critical to the Seam community (thank you for the poms!), but right now SeamTest does not work, and it should. (I need the ability to properly unit test my Seam code and get my code coverage analysis.) We need to get rid of these silly kitchen-sink "-all.jar"s... Where is the JIRA issue on that? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.pl... ] MariuszS commented on JBSEAM-2371: ---------------------------------- I agree with this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.pl... ] Geoffrey De Smet commented on JBSEAM-2371: ------------------------------------------ The seam download zip doesn't contain the embedded bootstrap jar. Here's the maven error when running "mvn test": Embedded error: Unable to download the artifact from any repository ... org.jboss.embedded:jboss-embedded-bootstrap:zip:beta3 Where can I find this mystical jar (preferable with pom) and any chance it can be deployed to the jboss repo to make our live a bit easier? :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2371?page=com.atlassian.jira.pl... ] Fred Bricon commented on JBSEAM-2371: ------------------------------------- Hi, FWIW, I've released *seam-ear-archetype* at http://code.google.com/p/open-archetypes/ it will generate a nested multi module project, allowing you to run integration tests (i.e. using the embedded JBoss) both compatible with eclipse (m2eclipse 0.9.9 and testng plugin required) and maven. It's an early version, so it will assume you already created a mysql database having the same name as your main artifact, and it's targeted at running on JBoss 5. I'm currently testing JBoss Tools integration. regards, Fred Bricon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-2371?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-2371: ---------------------------------- Fix Version/s: 2.3.0.ALPHA (was: The future) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-2371?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2371. --------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira