[ http://jira.jboss.com/jira/browse/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: exception.txt -- 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/JBIDE-2190?page=all ] Max Rydahl Andersen resolved JBIDE-2190. ---------------------------------------- Resolution: Incomplete Description Neither I or Denis can reproduce. Please provide server or console log for the AS instance. The stacktrace only shows the resulting error - not what might have happend before. -- 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/JBIDE-2190?page=all ] Anton Klimkovich reopened JBIDE-2190: ------------------------------------- Assignee: Denis Golovin -- 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/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: (was: boot.log) -- 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/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: (was: exception.txt) -- 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/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: boot.log server.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/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: Seam20EarProject.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/JBIDE-2190?page=all ] Anton Klimkovich updated JBIDE-2190: ------------------------------------ Attachment: Seam20Ear-ear.ear.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/JBIDE-2190?page=all ] Max Rydahl Andersen updated JBIDE-2190: --------------------------------------- Attachment: seam202basedear.zip here is a EAR that works for me (seam 2.0.2 based) -- 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/JBIDE-2190?page=comments#action_12413591 ] Anton Klimkovich commented on JBIDE-2190: ----------------------------------------- Sorry, but what do you mean about "call the project something else" ? Call from another browsers, or something else? -- 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/JBIDE-2190?page=comments#action_12413595 ] Anton Klimkovich commented on JBIDE-2190: ----------------------------------------- May be it would be ridiculous, but I tried to run Seam 2.0.2 GA EAR project and I couldn't . -- 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/JBIDE-2190?page=all ] Denis Golovin updated JBIDE-2190: --------------------------------- Attachment: console1.txt console2.txt -- 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/JBIDE-2190?page=all ] Max Rydahl Andersen updated JBIDE-2190: --------------------------------------- Summary: Project with first upper case letter has "no application scope" error (was: Seam 2.0.1 EAR web project can not be started on JBoss AS 4.3) -- 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/JBIDE-2190?page=all ] Max Rydahl Andersen updated JBIDE-2190: --------------------------------------- Fix Version/s: 2.1.x (was: 2.1.0.GA) I cant see this as being something tools is causing so not targeting for GA and I reaxched out to the seam dev team to hear if they can explain it. -- 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/JBIDE-2190?page=comments#action_12413769 ] Anton Klimkovich commented on JBIDE-2190: ----------------------------------------- I found that if we create Seam 2.0.1 EAR with name - SeamProject, then rename it and all related projects to seamProjectNew, then make redeploy of the renamed project to AS, after that try to run it and we have the same problem in console like before. -- 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/JBIDE-2190?page=comments#action_12413873 ] Max Rydahl Andersen commented on JBIDE-2190: -------------------------------------------- Yes Anton, because: 1) the names inside the descriptors will still be captial first letter 2) on windows the rename will most likely be a noop so its maybe still upper case anyway - this is not a tooling issue it is something in seam or AS that is causing it. -- 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/JBIDE-2190?page=all ] Max Rydahl Andersen updated JBIDE-2190: --------------------------------------- Fix Version/s: 3.0.alpha (was: 2.1.2) Priority: Critical (was: Major) this is most likely an appserver/seam issue - needs to be reduce to simplest possible deploy that causes the issue. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Bram Biesbrouck commented on JBIDE-2190: ---------------------------------------- Having the same issue here (Ubuntu Linux, JBoss 4.3 EAP, Seam 2.0.2.SP1) If I create a project (Using JBoss Developer Studio) named "test", it deploys fine. When I create one naming "blah", the issue above occurs. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Bram Biesbrouck commented on JBIDE-2190: ---------------------------------------- blah -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Bram Biesbrouck commented on JBIDE-2190: ---------------------------------------- Weird as hell; developers should be able to pick their own project names ;-) I'm using Seam 2.0.2.SP1, together with JBoss Developer Studio 1.1.0.GA, that has JBoss 4.3 EAP bundled. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Pete Muir commented on JBIDE-2190: ---------------------------------- As I have said before, stop putting stuff in MANIFEST.MF, and use the recommended Seam layout (jboss-seam.jar declared as an ejb module in application and placed in the root of the ear, and all other libs in the lib/ dir) - I know WTP doesn't support EE5 properly, but that must be fixed soon! I traced the problem down to declaring the the jboss-seam.jar as an ejb module (which is correct under EE5 spec) AND declaring in the MANIFEST.MF. I checked the JEE spec, and nowhere I can find does it say that it is valid to declare a module both in the application deployment descriptor and in the MANIFEST.MF (and it actually implies that this is a bad idea: "Make sure that each component in the application properly describes any dependencies it may have on other components in the application. A Java EE application should not assume that all components in the application will be available on the class path of the application at run time. Each component might be loaded into a separate class loader with a separate namespace. If the classes in a JAR file depend on classes in another JAR file, the first JAR file should reference the second JAR file using the Class-Path mechanism. A notable exception to this rule is JAR files located in the WEB-INF/lib directory of a web application. All such JAR files are included in the class path of the web application at runtime; explicit references to them using the Class-Path mechanism are not needed. Another exception to this rule is JAR files located in the library directory (usually named lib) in the application package. Note that the presence of component-declaring annotations in shared artifacts, such as libraries in the library directory and libraries referenced by more than one module through Class-Path references, can have unintended and undesirable consequences and is not recommended. " So, my recommendation (as for the last 10 months) is to switch to the packaging structure we use in Seam as described above. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Bram Biesbrouck commented on JBIDE-2190: ---------------------------------------- This does the trick indeed. Strange though that the new-project-generator automatically generates a deficient project. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Max Rydahl Andersen reassigned JBIDE-2190: ------------------------------------------ Assignee: Max Rydahl Andersen (was: Stan Silvert) -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Aliaksey Nis closed JBIDE-2190. ------------------------------- Rejected... Closed. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Max Rydahl Andersen reopened JBIDE-2190: ---------------------------------------- Assignee: Anton Klimkovich (was: Max Rydahl Andersen) Turns out we actually can do something to fix it from the tooling site by creating a different application descriptor - important to get this QA'ed for the various combinations. -- 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-2190. ---------------------------------------- Resolution: Done Anton, could you verify 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/JBIDE-2190?page=com.atlassian.jira.plu... ] Anton Klimkovich closed JBIDE-2190. ----------------------------------- Verified with such seam runtimes: Seam2.0FP Seam 2.1.2 snapshot Seam 2.2.0CR1 Server runtimes: JBoss AS 5.1GA JBoss EAP 4.3 -- 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