[ https://jira.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin.s... ] Max Andersen updated JBIDE-7470: -------------------------------- Assignee: Snjezana Peco Fix Version/s: 3.2.0.CR1 Snjezana, can you take a look and see where the difference comes from ? (note, I expect there to be differences since it is actualy packaged in two different ways, but functionally it should be similar) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin.s... ] Snjezana Peco commented on JBIDE-7470: -------------------------------------- There are several issues with this application and they are the following: 1. When creating an application using the Maven 2 command line (I have tested Maven 2.2.1), the application works properly on the JBoss AS 6. I have used AS 6 CR1. When using the Maven 3 command line or m2eclipse 0.12 embedded, the application doesn't work on AS 6 CR1.The problem is that Maven 3 adds the commons-logging library to WEB-INF/lib which causes the server to throw "Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed." exception. commons-logging is a transitive dependency (hibernate-core>ehcache>commons-logging). I think this is a bug in Maven 3. The solution would be to exclude commons-logging 2. Photoalbum uses resource filtering in the components.properties and components.xml files. That feature doesn't work in m2eclipse. The solution - removing resource filtering. 3. Photoalbum defines the artifactId element of ear,ejb and web projects using the ${projectName} property. m2eclipse imports projects based on artifactId. The projects are named ${projectName}-ear /ejb/web. JBT/WTP deploys such projects as ${projectName}-ear.ear that JBoss AS doesn't deploy correctly (the application name and repository loader are different) The solution would be to define the projects with fixed names (photoalbum, photoalbum-ejb, photoalbum-ear , photoalbum-web) 4. EAR's finalName is defined as $projectName-ear-$versionName}. JBT/WTP/m2eclipse ignores deployName and, as a result, the project is always deployed with the name <EclipseProjectName>.ear (photoalbum-ear.ear). The solution is to define EAR's final name as photoalbum-ear We have a project example that include all these fixes except the fix for the problem 1. It uses Richfaces 3.3.1 and Seam 2.2.0. Max, I could add the fixes to the photoalbum application or upgrade our project example to Richfaces 3.3.3 and Seam 2.2.1.CR2. WDYT? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-7470: -------------------------------------- Right, the photoalbum application. it would be necessary to update pom.xml, components.xml and components.properties. Changing pom.xml would update libraries (Richfaces 3.3.3 and Seam 2.2.1.CR3). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Jay Balunas commented on JBIDE-7470: ------------------------------------ I'm confused about a couple of things. Is this a bug with m2eclipse, or something with RF/Seam? Can you share some more info? Also the issue linked above [ JBIDE-5646 ], Iirc the main issue there was the naming of pom artifacts. I'm just confused how upgrading the versions of RF & Seam will help? Max had mentioned there are two photoalbum examples in tools. One is more-or-less straight from RichFaces project, and the other is modified by tools to be a pure eclipse project. I just need some clarification on the difference, and what we can do to make this acceptable. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Jay Balunas commented on JBIDE-7470: ------------------------------------ I'm confused then about the comments above about upgrading the RF and seam versions. Not a big deal, just was not sure where that impacted. We are planning to update 3.3.4 SNAPSHOT with fix, and prehaps remove resource filtering if possible. If we fix in 3.3.4-SNAPSHOT will this simplify this for you? That is what we are considering. When would these changes be needed, if this is the approach we take? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-7470: --------------------------------- Fix Version/s: 3.2.x (was: 3.2.0.CR1) Component/s: UpStream -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-7470: -------------------------------------- Correct. There are some instructions in JBIDE-5646 and http://community.jboss.org/thread/146597 I could create a patch against Richfaces 3.3.4-SNAPSHOT if you want. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-7470: -------------------------------------- Attached is a patch. I have tested importing and deploying the application with JBoss AS 4.2.3 and JBoss AS 5.1.0. I haven't tested the application with JBoss AS 6 because it uses Seam 2.1.1 which isn't compatible with JBoss AS 6.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Snjezana Peco updated JBIDE-7470: --------------------------------- Fix Version/s: 3.3.x (was: 3.2.x) An upstream issue. The problem is an incompatibility between the photoalbum application and m2eclipse. I have created a patch for the photoalbum application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Burr Sutter commented on JBIDE-7470: ------------------------------------ There are plans to have a RF4 Photoalbum - at least as an example of migration. RF3 photoalbum won't be officially supported without a bit of migration. Let's ask Brian to comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7470?page=com.atlassian.jira.plugin... ] Fred Bricon resolved JBIDE-7470. -------------------------------- Fix Version/s: (was: 3.3.x) Resolution: Won't Fix Closing as won't fix, as per Brian's comment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira