- This topic has 5 replies, 4 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
I have a JBoss J2EE application which consists of a EAR, an EJB project and two WARs. This works fine and setting it up with MyEclipseIDE was extremely simple.
However, I now want to add a .har (Hibernate Archive) and a .sar (Service Archive) to this application. I’m a bit lost here. I would like these to become part of the EAR but I only seem to be able to add EJB or WAR modules to it.
What is the correct way to create a .har archive and then add it to the EAR so that it will become part of the resulting archive?
Thanks,
Stefan
Stefan,
MyEclipse does not have direct support for these JBoss-specific module types, but people in the forums that do use them just get around this with a custom Ant script. Sorry for the inconvenience.I feel extremly ‘locked in’ to ME now. Maybe it is because I don’t fully understand the Eclipse build process, it is not exactly transparant. Little things like this that take days to figure out are the real J2EE productivity killer. I switched back to my classic ant build for now. Bah
It would be nice if ME would provide some generic archive builder; JBoss has SAR, WAR, JAR, WSR, HAR, RAR archives and their structure is basically all te same. Stuff in META-INF plus compiled code in the archive.
S.
Stefan,
You’ve asked your question at precisely the right time. In the next release of MyEclipse (3.8.3 – early December), we’ve added support for packaging any Java project into an EAR as a jar. This is really intended to add support for ‘library’ projects that are used by multiple modules in the EAR. I think this should work for packaging the specific module project types that you’re interested in. However, right now they would all be packaged with a .jar extension. It’s really late in the dev cycle to do too much about this, but what if we could add an enhancement that if the project name already includes an extension (ie. your project is named something.sar) then we use that name for the archive instead of the standard <projectname>.jar? Would that work for you?
I would appreciate the addition of the feature you propose, i.e., project name is foo.sar then use that name.
