[JBoss JIRA] Created: (JBIDE-1104) .sar file cannot be included in .ear file
by Juergen Zimmermann (JIRA)
.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
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
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-6320) EAR deployment with option "as compressed archives" results in ear containing invalid jars
by Gonne (JIRA)
EAR deployment with option "as compressed archives" results in ear containing invalid jars
------------------------------------------------------------------------------------------
Key: JBIDE-6320
URL: https://jira.jboss.org/browse/JBIDE-6320
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.1.0.GA
Environment: Windows XP Pro SP3, Java JDK 1.6.0_20, Eclipse IDE for JEE 3.5.2, JBoss Tools 3.1 (JBossAS Tools 2.1.0.v201003050540R-H56-GA), WTP Patches 3.1.2.v201003181725), m2Eclipse 0.10.0
Reporter: Gonne
Assignee: Rob Stryker
The deployment of a minimal Enterprise Application Project (consisting of e.g. jboss-seam.jar as ejb-module and mvel2.jar as 3rd-party jar) with the deployment option "Deploy projects as compressed archives" activated, results in an ear containing some invalid jars: These invalid jars are containing only one jar with the same name which finally contains the actual jar content.
E.g. the mvel2.jar contains a mvel2.jar which contains the "META-INF" and an "org" directory.
It seems that every supplied jar is affected that is determined as module jar, because it is an ejb-module (e.g. jboss-seam.jar) or its manifest contains a "Main-class" entry marking it as client-module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5728) Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support)
by Yahor Radtsevich (JIRA)
Enhance OpenOn for the name param of some JSF 2.0 tags (add JAR files and i18n support)
----------------------------------------------------------------------------------------
Key: JBIDE-5728
URL: https://jira.jboss.org/jira/browse/JBIDE-5728
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml source editing
Affects Versions: 3.1.0.CR1
Reporter: Yahor Radtsevich
Assignee: Alexey Kazakov
Fix For: 3.2.next
JSF 2.0 allows the following tags to refer to the resources:
h:outputStylesheet name="RESOURCE_NAME"
h:outputScript name="RESOURCE_NAME"
h:graphicImage name="RESOURCE_NAME"
This is quotation from the JSF 2.0 Documentation (http://java.sun.com/javaee/6/docs/api/javax/faces/application/ResourceHan... ):
The default implementation must support packaging resources in the web application root under the path
resources/<resourceIdentifier>
relative to the web app root.
For the default implementation, resources packaged in the classpath must reside under the JAR entry name
META-INF/resources/<resourceIdentifier>
<resourceIdentifier> consists of several segments, specified as follows.
[localePrefix/][libraryName/][libraryVersion/]resourceName[/resourceVersion]
The HTML Editor supports OpenOn only for the resources which are placed in WEB_ROOT/resources/[libraryName/]resourceName .
There is no support for:
1. JAR files
2. Locale
3. Library version
4. Resource version
The support should be added.
Also see: JBIDE-5382.
--
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
14 years, 6 months