[ http://jira.jboss.com/jira/browse/JBIDE-1104?page=all ] Max Andersen updated JBIDE-1104: -------------------------------- Fix Version/s: 2.1 Not sure how we can/will fix this since it's WTP that is "lacking" the understanding of what is in jboss-app.xml ....will have to wait after GA. -- 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-1104?page=comments#action_12383093 ] Rob Stryker commented on JBIDE-1104: ------------------------------------ Another alternative is to do the entire packaging structure in the Project Archives view, starting with a top level EAR and creating one packaging structure for the entire thing. But that's a bit of work, I admit. -- 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-1104?page=all ] Rob Stryker reassigned JBIDE-1104: ---------------------------------- Assignee: Rob Stryker -- 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-1104?page=comments#action_12389627 ] Juergen Zimmermann commented on JBIDE-1104: ------------------------------------------- I'm using a "General Project" for the .xml files to be packed into a .sar file. When the .sar file is produced via the "Project archives" view then the .sar file is created in the top-level directory of the "General Project". I'm not using a "Java Project" because the .sar only needs .xml files and thus there is no reason for a "src" subdirectory. I also tried to right click on the EAR project's properties and then selected "J2EE module dependencies". There is a button "Add JARs...". This way you can add 3rd-party .jar files to be included in the top-level directory of the (exploded) ear file. However, the following wizard only offers .jar files for the selection. There is no chance to select others e.g. .sar files. Well, the .sar file can be created so that the file is placed into the EAR project. However, the ear packaging issue remains: the deployed and exploded ear doesn't contain the .sar file and I don't see a way how to add the .sar file to the exploded ear. -- 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-1104?page=all ] Max Andersen resolved JBIDE-1104. --------------------------------- Resolution: Partially Completed if i understand you correctly you put your .sar file into META-INF for it to work....is that not the standard way to get jboss deployers to scan your sar or ? anyway closed since I have a hard time finding the tooling related bug in 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/JBIDE-1104?page=comments#action_12397028 ] Max Andersen commented on JBIDE-1104: ------------------------------------- ah got it...:) So yes, limitations of WTP's add jar functionallity (it thinks everything ends in .jar) but also that .sar could be a project type but that feels wrong somehow...but I guess that is the proper solution in context of WTP -- 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-1104?page=comments#action_12412216 ] Jonathan Fields commented on JBIDE-1104: ---------------------------------------- Hi All, I just voted for this. I am very pleased with JBoss Tools, especially the incremental deployment. However, I have several EAR applications developed using the old JBossIDE packaging, that include numerous MBeans packaged in SAR archives, configured using jboss-service.xml. I was disappointed to see that I was unable to migrate these projects to JBoss Tools, as-is, due to the lack of support for SAR archives in an EAR. I think that supporting SAR archives as a project type is the way to go. This is afterall, JBoss tools, and a SAR archive is a supported module type in a JBoss EAR ;-) What I have done as a workaround is move my MBeans into the EJB project, and used the JBoss @Service and @Management attributes to configure the MBeans as extended EJB3 "service objects" in the EJB module. This gets me 90% there, with virtually no code changes, but I have lost the ability to configure MBean attributes via jboss-service.xml. I have replaced that configuration with a properties file. This all works, but I'd still like to be able to include SAR archives in my EAR as a "first class" module type, as I could before. Also, what about the other module types - HAR (Hibernate Archive) and RAR? Although I don't expect that people will need HAR anymore with EJB3 and/or Seam. Thanks, Jon -- 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-1104?page=comments#action_12412919 ] Jonathan Fields commented on JBIDE-1104: ---------------------------------------- Hi Max, Thanks for the help. I've been able to use Project Archives and was able to create my .sar file. In particular, I now have project-ear/EarContent/project-jmx.sar along with my other utility jars. But, it does not get published to the project-ear.ear folder in JBoss deploy folder. I tried both full and incremental. Do I need to add project-jmx.sar as a Utility Jar? If so, I cannot figure out how to do that. In Import > J2EE Utility Jar > Utility Jar Import - Select Import Type, my choices are to copy an external jar into the EAR, or link an external jar into the EAR. Neither of these seems appropriate. I tried copy an external jar into the EAR, thinking I'd just choose project-jmx.sar itself, but I cannot do that since it has a .sar extension, not a .jar extension, and thus is not included in the list of jars. So it seems like I'm still stuck. Should I move this discussion to the forum instead of JIRA? Thanks, Jon -- 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-1104?page=comments#action_12413295 ] Max Rydahl Andersen commented on JBIDE-1104: -------------------------------------------- our patch for wtp wont solve 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/JBIDE-1104?page=all ] Rob Stryker updated JBIDE-1104: ------------------------------- Comment: was deleted -- 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-1104?page=all ] Rob Stryker updated JBIDE-1104: ------------------------------- Attachment: SarEar.tar Example project demonstrating how to publish a sar inside an ear -- 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://issues.jboss.org/browse/JBIDE-1104?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-1104: --------------------------------------- Fix Version/s: 3.0.0.GA (was: LATER) set to best guess version. -- 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