[JBoss JIRA] Created: (SHRINKWRAP-47) Design a way to handle multiple 'linked' Descriptor files
by Aslak (JIRA)
Design a way to handle multiple 'linked' Descriptor files
---------------------------------------------------------
Key: SHRINKWRAP-47
URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-47
Project: ShrinkWrap
Issue Type: Feature Request
Reporter: Aslak
Assignee: Andrew Lee Rubinger
When working with Archive Descriptors, doing a single web.xml is easy.
But when we move over to the container specific descriptors where some of the info in the 'auto' generated web.xml
will be needed to map something together in the jboss-web.xml.
ie:
web.xml -> resource-ref -> res-ref-name
jboss-web.xml -> resource-ref -> res-ref-name + jndi-name
The point being some of the info in web.xml is needed to create the jboss-web.xml.
Is there a way to link/automate this descriptor creation, so that the user avoid having to 'manually' add them both places.
ie:
desc = new WebArchiveDescriptor(JbossWebDescriptor, GlassfishWebDescriptor);
desc.addResourceRef(DataSource, Name, JndiName) {
this.addResourceRef(DataSource, Name);
JbossWebDescriptor.add(Name, JndiName);
GlassfishWebDescriptor.add(Name, JndiName);
}
I do realize that JNDI names could be a bad example, since in the old versions they were all container specific and in the new version they are standardized and not needed, but I'm sure there are other usecases...
--
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
13 years, 7 months
[JBoss JIRA] Created: (SHRINKWRAP-163) Make archive name optional in ShrinkWrap#create()
by Dan Allen (JIRA)
Make archive name optional in ShrinkWrap#create()
-------------------------------------------------
Key: SHRINKWRAP-163
URL: https://jira.jboss.org/jira/browse/SHRINKWRAP-163
Project: ShrinkWrap
Issue Type: Feature Request
Components: api
Affects Versions: 1.0.0-alpha-9
Reporter: Dan Allen
Fix For: 1.0.0-alpha-10
Make the Archive type first in the API, as it allows us to introduce defaults for the name and even introduce an extension constant.
ShrinkWrap.create(Class<T> type)
ShrinkWrap.create(Class<T> type, String name)
ShrinkWrap.create(Class<T> type, ExtensionType ext) ***maybe
ShrinkWrap.create(Class<T> type, String name, ExtensionType ext) ***maybe
For the simplest case (Weld SE Arquillian tests for instance), the name would be defaulted.
ShrinkWrap.create(JavaArchive.class)
The current usage would be flipped
ShrinkWrap.create(JavaArchive.class, "test.jar")
We could consider getting rid of the string-based extension classifier
ShrinkWrap.create(JavaArchive.class, "test", JAR)
Or, if you wanted to specify just an extension (for instance to create a WAR), you could do:
ShrinkWrap.create(JavaArchive.class, WAR)
To take another angle, maybe the extension can be implied based on the archive type:
JavaArchive = ".jar"
EnterpriseArchive = ".ear"
WebArchive = ".war"
In that case, we can just get back to:
ShrinkWrap.create(WebArchive.class)
--
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
13 years, 11 months