[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1104) .sar file cannot be included in .ear file

[Rob Stryker (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1104?page=comments#action_12389604 ] 
            
Rob Stryker commented on JBIDE-1104:
------------------------------------

Sorry to re-address this mostly-dormant issue, but I got curious.

Where is the output location of the .sar file's archive going?  For example, if you have a plain old java project you're filling with .SAR items, and creating a packaging configuration for it, where is the OUTPUT of the .sar going in the configuration?

Have you tried having the output of the archive, aka the completed and packaged .sar, be inside the ear project itself where it should sit?  

> .sar file cannot be included in .ear file
> -----------------------------------------
>
>                 Key: JBIDE-1104
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1104
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.Beta4
>         Environment: JBoss Tools nightly build 20071017
>            Reporter: Juergen Zimmermann
>         Assigned To: Rob Stryker
>             Fix For: 2.1
>
>
> I need a .ear file which contains a .sar file (service archive for JBoss). Such a .sar file is declared in META-INF/jboss-app.xml of the EAR project "hska" as follows:
> <jboss-app>
> 	<security-domain>java:/jaas/hska</security-domain>
> 	<module>
> 		<service>hska.sar</service>
> 	</module>
> </jboss-app>
> I have a "General Project" named hskaSAR which has a META-INF subdirectory for the xml files of the .sar file. Creating hskaSAR/hska.sar via the "Project Archives" view of JBoss Tools works fine. However, there is no possibility to include the .sar file within the (exploded)  .ear.
> I tried to edit and extend the file .settings/org.eclipse.wst.common.component within the EAR project as follows:
> <dependent-module deploy-path="/" handle="module:/classpath/lib/hskaSAR/hska.sar">
>             <dependency-type>uses</dependency-type>
> </dependent-module>
> However, this workaround doesn't work.

-- 
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