Details
-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.2.0-alpha-2
-
Component/s: None
-
Labels:None
Description
As Remy notes, we'll need support for JBoss-specific vendor extensions in jboss-web.xml. Model this in a Descriptor.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
I think the best solution would be to introduce a new attribute in the schemaXXX.xml, allowing the define descriptor names to any suitable name.
Show
Ralf Battenfeld
added a comment - I think the best solution would be to introduce a new attribute in the schemaXXX.xml, allowing the define descriptor names to any suitable name.
Ralf Battenfeld
added a comment - I think the best solution would be to introduce a new attribute in the schemaXXX.xml, allowing the define descriptor names to any suitable name.
Show
Andrew Rubinger
added a comment - Upstream: https://github.com/shrinkwrap/descriptors/commit/2775262014a55d132edac41b5221c83dd66165e2
Andrew Rubinger
added a comment - Upstream: https://github.com/shrinkwrap/descriptors/commit/2775262014a55d132edac41b5221c83dd66165e2 
I successfully generated the jbosswebDescriptor for jboss-common_6_0.xsd. I will add the one for jboss-web_5_1.xsd, if you don't mind.
Note, I had a little problem with xdd:stripNumbersFromString. The function is applied not only for the descriptor names. The method names are as well stripped from contatining any numbers. So far, no methods name has included a number but jboss-common_6_0.xsd does. The attribute 'java2ClassLoadingCompliance' is now 'javaClassLoadingCompliance'.
To change this is a little bigger effort, I guess. Let me know what you think. At the moment, I leave it as it is.