Description of problem: The Seam 2.3 distribution that is included with WFK must be usable from JBDS
*** This bug has been marked as a duplicate of bug 825037 ***
Daniel Hinojosa <dhinojosa> made a comment on jira JBSEAM-4960 [~akazakov] I have migrated the .project, .classpath, and .settings files to what I believe to be the latest Eclipse/JBT standards. What I have now, is this message. {noformat} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101) at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.NullPointerException at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateAll(FacesConfigValidator.java:314) at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:132) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) ... 2 more {noformat} See attached files of all the settings I have currently. I know I have something missing, but I am not sure what. BTW, the test project is called 'grapesofstash'.
Daniel Hinojosa <dhinojosa> made a comment on jira JBSEAM-4960 All the files currently migrated over to JBT for Seam 2.3
Max Rydahl Andersen <max.andersen> made a comment on jira JBSEAM-4960 Daniel - could you open a JBIDE specific bug on how to reproduce the NPE you get in facesconfigvalidator ?
Daniel Hinojosa <dhinojosa> made a comment on jira JBSEAM-4960 [~maxandersen] Done Max, https://issues.jboss.org/browse/JBIDE-12129.
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 Target namespace in components.xml in CR1 was changed from http://jboss.com/products/seam/components to http://jboss.org/schema/seam/components It caused some critical promlems for JBoss Tools. See JBIDE-12132 for details
Alexey Kazakov <akazakov> made a comment on jira JBIDE-11490 I've just tested Seam 2.3.CR1 WAR project generated by JBT 1. See https://issues.jboss.org/browse/JBIDE-12132 2. In runtime it seems to work. But.. 3. If I genearate new Action, Form, etc. (we use seam-gen templates for that) then the app fails. EL cannot be resolved to the new components I don't see any changes in these templates from Seam 2.2. So it seems that something was changed in Seam or JSF and these templates are not quite correct. Anyway it's a problem of seam-gen templates. Not JBT.
Alexey Kazakov <akazakov> made a comment on jira JBIDE-11490 I've just tested Seam 2.3.CR1 WAR and EAR projects generated by JBT 1. See https://issues.jboss.org/browse/JBIDE-12132 2. In runtime it seems to work. But.. 3. If I genearate new Action, Form, etc. (we use seam-gen templates for that) then the app fails. EL cannot be resolved to the new components I don't see any changes in these templates from Seam 2.2. So it seems that something was changed in Seam or JSF and these templates are not quite correct. Anyway it's a problem of seam-gen templates. Not JBT. {code} Caused by: javax.naming.NameNotFoundException: seamear-ear/NewActionBean/local -- service jboss.naming.context.java.seamear-ear.NewActionBean.local at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_31] at org.jboss.seam.Component.instantiateSessionBean(Component.java:1403) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] at org.jboss.seam.Component.instantiate(Component.java:1367) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] at org.jboss.seam.Component.newInstance(Component.java:2148) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] {code}
Alexey Kazakov <akazakov> made a comment on jira JBIDE-11490 I've just tested Seam 2.3.CR1 WAR and EAR projects generated by JBT # See https://issues.jboss.org/browse/JBIDE-12132 # In runtime it seems to work. But.. # If I genearate new Action, Form, etc. (we use seam-gen templates for that) then the app fails. EL cannot be resolved to the new components I don't see any changes in these templates from Seam 2.2. So it seems that something was changed in Seam or JSF and these templates are not quite correct. Anyway it's a problem of seam-gen templates. Not JBT. {code} Caused by: javax.naming.NameNotFoundException: seamear-ear/NewActionBean/local -- service jboss.naming.context.java.seamear-ear.NewActionBean.local at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_31] at org.jboss.seam.Component.instantiateSessionBean(Component.java:1403) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] at org.jboss.seam.Component.instantiate(Component.java:1367) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] at org.jboss.seam.Component.newInstance(Component.java:2148) [jboss-seam.jar:2.3.0.CR1-SNAPSHOT] {code}
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .settings/org.jboss.tools.seam.core.prefs has some errors: *seam.project.web.root.folder=/myproject/WebContent* should be *seam.project.web.root.folder=/myproject/view*
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .classpath still has two missing libs: <classpathentry kind="lib" path="lib/jboss-as-embedded-7.1.1.Final.jar"/> <classpathentry kind="lib" path="lib/testng-jdk15.jar"/>
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .settings/org.eclipse.wst.common.component points to the missing folder WebContent: <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/>
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .settings/org.eclipse.wst.common.component points to the missing folder WebContent: <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/> I guess it should be something like: <wb-resource deploy-path="/" source-path="/resources" tag="defaultRootSource"/> <wb-resource deploy-path="/" source-path="/view" tag="defaultRootSource"/>
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .settings/org.eclipse.wst.common.component points to the missing folder WebContent: <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/> I guess it should be something like: <wb-resource deploy-path="/" source-path="/resources" tag="defaultRootSource"/> <wb-resource deploy-path="/" source-path="/view"/>
Alexey Kazakov <akazakov> made a comment on jira JBSEAM-4960 .settings/org.eclipse.wst.common.component points to the missing folder WebContent: {code} ... <wb-resource deploy-path="/" source-path="/WebContent" tag="defaultRootSource"/> {code} I guess it should be something like: {code} ... <wb-resource deploy-path="/" source-path="/resources" tag="defaultRootSource"/> <wb-resource deploy-path="/" source-path="/view"/> ... {code}
Marek Novotny <mnovotny> made a comment on jira JBSEAM-4960 {quote} Alexey Kazakov added a comment - 08/Jun/12 2:03 AM .classpath still has two missing libs: <classpathentry kind="lib" path="lib/jboss-as-embedded-7.1.1.Final.jar"/> <classpathentry kind="lib" path="lib/testng-jdk15.jar"/> {quote} 1. there should be *lib/test/jboss-as-embedded-7.1.1.Final.jar* instead of -lib/jboss-as-embedded-7.1.1.Final.jar- 2. there should be *testng.jar* instead of -testng-jdk15.jar-
Daniel Hinojosa <dhinojosa> updated the status of jira JBSEAM-4960 to Resolved
Daniel Hinojosa <dhinojosa> made a comment on jira JBSEAM-4960 Sorry for the delay, seems the eclipse I had was corrupted and were showing errors that shouldn't have been displayed.
Martin Malina <mmalina> made a comment on jira JBIDE-11490 Today I started testing with Seam 2.3 Beta2 from WFK 2.0 ER8 and the issues Marek lists above are present (of course). Otherwise the generated apps seem to work, I even tried created an action. But when you deploy the app, this is in the server log: {code} 10:56:26,539 WARN [org.jboss.modules] (MSC service thread 1-4) Failed to define class org.drools.WorkingMemoryEntryPoint in Module "deployment.seamproj.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/drools/WorkingMemoryEntryPoint (Module "deployment.seamproj.war:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) at org.jboss.modules.Module.loadModuleClass(Module.java:527) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at java.lang.ClassLoader.defineClass1(Native Method) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [classes.jar:1.6.0_31] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [classes.jar:1.6.0_31] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) at org.jboss.modules.Module.loadModuleClass(Module.java:527) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at org.jboss.seam.init.DependencyManager.checkClassDependencies(DependencyManager.java:138) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.checkAllDependencies(DependencyManager.java:98) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.tryToInstall(DependencyManager.java:93) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.tryToInstall(DependencyManager.java:69) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.computeInstallSet(DependencyManager.java:49) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.installedSet(DependencyManager.java:30) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1111) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.Initialization.init(Initialization.java:737) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31] Caused by: java.lang.NoClassDefFoundError: org/drools/runtime/rule/WorkingMemoryEntryPoint at java.lang.ClassLoader.defineClass1(Native Method) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [classes.jar:1.6.0_31] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [classes.jar:1.6.0_31] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) ... 41 more Caused by: java.lang.ClassNotFoundException: org.drools.runtime.rule.WorkingMemoryEntryPoint from [Module "deployment.seamproj.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 47 more 10:56:26,543 WARN [org.jboss.modules] (MSC service thread 1-4) Failed to define class org.drools.WorkingMemory in Module "deployment.seamproj.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link org/drools/WorkingMemory (Module "deployment.seamproj.war:main" from Service Module Loader) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) at org.jboss.modules.Module.loadModuleClass(Module.java:527) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) at org.jboss.seam.init.DependencyManager.checkClassDependencies(DependencyManager.java:138) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.checkAllDependencies(DependencyManager.java:98) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.tryToInstall(DependencyManager.java:93) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.tryToInstall(DependencyManager.java:69) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.computeInstallSet(DependencyManager.java:49) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.DependencyManager.installedSet(DependencyManager.java:30) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1111) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.init.Initialization.init(Initialization.java:737) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.0.Beta2-redhat-1] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.16.Final-redhat-1.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31] Caused by: java.lang.NoClassDefFoundError: org/drools/WorkingMemoryEntryPoint at java.lang.ClassLoader.defineClass1(Native Method) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [classes.jar:1.6.0_31] at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [classes.jar:1.6.0_31] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) [classes.jar:1.6.0_31] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) ... 25 more Caused by: java.lang.ClassNotFoundException: org.drools.WorkingMemoryEntryPoint from [Module "deployment.seamproj.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) ... 31 more {code}
Check if there is knowledge-api.jar in EAR (i guess it is ear). That issue i already fixed and the fix should be in ER8. Can you validate your Seam runtime? Please use https://bugzilla.redhat.com/show_bug.cgi?id=825037 instead of this issue
Martin Malina <mmalina> made a comment on jira JBIDE-11490 Marek, no, it's not ear, it's a war project and there is no knowledge-api.jar. My Seam runtime is from WFK ER8 for sure.
Marek Novotny <mnovotny> made a comment on jira JBIDE-11490 then it is clear why it happens, war list jars is not fixed http://anonsvn.jboss.org/repos/seam/branches/enterprise/WFK-2_0/jboss-seam-gen/dist/build-scripts/deployed-jars-war.list misses knowledge-api.jar and http://anonsvn.jboss.org/repos/seam/branches/enterprise/WFK-2_0/jboss-seam-gen/dist/build-scripts/deployed-jars-ear.list has got it. I will create the standalone issue
Daniel Hinojosa <dhinojosa> made a comment on jira JBIDE-11490 Searched through the project and there is no mention of the word "knowledge" anywhere. I created the war list and the ear list based strictly on the dependencies. I assume that knowledge-api will need to be placed in the jboss-seam's project's web.xml.
Daniel Hinojosa <dhinojosa> made a comment on jira JBIDE-11490 Assign the ticket to me Marek, I have it in now in the project, and will commit.
Marek Novotny <mnovotny> made a comment on jira JBIDE-11490 This issue is owned by JBTools team - I can't assign it to you. What I meant by missing knowledge-api.jar is dependency of Drools integration in version 5.2.2 which we upgraded in different version of Seam in WFK product. That is the content of my comment https://issues.jboss.org/browse/JBIDE-11490?focusedCommentId=12700721&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12700721. It is another issue tracker which notifies/spams the community JIRA. Seam 2.3.0.Beta2-SNAPSHOT is not affected as it has got still Drools 5.1.1 and there is drools-api instead of knowledge-api. Just to be more clear Drools 5.2 renamed drools-api to knowledge-api ;-).
Tomas Remes <tremes> updated the status of jira JBSEAM-4918 to Reopened
Tomas Remes <tremes> made a comment on jira JBSEAM-4918 Hey Dan! My generated EAR still didn't get deployed in Eclipse with JBT, because it is missing META-INF/jboss-deployment-structure.xml. The reason is that project generated build.xml is missing following line (on 262): {noformat} <include name="jboss-deployment-structure.xml"/> {noformat} I am using locally built CR1-SNAPSHOT dist from 2012-06-21.
Daniel Hinojosa <dhinojosa> updated the status of jira JBSEAM-4918 to Resolved
Daniel Hinojosa <dhinojosa> made a comment on jira JBSEAM-4918 Thanks Tomas, Submitted the fix.
Tomas Remes <tremes> updated the status of jira JBSEAM-4960 to Reopened
Tomas Remes <tremes> made a comment on jira JBSEAM-4960 This problems is occuring again. Using Seam dist SNAPSHOT from 2012-07-23 gives in JBDS 5.0.1 following classpath errors for missing libraries: lib/testng-jdk15.jar lib/jboss-jsf-api_2.1_spec.jar lib/jboss-deployers-core-spi.jar lib/jboss-deployers-client-spi.jar lib/hsqldb.jar lib/cglib-nodep.jar
Tomas Remes <tremes> made a comment on jira JBSEAM-4960 This problem is occuring again. Using Seam dist SNAPSHOT from 2012-07-23 gives in JBDS 5.0.1 following classpath errors for missing libraries: lib/testng-jdk15.jar lib/jboss-jsf-api_2.1_spec.jar lib/jboss-deployers-core-spi.jar lib/jboss-deployers-client-spi.jar lib/hsqldb.jar lib/cglib-nodep.jar
Tomas Remes <tremes> updated the status of jira JBSEAM-4960 to Resolved
Tomas Remes <tremes> made a comment on jira JBSEAM-4960 Sorry, that was my mistake. Seam dist zip was not up to date.
Tomas Remes <tremes> made a comment on jira JBSEAM-4960 I have been confused by Seam dist zip's, but above mentioned libraries are really missing after import to JBDS.
Marek Novotny <mnovotny> made a comment on jira JBSEAM-4960 I believe these are not needed: lib/jboss-deployers-core-spi.jar - this is for JBoss Embedded usage lib/jboss-deployers-client-spi.jar - this is for JBoss Embedded usage lib/hsqldb.jar - we should use H2 as JBoss AS7 We should remove them and try if all works as before.
Tomas Remes <tremes> made a comment on jira JBIDE-11490 I had to add following jars (EAR/lib and WAR/WEB-INF/lib) and - drools-core-5.3.3.Final.jar, guava-12.0.jar, jboss-el-1.0_02.CR6.jar to successfully deploy (7.1.1) Seam 2.3 project created in JBDS 5.0.1. I used CR1-SNAPSHOT dist available at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Seam%20Framework/job/Seam-2.3.X-dist-nightly/
Tomas Remes <tremes> made a comment on jira JBIDE-11490 I had to add following jars (EAR/lib and WAR/WEB-INF/lib) - drools-core-5.3.3.Final.jar, guava-12.0.jar, jboss-el-1.0_02.CR6.jar to successfully deploy (7.1.1) Seam 2.3 project created in JBDS 5.0.1. I used CR1-SNAPSHOT dist available at http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Seam%20Framework/job/Seam-2.3.X-dist-nightly/
Marek Novotny <mnovotny> made a comment on jira JBIDE-11490 just heads up. I have upgraded Drools to 5.3.3 sometime ago also in community Seam 2.3, so there has to be changes like replacement of drools-api.jar with knowledge-api.jar