You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by chico charlesworth <ch...@googlemail.com> on 2009/02/10 15:39:23 UTC
shindig and spring integration
Hi all,
As you know shindig relies on guice as the preferred dependency injection
framework, and that is all good. Yet we've gone with the approach of using
both spring and guice, simply because spring offers us great support for JPA
(e.g. transaction management) and AOP, and it's likely that we'll be using
other Spring features down the line. There has been a couple of challenges
in getting the project working nicely with these two technologies side by
side, but we're fairly happy as things stand right now. Note that the
integration doesn't include any changes to the shindig codebase, that is, we
still let shindig use guice as expected.
My question to the community is, first and foremost, do you think this would
be beneficial to other people? And if so, what is the best approach in
contributing the shindig/spring integration work we've done?
At the minimum we would like to document this integration work and make it
available to the community, either in a WIKI or as a tutorial. Another
approach would be to include the code in the samples module, but then I
guess we would have to consider splitting the samples module into sub
projects?
Cheers,
Chico
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
Great news, the shindig spring example is now ready and waiting on:
http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
(source code available on svn [1])
Thx for Vincent's and Ian's help on this one, will hopefully pave way for
more contributions of Shindig example code :)
Any feedback welcome!
Cheers
Chico
[1]
https://svn.apache.org/repos/asf/incubator/shindig/sandbox/trunk/shindig-spring-example/
2009/2/17 Vincent Siveton <vi...@gmail.com>
> Hi Chico,
>
> NP, shoot me the code and I will commit it.
>
> Cheers,
>
> Vincent
>
> 2009/2/17 chico charlesworth <ch...@googlemail.com>:
> > great, thx Vincent for setting that up!
> >
> > I don't yet have commit access though .. still eagerly awaiting for my
> > account to be setup :)
> >
> > can I email you the code Vincent, and ask you to commit it on my behalf
> to:
> > https://svn.apache.org/repos/asf/incubator/shindig/sandbox
> > /shindig-spring-example/trunk
> >
> > Cheers
> > Chico
> >
> > 2009/2/17 Vincent Siveton <vi...@gmail.com>
> >
> >> Hi Chico,
> >>
> >> <Sorry for the delay.>
> >>
> >> Now that svn is up, I created a sandbox space in svn [1]. I guess that
> >> you could create a new folder/project for your code.
> >>
> >> Cheers,
> >>
> >> Vincent
> >>
> >> [1] https://svn.apache.org/repos/asf/incubator/shindig/sandbox
> >>
> >> 2009/2/17 chico charlesworth <ch...@googlemail.com>:
> >> > Does anyone know of a svn scratchpad space that would be suitable to
> put
> >> > example shindig code?
> >> >
> >> > Failing this, is it best instead to attach any such example source
> code
> >> to
> >> > the WIKI .. not ideal but might be ok for the interim?
> >> >
> >> > Cheers
> >> > Chico
> >> >
> >> > 2009/2/16 Ian Boston <ie...@tfd.co.uk>
> >> >
> >> >> Chico,
> >> >> Could you ask the question on list, everyone should be a part of the
> >> >> discussion, you never know some one might have an unexpected gem on
> the
> >> >> subject :)
> >> >> Thanks
> >> >> Ian
> >> >>
> >> >> On 16 Feb 2009, at 22:40, chico charlesworth wrote:
> >> >>
> >> >> Hi Vincent,
> >> >>>
> >> >>> Can you point me to the svn sandbook space that you mentioned .. I
> >> think
> >> >>> we all agree that it would be nice to have a standard place to put
> >> example
> >> >>> code, but Ian says he doesn't think that shindig has such a
> scratchpad
> >> place
> >> >>> (see below)?
> >> >>>
> >> >>> Failing this, I can just attach the example source code to the WIKI
> >> page
> >> >>> .. not ideal but might be ok for the interim?
> >> >>>
> >> >>> Cheers
> >> >>> Chico
> >> >>>
> >> >>> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
> >> >>> Chico,
> >> >>> I think some projects have a scratchpad space which is probably
> along
> >> side
> >> >>> trunk but not trunk.
> >> >>>
> >> >>> AFAIK, Shindig doesn't have one.
> >> >>>
> >> >>> I would bring it up on the list, as there may be a more standard
> place
> >> to
> >> >>> put it, and Vincent would certainly know.... sounds like a good idea
> to
> >> me
> >> >>> and reduces the effort levels required maintianing it.
> >> >>>
> >> >>> Remember, that committing anything into trunk comes with it a
> >> commitment
> >> >>> to nurture the committed code, and if its part of the trunk, then
> that
> >> can
> >> >>> be a pain.
> >> >>>
> >> >>> Ian
> >> >>>
> >> >>>
> >> >>> On 16 Feb 2009, at 14:25, chico charlesworth wrote:
> >> >>>
> >> >>> Hi Ian,
> >> >>>
> >> >>> Any idea where this svn sandbook space might be that Vincent
> mentioned?
> >> By
> >> >>> any chance have you got commit access to it?
> >> >>> I could just attach the spring example source code to the wiki page,
> >> but
> >> >>> would of course be best placed in svn so that it can be regularly
> >> updated to
> >> >>> keep in synch w/ shindig.
> >> >>>
> >> >>> Cheers
> >> >>> Chico
> >> >>>
> >> >>> 2009/2/13 chico charlesworth <ch...@googlemail.com>
> >> >>> I've created a new WIKI page entitled "Shindig Spring Example":
> >> >>> -
> >> >>>
> >>
> http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
> >> >>>
> >> >>> Can someone help me to get the source code into the svn sandbook
> space
> >> >>> that Vincent mentioned? Then I can update the WIKI page w/ a link to
> >> the
> >> >>> source code, so people can try out the example :)
> >> >>>
> >> >>> Cheers
> >> >>> Chico
> >> >>>
> >> >>> 2009/2/11 Vincent Siveton <vi...@gmail.com>
> >> >>>
> >> >>> Hi
> >> >>>
> >> >>> The wiki is definitely the best approach, a cookbook style could be
> a
> >> >>> good approach.
> >> >>> If you have some code, you could put it in a sandbok space in svn.
> >> >>>
> >> >>> Cheers,
> >> >>>
> >> >>> Vincent
> >> >>>
> >> >>> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
> >> >>> > Hi all,
> >> >>> >
> >> >>> > As you know shindig relies on guice as the preferred dependency
> >> >>> injection
> >> >>> > framework, and that is all good. Yet we've gone with the approach
> of
> >> >>> using
> >> >>> > both spring and guice, simply because spring offers us great
> support
> >> for
> >> >>> JPA
> >> >>> > (e.g. transaction management) and AOP, and it's likely that we'll
> be
> >> >>> using
> >> >>> > other Spring features down the line. There has been a couple of
> >> >>> challenges
> >> >>> > in getting the project working nicely with these two technologies
> >> side
> >> >>> by
> >> >>> > side, but we're fairly happy as things stand right now. Note that
> the
> >> >>> > integration doesn't include any changes to the shindig codebase,
> that
> >> >>> is, we
> >> >>> > still let shindig use guice as expected.
> >> >>> >
> >> >>> > My question to the community is, first and foremost, do you think
> >> this
> >> >>> would
> >> >>> > be beneficial to other people? And if so, what is the best
> approach
> >> in
> >> >>> > contributing the shindig/spring integration work we've done?
> >> >>> >
> >> >>> > At the minimum we would like to document this integration work and
> >> make
> >> >>> it
> >> >>> > available to the community, either in a WIKI or as a tutorial.
> >> Another
> >> >>> > approach would be to include the code in the samples module, but
> then
> >> I
> >> >>> > guess we would have to consider splitting the samples module into
> sub
> >> >>> > projects?
> >> >>> >
> >> >>> > Cheers,
> >> >>> > Chico
> >> >>> >
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >>
> >
>
Re: shindig and spring integration
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Chico,
NP, shoot me the code and I will commit it.
Cheers,
Vincent
2009/2/17 chico charlesworth <ch...@googlemail.com>:
> great, thx Vincent for setting that up!
>
> I don't yet have commit access though .. still eagerly awaiting for my
> account to be setup :)
>
> can I email you the code Vincent, and ask you to commit it on my behalf to:
> https://svn.apache.org/repos/asf/incubator/shindig/sandbox
> /shindig-spring-example/trunk
>
> Cheers
> Chico
>
> 2009/2/17 Vincent Siveton <vi...@gmail.com>
>
>> Hi Chico,
>>
>> <Sorry for the delay.>
>>
>> Now that svn is up, I created a sandbox space in svn [1]. I guess that
>> you could create a new folder/project for your code.
>>
>> Cheers,
>>
>> Vincent
>>
>> [1] https://svn.apache.org/repos/asf/incubator/shindig/sandbox
>>
>> 2009/2/17 chico charlesworth <ch...@googlemail.com>:
>> > Does anyone know of a svn scratchpad space that would be suitable to put
>> > example shindig code?
>> >
>> > Failing this, is it best instead to attach any such example source code
>> to
>> > the WIKI .. not ideal but might be ok for the interim?
>> >
>> > Cheers
>> > Chico
>> >
>> > 2009/2/16 Ian Boston <ie...@tfd.co.uk>
>> >
>> >> Chico,
>> >> Could you ask the question on list, everyone should be a part of the
>> >> discussion, you never know some one might have an unexpected gem on the
>> >> subject :)
>> >> Thanks
>> >> Ian
>> >>
>> >> On 16 Feb 2009, at 22:40, chico charlesworth wrote:
>> >>
>> >> Hi Vincent,
>> >>>
>> >>> Can you point me to the svn sandbook space that you mentioned .. I
>> think
>> >>> we all agree that it would be nice to have a standard place to put
>> example
>> >>> code, but Ian says he doesn't think that shindig has such a scratchpad
>> place
>> >>> (see below)?
>> >>>
>> >>> Failing this, I can just attach the example source code to the WIKI
>> page
>> >>> .. not ideal but might be ok for the interim?
>> >>>
>> >>> Cheers
>> >>> Chico
>> >>>
>> >>> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
>> >>> Chico,
>> >>> I think some projects have a scratchpad space which is probably along
>> side
>> >>> trunk but not trunk.
>> >>>
>> >>> AFAIK, Shindig doesn't have one.
>> >>>
>> >>> I would bring it up on the list, as there may be a more standard place
>> to
>> >>> put it, and Vincent would certainly know.... sounds like a good idea to
>> me
>> >>> and reduces the effort levels required maintianing it.
>> >>>
>> >>> Remember, that committing anything into trunk comes with it a
>> commitment
>> >>> to nurture the committed code, and if its part of the trunk, then that
>> can
>> >>> be a pain.
>> >>>
>> >>> Ian
>> >>>
>> >>>
>> >>> On 16 Feb 2009, at 14:25, chico charlesworth wrote:
>> >>>
>> >>> Hi Ian,
>> >>>
>> >>> Any idea where this svn sandbook space might be that Vincent mentioned?
>> By
>> >>> any chance have you got commit access to it?
>> >>> I could just attach the spring example source code to the wiki page,
>> but
>> >>> would of course be best placed in svn so that it can be regularly
>> updated to
>> >>> keep in synch w/ shindig.
>> >>>
>> >>> Cheers
>> >>> Chico
>> >>>
>> >>> 2009/2/13 chico charlesworth <ch...@googlemail.com>
>> >>> I've created a new WIKI page entitled "Shindig Spring Example":
>> >>> -
>> >>>
>> http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
>> >>>
>> >>> Can someone help me to get the source code into the svn sandbook space
>> >>> that Vincent mentioned? Then I can update the WIKI page w/ a link to
>> the
>> >>> source code, so people can try out the example :)
>> >>>
>> >>> Cheers
>> >>> Chico
>> >>>
>> >>> 2009/2/11 Vincent Siveton <vi...@gmail.com>
>> >>>
>> >>> Hi
>> >>>
>> >>> The wiki is definitely the best approach, a cookbook style could be a
>> >>> good approach.
>> >>> If you have some code, you could put it in a sandbok space in svn.
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Vincent
>> >>>
>> >>> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
>> >>> > Hi all,
>> >>> >
>> >>> > As you know shindig relies on guice as the preferred dependency
>> >>> injection
>> >>> > framework, and that is all good. Yet we've gone with the approach of
>> >>> using
>> >>> > both spring and guice, simply because spring offers us great support
>> for
>> >>> JPA
>> >>> > (e.g. transaction management) and AOP, and it's likely that we'll be
>> >>> using
>> >>> > other Spring features down the line. There has been a couple of
>> >>> challenges
>> >>> > in getting the project working nicely with these two technologies
>> side
>> >>> by
>> >>> > side, but we're fairly happy as things stand right now. Note that the
>> >>> > integration doesn't include any changes to the shindig codebase, that
>> >>> is, we
>> >>> > still let shindig use guice as expected.
>> >>> >
>> >>> > My question to the community is, first and foremost, do you think
>> this
>> >>> would
>> >>> > be beneficial to other people? And if so, what is the best approach
>> in
>> >>> > contributing the shindig/spring integration work we've done?
>> >>> >
>> >>> > At the minimum we would like to document this integration work and
>> make
>> >>> it
>> >>> > available to the community, either in a WIKI or as a tutorial.
>> Another
>> >>> > approach would be to include the code in the samples module, but then
>> I
>> >>> > guess we would have to consider splitting the samples module into sub
>> >>> > projects?
>> >>> >
>> >>> > Cheers,
>> >>> > Chico
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>
>> >
>>
>
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
great, thx Vincent for setting that up!
I don't yet have commit access though .. still eagerly awaiting for my
account to be setup :)
can I email you the code Vincent, and ask you to commit it on my behalf to:
https://svn.apache.org/repos/asf/incubator/shindig/sandbox
/shindig-spring-example/trunk
Cheers
Chico
2009/2/17 Vincent Siveton <vi...@gmail.com>
> Hi Chico,
>
> <Sorry for the delay.>
>
> Now that svn is up, I created a sandbox space in svn [1]. I guess that
> you could create a new folder/project for your code.
>
> Cheers,
>
> Vincent
>
> [1] https://svn.apache.org/repos/asf/incubator/shindig/sandbox
>
> 2009/2/17 chico charlesworth <ch...@googlemail.com>:
> > Does anyone know of a svn scratchpad space that would be suitable to put
> > example shindig code?
> >
> > Failing this, is it best instead to attach any such example source code
> to
> > the WIKI .. not ideal but might be ok for the interim?
> >
> > Cheers
> > Chico
> >
> > 2009/2/16 Ian Boston <ie...@tfd.co.uk>
> >
> >> Chico,
> >> Could you ask the question on list, everyone should be a part of the
> >> discussion, you never know some one might have an unexpected gem on the
> >> subject :)
> >> Thanks
> >> Ian
> >>
> >> On 16 Feb 2009, at 22:40, chico charlesworth wrote:
> >>
> >> Hi Vincent,
> >>>
> >>> Can you point me to the svn sandbook space that you mentioned .. I
> think
> >>> we all agree that it would be nice to have a standard place to put
> example
> >>> code, but Ian says he doesn't think that shindig has such a scratchpad
> place
> >>> (see below)?
> >>>
> >>> Failing this, I can just attach the example source code to the WIKI
> page
> >>> .. not ideal but might be ok for the interim?
> >>>
> >>> Cheers
> >>> Chico
> >>>
> >>> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
> >>> Chico,
> >>> I think some projects have a scratchpad space which is probably along
> side
> >>> trunk but not trunk.
> >>>
> >>> AFAIK, Shindig doesn't have one.
> >>>
> >>> I would bring it up on the list, as there may be a more standard place
> to
> >>> put it, and Vincent would certainly know.... sounds like a good idea to
> me
> >>> and reduces the effort levels required maintianing it.
> >>>
> >>> Remember, that committing anything into trunk comes with it a
> commitment
> >>> to nurture the committed code, and if its part of the trunk, then that
> can
> >>> be a pain.
> >>>
> >>> Ian
> >>>
> >>>
> >>> On 16 Feb 2009, at 14:25, chico charlesworth wrote:
> >>>
> >>> Hi Ian,
> >>>
> >>> Any idea where this svn sandbook space might be that Vincent mentioned?
> By
> >>> any chance have you got commit access to it?
> >>> I could just attach the spring example source code to the wiki page,
> but
> >>> would of course be best placed in svn so that it can be regularly
> updated to
> >>> keep in synch w/ shindig.
> >>>
> >>> Cheers
> >>> Chico
> >>>
> >>> 2009/2/13 chico charlesworth <ch...@googlemail.com>
> >>> I've created a new WIKI page entitled "Shindig Spring Example":
> >>> -
> >>>
> http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
> >>>
> >>> Can someone help me to get the source code into the svn sandbook space
> >>> that Vincent mentioned? Then I can update the WIKI page w/ a link to
> the
> >>> source code, so people can try out the example :)
> >>>
> >>> Cheers
> >>> Chico
> >>>
> >>> 2009/2/11 Vincent Siveton <vi...@gmail.com>
> >>>
> >>> Hi
> >>>
> >>> The wiki is definitely the best approach, a cookbook style could be a
> >>> good approach.
> >>> If you have some code, you could put it in a sandbok space in svn.
> >>>
> >>> Cheers,
> >>>
> >>> Vincent
> >>>
> >>> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
> >>> > Hi all,
> >>> >
> >>> > As you know shindig relies on guice as the preferred dependency
> >>> injection
> >>> > framework, and that is all good. Yet we've gone with the approach of
> >>> using
> >>> > both spring and guice, simply because spring offers us great support
> for
> >>> JPA
> >>> > (e.g. transaction management) and AOP, and it's likely that we'll be
> >>> using
> >>> > other Spring features down the line. There has been a couple of
> >>> challenges
> >>> > in getting the project working nicely with these two technologies
> side
> >>> by
> >>> > side, but we're fairly happy as things stand right now. Note that the
> >>> > integration doesn't include any changes to the shindig codebase, that
> >>> is, we
> >>> > still let shindig use guice as expected.
> >>> >
> >>> > My question to the community is, first and foremost, do you think
> this
> >>> would
> >>> > be beneficial to other people? And if so, what is the best approach
> in
> >>> > contributing the shindig/spring integration work we've done?
> >>> >
> >>> > At the minimum we would like to document this integration work and
> make
> >>> it
> >>> > available to the community, either in a WIKI or as a tutorial.
> Another
> >>> > approach would be to include the code in the samples module, but then
> I
> >>> > guess we would have to consider splitting the samples module into sub
> >>> > projects?
> >>> >
> >>> > Cheers,
> >>> > Chico
> >>> >
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
Re: shindig and spring integration
Posted by Vincent Siveton <vi...@gmail.com>.
Hi Chico,
<Sorry for the delay.>
Now that svn is up, I created a sandbox space in svn [1]. I guess that
you could create a new folder/project for your code.
Cheers,
Vincent
[1] https://svn.apache.org/repos/asf/incubator/shindig/sandbox
2009/2/17 chico charlesworth <ch...@googlemail.com>:
> Does anyone know of a svn scratchpad space that would be suitable to put
> example shindig code?
>
> Failing this, is it best instead to attach any such example source code to
> the WIKI .. not ideal but might be ok for the interim?
>
> Cheers
> Chico
>
> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
>
>> Chico,
>> Could you ask the question on list, everyone should be a part of the
>> discussion, you never know some one might have an unexpected gem on the
>> subject :)
>> Thanks
>> Ian
>>
>> On 16 Feb 2009, at 22:40, chico charlesworth wrote:
>>
>> Hi Vincent,
>>>
>>> Can you point me to the svn sandbook space that you mentioned .. I think
>>> we all agree that it would be nice to have a standard place to put example
>>> code, but Ian says he doesn't think that shindig has such a scratchpad place
>>> (see below)?
>>>
>>> Failing this, I can just attach the example source code to the WIKI page
>>> .. not ideal but might be ok for the interim?
>>>
>>> Cheers
>>> Chico
>>>
>>> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
>>> Chico,
>>> I think some projects have a scratchpad space which is probably along side
>>> trunk but not trunk.
>>>
>>> AFAIK, Shindig doesn't have one.
>>>
>>> I would bring it up on the list, as there may be a more standard place to
>>> put it, and Vincent would certainly know.... sounds like a good idea to me
>>> and reduces the effort levels required maintianing it.
>>>
>>> Remember, that committing anything into trunk comes with it a commitment
>>> to nurture the committed code, and if its part of the trunk, then that can
>>> be a pain.
>>>
>>> Ian
>>>
>>>
>>> On 16 Feb 2009, at 14:25, chico charlesworth wrote:
>>>
>>> Hi Ian,
>>>
>>> Any idea where this svn sandbook space might be that Vincent mentioned? By
>>> any chance have you got commit access to it?
>>> I could just attach the spring example source code to the wiki page, but
>>> would of course be best placed in svn so that it can be regularly updated to
>>> keep in synch w/ shindig.
>>>
>>> Cheers
>>> Chico
>>>
>>> 2009/2/13 chico charlesworth <ch...@googlemail.com>
>>> I've created a new WIKI page entitled "Shindig Spring Example":
>>> -
>>> http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
>>>
>>> Can someone help me to get the source code into the svn sandbook space
>>> that Vincent mentioned? Then I can update the WIKI page w/ a link to the
>>> source code, so people can try out the example :)
>>>
>>> Cheers
>>> Chico
>>>
>>> 2009/2/11 Vincent Siveton <vi...@gmail.com>
>>>
>>> Hi
>>>
>>> The wiki is definitely the best approach, a cookbook style could be a
>>> good approach.
>>> If you have some code, you could put it in a sandbok space in svn.
>>>
>>> Cheers,
>>>
>>> Vincent
>>>
>>> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
>>> > Hi all,
>>> >
>>> > As you know shindig relies on guice as the preferred dependency
>>> injection
>>> > framework, and that is all good. Yet we've gone with the approach of
>>> using
>>> > both spring and guice, simply because spring offers us great support for
>>> JPA
>>> > (e.g. transaction management) and AOP, and it's likely that we'll be
>>> using
>>> > other Spring features down the line. There has been a couple of
>>> challenges
>>> > in getting the project working nicely with these two technologies side
>>> by
>>> > side, but we're fairly happy as things stand right now. Note that the
>>> > integration doesn't include any changes to the shindig codebase, that
>>> is, we
>>> > still let shindig use guice as expected.
>>> >
>>> > My question to the community is, first and foremost, do you think this
>>> would
>>> > be beneficial to other people? And if so, what is the best approach in
>>> > contributing the shindig/spring integration work we've done?
>>> >
>>> > At the minimum we would like to document this integration work and make
>>> it
>>> > available to the community, either in a WIKI or as a tutorial. Another
>>> > approach would be to include the code in the samples module, but then I
>>> > guess we would have to consider splitting the samples module into sub
>>> > projects?
>>> >
>>> > Cheers,
>>> > Chico
>>> >
>>>
>>>
>>>
>>>
>>>
>>
>
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
Does anyone know of a svn scratchpad space that would be suitable to put
example shindig code?
Failing this, is it best instead to attach any such example source code to
the WIKI .. not ideal but might be ok for the interim?
Cheers
Chico
2009/2/16 Ian Boston <ie...@tfd.co.uk>
> Chico,
> Could you ask the question on list, everyone should be a part of the
> discussion, you never know some one might have an unexpected gem on the
> subject :)
> Thanks
> Ian
>
> On 16 Feb 2009, at 22:40, chico charlesworth wrote:
>
> Hi Vincent,
>>
>> Can you point me to the svn sandbook space that you mentioned .. I think
>> we all agree that it would be nice to have a standard place to put example
>> code, but Ian says he doesn't think that shindig has such a scratchpad place
>> (see below)?
>>
>> Failing this, I can just attach the example source code to the WIKI page
>> .. not ideal but might be ok for the interim?
>>
>> Cheers
>> Chico
>>
>> 2009/2/16 Ian Boston <ie...@tfd.co.uk>
>> Chico,
>> I think some projects have a scratchpad space which is probably along side
>> trunk but not trunk.
>>
>> AFAIK, Shindig doesn't have one.
>>
>> I would bring it up on the list, as there may be a more standard place to
>> put it, and Vincent would certainly know.... sounds like a good idea to me
>> and reduces the effort levels required maintianing it.
>>
>> Remember, that committing anything into trunk comes with it a commitment
>> to nurture the committed code, and if its part of the trunk, then that can
>> be a pain.
>>
>> Ian
>>
>>
>> On 16 Feb 2009, at 14:25, chico charlesworth wrote:
>>
>> Hi Ian,
>>
>> Any idea where this svn sandbook space might be that Vincent mentioned? By
>> any chance have you got commit access to it?
>> I could just attach the spring example source code to the wiki page, but
>> would of course be best placed in svn so that it can be regularly updated to
>> keep in synch w/ shindig.
>>
>> Cheers
>> Chico
>>
>> 2009/2/13 chico charlesworth <ch...@googlemail.com>
>> I've created a new WIKI page entitled "Shindig Spring Example":
>> -
>> http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
>>
>> Can someone help me to get the source code into the svn sandbook space
>> that Vincent mentioned? Then I can update the WIKI page w/ a link to the
>> source code, so people can try out the example :)
>>
>> Cheers
>> Chico
>>
>> 2009/2/11 Vincent Siveton <vi...@gmail.com>
>>
>> Hi
>>
>> The wiki is definitely the best approach, a cookbook style could be a
>> good approach.
>> If you have some code, you could put it in a sandbok space in svn.
>>
>> Cheers,
>>
>> Vincent
>>
>> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
>> > Hi all,
>> >
>> > As you know shindig relies on guice as the preferred dependency
>> injection
>> > framework, and that is all good. Yet we've gone with the approach of
>> using
>> > both spring and guice, simply because spring offers us great support for
>> JPA
>> > (e.g. transaction management) and AOP, and it's likely that we'll be
>> using
>> > other Spring features down the line. There has been a couple of
>> challenges
>> > in getting the project working nicely with these two technologies side
>> by
>> > side, but we're fairly happy as things stand right now. Note that the
>> > integration doesn't include any changes to the shindig codebase, that
>> is, we
>> > still let shindig use guice as expected.
>> >
>> > My question to the community is, first and foremost, do you think this
>> would
>> > be beneficial to other people? And if so, what is the best approach in
>> > contributing the shindig/spring integration work we've done?
>> >
>> > At the minimum we would like to document this integration work and make
>> it
>> > available to the community, either in a WIKI or as a tutorial. Another
>> > approach would be to include the code in the samples module, but then I
>> > guess we would have to consider splitting the samples module into sub
>> > projects?
>> >
>> > Cheers,
>> > Chico
>> >
>>
>>
>>
>>
>>
>
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
I've created a new WIKI page entitled "Shindig Spring Example":
- http://cwiki.apache.org/confluence/display/SHINDIG/Shindig+Spring+Example
Can someone help me to get the source code into the svn sandbook space that
Vincent mentioned? Then I can update the WIKI page w/ a link to the source
code, so people can try out the example :)
Cheers
Chico
2009/2/11 Vincent Siveton <vi...@gmail.com>
> Hi
>
> The wiki is definitely the best approach, a cookbook style could be a
> good approach.
> If you have some code, you could put it in a sandbok space in svn.
>
> Cheers,
>
> Vincent
>
> 2009/2/10 chico charlesworth <ch...@googlemail.com>:
> > Hi all,
> >
> > As you know shindig relies on guice as the preferred dependency injection
> > framework, and that is all good. Yet we've gone with the approach of
> using
> > both spring and guice, simply because spring offers us great support for
> JPA
> > (e.g. transaction management) and AOP, and it's likely that we'll be
> using
> > other Spring features down the line. There has been a couple of
> challenges
> > in getting the project working nicely with these two technologies side by
> > side, but we're fairly happy as things stand right now. Note that the
> > integration doesn't include any changes to the shindig codebase, that is,
> we
> > still let shindig use guice as expected.
> >
> > My question to the community is, first and foremost, do you think this
> would
> > be beneficial to other people? And if so, what is the best approach in
> > contributing the shindig/spring integration work we've done?
> >
> > At the minimum we would like to document this integration work and make
> it
> > available to the community, either in a WIKI or as a tutorial. Another
> > approach would be to include the code in the samples module, but then I
> > guess we would have to consider splitting the samples module into sub
> > projects?
> >
> > Cheers,
> > Chico
> >
>
Re: shindig and spring integration
Posted by Vincent Siveton <vi...@gmail.com>.
Hi
The wiki is definitely the best approach, a cookbook style could be a
good approach.
If you have some code, you could put it in a sandbok space in svn.
Cheers,
Vincent
2009/2/10 chico charlesworth <ch...@googlemail.com>:
> Hi all,
>
> As you know shindig relies on guice as the preferred dependency injection
> framework, and that is all good. Yet we've gone with the approach of using
> both spring and guice, simply because spring offers us great support for JPA
> (e.g. transaction management) and AOP, and it's likely that we'll be using
> other Spring features down the line. There has been a couple of challenges
> in getting the project working nicely with these two technologies side by
> side, but we're fairly happy as things stand right now. Note that the
> integration doesn't include any changes to the shindig codebase, that is, we
> still let shindig use guice as expected.
>
> My question to the community is, first and foremost, do you think this would
> be beneficial to other people? And if so, what is the best approach in
> contributing the shindig/spring integration work we've done?
>
> At the minimum we would like to document this integration work and make it
> available to the community, either in a WIKI or as a tutorial. Another
> approach would be to include the code in the samples module, but then I
> guess we would have to consider splitting the samples module into sub
> projects?
>
> Cheers,
> Chico
>
Re: Group Support in Shindig
Posted by Louis Ryan <lr...@google.com>.
The short answer is nothing beyond the user relative groups like @friends.
There has been some pretty lively discussion on the spec group about this (
http://groups.google.com/group/opensocial-and-gadgets-spec/topics) but
nothing is on the slate for 0.9
On Thu, Feb 12, 2009 at 6:18 AM, Gary Stevens <gs...@us.ibm.com> wrote:
> I've been wondering this as well.
>
> Gary F Stevens (gstevens@us.ibm.com)
>
>
> [image: Inactive hide details for Travis Winters ---02/10/2009 04:44:04
> PM---Hi all,]Travis Winters ---02/10/2009 04:44:04 PM---Hi all,
>
>
> *Travis Winters <tr...@cogentconsulting.com.au>*
>
> 02/10/2009 04:42 PM
> Please respond to
> shindig-dev@incubator.apache.org
>
>
> To
>
> shindig-dev@incubator.apache.org
> cc
>
>
> Subject
>
> Group Support in Shindig
>
> Hi all,
>
> I apologise in advance, as I believe this question gets asked about
> once every couple of months; what's the current support for Groups in
> Shindig?
>
> Cheers,
> Travis
>
> --
>
> Travis Winters
>
> e travis.winters@cogentconsulting.com.au
> w http://www.cogentconsulting.com.au/
> m 0412 373 167
>
>
> This email, including attachments, is intended only for the addressee and
> may be confidential, privileged and subject to copyright. If you have
> received this email in error, please advise the sender and delete it. If you
> are not the intended recipient of this email, you must not communicate to
> others content that is confidential or subject to copyright, unless you have
> the consent of the content owner.
>
>
>
Re: Group Support in Shindig
Posted by Gary Stevens <gs...@us.ibm.com>.
I've been wondering this as well.
Gary F Stevens (gstevens@us.ibm.com)
Travis Winters
<travis.winters@c
ogentconsulting.c To
om.au> shindig-dev@incubator.apache.org
cc
02/10/2009 04:42
PM Subject
Group Support in Shindig
Please respond to
shindig-dev@incub
ator.apache.org
Hi all,
I apologise in advance, as I believe this question gets asked about
once every couple of months; what's the current support for Groups in
Shindig?
Cheers,
Travis
--
Travis Winters
e travis.winters@cogentconsulting.com.au
w http://www.cogentconsulting.com.au/
m 0412 373 167
This email, including attachments, is intended only for the addressee and
may be confidential, privileged and subject to copyright. If you have
received this email in error, please advise the sender and delete it. If
you are not the intended recipient of this email, you must not communicate
to others content that is confidential or subject to copyright, unless you
have the consent of the content owner.
Group Support in Shindig
Posted by Travis Winters <tr...@cogentconsulting.com.au>.
Hi all,
I apologise in advance, as I believe this question gets asked about
once every couple of months; what's the current support for Groups in
Shindig?
Cheers,
Travis
--
Travis Winters
e travis.winters@cogentconsulting.com.au
w http://www.cogentconsulting.com.au/
m 0412 373 167
This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner.
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
Thx harry, nice to know that we're not the only ones also using Spring :)
2009/2/11 <ha...@nexgo.de>
> From the point of view of a shindig consumer having more example projects
> showing different integration forms would be very useful.
> The community project I am working at an integration we have an existing
> persistence part that uses spring, hibernate and AOP.
> I think many people deal with these technologies in their projects and
> would be thankful for some examples.
>
> Harry
>
>
> Erwischt! Bei Arcor sehen Sie die besten Promi-Bilder riesengroß und in
> Top-Qualität. Hier finden Sie die schönsten Schnappschüsse auf dem roten
> Teppich, lernen die Frauen des Womanizers Boris Becker kennen und schauen
> den Royals ins Wohnzimmer. Viel Spaß auf Ihrer virtuellen Reise durch die
> Welt der Stars und Sternchen: http://vip.arcor.de.
>
Re: shindig and spring integration
Posted by ha...@nexgo.de.
>From the point of view of a shindig consumer having more example projects showing different integration forms would be very useful.
The community project I am working at an integration we have an existing persistence part that uses spring, hibernate and AOP.
I think many people deal with these technologies in their projects and would be thankful for some examples.
Harry
Erwischt! Bei Arcor sehen Sie die besten Promi-Bilder riesengroß und in Top-Qualität. Hier finden Sie die schönsten Schnappschüsse auf dem roten Teppich, lernen die Frauen des Womanizers Boris Becker kennen und schauen den Royals ins Wohnzimmer. Viel Spaß auf Ihrer virtuellen Reise durch die Welt der Stars und Sternchen: http://vip.arcor.de.
Re: shindig and spring integration
Posted by chico charlesworth <ch...@googlemail.com>.
All valid points .. sounds best then if I start with documenting it in the
WIKI. Note that this will focus on shindig and spring integration, not
hibernate and AOP .. what Spring is used for after it has been integrated is
down to the user.
Regarding the samples module, imho it's somewhat losing its focus and is
becoming less effective than it should be. I'm also not convinced that the
validation of the SPI should sit in samples? I'd say it would be more useful
to the community if the samples module were to focus on being a good samples
code reference, but split into various mini example projects, each providing
a good test bed to all of shindig's integration hooks.
Cheers,
Chico
2009/2/10 Ian Boston <ie...@tfd.co.uk>
>
> The Samples project was intended as a validation of the SPI inside social.
>
> IMHO, Spring/Hibernate and AOP all make a jar/subsystem harder to embed in
> other projects, that don't use the same version of Spring/Hibernate[1]
>
> So I think:
> WIki Documentation +1
> A project on code.google.com that depends on Shindig and shares how to
> integrate with Spring +0
> Add Spring to Samples -0.5 (on the grounds of distraction, code base size &
> potential jar conflicts)
> Convert Shindig to Spring (not that you were suggesting this) -1
>
> Thats just my view based on having used Spring[2] for the past 4 years and
> recently converted to Guice[3].
>
> Ian
>
> [1] Try embedding Alfresco compared to embedding Jackrabbit
> [2] https://www.ohloh.net/p/3551
> [3] https://www.ohloh.net/p/sakai-kernel
>
>
> On 10 Feb 2009, at 14:39, chico charlesworth wrote:
>
> Hi all,
>>
>> As you know shindig relies on guice as the preferred dependency injection
>> framework, and that is all good. Yet we've gone with the approach of using
>> both spring and guice, simply because spring offers us great support for
>> JPA
>> (e.g. transaction management) and AOP, and it's likely that we'll be using
>> other Spring features down the line. There has been a couple of challenges
>> in getting the project working nicely with these two technologies side by
>> side, but we're fairly happy as things stand right now. Note that the
>> integration doesn't include any changes to the shindig codebase, that is,
>> we
>> still let shindig use guice as expected.
>>
>> My question to the community is, first and foremost, do you think this
>> would
>> be beneficial to other people? And if so, what is the best approach in
>> contributing the shindig/spring integration work we've done?
>>
>> At the minimum we would like to document this integration work and make it
>> available to the community, either in a WIKI or as a tutorial. Another
>> approach would be to include the code in the samples module, but then I
>> guess we would have to consider splitting the samples module into sub
>> projects?
>>
>> Cheers,
>> Chico
>>
>
>
Re: shindig and spring integration
Posted by Ian Boston <ie...@tfd.co.uk>.
The Samples project was intended as a validation of the SPI inside
social.
IMHO, Spring/Hibernate and AOP all make a jar/subsystem harder to
embed in other projects, that don't use the same version of Spring/
Hibernate[1]
So I think:
WIki Documentation +1
A project on code.google.com that depends on Shindig and shares how to
integrate with Spring +0
Add Spring to Samples -0.5 (on the grounds of distraction, code base
size & potential jar conflicts)
Convert Shindig to Spring (not that you were suggesting this) -1
Thats just my view based on having used Spring[2] for the past 4 years
and recently converted to Guice[3].
Ian
[1] Try embedding Alfresco compared to embedding Jackrabbit
[2] https://www.ohloh.net/p/3551
[3] https://www.ohloh.net/p/sakai-kernel
On 10 Feb 2009, at 14:39, chico charlesworth wrote:
> Hi all,
>
> As you know shindig relies on guice as the preferred dependency
> injection
> framework, and that is all good. Yet we've gone with the approach of
> using
> both spring and guice, simply because spring offers us great support
> for JPA
> (e.g. transaction management) and AOP, and it's likely that we'll be
> using
> other Spring features down the line. There has been a couple of
> challenges
> in getting the project working nicely with these two technologies
> side by
> side, but we're fairly happy as things stand right now. Note that the
> integration doesn't include any changes to the shindig codebase,
> that is, we
> still let shindig use guice as expected.
>
> My question to the community is, first and foremost, do you think
> this would
> be beneficial to other people? And if so, what is the best approach in
> contributing the shindig/spring integration work we've done?
>
> At the minimum we would like to document this integration work and
> make it
> available to the community, either in a WIKI or as a tutorial. Another
> approach would be to include the code in the samples module, but
> then I
> guess we would have to consider splitting the samples module into sub
> projects?
>
> Cheers,
> Chico