On 10/30/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > Simon Laws wrote: > > I seem to remember in the past that adding remote bindings to services > with > > interfaces not marked as remotable used to cause and error or a warning. > > > > This cropped up in the domain manager app which defines the following > > component. > > > > <component name="DomainManagerComponent"> > > <implementation.java class=" > > org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl"/> > > <service name="DomainManagerInitService"> > > <interface.java interface=" > > org.apache.tuscany.sca.domain.DomainManagerInitService"/> > > <binding.sca/> > > </service> > > <service name="DomainManagerNodeEventService"> > > <interface.java interface=" > > org.apache.tuscany.sca.domain.DomainManagerNodeEventService"/> > > <binding.ws/> > > </service> > > <service name="DomainManagementService"> > > <interface.java interface=" > > org.apache.tuscany.sca.domain.management.DomainManagementService"/> > > <t:binding.jsonrpc/> > > </service> > > </component> > > > > Where the DomainManagementService interface was not marked as remotable > when > > it should have been (my mistake) but the interesting effect is that > > everything works except that no databindings are applied to the wires so > > parameters/return types are messed up. > > > > Ah that's why :) > > We should detect that at build/wiring time and raise a warning then. > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
Ok, Sounds right. Am sure it used to work. I'll raise a JIRA and investigate why it didn't happen in this case. Simon
