Hmm I'm already half there and the modules are a lot smaller than their XML counterparts..looks like it wasnt really a big problem after all. Cant wait to get completely rid of XML and the spring.jars. On 20 Aug., 12:42, Mikkel Petersen <[EMAIL PROTECTED]> wrote: > Im not sure since I have so many objects and thousands of constants. > But let's see. > On 18 Aug., 23:15, "Robbie Vanbrabant" <[EMAIL PROTECTED]> > wrote: > > > > > Well, the good news is that you'll end up with considerably less > > configuration. :-) > > Robbie > > > On Mon, Aug 18, 2008 at 10:51 PM, Mikkel Petersen <[EMAIL PROTECTED]> wrote: > > > > Thanks I guess that Guice somehow commands you to think totally > > > different, and not to try to force it to work like Spring. > > > I'm aware of the Spring/Guice integration classes and in the beginning > > > I was using them as well. I soon found out that I was mostly still > > > using Spring, since too much configuration was impossible to remove > > > from the Spring XML. > > > So the only way is to recreate it completely in Guice. > > > On 18 Aug., 01:02, String Larson <[EMAIL PROTECTED]> wrote: > > > > Check this:http://www.jroller.com/mindcrime/ > > > > > On Aug 16, 2008, at 3:39 PM, Mikkel Petersen wrote: > > > > > > First let me say that Guice has changed my dev life.. > > > > > First Spring IOC changed it (to the better) and now Guice is doing it > > > > > (and even much better). > > > > > > However, I'm porting a large Spring IOC application (uses only IOC > > > > > container, nothing else from Spring) and I have a few problems porting > > > > > some "beans". > > > > > This is just an example, but I have lots of similar case. > > > > > > Say you have this > > > > > <bean id="basePerson" abstract="true" class="Person"> > > > > > ...let's say we configure a large amount of properties here > > > > > </bean> > > > > > > Now we want to create multiple instances of a Person, all inhereting > > > > > the properties from the "basePerson" bean and some even of a class > > > > > subclassing Person > > > > > > Like : > > > > > <bean parent="basePerson"> > > > > > <property name="firstName" value="John"/> > > > > > </bean> > > > > > > <bean parent="basePerson"> > > > > > <property name="firstName" value="Bob"/> > > > > > </bean> > > > > > > Now the large amount of basic properties are easely copied into these > > > > > new Person instances. > > > > > > How do you do this in a simple way in Guice ? > > > > > > Next problem, if your "person bean" subclasses Person but still > > > > > inherits properties from the basePerson bean.. > > > > > > Like > > > > > <bean parent="basePerson" class="WorkingPerson"> > > > > > <property firstName value="Joe"/> > > > > > <property name="profession" value="Street sweeper"/> > > > > > </bean> > > > > > Now this bean is a copy of "basePerson" but it's also an instance of > > > > > WorkingPerson which subclasses Person. > > > > > > I hope this can be done in Guice as well as it would make the port a > > > > > lot easier- Skjul tekst i anførselstegn - > > > > > - Vis tekst i anførselstegn -- Skjul tekst i anførselstegn - > > > - Vis tekst i anførselstegn -- Skjul tekst i anførselstegn - > > - Vis tekst i anførselstegn - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
