OK. I'll commit it so you can take a look at it while I fix that test.
I did move some classes from glassfish->grizzly which makes me nervous a
bit. I'd like more experienced hands to make sure what I have is
(politically) correct. I've tried to excise as many glassfish deps as I
can which makes certain parts of this more awkward than I like but I
decided to focus on getting it working first then refactoring out those
deps with input from the wider community. I'm going to talk to
Nazrul/Kedar today about branching glassfish (or using an existing
branch) and trying to finish the integration on that end.
But feedback would be very much appreciated. I know there are a lot of
rough edges here that could use some smoothing over.
Jeanfrancois Arcand wrote:
> Salut,
>
> Justin Lee wrote:
>> :)
>
> :-) Great! You should commit so it gets included in 1.9.6 (this is a
> start!)
>
>>
>> Now I'm running a test with a basic xml file and have a question. Do
>> we want to imply the presence of certain elements (like Http) or
>> require them in the document. My preference is to require them in
>> the document for now and relax that requirement down the road as we
>> build in better defaults. Requiring them up front now would let us
>> move on to things like glassfish integration which, imo, is a more
>> pressing need. Opinions?
>
> I agree. I like the step by step approach...but this steps is quite
> big!!!
>
> A+
>
> -- 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
>