Hi all I'd like to propose an extension to the ExcaliburTestCase class because we had some proplems using it for Phoenix based Blocks.
First let me introduce how we develop Phoenix Services: 1. Create an Avalon Component Role (Interface) to define the functionallity used for a Service (we only use the Framework classes/interfaces). 2. Create an implementation of the Role mentioned above. 3. Create a Phoenix Service interface extending the Components Role and eventually adding management functionallity. 4. Create a Phoenix Block implementation by extending the Component implementation and implementing the Service interface. Using the ExcaliburTestCase we can easily test the Components. Now we got into the problem that a Service we've written is using the masterstore from the cornerstone project. These implementations do a down cast of the Context object into a BlockContext object which the ExcaliburTestCase isn't able to deliver. So my proposal will be to extend the <context> part of the ExcaliburTestCase's configuration file by adding some attributes to it which will: 1. state what type of Context should be created (ie. type="block") 2. have specific attributes/elements for specific types (ie. for BlockContext populations like app-home, app-name, block-name, etc.) Please feel free to forward this to other lists (ie. -apps, -phoenix, etc.). What do you think about it? Giacomo ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
