Misleading exception thrown

[Nick Barrett]

Hi again folks. I thought I'd send another message to this group because let's face it, Yadic is a very unobtrusive and unassuming framework and has a correspondingly quiet group to match, and is probably a bit lonely.

So.... here's another observation. As a result of me making a mistake in the wiring one of my classes via an activator, yadic very correctly threw an exception but I think the nature of the exception was misleading. What I'd actually done was to specify the interface to activate rather than the concrete class, so yadic threw this:

Caused by: com.googlecode.yadic.ContainerException: me.v.service.query.StartSessionQueryService does not have any public static methods that return interface me.v.service.query.StartSessionQueryService

So the implication here is that yadic was trying to do what only Chuck Norris can do: to instantiate an interface :-) Perhaps the exception should be along the lines of me.v.service.query.StartSessionQueryService not being a concrete class?

[Daniel Worthington-Bodart]

Yea in fact it should blow on registration

--
You received this message because you are subscribed to the Google Groups "yadic" group.
To unsubscribe from this group and stop receiving emails from it, send an email to yadic+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Matt Savage]

Helpful exceptions are my obsession. Has anyone fixed this already?

Presume we need to fix this in StaticMethodResolver and ConstructorResolver (for completeness- obviously an interface wouldn't actually reach it if registered through SimpleContainer).