| Key: |
RHQ-570
|
| Type: |
Improvement
|
| Status: |
Accepted
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Mark Spritzler
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Date of First Response: |
19/Jul/08 06:08 PM
|
|
So in developing the ability to deploy ears and wars, it became a bit complicated in figuring out which ContentFacet interface methods had to be written.
It would be nice if we had a simple one method interface for simple content.
It could be as simple as creating an Abstract class (Template method pattern) that implements all the methods of ContentFacet, so the Plugin Container doesn't have to change. Then for simple content, you just extend the abstract class and implement one method.
|
|
Description
|
So in developing the ability to deploy ears and wars, it became a bit complicated in figuring out which ContentFacet interface methods had to be written.
It would be nice if we had a simple one method interface for simple content.
It could be as simple as creating an Abstract class (Template method pattern) that implements all the methods of ContentFacet, so the Plugin Container doesn't have to change. Then for simple content, you just extend the abstract class and implement one method. |
Show » |
|
Have a simplified version of the ContentFacet interface. For things like copying one file to one location