The struts2 extension included in guice2 was broken, and the workaround
included on trunk had its own issues.
 sam

On Thu, Nov 25, 2010 at 6:44 AM, Stuart McCulloch <[email protected]> wrote:

> On Nov 25, 2010, at 10:44, jordi <[email protected]> wrote:
>
> Where's Struts 2 Extension?
>
>
> It was recently discontinued, which is why it's in the last zip but not
> trunk:
>
>    <http://code.google.com/p/google-guice/source/detail?r=1423>
> http://code.google.com/p/google-guice/source/detail?r=1423
>
> as for why it was discontinued, personally I don't know
>
> --
> Cheers, Stuart
>
> It's bundled in the .zip's but I can't find it in the Javadoc API pointed
> by Guice30 wiki or in the source code via Google Code source browser
>
> jordi
>
> On Wed, Nov 24, 2010 at 9:22 PM, Simone Tripodi <<[email protected]>
> [email protected]> wrote:
>
>> sorry if I misunderstood, I thought you was trying to make a pure
>> JSR330'ed implementation too :P
>> BTW you gave me a reply, thanks :)
>> Simo
>>
>>  <http://people.apache.org/%7Esimonetripodi/>
>> http://people.apache.org/~simonetripodi/<http://people.apache.org/%7Esimonetripodi/>
>>  <http://www.99soft.org/>http://www.99soft.org/
>>
>>
>>
>> On Wed, Nov 24, 2010 at 7:34 PM, Adrian Cole < <[email protected]>
>> [email protected]> wrote:
>> > I guess I should underscore something :)  We aren't limited by guice
>> impl of
>> > 330 doesn't suggest we are not limited by 330 :)
>> >
>> > The JSR 330 spec is extremely limited, although it does keep most vendor
>> > injection annotations out of mainstream code.  I haven't seen any
>> evidence
>> > of further development of that spec, and I haven't checked to see if JSR
>> 299
>> > (CDI) handles optional injection better.
>> >
>> > jclouds tries to minimize usage of optional inject, but it does exist in
>> a
>> > few classes.  As 330 is written, it is really hard to swap out
>> > implementations anyway.  For example, the wiring logic of our spring
>> java
>> > config example is quite different than guice, and doesn't flow the same
>> > way.  CDI (at least weld) seems to flow slightly differently, too.
>> >
>> > Quite frankly, the impact of guice not releasing anything damages my
>> time
>> > and effectiveness much more than 330 has ever helped.
>> >
>> > my 2p.
>> > -a
>> >
>> > On Wed, Nov 24, 2010 at 4:14 PM, Simone Tripodi <<[email protected]>
>> [email protected]>
>> > wrote:
>> >>
>> >> Hi Adrian,
>> >> thanks for your reply :) I'm interested on wich workaround you adopted
>> >> for the @Inject(optional = true), can you point me please to some
>> >> sources?
>> >> Many thanks in advance!
>> >> Simo
>> >>
>> >> <http://people.apache.org/%7Esimonetripodi/>
>> http://people.apache.org/~simonetripodi/<http://people.apache.org/%7Esimonetripodi/>
>> >> <http://www.99soft.org/>http://www.99soft.org/
>> >>
>> >>
>> >>
>> >> On Wed, Nov 24, 2010 at 4:10 PM, Adrian Cole < <[email protected]>
>> [email protected]> wrote:
>> >> > Hi, Simone.
>> >> >
>> >> > One of the reasons jclouds really wants a guice release is that we've
>> >> > been
>> >> > jsr330ed for over a year now.  There are holes in that spec like
>> >> > optional
>> >> > inject, but we are not limited by guice at the moment.
>> >> >
>> >> > Cheers,
>> >> > -Adrian
>> >> >
>> >> > On Nov 24, 2010 12:56 PM, "Simone Tripodi" <<[email protected]>
>> [email protected]>
>> >> > wrote:
>> >> >> Hi Adrian! :)
>> >> >> for what I can see on jclouds revisions, you updated the new guice
>> >> >> jars and ran existing code/tests using the new library, did you try
>> to
>> >> >> JSR330'ing the code? I'm asking because I found some "issues", as I
>> >> >> previously wrote, and I'd like to get feedbacks/ share experience
>> also
>> >> >> from other users.
>> >> >> Please let me know, thanks in advance!
>> >> >> Simo
>> >> >>
>> >> >> <http://people.apache.org/%7Esimonetripodi/>
>> http://people.apache.org/~simonetripodi/<http://people.apache.org/%7Esimonetripodi/>
>> >> >> <http://www.99soft.org/>http://www.99soft.org/
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Wed, Nov 24, 2010 at 11:59 AM, AdrianCole < <[email protected]>
>> [email protected]>
>> >> >> wrote:
>> >> >>> +1 to release
>> >> >>>
>> >> >>> I've updated and tested jclouds with the current guice 3.0
>> snapshot.
>> >> >>>
>> >> >>> Cheers,
>> >> >>> -Adrian jclouds
>> >> >>>
>> >> >>> <http://code.google.com/p/jclouds/issues/detail?id=413>
>> http://code.google.com/p/jclouds/issues/detail?id=413
>> >> >>>
>> >> >>> On Nov 21, 12:27 am, Scott Hernandez <[email protected]>
>> wrote:
>> >> >>>> How should we report the good/bad, well I know where to report the
>> >> >>>> bad...? Just a response like this?
>> >> >>>>
>> >> >>>> I rolled out the newsnapshotand it works for me, no problems (in
>> the
>> >> >>>> first 3 minutes at least).
>> >> >>>>
>> >> >>>> On Sat, Nov 20, 2010 at 2:01 PM, Sam Berlin <[email protected]>
>> >> >>>> wrote:
>> >> >>>> > All,
>> >> >>>>
>> >> >>>> > I've uploaded a new guice 3.0snapshot.  Please see
>> >> >>>> > <http://code.google.com/p/google-guice/wiki/Guice30for>
>> http://code.google.com/p/google-guice/wiki/Guice30for new links and
>> >> >>>> > details
>> >> >>>> > of what changed since the lastsnapshot.  Also see the rest of
>> the
>> >> >>>> > page
>> >> >>>> > for
>> >> >>>> > a broad overview of new features since the 2.0 release, and the
>> >> >>>> > bottom
>> >> >>>> > of
>> >> >>>> > the page for notes about compatibility.
>> >> >>>>
>> >> >>>> > Please let us know how it works for you -- both good and bad!
>> >> >>>>
>> >> >>>> > Thanks!
>> >> >>>> >  sam
>> >> >>>>
>> >> >>>> > --
>> >> >>>> > You received this message because you are subscribed to the
>> Google
>> >> >>>> > Groups
>> >> >>>> > "google-guice-dev" group.
>> >> >>>> > To post to this group, send email to
>> >> >>>> > <[email protected]>
>> [email protected].
>> >> >>>> > To unsubscribe from this group, send email to
>> >> >>>> > <google-guice-dev%[email protected]>
>> [email protected].
>> >> >>>> > For more options, visit this group at
>> >> >>>> > <http://groups.google.com/group/google-guice-dev?hl=en>
>> http://groups.google.com/group/google-guice-dev?hl=en.
>> >> >>>
>> >> >>> --
>> >> >>> 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]>[email protected].
>> >> >>> To unsubscribe from this group, send email to
>> >> >>> <google-guice%[email protected]>
>> [email protected].
>> >> >>> For more options, visit this group at
>> >> >>> <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>> >> >>>
>> >> >>>
>> >> >>
>> >> >> --
>> >> >> 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]>[email protected].
>> >> >> To unsubscribe from this group, send email to
>> >> >> <google-guice%[email protected]>
>> [email protected].
>> >> >> For more options, visit this group at
>> >> >> <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>> >> >>
>> >> >
>> >> > --
>> >> > 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]>
>> [email protected].
>> >> > To unsubscribe from this group, send email to
>> >> > <google-guice%[email protected]>
>> [email protected].
>> >> > For more options, visit this group at
>> >> > <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>> >> >
>> >>
>> >> --
>> >> 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]>
>> [email protected].
>> >> To unsubscribe from this group, send email to
>> >> <google-guice%[email protected]>
>> [email protected].
>> >> For more options, visit this group at
>> >> <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>> >>
>> >
>> > --
>> > 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]>
>> [email protected].
>> > To unsubscribe from this group, send email to
>> > <google-guice%[email protected]>
>> [email protected].
>> > For more options, visit this group at
>> > <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>> >
>>
>> --
>> 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]>
>> [email protected].
>> To unsubscribe from this group, send email to
>> <google-guice%[email protected]>
>> [email protected].
>> For more options, visit this group at
>> <http://groups.google.com/group/google-guice?hl=en>
>> http://groups.google.com/group/google-guice?hl=en.
>>
>>
>  --
> 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.
>
>  --
> 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]<google-guice%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-guice?hl=en.
>

-- 
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.

Reply via email to