> > > A factory makes it nice and easy to get what one is after whilst providing >> a >> layer of separation that affords a lot of flex in building exactly what's >> required. >> > > Shall we go for a 'protected' for both registrar implementations then? > Because if you want to work with the binary dist, and stay out of the > package space for river, work without reflection, you need to have some > access. > > Okay, works for me.
- converting RegistrarImpl to public class Sim IJskes - QCG
- Re: converting RegistrarImpl to public class Dan Creswell
- Re: converting RegistrarImpl to public class Sim IJskes - QCG
- Re: converting RegistrarImpl to public clas... Peter Firmstone
- Re: converting RegistrarImpl to public ... Sim IJskes - QCG
- Re: converting RegistrarImpl to pu... Dan Creswell
- Re: converting RegistrarImpl t... Sim IJskes - QCG
- Re: converting RegistrarIm... Dan Creswell
- Re: converting RegistrarIm... Peter Firmstone
- Re: converting RegistrarIm... Sim IJskes - QCG
- Re: converting RegistrarIm... Peter
- Re: converting RegistrarIm... Sim IJskes - QCG
- Re: converting RegistrarIm... Peter Firmstone
- documenting creating relea... Sim IJskes - QCG
- Re: documenting creating r... Peter Firmstone
- Re: documenting creating r... Sim IJskes - QCG
- Re: converting RegistrarIm... Sim IJskes - QCG
- RE: converting RegistrarIm... Christopher Dolan