[
https://issues.jboss.org/browse/SHRINKDESC-151?page=com.atlassian.jira.pl...
]
Ralf Battenfeld commented on SHRINKDESC-151:
--------------------------------------------
I spent a lot time to find out a way of generating all the common and common sub type
classes. I couldn't find a solution for the fact, that we have to generate descriptors
in a isolated manner, e.g. JavaEE5 cannot be mixed with JavaEE6 but for an automated way,
this is required...
Ok, I spent therefore more time in the way of declaring the common types. As you can see,
I configured all the webApp descriptor sub types. This should work. I also made it
possible to generate a common sub sub type:-) Here you can help me. How do you want to
touch such sub sub types? Casting directly from the original sub type? Or do you want to
touch it from the common sub type? If yes, then you have to show me how. I am lost in the
generics universe :-)
Descriptors should generate a common parent for different spec
versions
-----------------------------------------------------------------------
Key: SHRINKDESC-151
URL:
https://issues.jboss.org/browse/SHRINKDESC-151
Project: ShrinkWrap Descriptors
Issue Type: Feature Request
Components: api-javaee
Reporter: George Gastaldi
Assignee: Ralf Battenfeld
This affects only the JavaEE API. Some usecases manipulate descriptors regardless of the
version it is currently on. The API could be abstracted to a common interface so that
common element types to the supported complex types could be used.
A sample is provided in
https://github.com/forge/javaee-descriptors/. The IMPL remains
untouched (as generated by the ShrinkWrap generator) and common types are refactored to a
super interface:
Super Interface:
https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java...
Sub Interfaces:
https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java...
https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java...
https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java...
The generated code doesn't need to change either. The existence of the super
interface is what matters most.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira