[JBoss JIRA] Created: (SHRINKDESC-9) Evaluate module separation strategy
by Aslak Knutsen (JIRA)
Evaluate module separation strategy
-----------------------------------
Key: SHRINKDESC-9
URL: https://jira.jboss.org/browse/SHRINKDESC-9
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Reporter: Aslak Knutsen
Fix For: 1.0.0-alpha-1
e.g.
WebAppDescriptor exposes javax.servlet.Filter and javax.servlet.Servlet classes in API
Depending on the Descriptor they might expose other APIs. We should make them separate modules so you don't have to pull in the whole of Java EE api to use the PersistenceDescriptor.
One module pr Descriptor with a BOM module that can group them ?
Modules :
WebAppDescriptor
PersistenceDescriptor
BeansDescriptor
BOMs:
JavaEnterprise-6
- depends on WebAppDescriptor, PersistenceDescriptor, BeansDescriptor
JavaEnterprise-5
- depends on WebAppDescriptor, PersistenceDescriptor
--
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, 7 months
[JBoss JIRA] Created: (SHRINKDESC-25) Import / Export should be able to handle unmapped entires
by Aslak Knutsen (JIRA)
Import / Export should be able to handle unmapped entires
---------------------------------------------------------
Key: SHRINKDESC-25
URL: https://jira.jboss.org/browse/SHRINKDESC-25
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Reporter: Aslak Knutsen
When using JAXB marshal/unmarshal, things that are not mapped in the JAXB model will not be exported. This means the Descriptors will have to map every possible option which is a bit tedious, and all comments etc will be gone.
The JAXB Binder should fix this according to spec/javadoc, but the RI bundled with JDK does this in a very simple way. It can map partial parts of a xml doc, but that part has to be fully mapped. but even fully mapped, comments are lost. (the complete mapped node is replaced, not merged like in EclipseLink Moxy)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (SHRINKWRAP-233) addClass with DefaultPackage opens addPackage to null arguments
by Aslak Knutsen (JIRA)
addClass with DefaultPackage opens addPackage to null arguments
---------------------------------------------------------------
Key: SHRINKWRAP-233
URL: https://jira.jboss.org/browse/SHRINKWRAP-233
Project: ShrinkWrap
Issue Type: Bug
Reporter: Aslak Knutsen
When adding a Class in addClass, we do a addPackage with a Filter to match inner classes of that class.
When adding a Class in Default package, the Package we padd to addPackage is null. Meaning addPackage can't verify non null values.
The downside is, if someone happens to add, e.g.
addPakcage(true, Package.get("some-missing-package")), addPackage will be called with null, and null means /, which means all found packages are added.
We need to split addPackage(boolean, Filter, Package...) into two methods, one external which does the null checks from the user and one internal that does not check for null(to support Class in default package).
--
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, 9 months