Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1-Beta2
-
Component/s: ACE-Components, ICE-Components
-
Labels:None
-
Environment:ICEfaces 2.1
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
Currently, when using the mandatoryResource configuration it is necessary for application developers to list each component to be preloaded by entering the complete component Java package for the component class. This is inconvenient and error-prone.
This improvement is to add support for optionally listing components inside a mandatoryResource configuration using just the component's tag name, such as "ace:dateTimeEntry ace:tabSet" etc. This will be much more convenient for application developers to use.
Note that in addition to the ACE components, the ice:inputRichText component is also now a mandatoryResource enabled component and will need to be updated as part of this work.
This improvement is to add support for optionally listing components inside a mandatoryResource configuration using just the component's tag name, such as "ace:dateTimeEntry ace:tabSet" etc. This will be much more convenient for application developers to use.
Note that in addition to the ACE components, the ice:inputRichText component is also now a mandatoryResource enabled component and will need to be updated as part of this work.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case | [] | |
| Fix Version/s | 2.1 [ 10241 ] | |
| Affects | [Documentation (User Guide, Ref. Guide, etc.)] | |
| Assignee Priority | P1 | |
| Assignee | Mark Collette [ mark.collette ] |
Modified every use of @MandatoryResourceComponent, in ACE and compat, to specify the tag name a well as the component name. Then modified the core processing code to match on either.
While doing this, I inadvertently audited the ACE components, and found some minor issues.
I then searched for all wiki documentation concerning @MandatoryResourceComponent, the mandatoryResourceConfiguration context-param, and the icecore:config mandatoryResource attribute, and updated them to both explain the new syntax, as well as to clarify the differences between ICEfaces 2.0 and 2.1 behaviours.
trunk
Subversion 26484
Show
Mark Collette
added a comment - Modified every use of @MandatoryResourceComponent, in ACE and compat, to specify the tag name a well as the component name. Then modified the core processing code to match on either.
While doing this, I inadvertently audited the ACE components, and found some minor issues.
I then searched for all wiki documentation concerning @MandatoryResourceComponent, the mandatoryResourceConfiguration context-param, and the icecore:config mandatoryResource attribute, and updated them to both explain the new syntax, as well as to clarify the differences between ICEfaces 2.0 and 2.1 behaviours.
trunk
Subversion 26484
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 3.0.RC1 [ 10300 ] | |
| Fix Version/s | 3.0 [ 10241 ] |
| Fix Version/s | 3.0 [ 10241 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
We'll just specify the tag name right in the @MandatoryResourceComponent annotation, and modify the code that processes them to double register it, by both the full component name and the tag name,