commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kohsuke Kawaguchi ...@kohsuke.org>
Subject Re: [javaflow] Knowing when there's nothing to continue
Date Thu, 28 Jul 2005 21:50:18 GMT
Torsten Curdt wrote:
>>
>> It looks like the other discussion is going to take longer, so  
>> meanwhile I have a few other simple changes.
> 
> Hehe ...bring it on ;)
> 
> Did you have a look into the Cocoon integration?
> Looking at javaflow from that standpoint you will
> probably understand some of my requirements.

I intend to do so, before I write a response on the MethodLookup thread. 
But I couldn't work on it yesterday. This isn'y my day job, unfortunately.

>>      /**
>> -     * get the current contex. only valid
> 
> The method is already called "getContext"
> ("get the current context" ;) ...so IMO all
> we need to explain is *what* this context is
> and what is so special about it.
> 
> In fact most of that information should
> be given inside ContinuationContext.java
> and we could link to it from here.
> 
> So in the end information that I think is
> important is as you state later on ...it's
> the same context object that is being passed
> in with start/continue.
> 
> IMHO that's it.
> 
> Don't want to be too picky ...but just tried
> to explain how I see that javadoc thingy ;)

I appreciate it. I think I'll remove the part that talks about the point 
of context and then you are OK with it.

> Please always use { } for if/else

I will do that.



-- 
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message