Lloyd Chambers wrote:
> Ludo,
>
> AFAIK, we are *not* making domain.xml a public interface, at least that
> was Kedar's view.
Users defeat everything when it comes to a text configuration file.
So, like it or not, domain.xml, its structure, elements etc. has become
our public interface. Nothing can fight with editing the text file in users'
favorite text editor. We can't say we won't support it if you ever edited
the file by hand, no let's not go there.
Situation would have been better if we had a "slick" editor/API for domain.xml
(and possibly other files in domain) *without* a running server. Offline
configurability is my long-cherished and unfulfilled dream that I continue
to cherish. Some day, I will make it a reality.
In spite of such an editor, domain.xml and any other text file
is a forced public interface. We even removed the comment in it that said "Don't
edit this file by hand!" from domain.xml.
> This will all have to be sorted out of course.
>
> Lloyd
>
> On Sep 11, 2008, at 1:50 PM, Ludovic Champenois wrote:
>
>> Lloyd Chambers wrote:
>>> +1
>>>
>>> ...and please be prepared to have an interface to "import" when doing
>>> ARC review. :)
>>>
>> Would be nice isn't it?
>> Yes, it would have been nice to have some code to share, but as Kedar
>> mentioned, it was not seen important for V3 prelude.
>> We would also need an OSR to add the exported interface JAR into the
>> NetBeans product.
>> Another one for adding it in Eclipse.
>> So far, java is an external public interface. Domain.xml content is as
>> well.
>>
>> Ludo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>