[infinispan-dev] Infinispan tutorial

Galder Zamarreño galder at redhat.com
Tue Jan 6 03:21:33 EST 2015


On 06 Jan 2015, at 09:17, Galder Zamarreño <galder at redhat.com> wrote:

> 
> On 06 Nov 2014, at 12:38, Tristan Tarrant <ttarrant at redhat.com> wrote:
> 
>> Thanks Galder,
>> 
>> - no logging in step-0: that is expected (and why it's called step '0'), 
>> and I will say so in the actual tutorial text
>> - logging is happening for me, haven't tried with the lower settings
>> 
>> I have added one more step which makes the cache clustered and I have 
>> updated the tags.
>> Obviously all of this is done via horrible git force pushing :)
> 
> ^ I was just thinking about that. If you want to make any changes to each step, say step-0, you have to change that commit and subsequent ones, right? 
> 
> e.g. I wanted to add IntelliJ files to step-0’s .gitignore

Or other adjustments, such as updating dependencies, update README information...etc.

> 
> Cheers,
> 
>> 
>> Tristan
>> 
>> On 05/11/14 08:34, Galder Zamarreño wrote:
>>> Hi Tristan,
>>> 
>>> +1 to having a more step-by-step tutorial :)
>>> 
>>> I’ve tried the tutorial locally and made some notes:
>>> 
>>> - step-0 is a bit confusing since nothing is logged. However, no logging is not due to not enabling it, but the fact that nothing kicks in until getCache() is called, and that only happens in step-1.
>>> 
>>> - How do you enable logging? Also, not sure what I need to change in logging.properties to see some logging of Infinispan. For example: how do you enable debug/trace logging? I’ve tried FINER/FINEST too but did not make a difference. Maybe I need a org.infinispan specific level/formatter combination?
>>> 
>>> - step-4 tag missing.
>>> 
>>> Great work!!
>>> 
>>> Cheers,
>>> 
>>> On 29 Oct 2014, at 14:47, Tristan Tarrant <ttarrant at redhat.com> wrote:
>>> 
>>>> Hi guys,
>>>> 
>>>> I've been working on how to spruce up our website, docs and code samples.
>>>> While quickstarts are ok, they come as monolithic blobs which tell you
>>>> nothing about how you got there. For this reason I believe a
>>>> step-by-step tutorial approach is better and I've been looking at the
>>>> AngularJS tutorials [0] as good examples on how to achieve this.
>>>> I have created a repo [1] on my GitHub user where each commit is a step
>>>> in the tutorial. I have tagged the commits using 'step-n' so that you
>>>> can checkout any of the steps and run them:
>>>> 
>>>> git checkout step-1
>>>> mvn clean package exec:java
>>>> 
>>>> The GitHub web interface can be used to show the diff between steps, so
>>>> that it can be linked from the docs [2].
>>>> 
>>>> Currently I'm not aiming to build a real application (although
>>>> suggestions are welcome in this sense), but just going through the
>>>> basics, adding features one by one, etc.
>>>> 
>>>> Comments are welcome.
>>>> 
>>>> Tristan
>>>> 
>>>> ---
>>>> [0] https://docs.angularjs.org/tutorial/step_00
>>>> [1] https://github.com/tristantarrant/infinispan-embedded-tutorial
>>>> [2]
>>>> https://github.com/tristantarrant/infinispan-embedded-tutorial/compare/step-0...step-1?diff=unified
>>>> 
>>>> _______________________________________________
>>>> infinispan-dev mailing list
>>>> infinispan-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> 
>>> --
>>> Galder Zamarreño
>>> galder at redhat.com
>>> twitter.com/galderz
>>> 
>>> 
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>> 
>>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> 
> --
> Galder Zamarreño
> galder at redhat.com
> twitter.com/galderz
> 


--
Galder Zamarreño
galder at redhat.com
twitter.com/galderz




More information about the infinispan-dev mailing list