----- Original Message ----
From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
To: users_at_grizzly.dev.java.net
Sent: Monday, October 27, 2008 5:11:40 PM
Subject: Re: 1.9.0: sugestions
Salut,
Richard Corbin wrote:
> I have a feature request, Could you please add inline JavaDocs :) I don't know what many of these Classes or Methods do, I'm blindly feeling my way through it. Am I missing something here? I downloaded the JDs jar file but. You know it's got no info?
>
<Reply>
It's here already from the left pan on grizzly.dev.java.net :-):
https://grizzly.dev.java.net/nonav/apidocs/index.html
You can also browse the code:
https://grizzly.dev.java.net/nonav/xref/index.html
</Reply>
Ahh yeah I had seen those, What I meant by "in-line javadocs" (Sorry thats just what I call it) is adding the JavaDoc Comments that are presented to the API user while exploring the package tree. The ones that are moved to the JavaDoc when you generate them like.
/**
* This method constructs .....
*_at_Returns ...
**/
public void ....
when I try to view these classes I get the ol "javadoc not found". I think can import these into the library, if I had the JavaDoc.jar file?
No that's great feedback. Can you file issue(s) here:
https://grizzly.dev.java.net/issues/
every time you found something strange?
I have a great deal of respect for all of you comet heads :). I have a
suggestion that I just thought might be better particularly for passing
serialized parameters that act as flow control flags in a routine.
Instead of passing Strings ( System.getProperty(String s) for example..)
why not use an enum there? so you could get a list of options with
JavaDocs* on the fly in any modern IDE and have a guarantee that you're
dealing with a valid parameter. If we have to use a string .. like a
directory for example, when its defined in the interface maybe we should
call it like.. String webDirectory. So that when the IDE prototypes the
class its more obvious than the dreaded String arg1, String arg2 :-)
Cannot agree more. Can I ask you to file an RFE here:
https://grizzly.dev.java.net/issues/
The idea is to file bug/rfe so not only developer can try to fix it, but
also anybody interested to becomes a Grizzly Commiter or someone
interested to contribute.
>
>
> For issue 287 I have been working on Session Management for OortCloud that's both independent and optionally compatible with existing HttpServletRequest.Session ... I'm not sure how its setup in Grizzly right now though, Im trying to check out from Svn, but keep getting empty packages for the standalone versions. What I have so far is a Session Manager thats a serializable singleton (An Enum with no constructor) that generates SessionId's or takes a Session Object on each request and updates its SessionContainer object (bla,bla). Then returns a "SessionContainer" Subclass Object, keeping a map of SessionId -> SessionContainer.. the best part is it already comes with inline java docs (But you can remove those) :)
What steps are you executing exactly when checking out?
Thanks
-- Jeanfrancois
>
> --Richard
>
>
>
>
>
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: users_at_grizzly.dev.java.net
> Cc: dev_at_grizzly.dev.java.net
> Sent: Monday, October 27, 2008 10:08:08 AM
> Subject: Re: 1.9.0: Defining Roadmap
>
> Salut,
>
> I'm re-spinning the thread of the topic as two weeks have passed and I
> saw a lot of new comer. Please share the functionality you would like to
> see added to 1.9.0 so we can plan accordingly. The current set of open
> issues/ref can be browsed here:
>
> http://tinyurl.com/5hwf9v
>
>
> A+
>
> -- Jeanfrancois
>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> gently reminder :-) If you have features/bugs/improvement, please make
>> sure you file an issue. That's the only way we can write a roadmap and
>> synschronize 1.9.0 and 2.0 :-) :-)
>>
>> Merci!
>>
>> -- Jeanfrancois
>>
>> Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> we are collecting issues/features that this community would like to
>>> see in Grizzly 1.9.0. If you have idea, please file issue here:
>>>
>>> https://grizzly.dev.java.net/issues/
>>>
>>> If possible, try to file them before 10/01 as we would like to draft a
>>> roadmap based on what we have collected.
>>>
>>> Thanks!
>>>
>>> -- Jeanfrancois
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
For additional commands, e-mail: users-help_at_grizzly.dev.java.net