Hi all, I'm gonna create a lot of binding object for each social services in Social, and a remark from Marek Schmidt made me wonder if it could be a good choice to create a specific submodule (i.e. jar) for each service ? Antoine _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Le 6 mai 2011 à 16:19, Pete Muir a écrit : > I don't think that is what marek meant. He was saying to just do the connection lazily when the service is first injected as the correct design. He then said another way to do it would be the below. > In fact my code already does this lazy init. I'm looking for the best design to support multi-account for the same service in the future and I got to the wrong conclusion with the SEAMSOCIAL-10 ticket. I was thinking of multi-module before... > Anyway, just bear in mind the more jars you create the more work you give to the developer to create an app... It's a hard balance. > That's the reason why I hesitated. On the other other hand this submodule approach could facilitate contribution for a new service. And the combined jar that George suggested could be a good way to limit complexity I think I'll try to fix my design issues and when I'll be happy with it, I'll take a decision on the splitting. > On 6 May 2011, at 10:03, Antoine Sabot-Durand wrote: > >> Hi all, >> >> I'm gonna create a lot of binding object for each social services in Social, and a remark from Marek Schmidt made me wonder if it could be a good choice to create a specific submodule (i.e. jar) for each service ? >> >> Antoine >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >