On Wed, Dec 22, 2010 at 10:55 AM, Rickard Öberg <[email protected]> wrote: > On 2010-12-20 19.59, Niclas Hedhman wrote: >> >> I have one Mixin that ONLY has Activatable methods. There are more >> than one usecase, but the 'current' one; >> >> The JaxWsService sitting in a library >> >> @Mixins( JaxWsService.JaxWsMixin.class ) >> public interface JaxWsService extends Activatable, ServiceComposite >> { >> >> public static abstract class JaxWsMixin >> implements JaxWsService >> { >> >> which sets up the CXF TypeCreator and the Endpoint for the service. >> >> and for 'simple' services (I have one with a single method), it just >> extends JaxWsService and an abstract mixin for that method. Instead of >> creating one more interface, ending up with 2 interface and one >> implementation class for a single method ;-) > > Could you make it an imported service instead? If it's that simplistic?
Uhhh... I guess I am not good at explaining, and not sure why you are even arguing the case. I am not asking you to do anything, just confirm the fix doesn't introduce any unwanted consequences. There is nothing to "import", I am "exporting". By extending JaxWsService instead of ServiceComposite, you can have your Qi4j service exposed over JAX-WS / WSDL. The JaxWsService mixin is generic. The Activatable in that interface is needed, otherwise the activate()/passivate()-only Mixin doesn't get included in the composite. The simplicity/complexity of the downstream service is beyond the control of the library, and quite irrelevant. The fix is generic, not only for the Jax-Ws work itself. But perhaps there are some usecase that I have not thought of where something strange will be the result. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
