here whatI think about that. Deployer evoled a lot from the little demo
that I did at first.
In the first release I was using xmlbeans.. but look like Sun didn't like
that :) so I switch to JAXB.
it's sure that we could generate the objects at compile time, but for me.. I
don't see the point because the schemas doesn't change. And if we generate
the files maybe with a new release of jaxb we could insert regression
problems.
I don't think the point is simply to replace the Sun's headers by Oracle. a
find and replace would do the job.
I'll continue to try to make Deployer better but you are the masters of the
project :)
2010/6/30 Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>
> No problem, thank you for joining!
>
>
> On Jun 30, 2010, at 19:31 , Sebastien Dionne wrote:
>
> Sorry I had to leave. My boss needed me.
>
> On Jun 30, 2010 11:37 AM, "Oleksiy Stashok" <Oleksiy.Stashok_at_sun.com>
> wrote:
>
> Agenda:
>
> + Grizzzly 1.9.19 updates
> + Grizzly 2.0 updates
> + HTTP servlet deployer: discuss schema objects generation.
>
> Logistics:
> Time: 10:00am Pacific Time, Noon Central Time, 13:00 Eastern Time, 19:00
> CET
> Phone numbers:
> Canada: 8662036092
> US: 8666824770
>
>
> Conf code: 2711931
>
> “security code:” 1111
>
> Every one is welcome!
>
> WBR,
> Alexey
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
>
--
-------------
A+
Sébastien.
Vous pouvez me suivre sur Twitter / You can follow me on Twitter :
http://twitter.com/survivant