> Can you pls. post the URL of that mapping document?
>
It's in the docs dir of the grizzly-config module
> I agree, for ex, in Java we see developers start to use annotations
> instead of having separate config file.
> But in our case, we want opposite effect. We want to have external
> Grizzly config, which will let us to start Grizzly with minimum Java
> code.
> Annotations are good, when they are simple, but if we'll try to write
> Grizzly config, based on annotations - then it could become much more
> ugly, than just having XML config file.
>
Fair enough.
> We can wait with Grizzly standalone implementation.
> What could be more important is to define common configuration
> interfaces and Glassfish support for them. You will define common
> configuration interfaces for GF anyway, right?
>
That'd certainly be ideal. Which is why i keep coming back to the hk2
approach since glassfish will be generating that stuff anyway, it'd be
easy enough to use common code i should think.
> I took a look what you've commited to grizzly workspace... there is
> GrizzlyConfig class, which imports config interfaces, but that
> interfaces are not in place. Do I miss something?
Those classes are generated by JAXB at the moment. Though I think I've
come to the end of the road for using those generated classes and i'll
need to move those into svn so I can modify them. The current stuff
works as far as it goes but to really clean this up into something
production ready, we'll want to customize and refactor a bit.