Hi Jason,
Great to get some more user feedback mate :)
On Tue, Jun 25, 2002 at 05:44:19PM -0400, Jason van Zyl wrote:
> On Tue, 2002-06-25 at 17:18, Jason van Zyl wrote:
> > Hi,
> >
> > I'm not sure where this error is coming from from but this basically
> > tells me that I'm not implementing a method for the Composable
> > interface, but my container doesn't implement Composable?
> >
>
> I just finished rebuilding everything from CVS and I get the same error
> telling me a method is missing which belongs to an interface I'm not
> implementing. Possibly something wrong in the ComponentStateValidator?
I just had a look at the code. In DefaultContainerManager, the
problem lies in the following snippet:
if( instance instanceof Serviceable )
{
validator.checkComposed();
((Serviceable)instance ).service((ServiceManager)initParameters.get(
SERVICE_MANAGER ) );
}
checkComposed() is looking for the Composable interface which
isn't implemented on AbstractContainer and is causing the
exception. As you already pointed out implementing Composable
doesn't help either, this is because it results in checkComposed()
being called twice causing your other exception to be thrown.
AFAIK ComponentStateValidator doesn't yet support Servicable,
so for the moment, comment out the .checkComposed() above and it should
get further.
I'll have a look at fixing it properly.
Hope that helps.
Cheers,
Marcus
> Additionally the build system from the base directory of excalibur
> misses the fortress build, the thread build and the event build after an
> 'ant clean'.
>
> Building fortress seems to trigger the build of the other component.
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
