You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by J Aaron Farr <ja...@yahoo.com> on 2003/01/30 03:29:56 UTC
Fortress Tutorial
Hello all.
I've been slowly working on a Fortress Newbie Tutorial. Shash
Chatterjee has also volunteered to help me.
Thus far I've mostly just been jotting down notes as I've been building
my own first Fortress app, but I hope to start really writing something
over the next few days (goal is to have at least "something" by
Sunday). Anyway, I know that Fortress has just undergone significant
refactoring and I was planning on basing the tutorial on the updated
CVS. Before I went through all the work to do that I wanted to check if
this was a wise idea. I'm assuming the refactored code is what's being
targeted for the 1.0 release.
I've divided the tutorial into a number of parts, but my first target
will simply be a "jump right in and get something running" document
based on the existing Fortress examples. Sort of a "hello world" in
Fortress followed by a detail explanation of how and why it works --
something that complements the "Developing with Avalon" documentation.
After that I'd like to write more about the other examples and then
about writing new services/components for Fortress.
Hopefully I'll have something finished in time for the 1.0 release. Any
suggestions or direction would be appriciated.
Thanks
--
jaaron <ja...@yahoo.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Fortress Tutorial
Posted by Stephen McConnell <mc...@apache.org>.
J Aaron Farr wrote:
>On Wed, 2003-01-29 at 21:32, Stephen McConnell wrote:
>
>
>>J Aaron Farr wrote:
>>
>>
>>
>>>Hello all.
>>>
>>>I've been slowly working on a Fortress Newbie Tutorial. Shash
>>>Chatterjee has also volunteered to help me.
>>>
>>>Thus far I've mostly just been jotting down notes as I've been building
>>>my own first Fortress app, but I hope to start really writing something
>>>over the next few days (goal is to have at least "something" by
>>>Sunday). Anyway, I know that Fortress has just undergone significant
>>>refactoring and I was planning on basing the tutorial on the updated
>>>CVS. Before I went through all the work to do that I wanted to check if
>>>this was a wise idea. I'm assuming the refactored code is what's being
>>>targeted for the 1.0 release.
>>>
>>>I've divided the tutorial into a number of parts, but my first target
>>>will simply be a "jump right in and get something running" document
>>>based on the existing Fortress examples. Sort of a "hello world" in
>>>Fortress followed by a detail explanation of how and why it works --
>>>something that complements the "Developing with Avalon" documentation.
>>>After that I'd like to write more about the other examples and then
>>>about writing new services/components for Fortress.
>>>
>>>Hopefully I'll have something finished in time for the 1.0 release. Any
>>>suggestions or direction would be appriciated.
>>>
>>>
>>>
>>I'm really intersted to know that interfaces/classes you need to
>>expose/use. Of particular interest to me in the usage of the component
>>handler and the default container (refer general Fortress / Merlin
>>discussions).
>>
>>Cheers, Steve.
>>
>>
>
>Well, I'm planning on migrating my code to use the newer Fortress code.
>That in addition to fact that my understanding of Avalon/Fortress has
>changed a lot since I started means that I'm probably going to change
>which interface/classes I use. I figured I could kill a couple birds
>with one stone by migrating the code and writing parts of the tutorial
>as I do it. Consequently I may be asking a few questions on the user
>list about the "best" way to do this or that so I eventually get it
>right.
>
Cool - I'll be watching and I'll be thinking about (a) Fortress/Merlin
sync. + (b) Fortess liabilities on relase. I.e. what can be converged
today before release and what are we going to have to take care of in
the near term.
Cheers, Steve.
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Fortress Tutorial
Posted by J Aaron Farr <ja...@yahoo.com>.
On Wed, 2003-01-29 at 21:32, Stephen McConnell wrote:
> J Aaron Farr wrote:
>
> >Hello all.
> >
> >I've been slowly working on a Fortress Newbie Tutorial. Shash
> >Chatterjee has also volunteered to help me.
> >
> >Thus far I've mostly just been jotting down notes as I've been building
> >my own first Fortress app, but I hope to start really writing something
> >over the next few days (goal is to have at least "something" by
> >Sunday). Anyway, I know that Fortress has just undergone significant
> >refactoring and I was planning on basing the tutorial on the updated
> >CVS. Before I went through all the work to do that I wanted to check if
> >this was a wise idea. I'm assuming the refactored code is what's being
> >targeted for the 1.0 release.
> >
> >I've divided the tutorial into a number of parts, but my first target
> >will simply be a "jump right in and get something running" document
> >based on the existing Fortress examples. Sort of a "hello world" in
> >Fortress followed by a detail explanation of how and why it works --
> >something that complements the "Developing with Avalon" documentation.
> >After that I'd like to write more about the other examples and then
> >about writing new services/components for Fortress.
> >
> >Hopefully I'll have something finished in time for the 1.0 release. Any
> >suggestions or direction would be appriciated.
> >
>
> I'm really intersted to know that interfaces/classes you need to
> expose/use. Of particular interest to me in the usage of the component
> handler and the default container (refer general Fortress / Merlin
> discussions).
>
> Cheers, Steve.
Well, I'm planning on migrating my code to use the newer Fortress code.
That in addition to fact that my understanding of Avalon/Fortress has
changed a lot since I started means that I'm probably going to change
which interface/classes I use. I figured I could kill a couple birds
with one stone by migrating the code and writing parts of the tutorial
as I do it. Consequently I may be asking a few questions on the user
list about the "best" way to do this or that so I eventually get it
right.
Thanks.
--
jaaron <ja...@yahoo.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Fortress Tutorial
Posted by Stephen McConnell <mc...@apache.org>.
J Aaron Farr wrote:
>Hello all.
>
>I've been slowly working on a Fortress Newbie Tutorial. Shash
>Chatterjee has also volunteered to help me.
>
>Thus far I've mostly just been jotting down notes as I've been building
>my own first Fortress app, but I hope to start really writing something
>over the next few days (goal is to have at least "something" by
>Sunday). Anyway, I know that Fortress has just undergone significant
>refactoring and I was planning on basing the tutorial on the updated
>CVS. Before I went through all the work to do that I wanted to check if
>this was a wise idea. I'm assuming the refactored code is what's being
>targeted for the 1.0 release.
>
>I've divided the tutorial into a number of parts, but my first target
>will simply be a "jump right in and get something running" document
>based on the existing Fortress examples. Sort of a "hello world" in
>Fortress followed by a detail explanation of how and why it works --
>something that complements the "Developing with Avalon" documentation.
>After that I'd like to write more about the other examples and then
>about writing new services/components for Fortress.
>
>Hopefully I'll have something finished in time for the 1.0 release. Any
>suggestions or direction would be appriciated.
>
I'm really intersted to know that interfaces/classes you need to
expose/use. Of particular interest to me in the usage of the component
handler and the default container (refer general Fortress / Merlin
discussions).
Cheers, Steve.
>
>Thanks
>
>
>
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Fortress Tutorial
Posted by Berin Loritsch <bl...@apache.org>.
J Aaron Farr wrote:
> Hello all.
>
> I've been slowly working on a Fortress Newbie Tutorial. Shash
> Chatterjee has also volunteered to help me.
>
> Thus far I've mostly just been jotting down notes as I've been building
> my own first Fortress app, but I hope to start really writing something
> over the next few days (goal is to have at least "something" by
> Sunday). Anyway, I know that Fortress has just undergone significant
> refactoring and I was planning on basing the tutorial on the updated
> CVS. Before I went through all the work to do that I wanted to check if
> this was a wise idea. I'm assuming the refactored code is what's being
> targeted for the 1.0 release.
>
> I've divided the tutorial into a number of parts, but my first target
> will simply be a "jump right in and get something running" document
> based on the existing Fortress examples. Sort of a "hello world" in
> Fortress followed by a detail explanation of how and why it works --
> something that complements the "Developing with Avalon" documentation.
> After that I'd like to write more about the other examples and then
> about writing new services/components for Fortress.
>
> Hopefully I'll have something finished in time for the 1.0 release. Any
> suggestions or direction would be appriciated.
>
> Thanks
Awesome! Please send it in!
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Fortress Tutorial
Posted by Leo Simons <le...@apache.org>.
J Aaron Farr wrote:
> Hello all.
>
> I've been slowly working on a Fortress Newbie Tutorial. Shash
> Chatterjee has also volunteered to help me.
way cool! I'll be happy to answer any questions I can :D
> Thus far I've mostly just been jotting down notes as I've been building
> my own first Fortress app, but I hope to start really writing something
> over the next few days (goal is to have at least "something" by
> Sunday). Anyway, I know that Fortress has just undergone significant
> refactoring and I was planning on basing the tutorial on the updated
> CVS. Before I went through all the work to do that I wanted to check if
> this was a wise idea. I'm assuming the refactored code is what's being
> targeted for the 1.0 release.
yes. Note the refactoring is 99% class movement and only 1% something
else. You probably only have to change package names for various classes.
> I've divided the tutorial into a number of parts, but my first target
> will simply be a "jump right in and get something running" document
> based on the existing Fortress examples. Sort of a "hello world" in
> Fortress followed by a detail explanation of how and why it works --
> something that complements the "Developing with Avalon" documentation.
sounds smart. It would be nice to have the code from that helloworld
example in source code form in the source tree (ie @
jakarta-avalon-excalibur/fortress/examples/).
> After that I'd like to write more about the other examples and then
> about writing new services/components for Fortress.
sounds good, too.
> Hopefully I'll have something finished in time for the 1.0 release. Any
> suggestions or direction would be appriciated.
my suggestion would be "release early, release often". Once you get
something up you are not afraid of showing to the outside world, put it
somewhere public (you could put a zipfile in bugzilla or something like
that, for example), and providing feedback would be easier.
Also, don't worry too much about release schedules. Your tutorial can go
online regardless of whether it is completely polished, and we can
reference it from the distribution.
cheers (and thanks for taking this up!),
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org